How To Fix PRC_PRI171 - Call of getCurrencyValue() or getPhysicalValue() failed.

SAP Error Message - Details

• Message type: E = Error

• Message class: PRC_PRI - Messages for Pricing Engine

• Message number: 171

• Message text: Call of getCurrencyValue() or getPhysicalValue() failed.

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 PRC_PRI171 - Call of getCurrencyValue() or getPhysicalValue() failed. ?

  The SAP error message PRC_PRI171, which states "Call of getCurrencyValue() or getPhysicalValue() failed," typically occurs in the context of SAP's Project System (PS) or Controlling (CO) modules, particularly when dealing with currency conversions or value calculations. This error can arise due to various reasons, including configuration issues, missing data, or inconsistencies in the master data.
  Causes:
  
  Missing or Incorrect Currency Configuration: The currency settings for the project or cost center may not be properly configured.
  Missing Master Data: Required master data (like cost elements, internal orders, or projects) may be missing or incomplete.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the system from retrieving the necessary values.
  Authorization Issues: The user may not have the necessary authorizations to access the required data.
  System Bugs or Limitations: There may be bugs in the SAP version being used or limitations in the implementation.
  
  Solutions:
  
  
  Check Currency Configuration:
  
  Ensure that the currency settings for the project or cost center are correctly defined in the system.
  Verify that the currency types are correctly assigned in the configuration.
  
  
  
  Review Master Data:
  
  Check if all necessary master data is created and correctly maintained.
  Ensure that cost elements, internal orders, and projects are active and correctly configured.
  
  
  
  Data Consistency Check:
  
  Run consistency checks on the relevant data to identify any discrepancies.
  Use transaction codes like CKM3 (for cost estimates) or COSS (for cost element reports) to analyze data.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the required data.
  Check the user roles and profiles to ensure they include the necessary permissions.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the code where the error occurs to identify the root cause.
  Look for any custom code or enhancements that might be affecting the standard functionality.
  
  
  
  SAP Notes and Support:
  
  Check the SAP Support Portal for any relevant SAP Notes that address this specific error.
  If the issue persists, consider reaching out to SAP support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJI3 (Project Actual Line Items), and KSB1 (Cost Centers: Actual Line Items) to analyze project and cost data.
  Documentation: Review SAP documentation related to currency management and project costing for best practices and configuration guidelines.
  Community Forums: Engage with SAP community forums or user groups to see if others have encountered and resolved similar issues.
  
  By following these steps, you should be able to diagnose and resolve the PRC_PRI171 error in your SAP environment.