2756560 - Cloud BAdIs for pricing

It is not known,

• how to influence the calculation of the condition amount or condition base value, or
• how to define a new requirement

in pricing by custom logic.

SAP S/4HANA Cloud Public Edition

With the Custom Fields and Logic app, it is possible implement logic for the following Business Add-Ins (BAdIs) under business context "Pricing" and assign a unique filter value to it. The following Cloud BAdIs are available:

• PRCG_DOC_CONDITION_AMOUNT : Define Alternative Calculation of Condition Amount in Document
• PRCG_DOC_ITEM_CONDITION_AMOUNT: Define Alternative Calculation of Condition Amount in Document Item
• PRCG_DOC_ITM_CNDN_BASE_VALUE: Define Alternative Calculation of Condition Base Value in Document Item
• PRICING_DOCUMENT_REQUIREMENT: Define Requirement in Pricing for Document
• PRCG_DOCUMENT_ITEM_REQUIREMENT: Define Requirement in Pricing for Document Item

Please see the documentation below about BAdIs to understand their use. EKT materials are also attached to better understand the needed settings.

Here are some common questions and answers about the above BAdIs:

Q1. How to calculate the condition amount or condition base value of condition B based on a previous condition A?

A1. To calculate the condition amount or condition base value of condition B based on a previous condition A, a subtotal can be assigned to the pricing procedure step of condition A.

For example, the amount of the previous condition A can be stored in a field assigned to subtotal D (Copy value to XWORKD). The interface of the BAdI methods CHANGE_CONDITION_AMOUNT respectively CHANGE_CONDITION_BASE_VALUES receive this field as part of the importing parameter ITEM_AMOUNTS (field conditionamountbufferxworkd). So if condition type B follows in a pricing procedure step subsequent to condition A, the condition amount of condition A can be accessed via this subtotal field of the pricing procedure.

Q2. Which Cloud BAdI should be used for group conditions?

A2. The Cloud BAdI PRCG_DOC_CONDITION_AMOUNT should be used. Otherwise, the sales document may have incomplete log due to pricing error.

Q3. Can subtotal lines use a custom formula for the alternative calculation of the condition amount on header level?

A3. Using a formula for the alternative calculation of the condition amount on header level is not supported for subtotal lines.

To have the subtotal also on header level as sum of the subtotals on the item level, a condition type can be created for that. This condition type does not need an access sequence.

Adding this condition type to the pricing procedure with the same setting as the subtotal line should solve the issue.

• The BADIs could be implemented technically in OP, but it is not meant to be used for OP/Private Cloud. The BADIs are not released for private cloud usage. Please continue to use VOFM routines and user exits in S4HANA on-premise releases.

• Product assistance for the following:

Custom Logic: Condition Amount
Custom Logic: Condition Base Value
Custom Logic: Requirement

cloud BAdI, PRCG_DOC_CONDITION_AMOUNT, PRCG_DOC_ITM_CNDN_BASE_VALUE, PRCG_DOC_ITEM_CONDITION_AMOUNT, CHANGE_CONDITION_AMOUNT, VOFM successor , KBA , SD-BF-PR , Pricing , SD-BF-PR-2CL , Pricing (Public Cloud) , How To