How To Fix /SAPCND/TRANSPORT060 - Condition record for VARNUMH=&2 and client=&1 in /SAPCND/CONDRECS

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/TRANSPORT -

• Message number: 060

• Message text: Condition record for VARNUMH=&2 and client=&1 in /SAPCND/CONDRECS

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 /SAPCND/TRANSPORT060 - Condition record for VARNUMH=&2 and client=&1 in /SAPCND/CONDRECS ?

  The SAP error message /SAPCND/TRANSPORT060 typically indicates an issue related to the transport of condition records in the SAP system. This error occurs when there is a problem with the condition record for a specific variable number (VARNUMH) and client.
  Cause:
  
  Missing Condition Record: The condition record for the specified variable number and client may not exist in the system.
  Transport Issues: There may be issues with the transport request that is supposed to carry the condition records from one environment to another (e.g., from development to production).
  Authorization Issues: The user may not have the necessary authorizations to access or transport the condition records.
  Data Inconsistency: There could be inconsistencies in the data related to the condition records, possibly due to manual changes or failed transports.
  
  Solution:
  
  
  Check Existence of Condition Record: Verify if the condition record for the specified VARNUMH and client exists in the system. You can do this by navigating to the relevant transaction (e.g., VK13 for pricing conditions) and checking if the record is present.
  
  
  Transport Request Review: If the condition record is missing, check the transport request to ensure that it includes the necessary condition records. You may need to re-transport the records if they were not included.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to view and transport condition records. You may need to consult with your SAP security team to verify this.
  
  
  Data Consistency Check: Run consistency checks on the condition records to identify any inconsistencies. You can use transaction codes like SE11 to check the database table /SAPCND/CONDRECS for any anomalies.
  
  
  Recreate Condition Record: If the condition record is indeed missing, you may need to recreate it manually in the system.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK13 (Display Condition), VK12 (Change Condition), and SE10 (Transport Organizer).
  SAP Documentation: Review SAP documentation related to condition records and transport management for more detailed guidance.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.