What is Condition Update in SAP SD

[meghnadwivedi]

As an SAP SD consultant, I come across many such magical configurations and settings after analyzing the screens day in and day out. Here are my findings for all SAP Consultants out there, making their life easier.

So, today we are going to talk about the use of "Condition Update" in SAP SD. This is one of the most commonly asked questions in SAP SD Interviews too.

Pre-req: You should be well aware of SAP SD Pricing Procedure configuration and assignment.

What does every SAP Consultant know?

"Condition Update" is one of the characteristics of "Condition Type" that helps control discounts. It lets us set limits on how much discount or how many orders can get a particular discount. It's useful to manage discounts and make sure they are used the way we want.

Now what is Condition Type? Condition type is an element assigned to each category of pricing element while setting up the pricing. For eg: Freight, Discount, Surcharge, Tax, List Price, Min Order Charge, etc are all different type of pricing elements that sums up to reach the final price for a product. These are all Condition Types. Enough of condition type! (Tcode: V/06) Can we get back to the original topic? CONDITION UPDATE!

So, the condition update is a boolean attribute that can be checked or unchecked in the Condition Type configuration screen. This attribute sets a limit on Condition type based on the below restrictions:

1. Maximum Cond. Value


2. Maximum Number of Sales Orders


3. Maximum Cond. Base Value

If either of the above settings is maintained then the condition type would behave according to it. If Max. cond. value is reached then the condition type would not trigger an additional discount.

Which information do SAP Consultants miss out on?

Well, all of the above makes sense, but how does it work in action? How system identifies that the above condition type is not applicable anymore as it had a "condition update" setup as per either of the three criteria?

Let's dive deeper.

Condition Update in action:

As we enable this "Condition Update" configuration in the condition type config screen, its impact would be visible while maintaining the condition record (Tcode: VK13). Each condition record created for the above condition type would have the option to set up any of the below three condition update settings.

Maximum Condition Value:

For Example: if we set up a Maximum Condition Value of 100 Euros in the discount condition record for a discount condition type, that means this condition type would be triggered in orders and show the corresponding discount condition value till the maximum discount of 100 Euros is not reached. If the discount condition value comes out to be more than 100 Euros, then the discount condition value will reflect a maximum discount of 100 Euros only and not the expected discount of 125 Euros.

MRP of Heater: 100 Eu

Discount scheme	25 Eu per heater
Max Cond. Value	100 Eu

 

Transactions	Prod	Qty	MRP	Discount	Expected Discount
Order 1	Heater	5	500	100	125
Order 2	Heater	2	200	50	50

 

Real-time scenario: If you buy a heater from us, you will get a discount of 2000 per piece maximum of up to 10000 Rs.

Maximum Number of sales orders:

For Example: If the Maximum Number of sales orders = 2 for X001 condition type.

The condition type X001 would not trigger from the 3rd order onwards which would have otherwise expected.

Discount Scheme	25% per heater
Max no. of orders	2

 

Transactions	Prod	Qty	MRP	Discount	Expected Discount
Order 1	Heater	5	500	125	125
Order 2	Heater	2	200	50	50
Order 3	Heater	1	100	0	25

 

Real-time scenario: 50% discount for the first three orders.

Maximum Cond. Base Value: 

It is named as Base value but it is actually a quantity indicator.

For Example: If we set up a Maximum Cond. base Value of 10 Each for a discount condition type X001. That means this condition type would be triggered in orders and show the corresponding discount till the maximum discount of 10 quantities of that line item is not reached. If the quantity comes out to be more than 10 Each, then the discount condition value will reflect a maximum discount of 10 quantities only and not what is otherwise expected.

Discount Scheme	10 Eu Discount per heater for 10 heaters
Max Cond. Base value	10

 

Transactions	Prod	Qty	MRP	Discount	Expected Discount
Order 1	Heater	12	1200	100	120
Order 2	Heater	5	500	50	50

 

Real-time scenario: If you buy a laptop from us, you will get Rs.1000 discount per laptop for the first 4 quantities.

Now how system remembers these updates like 9 quantities are ordered and now only 1 more quantity can have a discount. Post that, stop giving discounts. That is stored in an info structure: S071 (Tcode: OMO1, Table: S071). Orders containing that condition type (with condition update) would be recorded in this info structure and the same record would keep updating and help determine the restriction during sales order creation.

Wait a sec, What is info structure? How it's different than regular tables? Well! info structure is again a table but is maintained for a different purpose. This table is created for operative purposes, that stores data along with frequency. Three main fields of info structure are period units, characteristics, and key figures. Period stores frequency like a day week, month, etc, and characteristic is master data that stores data like plant, company code. etc and key figures store transactional data like sales volume, value, etc. Want to know more? click here.

Key Pointers:

1. This config. is generally used during NPI (New Product introduction) when the seller tries to increase product adoption. So, you might not find it used often.


2. For percentage condition types (like K007), Maximum Cond. Base Value - Condition Update setting is not present as a parameter to restrict condition types.


3. SAP Gap: SAP ECC allows only "01"-"03" as input for the "Maximum Number of Orders" field. For more than that, additional ABAP changes (code changes) would be required.


4. Generally, "Maximum Cond. Value" is utilized for providing discounts. So when you maintain it in the VK13 condition record, make sure you input "-" minus along with the amount and unit of measurement as well.


5. "Maximum Number of sales orders" is generally used for the condition types where "Calculation type" is equal to a percentage (Calcul. Type: A).


6. "Maximum Cond. Base Value" does not work for the condition types where "Calculation type" is equal to a percentage (Calcul. Type: A).


7. Pricing Tables-fields: Maximum Cond. Value = KONP-KOMXWRT, Maximum No. of Orders = KONP-ANZAUF, Maximum Cond. Base Value = MXKBAS.

I hope this will help you. Please leave comments in case I missed anything.

Thank you.

Happy learning 🙂