How To Fix /PRA/COMMON035 - Bad Price Year

/PRA/COMMON035 - Overview

• Message type: E = Error

• Message class: /PRA/COMMON -

• Message number: 035

• Message text: Bad Price Year

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 /PRA/COMMON035 - Bad Price Year ?

  The SAP error message /PRA/COMMON035 Bad Price Year typically occurs in the context of SAP's Pricing and Revenue Management (PRM) module, particularly when dealing with pricing conditions or price determination processes. This error indicates that there is an issue with the price year being referenced in the system.
  
  Cause:
  
  Invalid Price Year: The price year specified in the transaction or configuration does not exist in the system. This could be due to a typo or an incorrect year being referenced.
  
  Configuration Issues: The pricing configuration may not be set up correctly, leading to the system not recognizing the specified price year.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that reference pricing information.
  Year Not Open for Pricing: The specified year may not be open for pricing activities, meaning that the system is not allowed to process pricing for that year.
  
  
  Solution:
  
  Check the Price Year: Verify the price year being used