How To Fix MRNB015 - No new price could be determined for purchasing document &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: MRNB - Messages for Revaluation (Retro Active Pricing)

• Message number: 015

• Message text: No new price could be determined for purchasing document &1/&2

What causes this issue?

The system could not determine a new price for purchasing document &V1&
/&V2&.

System Response

No price was maintained in purchasing document &V1&/&V2& or a system
error occurred during price determination.

How to fix this error?

Maintain a price in the purchasing document or inform the system
administrator.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MRNB015 - No new price could be determined for purchasing document &1/&2 ?

  The SAP error message MRNB015 ("No new price could be determined for purchasing document &1/&2") typically occurs during the processing of a purchasing document, such as a purchase order or a contract, when the system is unable to determine a new price for the item being processed. This can happen for several reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Missing or Incorrect Info Records: The system may not find a valid info record for the material and vendor combination, or the info record may not have the necessary pricing conditions.
  
  
  Pricing Conditions: The pricing conditions may not be maintained correctly in the condition records. This includes missing condition types or incorrect validity periods.
  
  
  Material Master Data: The material master data may not be set up correctly, particularly in the purchasing view. This can include missing purchasing group or valuation class.
  
  
  Vendor Master Data: The vendor master data may not be complete or may not have the necessary purchasing information.
  
  
  Price Change: If there has been a recent price change that has not been updated in the system, it may lead to discrepancies.
  
  
  Currency Issues: If there are currency conversion issues or if the currency in the purchasing document does not match the currency in the pricing conditions.
  
  
  Account Assignment: If the account assignment category does not allow for the determination of a price, this error may occur.
  
  
  Solutions:
  
  
  Check Info Records: Verify that the info records for the material and vendor combination exist and are correctly maintained. Ensure that the necessary pricing conditions are present.
  
  
  Review Condition Records: Go to the condition records (transaction code MEK1, MEK2, MEK3) and check if the relevant pricing conditions are maintained for the material and vendor.
  
  
  Validate Material Master: Check the material master data (transaction code MM03) to ensure that the purchasing view is correctly set up, including the purchasing group and valuation class.
  
  
  Examine Vendor Master: Review the vendor master data (transaction code XK03) to ensure that all necessary purchasing information is complete.
  
  
  Update Prices: If there has been a recent price change, ensure that the new prices are updated in the system.
  
  
  Currency Settings: Check the currency settings in the purchasing document and ensure they match the pricing conditions.
  
  
  Account Assignment Review: Ensure that the account assignment category used in the purchasing document allows for price determination.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), MEK1/MEK2/MEK3 (Maintain Condition Records), and MM03 (Display Material Master).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  Documentation: Review SAP documentation and help resources for further insights into pricing procedures and condition records.
  
  By systematically checking these areas, you should be able to identify the cause of the MRNB015 error and implement the appropriate solution.