Symptom
When adding a pricing condition type in pricing elements, an existing condition type become inactive because of subsequent price.
However, the amount of the inactive condition type is still added in the "Surcharges".
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Enter "Change Billing Documents" and enter the billing document number.
- In the header level, switch to "Condition" tab.
- Add a pricing condition type and the existing condition type become inactive.
- Observe the "Surcharges" and the amount of the inactive condition type is still added to "Surcharges".
Cause
This is standard behavior.
The condition type is de-activated due to a follow-up price (KINAK = 'Y').
In this case, if the "Surcharges" is referred to by from/to steps, the value will still be considered.
Resolution
The behavior will not be changed because there are other use cases that need to access the value of a condition, that has been de-activated by a follow-up price.
There are two possible workarounds:
- Consider using an exclusion procedure where the follow-up price explicitly excludes the inactive condition. This would set the KINAK to 'A'. Some details regarding it can be found from the documentation below:
- Assign a formula to the inactive condition where it is set to zero if KINAK = 'Y'. Refer to KBA 0002885513 - VOFM - Pricing custom routine in SAP S/4HANA Cloud Public Edition for more details on creating a custom pricing routine in SAP S/4HANA Cloud Public Edition.
See Also
- 0002885513 - VOFM - Pricing custom routine in SAP S/4HANA Cloud Public Edition
Keywords
SAP S/4HANA Cloud Public Edition, Pricing, Pricing Procedure, Inactive Conditions, Invoice Layout, Surcharge, KINAK, Condition Exclusion, Custom Pricing Routine. , KBA , SD-BF-PR-2CL , Pricing (Public Cloud) , Problem