Supplementary Condition以及purchase pricing FAQ

如果有一些价格条件是依附于特定物料的，则我们可以使用Supplementary condition。一般它都用来计算surcharge和discount. 因为supplementary condition是依附于main condition也就是说与main condition有同样的有效期间，而且condition type都不会分配access sequence. 具体的配置方法是在main condition type编辑画面，分配supplementary pricing procedure schema。比如SAP标准的PB00就分配了RM0002(Condition Supplement Price)，在RM0002中配置这些supplementary condition type。然后当我们维护info record的condition时，可以点击下面的小加号button让SAP提案所有的condition。

但是有一点要注意，所有的supplementary condition如果想在采购价格计算时起作用的话，必须同样将这些conditiont type配置进采购的定价过程，否则系统将忽略。

SAP Note 456691 - FAQ: Price determination in purchasing 有其他采购定价相关的讲解。这篇Note很不错

 

Summary

Symptom

This note contains questions and answers that are often presented dealing with price determination. Information on conditions are available in Note 456690.

Catalog of questions

1. Problems occur during the price determination in Transaction ME21N/ME22N.

2. What does master conditions (time-dependent conditions) distinguish from document conditions?

3. How does price determination determine the conditions via a 'Last purchase order'?

4. Why does no price determination occur during the creation of a scheduling agreement?

5. Rounding errors occur during a price determination with consideration of conditions in the info record.

6. Why is a condition type not used during the creation of a purchasing document?

7. When you create a scheduling agreement with reference to a contract, why are the conditions from the contract not transferred to the scheduling agreement?

8. Why are no prices found when you post a goods receipt for a scheduling agreement / during the price simulation for a scheduling agreement (scheduling agreement was created with reference to a contract)?

9. How can you maintain conditions for a material group item in the contract?

10. A plant-dependent info record and a cross-plant info record exist.They are both flagged for deletion (EINE-LOEKZ).Why is then the price of the cross-plant info record still used during the creation of a purchase order?

11. Why is the 'Update' (update prices) pushbutton not activated on the header conditions screen in a purchase order?

12. Why are conditions not automatically determined during the maintenance of a quotation (Transaction ME47)?

13. Why is the price not copied from the purchase requisition to the purchase order?

14. ME22N. Why is the price of the purchase order not converted to the new currency when the vendor is changed (other currency)?

15. If the data of a purchase order item is changed, for example the material group, account assignment category and so on, a new price determination is carried out automatically in the new Enjoy Transaction (ME21N/ME22N) whereas this does not occur in the 'old' Transaction ME21/ME22.

16. Why are absolute conditions of a purchasing document are adjusted/calculated proportionally when posting a goods receipt to the GR quantity?

17. How does a new price determination affect the values posted during goods receipt when a goods receipt is cancelled?

18. When are the header conditions updated if a purchase order item is deleted?

19. When displaying/changing a purchasing document (scheduling agreement/contract) a runtime error occurs since the price (net price or effective price) is negative. How can this problem be solved?

20. Why does the system display different/additional conditions when displaying/changing a purchase order that were not displayed during the creation of the document?

              Why is the manual gross price (PBXX) suddenly displayed next to the gross price (PB00) (or vice versa)?

21. Why does the price determination not determine any price although in the master conditions (info record, contract, scheduling agreement) valid prices (with scales) exist?

22. In a contract or scheduling agreement (with time-dependent conditions), currently valid conditions have been maintained.Why does the system nevertheless display an obsolete price in the item overview?

23. A purchase order item contains a manual gross price (in standard PBXX). By using Transaction ME21N or ME22N, you can change basic data such as the plant.

              What does it depend on whether the price (the conditions) remain or whether these are deleted (the system displays message 06 218 "Net price must be greater than 0")?

24. Why does the system not take into account the better price that results from the scales for a purchase order (several items for the same material, scales are maintained in master conditions)?

