How To Fix RSCRM035 - Condition &1 &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: RSCRM - RSCRM: Messages

• Message number: 035

• Message text: Condition &1 &2 does not exist

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 RSCRM035 - Condition &1 &2 does not exist ?

  The SAP error message RSCRM035, which states "Condition &1 &2 does not exist," typically occurs in the context of SAP's CRM (Customer Relationship Management) or when dealing with pricing conditions in the SAP system. This error indicates that the system is unable to find a specific condition record that is required for processing a transaction.
  Cause:
  
  
  Missing Condition Record: The most common cause of this error is that the condition record specified by the keys (represented by &1 and &2) does not exist in the system. This could be due to:
  
  The condition type not being maintained.
  The specific condition record not being created for the relevant combination of keys (e.g., pricing, discounts, etc.).
  
  
  
  Incorrect Configuration: There may be issues with the configuration of the pricing procedure or condition types that lead to the system not being able to find the required condition.
  
  
  Data Inconsistency: Sometimes, data inconsistencies or issues during data migration can lead to missing condition records.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Use transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the condition record exists for the specified condition type and keys.
  If it does not exist, create the necessary condition record.
  
  
  
  Review Configuration:
  
  Check the configuration of the pricing procedure in transaction V/08 to ensure that the condition types are correctly set up and assigned.
  Ensure that the condition types are included in the relevant pricing procedure.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the program or transaction that triggered the error to understand why it is looking for that specific condition record.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for specific details about the condition type and its requirements.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to view or create condition records.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11, VK12, VK13 (for managing condition records)
  V/08 (for pricing procedure configuration)
  
  
  
  Condition Types: Familiarize yourself with the specific condition types relevant to your business processes, as they can vary widely depending on the industry and configuration.
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance related to this error message.
  
  
  By following these steps, you should be able to identify the cause of the RSCRM035 error and implement a solution to resolve it.