FAQ: Conditions in Purchasing
Q1. Why is an incorrect condition screen displayed for a document with time-dependent conditions (for example quotation, contract)?
for quotation: Program SAPMV13A, screen 1016
'Create AP gross price (PB00): fast entry'
Program SAPMV13A, screen 1019
'Create % from gross (RA01): fast entry'
Answer: Check whether the correct calculation schema is entered (Transaction M/06) for condition PB00 or RA01. In the R/3 Standard System, schema RM0002 must be entered for condition PB00, and schema RM0001 for condition RA01.
Q2:Why is the valid-to date (for example, transaction ME13, purchasing info record -> purchasing data 1-screen, database field EINE-PRDAT) set on the current date (SY-DATLO) during the mass change of the conditions for the purchasing info record by means of transaction MEKC?
Answer: By programming it is not possible to again determine the valid-to date from the condition records. As after the change of the info record conditions by means of the condition maintenance (for example, MEKC) report RM06INP0 should run in spite of that, in this case the valid-to date is again determined and thus the inconsistency is corrected by itself (for details on report RM06INP0 refer to note 392988).
Q3: Why is a condition not determined during the creation of a contract although this condition is found during the creation of a purchase order with identical data?
Answer: During the creation of a contract, no price determination occurs as in the purchase order; the conditions are only copied from the info record or from the reference document.
The conditions in a contract are master conditions. For this purpose, also consider note 456691, question 2.