How To Fix 64723 - Data inconsistent; status &1 company code &2 no longer in table TZC37

SAP Error Message - Details

• Message type: E = Error

• Message class: 64 - Treasury Management: Securities

• Message number: 723

• Message text: Data inconsistent; status &1 company code &2 no longer in table TZC37

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 64723 - Data inconsistent; status &1 company code &2 no longer in table TZC37 ?

  The SAP error message 64723 indicates that there is an inconsistency in the data related to the company code in the system. Specifically, it suggests that the status of a company code is no longer found in the table TZC37, which is used to store the status of company codes in the SAP system.
  Cause:
  
  Data Deletion or Modification: The company code might have been deleted or modified in a way that it no longer has a corresponding entry in the TZC37 table.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production), there might have been issues during the transport that led to inconsistencies.
  Custom Development: Custom programs or modifications might have inadvertently altered the data integrity.
  Database Issues: Corruption or issues in the database could lead to missing entries.
  
  Solution:
  
  Check Company Code Configuration: Verify the configuration of the company code in the system. Ensure that it exists and is correctly set up.
  Review Table TZC37: Use transaction SE11 or SE16 to check the contents of the TZC37 table. Look for the specific company code and its status.
  Recreate Missing Entries: If the company code is missing from TZC37, you may need to recreate the entry. This can often be done through the configuration transaction (e.g., OX15 for company code).
  Transport Request Review: If the issue arose after a transport, review the transport logs to identify any errors or warnings that occurred during the transport process.
  Database Consistency Check: Run consistency checks on the database to identify and rectify any inconsistencies.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: 
  
  SE11: Data Dictionary
  SE16: Data Browser
  OX15: Create/Change Company Code
  
  
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, especially if it involves complex data integrity issues.
  Documentation: Review SAP documentation related to company code configuration and the TZC37 table for more detailed information.
  
  Always ensure to back up your data before making any changes to the configuration or database to prevent data loss.