Skip to Content
avatar image
Former Member

Copy Controls:

Ideally What Should be copy control Pricing Type for the Following:

Delivery to Billing.

Also tell me the explanation and where should the following pricing type be used.






Thanks in advance


Amlan Sarkar

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Jul 05, 2008 at 10:23 PM

    Pricing type would depend on business requirements.

    For example, In standard LF to F2 copy settings,

    Item category DLN (Standard item w/order) has pricing type B

    Item category TAN (standard item) has pricing type G.

    As a rule of thumb, you should have all item categories for a particular sales document with the same settings. You may generally use pricing type B, u201Ccarry out new pricing,u201D or G, u201Ccopy pricing elements unchanged and redetermine taxes.u201D. When using condition B, all manual pricing condition types are lost.

    Pricing type details (source: Note 24832)

    • 'A' (Copy price components and redetermine scales):

    No condition types are redetermined. Only the scaled prices are adapted due to a changed basis.

    • ' B' (Complete new pricing): Completely new pricing (as if you created a new item), manual conditions are lost.

    Restriction: Condition types which are not determined via condition technique (for example, condition type 'VPRS' or condition types with KNTYP = 'G' which are determined using formulas) are NOT redetermined even if you do not change them manually.

    • 'C' (Copy manual pricing elements and redetermine the others): Completely new pricing, manual ones are copied.

    Caution: Here you have to make sure that all condition types that can possibly be changed manually have T685A-KMANU = 'C' (Manual entry has priority) in Customizing. Otherwise, it is possible that the conditions are displayed twice (automatically and manually) and that both are active.

    • 'D' (Copy pricing elements unchanged): As in pricing type 'A' but the prices are fixed (no scales are read). Condition base value and value are redetermined.

    • 'G' (Copy pricing elements unchanged and redetermine taxes):

    a) The following condition types are redetermined:

    Condition class KOAID = 'D' (Taxes)

    Condition class KOAID = 'C' (Volume-based rebate)

    Condition category KNTYP = 'I' (Intercompany billing conditions)

    Condition category KNTYP = 'R' (Invoice list conditions)

    Condition category KNTYP = 'L' (Always new when copying)

    Condition category KNTYP = 'G' (Cost conditions)

    Condition category KNTYP = 'E' (Cash discount conditions)

    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.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 05, 2008 at 04:30 PM

    Dear Amlan

    Almost all the companies are configured for either B or G Pricing Types, to the best of my knowledge. My first preference would always be G where the pricing conditions will be copied from sale order to billing. Even if your pricing conditions have different pricing, while creating billing, by default, the unit rate will flow from sale order. Of course, if you want to change, you can go to item condition tab where if you click on update button, you will find a screen where you double click on B, your pricing would be updated.

    If you maintain B, irrespective of your sale order price, while creating billing, whatever you maintain in VK11, that price will be copied into your billing. In some instances this is not suitable where there would be an agreement between the supplier and the customer that whatever price is accepted while placing the order, supplies should be executed only at that price. Any price revision (either plus or minus) would be applicable only for new orders. So in this case, B wont suit the requirement.


    G. Lakshmipathi

    Add comment
    10|10000 characters needed characters exceeded