How To Fix FX037 - Prog.error: Cross-system co.cde & not in table T001


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FX - Distributed FI Application Messages

  • Message number: 037

  • Message text: Prog.error: Cross-system co.cde & not in table T001

  • Show details Hide details
  • What causes this issue?

    Program error: A cross-system company code &V1& has no local company
    code alias.

    System Response

    Processing is cancelled; entered or changed data is lost.

    How to fix this error?

    This error should not have occurred here. A possible error cause might
    be that a company code carrying the cross-system company code
    identifier &V1& was deleted from the table T001 during the program run.
    Contact your system administrator.
    Procedure for the System Administrator
    Maintain this cross-system company code again. You can proceed by
    carrying out the following steps and then restarting processing:
    Create a cross-system company code &V1& (also report the identifier to
    all SAP installations of the corporate group):
    <DS:TRAN.OB72>Proceed</>
    Allocate the cross-system company code to the local company code:
    <DS:TRAN.OBB5>Proceed</>

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FX037 - Prog.error: Cross-system co.cde & not in table T001 ?

    The SAP error message FX037, which states "Prog.error: Cross-system co.cde & not in table T001," typically occurs in the context of cross-system transactions or when dealing with different company codes in SAP. Here’s a breakdown of the cause, potential solutions, and related information:

    Cause:

    1. Missing Company Code: The error indicates that the company code referenced in the transaction is not found in the T001 table, which contains all the company codes in the SAP system.
    2. Cross-System Configuration: If you are working in a cross-system environment (e.g., using multiple SAP systems), the company code may exist in one system but not in the other.
    3. Data Consistency Issues: There may be inconsistencies in the configuration or data transfer between systems, leading to the company code not being recognized.

    Solution:

    1. Check Company Code in T001:

      • Go to transaction code SE16 or SE16N.
      • Enter the table name T001 and check if the company code in question exists.
      • If it does not exist, you may need to create it or ensure that the correct company code is being used in your transaction.
    2. Verify Cross-System Configuration:

      • Ensure that the company codes are properly configured in all relevant systems.
      • If you are using a central system or a different instance, make sure that the company code is replicated or available in that system.
    3. Data Transfer and Consistency:

      • If you are transferring data between systems (e.g., using ALE/IDocs), ensure that the configuration is correct and that the company code is included in the data transfer.
      • Check for any errors in the data transfer logs that might indicate issues with the company code.
    4. Consult with Basis or Technical Team:

      • If the issue persists, it may be necessary to involve your SAP Basis or technical team to investigate any underlying system issues or configurations that may be causing the error.

    Related Information:

    • T001 Table: This table contains the company code data, including the company code itself, name, and other relevant details.
    • Cross-System Transactions: Understanding how your SAP landscape is set up for cross-system transactions can help in troubleshooting issues related to company codes.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common errors.

    By following these steps, you should be able to identify the cause of the FX037 error and implement a solution to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant