How To Fix /SAPCND/CUSTOMIZING624 - Original of this table is not in the system

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUSTOMIZING -

• Message number: 624

• Message text: Original of this table is not in the system

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/CUSTOMIZING624 - Original of this table is not in the system ?

  The SAP error message /SAPCND/CUSTOMIZING624: Original of this table is not in the system typically occurs in the context of SAP Customizing and is related to the condition tables used in pricing or other customizing scenarios. This error indicates that the system is trying to access a condition table that is not available in the current system or client.
  Cause:
  
  Missing Table: The original condition table that is referenced in the customizing is not present in the system. This could happen if the table was deleted or if the system was not properly configured.
  Transport Issues: If the customizing settings were transported from another system, the transport might not have included the necessary condition tables.
  Client-Specific Settings: The condition table might exist in another client but not in the current client you are working in.
  Incorrect Configuration: There may be a misconfiguration in the customizing settings that references a non-existent table.
  
  Solution:
  
  Check Table Existence: Verify if the condition table exists in the system. You can do this by using transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to check for the specific table.
  Transport the Table: If the table is missing, you may need to transport it from another system where it exists. Ensure that the transport request includes the necessary objects.
  Recreate the Table: If the table was deleted and cannot be transported, you may need to recreate it manually in the system.
  Check Customizing Settings: Review the customizing settings to ensure that they are correctly configured and do not reference any non-existent tables.
  Client-Specific Configuration: If the table exists in another client, consider using transaction SCC1 to copy the customizing settings from that client to the current one.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), and SPRO (SAP Reference IMG) for customizing settings.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to condition tables and customizing to understand the dependencies and configurations better.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or ABAP team for further investigation.