How To Fix M8516 - Prices in & items were not reached or were exceeded

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 516

• Message text: Prices in & items were not reached or were exceeded

What causes this issue?

The price of the invoice items was changed on the basis of the
condition changes.
The system checked the price changes against the tolerance limit. For
&V1& items, the system discovered that the price was outside the
allowed tolerance limits.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

In &V2& items, the price was too high
In &V3& items, the price was too low
&HINTS&
You can change the type of messages '082', '083', '084' and '085' in
Customizing for Invoice Verification. So you might receive a message as
an error message, although it appears as a warning message in the
standard system.

System Response

In the case of a warning message, the blocking indicator is set
accordingly. When you post the invoice, the system blocks it for
payment with the blocking reason "Price variance".
In the case of an error message, the condition changes are not adopted
in the item amounts. Since the amounts are not changed in this case,
the system does not set the blocking indicator.

How to fix this error?

Check your entries and make any necessary corrections. If you post the
document despite the variance (does not apply to an error message), the
system posts the invoice and makes the associated account movements.
However, the document receives a blocking indicator at the same time,
so that it cannot be paid.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M8516 - Prices in & items were not reached or were exceeded ?

  The SAP error message M8516 ("Prices in & items were not reached or were exceeded") typically occurs during the processing of a purchase order, sales order, or during the goods movement when the system detects that the pricing conditions defined for the items are not met. This can happen in various scenarios, such as when the actual price exceeds the expected price or when the pricing conditions are not properly configured.
  Causes:
  
  Price Conditions Not Met: The actual price of the item exceeds the maximum price defined in the pricing conditions.
  Missing Pricing Conditions: The required pricing conditions (like discounts, surcharges, etc.) are not maintained in the system.
  Incorrectly Configured Pricing Procedure: The pricing procedure may not be set up correctly, leading to discrepancies in price calculations.
  Currency Issues: If there are currency conversions involved, discrepancies can arise due to exchange rate differences.
  Master Data Issues: Incorrect or incomplete master data for materials, vendors, or customers can lead to pricing issues.
  
  Solutions:
  
  Review Pricing Conditions: Check the pricing conditions for the items in question. Ensure that the conditions are correctly defined and that the expected prices are set appropriately.
  Adjust Pricing Procedure: If the pricing procedure is not configured correctly, you may need to adjust it to ensure that it reflects the intended pricing strategy.
  Update Master Data: Ensure that the master data for materials, vendors, and customers is complete and accurate. This includes checking for any missing or incorrect pricing information.
  Check Currency Settings: If currency conversion is involved, verify that the exchange rates are up to date and that the currency settings are correct.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on pricing conditions and procedures.
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like ME23N (Display Purchase Order), ME22N (Change Purchase Order), or VA03 (Display Sales Order) to review the relevant documents and pricing conditions.
  Pricing Condition Records: Use transaction code VK11 to create or change pricing condition records.
  Debugging: If you have access to debugging tools, you can analyze the pricing determination process to identify where the error is occurring.
  SAP Notes: Check for any relevant SAP Notes that may address known issues related to pricing errors.
  
  By following these steps, you should be able to identify the cause of the M8516 error and implement the necessary solutions to resolve it.