
In this blog, we want to give you an introduction into the extension concept of the solution SAP Variant Configuration and Pricing.
Note: This blog is partially outdated. The extension framework for SAP Variant Configuration and Pricing was enhanced in the meantime and offers now two approaches: 'local extensions' and 'remote extensions'. This blog only talks about remote extensions. See also the updated Extension Guide for SAP Variant Configuration and Pricing and the eLearning Implementation of Local Extensions for SAP Variant Configuration and Pricing (ICVCP3_EN_Col01).
SAP Business Technology Platform does not offer a framework which would allow us to execute customer code tightly coupled to the Pricing service (user exits) or the Variant Configuration service (variant functions), because this concept does not fit well into a multi-tenancy cloud architecture.
We strongly recommend reviewing your pricing procedure and/or configuration model. Ideally, you can (partially) forego custom code and simplify your system:
One approach is to avoid customer code in the first place by using extensions provided by SAP. This is a win-win: it simplifies customizing resp. modeling and lowers TCO on customer side while the code works in the cloud engine as well.
All SAP pre-delivered ABAP user-exits were analyzed; about 60 relevant routines were identified and implemented within the Pricing service.
Supported Standard Pricing Exits:
https://help.sap.com/docs/SAP_VARIANT_CONFIGURATION_AND_PRICING/60117f3b58cc4876b0cb33b5bc9a7b5f
A subset of pricing exits supported out-of-the-box in a Commerce scenario as documented here (choose your Commerce release):
https://help.sap.com/docs/SAP_COMMERCE_INTEGRATIONS/80c3212d1d4646c5b91db43b84e9db47/cbb57b253ba343b...
Same for CPQ integration as pricing exits depend on supported pricing attributes
(choose your CPQ release):
https://help.sap.com/docs/SAP_CPQ/f80fbcd4f1c74232839c30ce26886f07/21b0e023c74744b6960d901c9a05619b....
SAP provides a library of predefined variant functions in back end and front end. Customers do not have to maintain any code to use them.
Examples:
SAP delivered variant functions:
Conversions:
String Operations:
Auxiliary functions:
See SAP Notes 2695561, 2790161, and related notes for attached documentation.
If there really is no way of preventing the use of (non-standard) custom code, we introduced a framework that permits the use of custom code via a loose coupling:
Variant functions and pricing exits are mapped to REST calls with well-defined APIs (and thus properly decoupled). The custom code may run in the SAP Business Technology Platform but could be executed in an arbitrary environment in arbitrary language.
Overview
For more details, please refer to the Extension Guide for SAP Variant Configuration and Pricing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |