How To Fix J#055 - The purchase price in transaction currency was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: J# -

• Message number: 055

• Message text: The purchase price in transaction currency was not found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message J#055 - The purchase price in transaction currency was not found ?

  The SAP error message J#055, which states "The purchase price in transaction currency was not found," typically occurs in the context of purchasing and procurement processes. This error indicates that the system is unable to find a valid purchase price for a material or service in the specified transaction currency.
  Causes:
  
  Missing Price in Master Data: The most common cause is that the material master or info record does not have a price defined in the transaction currency.
  Currency Mismatch: The currency used in the transaction may not match the currency in which the price is defined.
  Price Conditions: The pricing conditions may not be set up correctly in the pricing procedure.
  Invalid or Incomplete Info Records: The info record for the vendor-material combination may be incomplete or not maintained properly.
  Purchasing Organization Issues: The purchasing organization may not have the necessary data or settings to retrieve the price.
  
  Solutions:
  
  
  Check Material Master Data:
  
  Go to the material master record (MM03) and check if the purchasing view has the price maintained in the correct currency.
  Ensure that the price is maintained for the relevant purchasing organization.
  
  
  
  Review Info Records:
  
  Check the info record (ME13) for the vendor and material combination to ensure that a valid price is maintained.
  If necessary, create or update the info record with the correct price.
  
  
  
  Verify Pricing Conditions:
  
  Check the pricing conditions in the pricing procedure (transaction code: MEK1) to ensure that the conditions are set up correctly for the transaction.
  Ensure that the condition types are active and correctly configured.
  
  
  
  Currency Settings:
  
  Verify that the currency settings in the purchasing document match the currency in which the price is maintained.
  If there is a currency conversion involved, ensure that the exchange rates are maintained correctly.
  
  
  
  Consult with SAP Support:
  
  If the issue persists after checking the above points, consider consulting with your SAP support team or refer to SAP Notes for any known issues related to this error.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  MM03: Display Material Master
  ME13: Display Info Record
  MEK1: Maintain Pricing Conditions
  
  
  SAP Documentation: Refer to SAP Help Portal for detailed documentation on purchasing and pricing procedures.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  
  By following these steps, you should be able to identify and resolve the cause of the J#055 error in SAP.