To know about Blackbox concept: (https://blogs.sap.com/2018/10/11/sap-opp-black-box-concept-implementation-guidance-for-non-sap-envir... )
Omnichannel Promotion Pricing Service (PPS) calculates the effective sales prices and promotions by using the data stored in OPP - CAR. This provides an easy way to implement new offer types.
A local implementation of the service on the local server of each store is recommended to ensure correct, consistent and high-volume calculation, even in asynchronously connected sales applications. A local repository helps avoid traffic and network load and communication, as well as avoid performance issues by handling many remote price calculations.
But it’s possible that according to your architecture a local repository isn’t available. Here you can find a solution.
If you are working with 3th party POS system and you want to deploy Promotion Pricing Service you have three mainly options:
As already mentioned, this implementation is hosted on the server of each sales channel, therefore it runs locally in the designated database of the application. Promotions and prices are replicated from the central repository, so you can work without continually connecting to a remote system.
In this option, the promotion pricing service (SAP HANA XS advanced application) runs in the central repository in SAP CAR.
pros and cons
Local:
+You can work locally without having to constantly call a remote system.
+ Designed to handle large volumes of requests.
-You need a server in each sales channel to install a Black Box and a database.
-Installation and maintenance on each server.
-Promotions and prices must be sent from CAR to the local repository at least once a day (scheduled job to send idocs: /ROP/BASE_PRICE & /ROP/PROMOTION)
Central:
+Designed to handle low volumes of requests.
+You don't need to install Black Box.
+You do not need to send prices and promotions to an external storage.
-Not recommended for high volumes of calls to the PPS.
OPP Cloud service
- The OPPS cloud service comes with a subscription license pricing based on the number of mio. API calls.
To know more benefits please go to: https://blogs.sap.com/2019/08/16/sap-omnichannel-promotion-pricing-new-cloud-service/
SOLUTION: Hybrid implementation for Black Box
It is possible that you need to handle high volume but you don´t have servers in the store or for example your points of sale are tablets (where you can not install a BlackBox), you may need an intermediate or hybrid architecture. You can install your BlackBox on a central server such as the AWS cloud and make calls to the PPS from your tablet or any POS through APIs (to learn more follow this link: https://api.sap.com/package/OPPS/all , https://help.sap.com/viewer/ace37badc0774b4a8e540fdc7f56a802/Cloud/en-US/a2c5f7f07c964550a1ebb1804cd... ). You will have the benefits of the local deployment without maintaining a repository in each store.
Note: you will have to update your prices and promotions through idocs as local deployment, but you will have one repository to call from different POS as a central deployment.
Omnichannel Promotion Pricing Service (PPS) calculates the effective sales prices and promotions by using the data stored in OPP - CAR. This provides an easy way to implement new offer types.
A local implementation of the service on the local server of each store is recommended to ensure correct, consistent and high-volume calculation, even in asynchronously connected sales applications. A local repository helps avoid traffic and network load and communication, as well as avoid performance issues by handling many remote price calculations.
But it’s possible that according to your architecture a local repository isn’t available. Here you can find a solution.
If you are working with 3th party POS system and you want to deploy Promotion Pricing Service you have three mainly options:
- Local deployment
As already mentioned, this implementation is hosted on the server of each sales channel, therefore it runs locally in the designated database of the application. Promotions and prices are replicated from the central repository, so you can work without continually connecting to a remote system.
- Central deployment
In this option, the promotion pricing service (SAP HANA XS advanced application) runs in the central repository in SAP CAR.
- Public Cloud service deployment.
pros and cons
Local:
+You can work locally without having to constantly call a remote system.
+ Designed to handle large volumes of requests.
-You need a server in each sales channel to install a Black Box and a database.
-Installation and maintenance on each server.
-Promotions and prices must be sent from CAR to the local repository at least once a day (scheduled job to send idocs: /ROP/BASE_PRICE & /ROP/PROMOTION)
Central:
+Designed to handle low volumes of requests.
+You don't need to install Black Box.
+You do not need to send prices and promotions to an external storage.
-Not recommended for high volumes of calls to the PPS.
OPP Cloud service
- The OPPS cloud service comes with a subscription license pricing based on the number of mio. API calls.
To know more benefits please go to: https://blogs.sap.com/2019/08/16/sap-omnichannel-promotion-pricing-new-cloud-service/
Black box on the cloud
SOLUTION: Hybrid implementation for Black Box
It is possible that you need to handle high volume but you don´t have servers in the store or for example your points of sale are tablets (where you can not install a BlackBox), you may need an intermediate or hybrid architecture. You can install your BlackBox on a central server such as the AWS cloud and make calls to the PPS from your tablet or any POS through APIs (to learn more follow this link: https://api.sap.com/package/OPPS/all , https://help.sap.com/viewer/ace37badc0774b4a8e540fdc7f56a802/Cloud/en-US/a2c5f7f07c964550a1ebb1804cd... ). You will have the benefits of the local deployment without maintaining a repository in each store.
Note: you will have to update your prices and promotions through idocs as local deployment, but you will have one repository to call from different POS as a central deployment.
- SAP Managed Tags:
1 Comment
