SAP Note
24832 - Pricing rules (KNPRS)/TVCPA/TVCPF
Component: SD-BF-PR (Pricing), Version: 33, Released On: 20.12.2023
Symptom
Whether or not the system should redetermine conditions depends on the situation. For this,
1. During the creation of orders or billing documents, some conditions are redetermined
even though you want to copy the conditions from the reference document.
2. However, in other transactions, you want to redetermine the conditions instead of
copying them.
3. The new 'New pricing document' function in the order document menu
redetermines all conditions, which means that it works with the pricing type 'B'.
However, you require a different pricing type instead of the pricing type 'B'.
A) Examples of pricing type usage
B) Different pricing types
1. 'A' (Copy price components and redetermine scales)
3. 'C' (Copy manual pricing elements and redetermine the others)
4. 'D' (Copy pricing elements unchanged)
5. 'E' (Adopt price components and fix values)
6. 'F' (Copy pricing elements, turn value and fix)
7. 'G' (Copy pricing elements unchanged and redetermine taxes)
8. 'H' (Redetermine freight conditions)
9. 'I' (Redetermine rebate conditions)
10. 'J' (Redetermine confirmed purchase net price/value)
11. 'K' (Adopt price components and costs. Redetermine taxes)
12. 'M' (Copy pricing elements, turn value)
13. 'N' (Transfer pricing components unchanged, new cost)
14. 'O' (Redetermine variant conditions)
16. 'Q' (Redetermine calculation conditions)
17. 'R' (Apply price parts and bonus conditions)
18. 'S' (Ship & Debit (IBU HiTec))
19. 'U' (Redetermine precious metal conditions)
C) Changing the default behavior
1. Introduction of new pricing types as variants of existing pricing types (examples 1 to
4)
2. Execution of new pricing in the dialog (example 5)
D) Additional information
A) Examples of pricing type usage
The following text provides some examples of the use of the pricing type (KNPRS)
You want to copy the condition type 'VPRS' (Cost) from the order to the billing document.
You are using the pricing type G. However, as a consequence, the value of the VPRS condition
in the billing document may differ from the value of the goods issue posting.
You want to copy the condition type 'PI01' (Price for intercompany billing) from the order
to the billing document. You are using the pricing type G.
The cost 'VPRS' is to be redetermined when a credit memo request is copied from a billing
document. This is required if you defined the credit memo item in such a way that no costs
are to be determined. Since the pricing conditions are no longer checked during copying, you
must proceed in this way to eliminate the VPRS condition.
Billing is to be performed using the pricing type G. However, condition types with condition
category S and T (standard cost or moving cost) are also to be redetermined in the billing
document. In the standard system, this pricing type copies those condition types from the
order.
When you choose the 'Edit -> New Pricing Document' function in the menu of the order
document, you require a different pricing type than pricing type B.
B) Different pricing types
The pricing type controls which condition types are redetermined and which are copied
unchanged. (However, the item is always revaluated; see also SAP Note 930870.) Below, you
will find a description of the pricing type characteristics that are used in the standard
system (for the enhancement options for customers, see SAP Note 26115).
Note that the specified standard pricing types sometimes do not exist in older releases,
or that the standard pricing type characteristic may be different in the individual
releases. Therefore, the given consulting note should not be considered to be exhaustive.
It merely serves to explain the principle of how a pricing type is structured and how its
characteristics can be influenced.
The exact characteristic of a pricing type in the release being used can be seen directly
in the source code of the form routine KONDITIONSVORSTEP in the main program SAPLV61A.
The list below provides a rough overview of the behavior of the various pricing types:
No condition types are redetermined. Only the scale prices are adapted, due to a changed
basis.
Completely new pricing (as if you created a new item), manual conditions are lost.
Restriction: Condition types that are not determined via the condition technique (for
example, the condition type 'VPRS' or condition types with KNTYP = 'G', which are determined
using formulas) are NOT redetermined even if they have not been changed manually.
Completely new pricing, manual ones are copied.
Caution: Here you have to make sure that all condition types that can potentially be changed
manually have T685A-KMANU = 'C' ('Manual entry has priority') in customizing. Otherwise, the
conditions may be displayed twice (automatic and manual) and both may be active.
As in pricing type A but the prices are fixed (no scales are read). Condition basis and
condition value are redetermined.
As in pricing type D but neither the condition basis nor the condition value are
redetermined.
Only used within the program.
Condition class KOAID = 'D' (Taxes)
Condition class KOAID = 'C' (Rebate)
Condition class KOAID = 'E' (Extra Pay)
Condition class KOAID = 'G' (Tax Code)
Condition class KOAID = 'Q' (Totals record for fees (only IS-OIL))
Condition class KOAID = 'W' (Withholding tax)
Condition category KNTYP = 'I' (Intercompany billing conditions)
Condition category KNTYP = 'R' (Remuneration list conditions)
Condition category KNTYP = 'L' (Generally new when copying)
Condition category KNTYP = 'G' (Cost)
Condition category KNTYP = 'E' (Cash discount conditions)
Condition category KNTYP = 'f' (Free goods - inclusive)
Condition category KNTYP = 'b' (Transfer price for group valuation)
Condition category KNTYP = 'h' (Profit center cost)
Condition category KNTYP = 'n' (Profit center internal price (route))
All remaining condition types are dealt with like pricing type D. In particular, with
pricing type G, the system does not only redetermine the taxes but also the cost conditions
and the intercompany billing conditions.
Condition category KNTYP = 'B' (Delivery costs)
Condition category KNTYP = 'F' (Freight conditions)
Condition category KNTYP = 'L' (Generally new when copying)
Condition category KNTYP = 'f' (Free goods - inclusive)
Rebate conditions and scales are redetermined.
Condition types with the condition category KNTYP = 'd' (Confirmed purchase net price/value)
are redetermined.
Condition class KOAID = 'D' (Taxes)
Condition class KOAID = 'C' (Rebate)
Condition class KOAID = 'E' (Extra Pay)
Condition class KOAID = 'G' (Tax Code)
Condition class KOAID = 'Q' (Totals record for fees (only IS-OIL))
Condition category KNTYP = 'R' (Remuneration list condition)
Condition category KNTYP = 'I' (Price for intercompany billing)
Condition category KNTYP = 'E' (Cash discount)
No conditions are redetermined; the condition values are multiplied by -1 when copied.
Condition types with condition category KNTYP = 'G' (Cost) are redetermined.
Please note that this pricing type has NO effect on the billing document since here the
goods issue value from the delivery is usually directly transferred to pricing.
Redetermination of the costs by subsequently reading the material valuation segment when
executing pricing type N would result in the goods issue value information being
irretrievably lost.
This standard behavior can be changed by a modification only. If required, please contact
your local consultant or SAP Remote Consulting.
Condition types with condition category KNTYP = 'O' (Variants) are redetermined.
The system does not redetermine any conditions; only the revaluation occurs.
Condition types with condition category KNTYP = 'Q' (Costing) are redetermined.
Condition class KOAID = 'D' (Taxes)
Condition class KOAID = 'E' (Extra Pay)
Condition class KOAID = 'G' (Tax Code)
...