SD-sap是如何确定条件值的计算基值(KAWRT)的?
2013-09-18 16:46
274 查看
Note
834174 - How are 'value-related' condition bases determined?
Note内容摘抄如下:
This consulting note describes how the condition basis (field XKOMV-KAWRT) of conditions is determined with calculation type "Fixed amount" (KRECH 'B') or 'Percentage' (KRECH 'A', 'H' or 'I').
The condition basis for these calculation types consists of one or more condition values in the document currency and is therefore a 'value-related' condition basis (in EUR, USD, and so on), as opposed to a condition basis related to quantity,
weight or volume (for example PC, KG, M3, and so on).
The determination of the condition basis depends on the settings in the pricing procedure that is used.
In all cases, it should be noted that the conditions and subtotal lines are edited successively from top to bottom in the sequence in which they are specified in the pricing procedure.
1.
No reference steps are maintained:
If no from-to reference steps are maintained in the pricing procedure (fields STUNB and STUN2), the condition basis is filled from the current value in the internal variable ZWISU. In the variable ZWISU, the condition values of the (current) last pricing condition
(condition with condition class KOAID = 'B' and inactivity indicator KINAK not set to 'Y') as well as the subsequent conditions (for example, surcharges and discounts, taxes, and so on) are added together, as long as they were not deactivated with one of the
'AKLMXZ' indicators (see Note 836243).
Due to the successive processing of the conditions in the pricing procedure, ZWISU therefore generally increases step by step with every (active) positive condition, reduces with every (active) negative condition, and is reset with the occurrence of a new (active)
pricing condition and filled with its value.
2.
One or more reference steps are maintained:
Only step numbers that are smaller than the current reference step can be chosen as reference steps. This is because the condition values of following step numbers have not yet been determined due to the successive processing of the pricing procedure (see above).
If only the from-reference step is maintained, the system internally fills the to-reference step with the from-reference step. In this case therefore only this one reference step is relevant.
If both the from-reference step and the to-reference step (greater or equal to the from-reference step) are maintained, all step numbers are relevant, that are greater than or equal to the from-reference step and smaller than or equal to the to-reference step.
To determine the condition basis, the system now adds the condition values of all relevant conditions that are not inactive with an 'AKLMX' indicator (see Note 836243).
It should be noted that in this case pricing conditions with the inactivity indicator 'Y' are taken into account during the determination of the condition basis, as long as their step number is in the relevant area.
In addition, the system also takes subtotals into account, as long as their step number is in the relevant area.
3.
Using a condition basis formula:
You can also use a condition basis formula to fill the condition basis. In this case, you must enter the number of the relevant formula in the pricing procedure in the 'BasFrm' column (field KOFRA). The use of a condition basis formula is more binding than
the possible maintenance of reference steps. Therefore, the system rejects a condition basis that is first determined according to section 1 or 2 if the formula determines a different condition basis.
For example, the standard condition basis formula 002 fills the condition basis from the current accrued net value of the item (KOMP-NETWR). Here, the net value is the total of the active non-statistical conditions (KINAK not set to 'AKLMXZ' and not set to
'Y', as well as KSTAT not set to 'X').
Due to the successive processing of the conditions in the pricing procedure, the net value generally increases step by step with every (active) surcharge, is reduced with every (active) discount, and is reset with the appearance of a new non-statistical (active)
pricing condition and filled with its value.
4.
Tax conditions:
For (percentage) tax conditions (condition class KOAID = 'D'), we generally recommend the condition basis formula 016.
In the case of intercompany billing or rebate settlement documents, the system always determines the condition basis with the condition basis formula 002, even if it is not explicitly maintained in the pricing procedure.
However, this does not apply if a different condition basis formula is maintained in the pricing procedure. In this case, the condition basis formula entered in the pricing procedure is used.
Example:
1. Customizing for the pricing procedure (for example, Transaction V/08):
Step CTyp Description Fro To AltCBV
010 ZPR1 Pricing condition 1
015 ZPR2 Pricing condition 2
020 Gross
025 ZMA1 Material discount 1
030 ZMA2 Material discount 2 010 015
035 ZKU3 Customer discount 3
040 ZKU4 Customer discount 4 015 030
045 Net
050 MWST Output tax 016
2. Pricing result:
Due to the specified pricing procedure, the system issues
the following pricing result for a quantity of 2 PC:
Condition Amount Basis Value Inactive
ZPR1 Pr cond 1 EUR 60.00/1 PC 2.000 PC EUR 120.00 Y
ZPR2 Pr cond 2 EUR 54.00/1 PC 2.000 PC EUR 108.00 Y
ZPR2 Pr cond 2 EUR 56.00/1 PC 2.000 PC EUR 112.00
Gross EUR 56.00/1 PC 2.000 PC EUR 112.00
ZMA1 Mat disc 1 1.000-% EUR 112.00 EUR 1.12- A
ZMA2 Mat disc 2 2.000-% EUR 340.00 EUR 6.80-
ZKU3 Cust disc 3 3.000-% EUR 105.20 EUR 3.16-
ZKU4 Cust disc 4 4.000-% EUR 325.20 EUR 13.01-
Net EUR 44.52/1 PC 2.000 PC EUR 89.03
MWST Output tax 16.000% EUR 89.03 EUR 14.24
3. How did the condition bases result?
a) Due to reference steps that are not maintained, the condition basis for the discount ZMA1 results only from the last active pricing condition ZPR2 with the condition value EUR 112.00 ("ZWISU logic" in accordance with section
1).b) Since reference steps 10 to 15 were maintained for the discount ZMA2, all three pricing conditions are relevant for this discount, including the one deactivated with 'Y'. Therefore, in accordance with section 2, this results
in a condition basis of EUR 120.00 + 108.00 + 112.00 = EUR 340.00.c) For ZKU3, the condition basis is EUR 105.20, resulting from the condition values of the active conditions ZPR2 with EUR 112.00 and ZMA2 with EUR -6.80. The discount ZMA1 that is inactive with 'A' due to an exclusion by means
of exclusion groups has no function ("ZWISU logic" in accordance with section 1).d) Since reference steps 15 to 30 are maintained for ZKU4, all condition values in this area are relevant for ZKU4, except for the discount ZMA1 that is inactive with 'A', but including the subtotal 'Gross' from step 020. The condition
basis that results in accordance with section 2 is 108.00 + 112.00 + 112.00 - 6.80 = EUR 325.20.e) For the MWST tax, the condition basis results in accordance with section 3 and 4 from the accrued (up to now) net value EUR 112.00 - 6.80 - 3.16 - 13.01 = EUR 89.03 (conditions ZPR2, ZMA2, ZKU3, and ZKU4).
834174 - How are 'value-related' condition bases determined?
Note内容摘抄如下:
This consulting note describes how the condition basis (field XKOMV-KAWRT) of conditions is determined with calculation type "Fixed amount" (KRECH 'B') or 'Percentage' (KRECH 'A', 'H' or 'I').
The condition basis for these calculation types consists of one or more condition values in the document currency and is therefore a 'value-related' condition basis (in EUR, USD, and so on), as opposed to a condition basis related to quantity,
weight or volume (for example PC, KG, M3, and so on).
The determination of the condition basis depends on the settings in the pricing procedure that is used.
In all cases, it should be noted that the conditions and subtotal lines are edited successively from top to bottom in the sequence in which they are specified in the pricing procedure.
1.
No reference steps are maintained:
If no from-to reference steps are maintained in the pricing procedure (fields STUNB and STUN2), the condition basis is filled from the current value in the internal variable ZWISU. In the variable ZWISU, the condition values of the (current) last pricing condition
(condition with condition class KOAID = 'B' and inactivity indicator KINAK not set to 'Y') as well as the subsequent conditions (for example, surcharges and discounts, taxes, and so on) are added together, as long as they were not deactivated with one of the
'AKLMXZ' indicators (see Note 836243).
Due to the successive processing of the conditions in the pricing procedure, ZWISU therefore generally increases step by step with every (active) positive condition, reduces with every (active) negative condition, and is reset with the occurrence of a new (active)
pricing condition and filled with its value.
2.
One or more reference steps are maintained:
Only step numbers that are smaller than the current reference step can be chosen as reference steps. This is because the condition values of following step numbers have not yet been determined due to the successive processing of the pricing procedure (see above).
If only the from-reference step is maintained, the system internally fills the to-reference step with the from-reference step. In this case therefore only this one reference step is relevant.
If both the from-reference step and the to-reference step (greater or equal to the from-reference step) are maintained, all step numbers are relevant, that are greater than or equal to the from-reference step and smaller than or equal to the to-reference step.
To determine the condition basis, the system now adds the condition values of all relevant conditions that are not inactive with an 'AKLMX' indicator (see Note 836243).
It should be noted that in this case pricing conditions with the inactivity indicator 'Y' are taken into account during the determination of the condition basis, as long as their step number is in the relevant area.
In addition, the system also takes subtotals into account, as long as their step number is in the relevant area.
3.
Using a condition basis formula:
You can also use a condition basis formula to fill the condition basis. In this case, you must enter the number of the relevant formula in the pricing procedure in the 'BasFrm' column (field KOFRA). The use of a condition basis formula is more binding than
the possible maintenance of reference steps. Therefore, the system rejects a condition basis that is first determined according to section 1 or 2 if the formula determines a different condition basis.
For example, the standard condition basis formula 002 fills the condition basis from the current accrued net value of the item (KOMP-NETWR). Here, the net value is the total of the active non-statistical conditions (KINAK not set to 'AKLMXZ' and not set to
'Y', as well as KSTAT not set to 'X').
Due to the successive processing of the conditions in the pricing procedure, the net value generally increases step by step with every (active) surcharge, is reduced with every (active) discount, and is reset with the appearance of a new non-statistical (active)
pricing condition and filled with its value.
4.
Tax conditions:
For (percentage) tax conditions (condition class KOAID = 'D'), we generally recommend the condition basis formula 016.
In the case of intercompany billing or rebate settlement documents, the system always determines the condition basis with the condition basis formula 002, even if it is not explicitly maintained in the pricing procedure.
However, this does not apply if a different condition basis formula is maintained in the pricing procedure. In this case, the condition basis formula entered in the pricing procedure is used.
Example:
1. Customizing for the pricing procedure (for example, Transaction V/08):
Step CTyp Description Fro To AltCBV
010 ZPR1 Pricing condition 1
015 ZPR2 Pricing condition 2
020 Gross
025 ZMA1 Material discount 1
030 ZMA2 Material discount 2 010 015
035 ZKU3 Customer discount 3
040 ZKU4 Customer discount 4 015 030
045 Net
050 MWST Output tax 016
2. Pricing result:
Due to the specified pricing procedure, the system issues
the following pricing result for a quantity of 2 PC:
Condition Amount Basis Value Inactive
ZPR1 Pr cond 1 EUR 60.00/1 PC 2.000 PC EUR 120.00 Y
ZPR2 Pr cond 2 EUR 54.00/1 PC 2.000 PC EUR 108.00 Y
ZPR2 Pr cond 2 EUR 56.00/1 PC 2.000 PC EUR 112.00
Gross EUR 56.00/1 PC 2.000 PC EUR 112.00
ZMA1 Mat disc 1 1.000-% EUR 112.00 EUR 1.12- A
ZMA2 Mat disc 2 2.000-% EUR 340.00 EUR 6.80-
ZKU3 Cust disc 3 3.000-% EUR 105.20 EUR 3.16-
ZKU4 Cust disc 4 4.000-% EUR 325.20 EUR 13.01-
Net EUR 44.52/1 PC 2.000 PC EUR 89.03
MWST Output tax 16.000% EUR 89.03 EUR 14.24
3. How did the condition bases result?
a) Due to reference steps that are not maintained, the condition basis for the discount ZMA1 results only from the last active pricing condition ZPR2 with the condition value EUR 112.00 ("ZWISU logic" in accordance with section
1).b) Since reference steps 10 to 15 were maintained for the discount ZMA2, all three pricing conditions are relevant for this discount, including the one deactivated with 'Y'. Therefore, in accordance with section 2, this results
in a condition basis of EUR 120.00 + 108.00 + 112.00 = EUR 340.00.c) For ZKU3, the condition basis is EUR 105.20, resulting from the condition values of the active conditions ZPR2 with EUR 112.00 and ZMA2 with EUR -6.80. The discount ZMA1 that is inactive with 'A' due to an exclusion by means
of exclusion groups has no function ("ZWISU logic" in accordance with section 1).d) Since reference steps 15 to 30 are maintained for ZKU4, all condition values in this area are relevant for ZKU4, except for the discount ZMA1 that is inactive with 'A', but including the subtotal 'Gross' from step 020. The condition
basis that results in accordance with section 2 is 108.00 + 112.00 + 112.00 - 6.80 = EUR 325.20.e) For the MWST tax, the condition basis results in accordance with section 3 and 4 from the accrued (up to now) net value EUR 112.00 - 6.80 - 3.16 - 13.01 = EUR 89.03 (conditions ZPR2, ZMA2, ZKU3, and ZKU4).
相关文章推荐
- SD-sap是如何确定条件值的定价值(KWERT)的?
- SD-sap是如何确定条件值的数值或者比例(KBERT)的?
- SAP-MM 价格条件详解-01计算方案的确定及部分概念说明
- 浮点型计算如何确定精度
- 如何确定抽样统计的最小样本量(附:随机抽样统计的抽样误差Excel计算表格)
- 如何确定抽样统计的最小样本量(附:随机抽样统计的抽样误差Excel计算表格)
- 如何根据条件来确定某个字段是否应该被序列化
- SAP里面的销售税是如何确定的
- SAP SD销售收入科目确定VKOA
- 在opencv中,强分类器阈值是如何确定的?虚警率是怎么计算的?
- 如何确定抽样统计的最小样本量(附:随机抽样统计的抽样误差Excel计算表格)
- sd--如何控制定价条件根据用户不同而操作不同(有的可以输入有的不可以)
- sd--如何控制定价条件根据用户不同而操作不同(有的可以输入有的不可以)
- sd--如何控制定价条件根据用户不同而操作不同(有的可以输入有的不可以)
- sd--如何控制定价条件根据用户不同而操作不同(有的可以输入有的不可以)
- SAP SD Billing的科目确定
- Note 23888 - SD performance and tuning: A basis for notes(sap条件类型性能优化NOTE)
- 【SAP-SD】销售订单的开票冻结状态如何复制至外向交货单
- 图解:sap中的账户确定(账户决定或者科目确定)如何实现如总账的集成
- SAP MM和SD中的条件表