How To Fix /SAPCND/CUSTOMIZING752 - Caller &1 &2 is not registered in table /SAPCND/T681Z

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUSTOMIZING -

• Message number: 752

• Message text: Caller &1 &2 is not registered in table /SAPCND/T681Z

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/CUSTOMIZING752 - Caller &1 &2 is not registered in table /SAPCND/T681Z ?

  The SAP error message /SAPCND/CUSTOMIZING752 indicates that a caller (which could be a program, function module, or transaction) is not registered in the customizing table /SAPCND/T681Z. This table is used in the context of condition management, particularly for condition-based pricing and other related functionalities.
  Cause:
  The error typically occurs due to one of the following reasons:
  
  Missing Registration: The caller (identified by the parameters &1 and &2) has not been registered in the /SAPCND/T681Z table. This could happen if a new program or function module was created but not properly registered.
  Incorrect Configuration: There may be a configuration issue where the caller is expected to be registered but is not due to a misconfiguration or oversight.
  Transport Issues: If the system has recently undergone a transport of changes, the registration might not have been included or properly activated in the target system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Registration:
  
  Go to transaction SE11 (Data Dictionary) and view the table /SAPCND/T681Z.
  Check if the caller (with the identifiers provided in the error message) is listed in the table. If not, you will need to register it.
  
  
  
  Register the Caller:
  
  If the caller is missing, you can register it by using transaction code SPRO to navigate to the relevant customizing settings for condition management.
  Look for the section related to condition types or pricing procedures and ensure that the caller is properly registered.
  
  
  
  Review Configuration:
  
  Ensure that all necessary configurations related to condition management are correctly set up. This includes checking condition types, access sequences, and pricing procedures.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, verify that all necessary objects were included in the transport request and that they have been properly imported into the target system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to condition management for any specific requirements or additional steps that may be necessary for your particular scenario.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is a production environment.
  
  
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SPRO (Customizing), SE80 (Object Navigator).
  Tables: /SAPCND/T681Z (Condition Management Customizing).
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.