How To Fix PRS122 - Repricing not possible (due to non changeable values / quantities)

SAP Error Message - Details

• Message type: E = Error

• Message class: PRS - Message class for PROF_SERV packages.

• Message number: 122

• Message text: Repricing not possible (due to non changeable values / quantities)

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 PRS122 - Repricing not possible (due to non changeable values / quantities) ?

  The SAP error message PRS122, which states "Repricing not possible (due to non-changeable values / quantities)," typically occurs in the context of pricing and conditions in SAP, particularly when dealing with purchasing documents, sales orders, or other transactional data where pricing is involved.
  Cause:
  The error is generally caused by one or more of the following reasons:
  
  
  Non-Changeable Values: The pricing conditions or values in the document are set to be non-changeable. This can happen if the document is in a status that does not allow changes, such as being completed or already processed.
  
  
  Locked Document: The document may be locked for changes due to various reasons, such as being in a workflow, being posted, or being part of a closed period.
  
  
  Incorrect Configuration: The pricing procedure or condition records may not be configured correctly, leading to issues when trying to reprice.
  
  
  Manual Changes: If manual changes were made to the pricing conditions that conflict with the system's ability to reprice, this could trigger the error.
  
  
  Dependencies on Other Documents: If the document is dependent on other documents (like a purchase order linked to a contract), changes may not be allowed.
  
  
  Solution:
  To resolve the PRS122 error, you can take the following steps:
  
  
  Check Document Status: Verify the status of the document. If it is completed or locked, you may need to unlock it or change its status before repricing.
  
  
  Review Pricing Conditions: Check the pricing conditions and ensure that they are set to allow changes. You may need to adjust the configuration in the pricing procedure.
  
  
  Consult Configuration: If you have access to the configuration settings, review the pricing procedure and condition records to ensure they are set up correctly.
  
  
  Use Transaction Codes: Use transaction codes like ME22N (for purchase orders) or VA02 (for sales orders) to check the document and its pricing conditions.
  
  
  Check for Dependencies: Ensure that there are no dependencies on other documents that might prevent repricing.
  
  
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting the SAP community for further assistance.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation on pricing procedures and condition records for a better understanding of how they work.
  User Forums: Engage with SAP user forums or communities for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the PRS122 error and implement a solution to resolve it.