How To Fix /SAPCND/CUST_T013 - End of exit &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUST_T -

• Message number: 013

• Message text: End of exit &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 /SAPCND/CUST_T013 - End of exit &1 ?

  The SAP error message /SAPCND/CUST_T013 End of exit &1 typically relates to issues in the condition management or pricing procedures within SAP. This error can occur during the execution of a program or transaction that involves condition records, such as pricing, discounts, or other condition types.
  Cause:
  
  Incomplete Configuration: The error may arise if the condition table or the related configuration is not set up correctly in the system.
  Missing Data: If the system is trying to access a condition record that does not exist or is incomplete, it can trigger this error.
  Custom Code Issues: If there are custom enhancements or modifications in the pricing logic, they may not be handling certain conditions properly, leading to this error.
  Transport Issues: If the transport of configuration or custom code has not been done correctly, it may lead to inconsistencies in the system.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the condition tables and ensure that they are set up correctly. This includes checking the access sequences and condition types.
  Validate Condition Records: Ensure that the necessary condition records exist and are complete. You can do this by navigating to the relevant transaction (e.g., VK11 for creating condition records) and checking the records.
  Debugging: If the error is related to custom code, use the debugger to trace the execution and identify where the error is occurring. Look for any logic that may not be handling certain conditions correctly.
  Review Enhancements: If there are any user exits or BAdIs implemented, review them to ensure they are not causing the issue.
  Check Transport Requests: If the issue arose after a transport, verify that all necessary objects were included in the transport request and that they were imported correctly.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that may address this specific error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  SAP Documentation: Review SAP documentation related to condition management and pricing procedures for a deeper understanding of how these components interact.
  Community Forums: Engage with SAP community forums or support channels for additional insights or similar experiences from other users.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.