Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix MN518 - Price determination data missing for purchasing document &1, item &2


SAP Error Message - Details

  • 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

  • Show details Hide details
  • What causes this issue?

    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.

    How to fix this error?

    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 document
    &V1& in the system.
    whether or not the missing data has already been archived.
    If this is an error message, the document conditions for a recompilation
    of the supplier business volumes are missing. Under certain
    circumstances you can ignore a warning message (compilation of
    supplementary supplier business volume) if the document is not relevant
    to the rebate arrangement.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message 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:

    1. 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.

    2. Missing Conditions: The pricing conditions (like price, discounts, etc.) may not be maintained in the condition records for the relevant purchasing document.

    3. Material Master Data Issues: The material master may not have the necessary purchasing data maintained, such as the purchasing group or valuation class.

    4. 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.

    5. Price Control Settings: The price control settings in the material master (standard price vs. moving average price) may not be configured correctly.

    6. Document Type Configuration: The document type used for the purchasing document may not be configured to allow price determination.

    Solutions:

    1. 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).

    2. 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).

    3. 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.

    4. 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.

    5. Review Price Control Settings: Check the price control settings in the material master to ensure they are appropriate for your purchasing scenario.

    6. 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:

      • ME13: Display Info Record
      • MEK1/MEK2: Create/Change Condition Records
      • MM03: Display Material Master
      • XK03: Display Vendor Master
      • ME21N: Create Purchase Order
      • ME22N: Change Purchase Order
    • 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.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author