Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 518
Message text: Price determination data missing for purchasing document &1, item &2
No document conditions exist for item &V2& purchasing document &V1&.
SYSTEM_RESPONSE<(>&<)>
It is not possible to update the business volume statistics for
subsequent (end-of-period rebate) settlement purposes with respect to
this document item.
As a rule, a purchasing document always has document conditions.
Therefore, you should check:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
that there really are no document conditions for purchasing documentError message extract from SAP system. Copyright SAP SE.
MN518
- Price determination data missing for purchasing document &1, item &2 ?The SAP error message MN518, "Price determination data missing for purchasing document &1, item &2," typically occurs in the context of purchasing documents, such as purchase orders or contracts, when the system is unable to determine the price for a specific item. This can happen for several reasons, and understanding the cause is essential for resolving the issue. Causes: Missing or Incorrect Info Records: The system may not find a valid info record for the material and vendor combination. Info records contain pricing and other purchasing information. Missing Conditions: The pricing conditions (like price, discounts, etc.) may not be maintained in the condition records for the relevant purchasing document. Material Master Data Issues: The material master may not have the necessary purchasing data maintained, such as the purchasing group or valuation class. Vendor Master Data Issues: The vendor master data may not be correctly set up, or the vendor may not be assigned to the
Get instant SAP help. Sign up for our Free Essentials Plan.
MN517
Multiple update of "actual" data may occur (see long text)
What causes this issue? Version '000' contains the supplier business volumes subject to settlement. These will be changed when the report i...
MN516
Update data for rebate arrangement &1 will not be posted
What causes this issue? The business volume data created for arrangement &V1& are probably not correct, for example calculation schema is inc...
MN519
Business volume already updated
What causes this issue? The business volume update has already taken place.System Response The current transaction or event will be ignored (no upda...
MN520
Update date &1 adopted (normal update)
What causes this issue? The condition is included among the document conditions of item &V4& of purchasing document &V3&. The supplie...
Click on this link to search all SAP messages.