How To Fix GC105 - Reference company & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: GC - Error Messages for Consolidation/Extended General Ledger

• Message number: 105

• Message text: Reference company & does not exist

What causes this issue?

The company you are using as a reference, does not exist.

How to fix this error?

Use an existing company as a reference.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GC105 - Reference company & does not exist ?

  The SAP error message GC105, which states "Reference company & does not exist," typically occurs in the context of financial transactions or reporting when the system is unable to find a reference company that is required for processing. This can happen in various scenarios, such as during the creation of financial documents, intercompany transactions, or when generating reports that involve multiple companies.
  Cause:
  
  Missing Configuration: The reference company may not be defined in the system. This could be due to incorrect configuration or missing entries in the company code settings.
  Incorrect Company Code: The company code specified in the transaction may be incorrect or misspelled.
  Data Inconsistency: There may be inconsistencies in the master data, such as the company code not being properly activated or set up.
  Authorization Issues: The user may not have the necessary authorizations to access the reference company.
  
  Solution:
  
  
  Check Company Code Configuration:
  
  Go to the transaction code OBY6 (or SPRO for configuration) and verify that the reference company code exists and is properly configured.
  Ensure that the company code is active and has all necessary settings (like currency, fiscal year variant, etc.) configured.
  
  
  
  Verify Input Data:
  
  Double-check the company code entered in the transaction. Ensure that it matches the existing company codes in the system.
  Look for any typographical errors or discrepancies in the company code.
  
  
  
  Review Master Data:
  
  Check the master data for the company code in question. Ensure that all necessary data is complete and consistent.
  Use transaction codes like OB52 to check the fiscal year settings and ensure that the company code is included.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the reference company. This can be checked with the security team or by reviewing the user roles and authorizations.
  
  
  
  Consult Documentation:
  
  If the issue persists, consult SAP documentation or support for further troubleshooting steps specific to your version and configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, SPRO, OB52, and others that may help in configuration and troubleshooting.
  SAP Notes: Check for any SAP Notes related to error GC105 for specific patches or updates that may address known issues.
  Support: If the problem cannot be resolved internally, consider reaching out to SAP support for assistance.
  
  By following these steps, you should be able to identify and resolve the issue related to the GC105 error message in SAP.