How To Fix PRC_PRI135 - Call of getConditionType() failed

SAP Error Message - Details

• Message type: E = Error

• Message class: PRC_PRI - Messages for Pricing Engine

• Message number: 135

• Message text: Call of getConditionType() 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_PRI135 - Call of getConditionType() failed ?

  The SAP error message PRC_PRI135, which states "Call of getConditionType() failed," typically occurs in the context of pricing procedures or condition records in SAP. This error can arise due to various reasons, including configuration issues, missing condition types, or problems with the pricing procedure.
  Causes:
  
  Missing Condition Type: The condition type that is being referenced in the pricing procedure may not be defined or may not exist in the system.
  Incorrect Configuration: The pricing procedure may not be correctly configured, leading to issues when trying to retrieve condition types.
  Authorization Issues: The user may not have the necessary authorizations to access certain condition types or pricing procedures.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that are causing the system to fail when trying to retrieve the condition type.
  Custom Code Issues: If there are custom enhancements or modifications in the pricing logic, they may be causing the error.
  
  Solutions:
  
  Check Condition Types: Verify that the condition type referenced in the pricing procedure exists and is correctly configured. You can do this by navigating to the condition type configuration in the SAP system.
  Review Pricing Procedure: Ensure that the pricing procedure is correctly set up and that all necessary condition types are included. You can check this in the configuration settings for pricing procedures.
  Authorization Check: Ensure that the user encountering the error has the necessary authorizations to access the relevant condition types and pricing procedures.
  Data Validation: Check the master data (e.g., customer master, material master) and transaction data (e.g., sales orders, purchase orders) for any inconsistencies that might be causing the issue.
  Debugging: If the issue persists, consider debugging the code to identify where the failure occurs. This may require the assistance of a developer or SAP support.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition records.
  Configuration Path: The configuration for pricing procedures can typically be found under the following path in the SAP menu: SPRO > IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights or similar experiences from other users.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.