|
This message tells you that the condition record exists, but has notbeen set in the document. If pricing was carried out again for thedocument item, then the condition would be set. There are different reasons for this: The condition was deleted manually in the item condition screen. The condition record was created later. Please note that orderprocessing and pricing have buffer mechanisms. This means that a newlyadded condition record might only be found after order processing hasbeen left completely and then started again. If the condition type is used for subsequent settlement (rebate), theremay be subsequent updating of business volume (the agreement is iscreated retrospectively). The document conditions do not contain thecondition record, as the condition record was not created when pricingwas carried out. Updating of business volume is carried out usingspecial functions for subsequent settlement. When an item was added, the condition record was accessed with keyfields other than change time. This could lead to different results inthe requirements check at the time of adding and the change time. Thiscan occur when modifications are made. In billing (or when copying orders): Certain condition types were notdetermined in the source document (this is usually controlled by thepricing requirements). When creating the document, the document flow(TVCPF,TVCPA) is processed using a pricing type that does notredetermine these condition types, although they are supposed to becalled via the requirements. |