25. You create a purchase order with reference to a quotation with document conditions.The quotation contains next to the gross price (in the standard PBXX) further conditions such as discounts or surcharges.

              If you carry out a price determination of type 'C' ("Copy manual pricing elements and redetermine the others") for the purchase order item (manually or arranged by the system, for example when changing the account assignment category's), the system doubles conditions. Why?

26. You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Why are conditions determined twice during pricing?

27. You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Error message ME573 "The transaction cannot be posted because of an error in the price determination" is generated.

28. What does it depend on whether the net price on the item overview of a purchase order is ready for entry?

29. What does it depend on whether the condition value for the condition of a returns item becomes negative?

30. How is pricing carried out in the info record or contract, if fixed conditions are taken into account for the net price (calculation rule 'B', fixed amount)?

31. You are using the user exit EXIT_SAPLMEKO_002 and find differences in pricing between Transaction ME21N and Transactions ME21/ME59.

32. You copy a purchase order item (ME21/ME22 or ME21N/ME22N), the reference item contains taxes. Why is the corresponding condition copied but the condition amount/value is not?

33. When posting goods receipt for a scheduling agreement of price date type '5' (new pricing at goods receipt), how can a price with value '0' be determined which is reflected in the purchasing history (and in the GR/IR clearing account)?

34. Can conditions be changed after a goods/invoice receipt or is a new price determination still possible then?

35. The net price in the contract is to be updated using Report RM06ENP0. The document contains valid conditions. Why does the report not determine any net price?

36. In a scheduling agreement with time-dependent conditions, you maintain a condition with scales. Is it deliberate that always the first scale level is used for calculating the net price?

37. You add supplementary conditions to a quotation, for example, discounts (condition type RA10). Why does the system ignore these conditions during the quotation comparison (Transaction ME49)?

--------------------------

1. Question:

Problems occur during the price determination in Transaction ME21N/ME22N.

Answer:

It is highly recommended to implement Note 381391 and the related notes contained in that note, provided that - according to the R/3 Support Package Release - this has not occurred yet.

--------------------------

1. Question:

What does master conditions (time-dependent conditions) distinguish from document conditions?

Answer:

Conditions in the info record and contract are master conditions.The difference between quotations and scheduling agreements is made by the document type (indicator 'time-dependent conditions').Master conditions are limited to a certain validity period, have master data status and are rather valid on a long-term basis.
Master conditions, which refer to more general price agreements such as vendor, material type, ... (general conditions, Transactions MEK*), can also be represented.
Generally conditions in purchase orders are document conditions.They are only valid for this document.Document conditions are also available for quotations and scheduling agreements if this is set in Customizing.

--------------------------

1. Question:

How does price determination determine the conditions via a 'Last purchase order'?

Answer:

No valid conditions are in the info record, one, however, exists for the info record 'last document', then all become (!)Conditions copied from this document if following requirements are fulfilled:

• After the system has carried out the price determination, the net price must be equal to zero (EKPO-NETPR = 0.00).

           However, if you maintained master conditions on the vendor or material group level, that affect the net price calculation, the net price is not equal to zero after the system has carried out the price determination and the conditions from the last purchase order are not copied.

• The last document must not be a request for quotation.

• The info record must not be deleted.

• Vendor and material from info record and last document must be identical.

• The calculation schema of the last document must correspond to the currently determined schema.
  

During the transfer of the conditions from the last document a pure copy function is carried out. In that case the conditions of the calculation schema are not checked.
Condition records of the subsequent billing (condition category has condition class C) are not copied, but rather thoroughly redetermined in order to ensure the consistency of the condition records for the field contents (also see Note 486757).
If copying conditions from the last purchase order is generally not required, you have the option of deactivating this procedure via user parameter EVO (see also Note 675523).

--------------------------

1. Question:

Why does no price determination occur during the creation of a scheduling agreement?

Answer:

Check the Customizing for the document type of the scheduling agreement (Transaction OMED).A price determination only occurs during the creation of the scheduling agreement if the 'time-dependent conditions' indicator is not set.

--------------------------

1. Question:

Rounding errors occur during a price determination with consideration of conditions in the info record.

Answer:

Check the standard quantity and price unit in the info record (considering Notes 30658 and 39963).
On the condition screen, go to the condition analysis.('Analysis' pushbutton).There you will see all the conditions of the calculation schema. By double-clicking on the condition type (or on the access) the system will open the detail display to the right. If you go to the technical view ('View' pushbutton) there, you will receive information on the field contents that were used for the access to the condition table or the fields which were not filled for the access.You can avoid rounding errors by choosing a standard quantity that is at least as large as the price unit.

--------------------------

1. Question:

Why is a condition type not used during the creation of a purchasing document?

Answer:

On the condition screen, go to the condition analysis. ('Analysis' pushbutton).There you will see all the conditions of the calculation schema. By double-clicking on the condition type (or on the access) the system will open the detail display to the right. If you go to the technical view ('View' pushbutton) there, you will receive information on the field contents that were used for the access to the condition table or the fields which were not filled for the access.

--------------------------

1. Question:

When you create a scheduling agreement with reference to a contract, why are the conditions from the contract not transferred to the scheduling agreement?

Answer:

See Note 160630.

--------------------------

1. Question:

Why are no prices found when you post a goods receipt for a scheduling agreement / during the price simulation for a scheduling agreement (scheduling agreement was created with reference to a contract)?

Answer:

See Note 431460.

--------------------------

1. Question:

How can you maintain conditions for a material group item in the contract?

Answer:

Conditions for material group items are not allowed in the contract. (See notes 62729 and 105899).

--------------------------

1. Question:

A plant-dependent info record and a cross-plant info record exist.They are both flagged for deletion (EINE-LOEKZ).Why is then the price of the cross-plant info record still used during the creation of a purchase order?

Answer:

Since the corresponding condition tables are read by an external SD module, the information on the deletion indicator of the info record is not available there.
You can only set that the conditions of the cross-plant info record are to be read, if the plant-dependent info record is deleted, by means of a corresponding transfer parameter (komp-no017, set in module ME_FILL_KOMP_PO).
For the case that both info records are deleted you have the option of changing the validity period of the conditions to a past date or archiving the info record.

--------------------------

1. Question:

Why is the 'Update' (update prices) pushbutton not activated on the header conditions screen in a purchase order?

Answer:

The pushbutton does not have any function on header level.It is not meant to trigger a new pricing for all items of one document.This can only occur by item. Thus the pushbutton is not active on header level (in the standard system).
You can use Transaction MEI2 to perform the mass adjustment of documents according to condition changes. However, consider the functional restrictions in the online documentation or in Note 457511 "FAQ: Purchase order change and goods receipt in purchasing".
--------------------------

1. Question:

Why are conditions not automatically determined during the maintenance of a quotation (Transaction ME47)?

Answer:

During quotation maintenance, no pricing occurs.The conditions must be maintained manually.

--------------------------

1. Question:

Why is the price not copied from the purchase requisition to the purchase order?

Answer:

See Note 393367.

--------------------------

1. Question:

ME22N. Why is the price of the purchase order not converted to the new currency when the vendor is changed (other currency)?

Answer:

See Note 445509.

--------------------------

1. Question:

If the data of a purchase order item is changed, for example the material group, account assignment category and so on, a new price determination is carried out automatically in the new Enjoy Transaction (ME21N/ME22N) whereas this does not occur in the 'old' Transaction ME21/ME22.

Answer:

This is not an error.The new Enjoy Transaction was intentionally designed in such a way and is much more extensive with regard to the price determination.

--------------------------

1. Question:

Why are absolute conditions of a purchasing document are adjusted/calculated proportionally when posting a goods receipt to the GR quantity?

Answer:

See Note 304178.

--------------------------

1. Question:

How does a new price determination affect the values posted during goods receipt when a goods receipt is cancelled?

Answer:

See Note 508009.

--------------------------

1. Question:

When are the header conditions updated if a purchase order item is deleted?

Answer:

If a purchase order item is deleted, the item is marked as 'statistical' (field EKPO-STAPO = X) and the change is reflected in the header conditions.
However, if for the item the final invoice indicator (EKPO-EREKZ) or the inward delivery completed indicator (EKPO-ELIKZ) is set, the item is not marked as 'statistical' (EKPO-STAPO is not set) and thus the header conditions are not updated.

--------------------------

1. Question:

When displaying/changing a purchasing document (scheduling agreement/contract) a runtime error occurs since the price (net price or effective price) is negative. How can this problem be solved?

Answer:

Proceed as follows to determine the condition that results in the negative price:
Scheduling agreement:Display the document using Transaction ME3N. Select the item and navigate via Edit to the price simulation.
Contract:Display the conditions for the contract via Transaction MEKA. These can be changed directly from here.

--------------------------

1. Question:

Why does the system display different/additional conditions when displaying/changing a purchase order that were not displayed during the creation of the document?
Why is the manual gross price (PBXX) suddenly displayed next to the gross price (PB00) (or vice versa)?

Answer:

These problems indicate that, after the creation of the purchase order, the calculation schema has been changed.This must absolutely be avoided.

--------------------------

1. Question:

Why does the price determination not determine any price although in the master conditions (info record, contract, scheduling agreement) valid prices (with scales) exist?

Answer:

Check whether a scale exists for the quantity on which the price determination is based.It is recommended to set the quantity of the first scale to zero in order to avoid such problems.

--------------------------

1. Question:

In a contract or scheduling agreement (with time-dependent conditions), currently valid conditions have been maintained.Why does the system nevertheless display an obsolete price in the item overview?

Answer:

During the maintenance of condition validity periods, the system uses the price of the currently valid period for the item (field EKPO-NETPR). However, if a condition validity period expires, the net price of the item is not updated automatically.This can be made up with report RM06ENP0 (for contracts) or report RM06ENP1 (for scheduling agreements).
The obsolete price does not affect the creation of a purchase order with reference to such a document because basically the system uses the current price from the conditions without taking into account the price of the item (EKPO-NETPR).

--------------------------

1. Question:

A purchase order item contains a manual gross price (in standard PBXX).By using Transaction ME21N or ME22N, you can change basic data such as the plant.
What does it depend on whether the price (the conditions) remain or whether these are deleted (the system displays message 06 218 "Net price must be greater than 0")?

Answer:

In case of the change of basic data, a new price determination is triggered.Here, if no price is found, the system checks whether the price existing before was a 'manual price'.
(A price is considered as being 'manual' if the net price is equal to the gross price (PBXX), that is, no further conditions have been included in the net price.This can be seen by the fact that field 'net price' is ready for input in the item overview).
If this is the case, the system transfers the price existing before.As a result, the user gets the impression as if the price had not been changed through the change at the item.
Otherwise (net price not equal to gross price -> field 'net price' in the item overview is not ready for input) the price existing before (the conditions) cannot be transferred.The price must be maintained again, the system displays error message 06 218 "Net price must be greater than 0".

--------------------------

1. Question:

Why does the system not take into account the better price that results from the scales for a purchase order (several items for the same material, scales are maintained in master conditions)?

Answer:

The purchase order quantities of the items are only grouped together for the consideration of scales if the document is saved or checked.

--------------------------

1. Question:

You create a purchase order with reference to a quotation with document conditions.The quotation contains next to the gross price (in the standard PBXX) further conditions such as discounts or surcharges.
If you carry out a price determination of type 'C' ("Copy manual pricing elements and redetermine the others") for the purchase order item (manually or arranged by the system, for example when changing the account assignment category's), the system doubles conditions. Why?

Answer:

In case of a reference to the quotation the conditions are copied from the quotation.If you carry out a price determination of type 'C' afterwards, the manually maintained conditions (from the quotation, as PBXX) will remain, in addition the gross price from the master condition is set(for example info record). this can be seen on the detail screen for the condition.

For more information you can also refer to Notes 76774 and 548900.

----------------------------------------------------------------------

1. Question:

You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Why are conditions determined twice during pricing?

Answer:

You changed/maintained this condition manually in the purchase order. In addition, the condition has been maintained in the master conditions (e.g. info record).
During goods receipt, pricing of type 'C' is carried out. This means that the condition changed/maintained manually from the document is kept and is determined from the master conditions in addition.
This problem can be solved by choosing the following customizing setting (Transaction m/06) for the condition:
     Manual entries:   C 'The manual setting takes priority'
If during goods receipt, the pricing of type 'C' determines an already existing condition from the master conditions, that condition is set to inactive since the manual condition from the document takes priority (to be seen on the condition details screen).
Please also refer to Note 548900.

--------------------------

1. Question:

You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Error message ME573 "The transaction cannot be posted because of an error in the price determination" is generated.

Answer:

It is possible that, during the price determination, condition records are used that do not yet exist at the time of the creation of the document item. As, for example, an additional discount on the vendor level, ... These additionally determined conditions can, for example, result in the net price being negative or 0.
In order to find out from where the conditions are coming that lead to an incorrect price, it can help in some cases to create a purchase order item with identical data. Branch to the condition screen in the 'analysis'. Here, you can find out which condition record results in the undesired result.

--------------------------

1. Question:

What does it depend on whether the net price on the item overview of a purchase order is ready for entry?

Answer:

The net price is not ready for entry (price can be changed on the condition screen only), if

• the document currency is not the same as the condition currency of the price,

• apart from the basic price PB00, other conditions are used to calculate the gross amount (e.g. variants),

• if the net amount is not the same as the gross amount.
  
  --------------------------
  

1. Question:

What does it depend on whether the condition value for the condition of a returns item becomes negative?

Answer:

The condition value for the condition of a returns item receives a negative sign, if in the customizing of the condition type
- condition type 'B' (delivery costs) is not set,
- the provision indicator is not set,
- in the calculation schema for the condition the statistical indicator
  is not set.

The condition value for a condition of type 'B' (delivery costs) only receives a negative sign, if calculation rule 'A' (percentage) is set for the condition.
(see LV61AA43, FORM xkomv_kwert_ermitteln)

--------------------------

1. Question:

How is pricing carried out in the info record or contract, if fixed conditions are taken into account for the net price (calculation rule 'B', fixed amount)?

Answer:

See Note 586856.

--------------------------

1. Question:

You are using the user exit EXIT_SAPLMEKO_002 and find differences in pricing between Transaction ME21N and Transactions ME21/ME59.

Answer:

A frequent cause for the fact why pricing is different for Transaction ME21/ME59 when using user exit EXIT_SAPLMEKO_002 is the use of fields EKPO-BANFN / EKPO-BNFPO in the user exit. These two fields are filled only when Transaction ME21N is used. In Transactions ME21/ME59, these fields have their initial values, but the document and item numbers of the purchase requisition are available in Table EKET.
This difference results from the enhanced functional range of the Enjoy purchasing transaction and cannot be interpreted as an error in the R/3 standard program.
To achieve identical behavior of the mentioned transactions, you can enhance the interface of user exit EXIT_SAPLMEKO_002 and function module ME_FILL_KOMP_PO accordingly.

--------------------------

1. Question:

You copy a purchase order item (ME21/ME22 or ME21N/ME22N), the reference order item contains taxes. Why is the corresponding condition copied but the condition amount/value is not?

Answer:

Amount and value are not copied to the new purchase order item. Amount and value are determined as soon as a PRICING_COMPLETE is carried out. This is the case when checking or posting the document and when going to the header conditions.

--------------------------

1. Question:

When posting goods receipt for a scheduling agreement of price date type '5' (new pricing at goods receipt), how can a price with value '0' be determined which is reflected in the purchasing history (and in the GR/IR clearing account)?

Answer:

See Note 683646.

--------------------------

1. Question:

Can conditions be changed after a goods/invoice receipt or is a new price determination still possible then?

Answer:

Changing the delivery costs is impossible after the goods receipt has been posted.
After applying Note 549408, changing conditions of type 'B' (delivery costs) is no longer possible after the invoice has been posted or parked.
If data are changed in the purchase order which normally trigger a new price determination of type 'B' or 'C', that automatic price determination is not carried out, if goods receipt or invoice receipt has already been posted.
See also Note 457511, Question 3.

--------------------------

1. Question:

The net price in the contract is to be updated using Report RM06ENP0. The document contains valid conditions. Why does the report not determine any net price?

Answer:

The net price is determined based on the release quantity. If the release quantity is lower than the price unit, it may happen that the net price is rounded off to zero if the gross price is low.
The release quantity should always be higher than or equal to the price unit.

--------------------------

1. Question:

In a scheduling agreement with time-dependent conditions, you maintain condition with scales. Is it deliberate that always the first scale level is used for calculating the net price?

Answer:

Price determination in the scheduling agreement cannot be compared to the one in purchase orders, if the scheduling agreement is a document with time-dependent conditions (master conditions). To display the price in the scheduling agreement, always the first scale level is taken into account.
On the topic "Goods receipt in scheduling agreements with scales", please read Note 401941.

--------------------------

1. Question:

You add supplementary conditions to a quotation, for example, discounts (condition type RA01). Why does the system ignore these conditions during the quotation comparison (Transaction ME49)?

Answer:

The problem occurs if you use a supplementary calculation schema (RM0002 in the standard system) that included conditions that are not contained in the calculation schema of the document (RM0000 in the standard system). All condition types used in a supplementary calculation schema must be defined in the calculation schema of the document.

--------------------------

Other terms

FAQ, PRICING, NETPR, EFFPR, NETWR, NETPR, KSCHL, EBAN-BPUEB,
BEKPO-NETZU