How to configure pricing procedure to choose only one among the different condition type?
ECC 6 - Exclusion group Customizing is in the following IMG path (transaction SPRO):
Sales and Distribution > Basic Functions > Pricing > Condition Exclusion > Condition Exclusion for Groups of Conditions Carry out the following steps:
a) Define condition exclusion groups:
First create one or more exclusion groups, for example:
b) Assign condition types to the exclusion groups:
Then the required condition types are assigned to the exclusion groups, for example:
c) Maintain condition exclusion for pricing procedures:
Finally, define the required exclusion rules for each pricing procedure. In this case, you can create exclusions in accordance with the following predefined rules (KAUVF field):
- 'A' - Selection of the most favorable condition type within a condition exclusion group
- 'B' - Selection of the most favorable condition record of a condition type if several condition records exist (for example, selection under various condition records of the condition type PR00)
- 'C' - Selection of the most favorable of the two condition exclusion groups (in this case, all of the condition types of the two groups are cumulated and the totals are compared with each other).
- 'D' - "Exclusive" procedure: If any of the condition types of the first group exists on the item, all of the condition types of the second exclusion group are excluded.
- 'E' - Similar to 'B', but with the most unfavorable condition record.
- 'F' - Similar to 'C', but with the more unfavorable condition exclusion group.
The actual exclusion rules for a pricing procedure are maintained with a sequence number and completed by specifying the exclusion rule and the affected exclusion group(s):
- 10 D Exclusive G002 Discount Group 2 G001 Discount Group 1
- 20 A More favorable ... G002 Discount Group 2
This data is stored in the T684S database table.
All exclusion rules except for rule 'D' are based on the knowledge of the condition values of the condition types involved. In accordance with exclusion group Customizing, the condition exclusion is therefore also created in pricing in the FORM XKOMV_AUSSCHLUSS (include LV61AA56)
- after an 'initial' (preliminary) valuation (FORM XKOMV_BEWERTEN, Include LV61AA55) of the pricing result
- and after the condition exclusion based on the KMANU field
(FORM XKOMV_AUSSCHLUSS, Include LV61AA56)
The exclusion is created with inactivity indicator 'A'.
The information in section 3 also applies here: If conditions were excluded from FORM XKOMV_AUSSCHLUSS, a 'second' (final) valuation of the pricing result takes place once again (FORM XKOMV_BEWERTEN), in order to update the pricing result based on the exclusions made. In this case, conditions with inactivity indicator 'A' are no longer valuated.
Note:
a) Since the exclusion of a condition may influence the condition basis and therefore also the condition value of follow-up conditions, a condition or exclusion group that was more favorable (more unfavorable) than another condition or exclusion group after the preliminary valuation may have been more unfavorable (more favorable) after the final valuation. See also the following example.
In such a case, another exclusion or valuation based on the last valuation is NOT triggered. This procedure could result in a continuous loop (the "flip flop effect"). For more information, see Note 217009.
b) In the R/3 standard system, conditions with a zero condition value do not participate in exclusions according to exclusion groups. However, you can change the system response in such a way that conditions with a zero condition value also participate in exclusions.
To do this, add the value formula 038 (Include FV64A038), or a corresponding user-defined value formula that contains the source code from value formula 038, to the pricing procedure used for a condition that will definitely be part of the pricing result.
c) Conditions that the condition exclusion indicator (see section 2) already fully excluded from the pricing result of an item no longer participate in exclusions according to exclusion groups. As a result, you can no longer use rule 'D' to exclude the conditions of another group.
d) Exclusion group Customizing should not be maintained randomly, but rather with care. If exclusion group Customizing is so extensive that you can no longer comprehend the formation of the 'final result', it is time to reconsider the relevant business process.
Example:
The aforementioned exclusion group Customizing is valid. Before an exclusion is created, a document item contains the following preliminary pricing result, which of course is not displayed in this form. In this case, the percentage discount ZD02 refers to the price ZPR0 and the percentage discount ZD04 refers to subtotal 1.
Condtns Amt Condtns Val Inactive
In accordance with exclusion rule 10, the discounts ZD01 and ZD02 are excluded from the G001 exclusion group since conditions were determined from the G002 exclusion group with the discounts ZD03 and ZD04.
In accordance with exclusion rule 20, discount ZD03 (condition value EUR -9.50) excludes discount ZD04 (condition value EUR -9.10) since ZD03 is the more favorable discount in the G002 exclusion group.
After you create the exclusion and the conditions have been valuated again, you finally receive the following final pricing result:
Condtns Amt Condtns Val Inactive
Note that, if subsequently considered, discount 4 would now be more favorable than discount 3, since the exclusion of discounts 1 and 2 influenced the condition basis of the percentage discount 4, but it did not influence the absolute discount 3.
ECC 6 - Exclusion group Customizing is in the following IMG path (transaction SPRO):
Sales and Distribution > Basic Functions > Pricing > Condition Exclusion > Condition Exclusion for Groups of Conditions Carry out the following steps:
a) Define condition exclusion groups:
First create one or more exclusion groups, for example:
- G001 Discount group 1
- G002 Discount group 2
b) Assign condition types to the exclusion groups:
Then the required condition types are assigned to the exclusion groups, for example:
- G001 Discount Group 1 ZD01 Discount 1
- G001 Discount Group 1 ZD02 Discount 2
- G002 Discount Group 2 ZD03 Discount 3
- G002 Discount Group 2 ZD04 Discount 4
c) Maintain condition exclusion for pricing procedures:
Finally, define the required exclusion rules for each pricing procedure. In this case, you can create exclusions in accordance with the following predefined rules (KAUVF field):
- 'A' - Selection of the most favorable condition type within a condition exclusion group
- 'B' - Selection of the most favorable condition record of a condition type if several condition records exist (for example, selection under various condition records of the condition type PR00)
- 'C' - Selection of the most favorable of the two condition exclusion groups (in this case, all of the condition types of the two groups are cumulated and the totals are compared with each other).
- 'D' - "Exclusive" procedure: If any of the condition types of the first group exists on the item, all of the condition types of the second exclusion group are excluded.
- 'E' - Similar to 'B', but with the most unfavorable condition record.
- 'F' - Similar to 'C', but with the more unfavorable condition exclusion group.
The actual exclusion rules for a pricing procedure are maintained with a sequence number and completed by specifying the exclusion rule and the affected exclusion group(s):
- 10 D Exclusive G002 Discount Group 2 G001 Discount Group 1
- 20 A More favorable ... G002 Discount Group 2
This data is stored in the T684S database table.
All exclusion rules except for rule 'D' are based on the knowledge of the condition values of the condition types involved. In accordance with exclusion group Customizing, the condition exclusion is therefore also created in pricing in the FORM XKOMV_AUSSCHLUSS (include LV61AA56)
- after an 'initial' (preliminary) valuation (FORM XKOMV_BEWERTEN, Include LV61AA55) of the pricing result
- and after the condition exclusion based on the KMANU field
(FORM XKOMV_AUSSCHLUSS, Include LV61AA56)
The exclusion is created with inactivity indicator 'A'.
The information in section 3 also applies here: If conditions were excluded from FORM XKOMV_AUSSCHLUSS, a 'second' (final) valuation of the pricing result takes place once again (FORM XKOMV_BEWERTEN), in order to update the pricing result based on the exclusions made. In this case, conditions with inactivity indicator 'A' are no longer valuated.
Note:
a) Since the exclusion of a condition may influence the condition basis and therefore also the condition value of follow-up conditions, a condition or exclusion group that was more favorable (more unfavorable) than another condition or exclusion group after the preliminary valuation may have been more unfavorable (more favorable) after the final valuation. See also the following example.
In such a case, another exclusion or valuation based on the last valuation is NOT triggered. This procedure could result in a continuous loop (the "flip flop effect"). For more information, see Note 217009.
b) In the R/3 standard system, conditions with a zero condition value do not participate in exclusions according to exclusion groups. However, you can change the system response in such a way that conditions with a zero condition value also participate in exclusions.
To do this, add the value formula 038 (Include FV64A038), or a corresponding user-defined value formula that contains the source code from value formula 038, to the pricing procedure used for a condition that will definitely be part of the pricing result.
c) Conditions that the condition exclusion indicator (see section 2) already fully excluded from the pricing result of an item no longer participate in exclusions according to exclusion groups. As a result, you can no longer use rule 'D' to exclude the conditions of another group.
d) Exclusion group Customizing should not be maintained randomly, but rather with care. If exclusion group Customizing is so extensive that you can no longer comprehend the formation of the 'final result', it is time to reconsider the relevant business process.
Example:
The aforementioned exclusion group Customizing is valid. Before an exclusion is created, a document item contains the following preliminary pricing result, which of course is not displayed in this form. In this case, the percentage discount ZD02 refers to the price ZPR0 and the percentage discount ZD04 refers to subtotal 1.
Condtns Amt Condtns Val Inactive
- ZPR0 Price EUR 100.00 1 PC EUR 100.00
- ZD01 Discount 1 EUR 4.00 1 PC EUR - 4.00
- ZD02 Discount 2 5.000% EUR - 5.00
- ZD03 Discount 3 EUR 9.50 1 PC EUR - 9.50
- ZD04 Discount 4 10.000% EUR - 9.10
In accordance with exclusion rule 10, the discounts ZD01 and ZD02 are excluded from the G001 exclusion group since conditions were determined from the G002 exclusion group with the discounts ZD03 and ZD04.
In accordance with exclusion rule 20, discount ZD03 (condition value EUR -9.50) excludes discount ZD04 (condition value EUR -9.10) since ZD03 is the more favorable discount in the G002 exclusion group.
After you create the exclusion and the conditions have been valuated again, you finally receive the following final pricing result:
Condtns Amt Condtns Val Inactive
- ZPR0 Price EUR 100.00 1 PC EUR 100.00
- ZD01 Discount 1 EUR 4.00 1 PC EUR - 4.00 A
- ZD02 Discount 2 5.000% EUR - 5.00 A
- ZD03 Discount 3 EUR 9.50 1 PC EUR - 9.50
- ZD04 Discount 4 10.000% EUR - 9.10 A
Note that, if subsequently considered, discount 4 would now be more favorable than discount 3, since the exclusion of discounts 1 and 2 influenced the condition basis of the percentage discount 4, but it did not influence the absolute discount 3.
No comments:
Post a Comment