How To Fix GC613 - Entries for company & not maintained

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 613

• Message text: Entries for company & not maintained

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 GC613 - Entries for company & not maintained ?

  The SAP error message GC613 ("Entries for company & not maintained") typically occurs when there is an attempt to perform a transaction or access data for a company code that has not been properly configured or does not have the necessary entries in the relevant tables.
  Cause:
  
  Missing Configuration: The company code may not have been set up correctly in the system. This could include missing entries in tables related to financial accounting, controlling, or other relevant modules.
  Incorrect Company Code: The company code being referenced in the transaction may be incorrect or does not exist in the system.
  Data Migration Issues: If data was migrated from another system, there may have been issues that resulted in missing entries for the company code.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the data for the specified company code.
  
  Solution:
  
  
  Check Company Code Configuration:
  
  Go to the transaction code OBY6 (or SPRO -> Financial Accounting -> General Settings -> Company Code -> Define Company Code) and verify that the company code exists and is properly configured.
  Ensure that all necessary settings (like currency, fiscal year variant, etc.) are maintained.
  
  
  
  Verify Master Data:
  
  Check if the relevant master data (like G/L accounts, cost centers, etc.) is maintained for the company code in question.
  Use transaction codes like FS00 for G/L accounts or KS01 for cost centers to verify their existence.
  
  
  
  Check Transaction Data:
  
  If the error occurs during a specific transaction, ensure that the data being entered is correct and corresponds to the existing company codes.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the company code. This can be checked in the user roles and profiles.
  
  
  
  Consult with Basis Team:
  
  If the issue persists, it may be beneficial to consult with the SAP Basis team to check for any underlying system issues or inconsistencies.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, FS00, KS01, and SPRO for configuration and verification.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for financial accounting and controlling to ensure that all necessary configurations are in place.
  
  By following these steps, you should be able to identify and resolve the issue related to the GC613 error message in SAP.