How To Fix PRC_PRI172 - Creation and copying of a new PricingCondition failed: &1

SAP Error Message - Details

• Message type: E = Error

• Message class: PRC_PRI - Messages for Pricing Engine

• Message number: 172

• Message text: Creation and copying of a new PricingCondition failed: &1

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_PRI172 - Creation and copying of a new PricingCondition failed: &1 ?

  The SAP error message PRC_PRI172 indicates that there was a failure in the creation or copying of a new pricing condition. This error can occur in various scenarios, such as when trying to create or modify pricing conditions in the SAP system, particularly in the context of pricing procedures.
  Causes:
  
  Missing Required Fields: The error may occur if mandatory fields for the pricing condition are not filled in correctly or are left blank.
  Incorrect Condition Type: The condition type being used may not be valid or may not be set up correctly in the system.
  Authorization Issues: The user may not have the necessary authorizations to create or modify pricing conditions.
  Data Inconsistencies: There may be inconsistencies in the data being used, such as invalid master data or configuration settings.
  Custom Code or Enhancements: If there are custom developments or enhancements in the pricing logic, they may be causing the error.
  
  Solutions:
  
  Check Required Fields: Ensure that all mandatory fields for the pricing condition are filled out correctly. Review the configuration for the condition type to identify required fields.
  Validate Condition Type: Verify that the condition type you are trying to use is correctly configured in the system. Check the settings in the condition type configuration (transaction code: V/06).
  Review Authorizations: Ensure that the user has the necessary authorizations to create or modify pricing conditions. This can be checked with the security team or by reviewing the user's roles and authorizations.
  Data Consistency Check: Review the master data and configuration settings related to pricing. Ensure that there are no inconsistencies or missing data that could lead to the error.
  Debugging: If the issue persists, consider debugging the process to identify the exact point of failure. This may require technical expertise in ABAP or access to a developer.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to manage pricing conditions.
  Pricing Procedure: Review the pricing procedure assigned to the relevant sales document type to ensure it is set up correctly.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.