How To Fix /SAPCND/CUST_T020 - Exit &1 is not executed in case RUNS_IN_SOURCE = &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUST_T -

• Message number: 020

• Message text: Exit &1 is not executed in case RUNS_IN_SOURCE = &2

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_T020 - Exit &1 is not executed in case RUNS_IN_SOURCE = &2 ?

  The SAP error message /SAPCND/CUST_T020 Exit &1 is not executed in case RUNS_IN_SOURCE = &2 typically relates to the condition management in SAP, particularly when dealing with condition records and their processing in the pricing procedure.
  Cause:
  This error usually occurs when there is a mismatch or an issue with the configuration of condition types or the exit routines that are supposed to be executed during the pricing process. The specific message indicates that a certain exit (a user-defined routine) is not being executed because the condition is not set to run in the source system as expected.
  Possible Causes:
  
  Configuration Issues: The condition type may not be properly configured to execute the exit.
  Exit Not Implemented: The exit routine may not be implemented or activated in the system.
  Incorrect Settings: The settings for the condition type or the pricing procedure may not align with the expected behavior.
  Transport Issues: If the configuration was transported from another system, there may be inconsistencies or missing elements.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the transaction code V/06 (for condition types) and verify the configuration of the condition type in question.
  Ensure that the exit is correctly assigned to the condition type.
  
  
  
  Review the Exit Implementation:
  
  Check if the exit routine (function module) is implemented in the system. You can do this by going to transaction SE80 or SE37 and searching for the exit function module.
  If it is not implemented, you may need to create or activate it.
  
  
  
  Check Pricing Procedure:
  
  Review the pricing procedure assigned to the sales document type or the relevant transaction. Ensure that the condition type is included in the pricing procedure and that it is set to execute under the correct circumstances.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing procedure to see why the exit is not being called. You can set breakpoints in the relevant function modules to trace the execution flow.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type and exit to ensure that you are following best practices.
  
  
  
  Transport Consistency:
  
  If the issue arose after a transport, check for any inconsistencies in the transport logs and ensure that all necessary objects were transported correctly.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific condition type or exit.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Documentation: Refer to the SAP Help Portal for detailed documentation on condition management and pricing procedures.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message. If the problem persists, consider reaching out to SAP support for further assistance.