C_TS462_2021 · Question #63
You want to set up a discount with a scale value (condition type K029) that is based on the material group "spare parts". The discount should be granted for all items in a sales order that are spare…
The correct answer is B. You need to set up condition type K029 as a group condition. Option B is correct because a group condition instructs SAP to accumulate the quantities (or values) across all relevant line items - in this case, all spare parts - before evaluating the pricing scale. Without this setting, SAP would evaluate K029's scale threshold per…
Question
You want to set up a discount with a scale value (condition type K029) that is based on the material group "spare parts". The discount should be granted for all items in a sales order that are spare parts. What do you need to set up for condition type K029 so it meets this requirement?
Options
- AYou need to set up condition type K029 as a header condition.
- BYou need to set up condition type K029 as a group condition.
- CYou need to set the Condition Index indicator for condition type K029.
- DYou need to set the Condition Update indicator for condition type K029.
How the community answered
(33 responses)- A15% (5)
- B76% (25)
- C3% (1)
- D6% (2)
Explanation
Option B is correct because a group condition instructs SAP to accumulate the quantities (or values) across all relevant line items - in this case, all spare parts - before evaluating the pricing scale. Without this setting, SAP would evaluate K029's scale threshold per individual line item, likely failing to reach the discount tier; with it, the combined spare parts quantity is used, and the resulting scale discount is then applied back to each qualifying item.
A is wrong because a header condition distributes a single discount across all order items regardless of material group - you cannot restrict it to spare parts only, and it doesn't use scale logic per group.
C is wrong because the Condition Index indicator only creates a searchable index for finding condition records faster; it has no effect on how the scale is evaluated across items.
D is wrong because the Condition Update indicator tracks cumulative usage of a condition (e.g., to enforce a maximum discount budget across multiple orders/billing documents) - it is a consumption-tracking tool, not a within-order aggregation tool.
Memory tip: Think of "group condition" as pooling items into one basket before checking the scale - just like a bulk discount that only kicks in when you combine all your spare parts purchases into a single total.
Topics
Community Discussion
No community discussion yet for this question.