Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
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 purchasing organization.
Price Control Settings: The price control settings in the material master (standard price vs. moving average price) may not be configured correctly.
Document Type Configuration: The document type used for the purchasing document may not be configured to allow price determination.
Solutions:
Check Info Records: Verify that the info record for the material and vendor exists and is correctly maintained. You can do this using transaction code ME13 (Display Info Record).
Maintain Condition Records: Ensure that the necessary condition records for pricing are maintained. You can check this using transaction code MEK1 (Create Condition) or MEK2 (Change Condition).
Review Material Master Data: Use transaction code MM03 to check the material master data for the relevant purchasing views. Ensure that all necessary fields are filled out correctly.
Check Vendor Master Data: Use transaction code XK03 to review the vendor master data. Ensure that the vendor is assigned to the correct purchasing organization and that all relevant data is maintained.
Review Price Control Settings: Check the price control settings in the material master to ensure they are appropriate for your purchasing scenario.
Document Type Configuration: If the issue persists, check the configuration of the document type in the customizing settings (transaction SPRO) to ensure it allows for price determination.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to price determination in your version of SAP.
Documentation: Refer to SAP Help documentation for detailed information on purchasing processes and price determination.
By following these steps, you should be able to identify the root cause of the MN518 error and implement the necessary corrections to resolve it.
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.