How To Fix /SRMERP/OL_COMMON012 - G/L account & has not been created in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMERP/OL_COMMON -

• Message number: 012

• Message text: G/L account & has not been created in company code &

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 /SRMERP/OL_COMMON012 - G/L account & has not been created in company code & ?

  The SAP error message /SRMERP/OL_COMMON012 indicates that a General Ledger (G/L) account has not been created in the specified company code. This error typically arises when you attempt to post a transaction that involves a G/L account that is not set up for the company code you are working with.
  Cause:
  
  Missing G/L Account: The G/L account you are trying to use has not been created in the specified company code.
  Incorrect Company Code: The transaction may be referencing the wrong company code.
  Account Group Restrictions: The account group associated with the G/L account may have restrictions that prevent the account from being used in the specified company code.
  Data Migration Issues: If data was migrated from another system, there may have been issues in creating the necessary G/L accounts in the target company code.
  
  Solution:
  
  
  Create the G/L Account:
  
  Navigate to the transaction code FS00 (G/L Account Master Record).
  Enter the required details, including the G/L account number and the company code.
  Ensure that the account is created with the correct settings (e.g., account type, currency, etc.).
  
  
  
  Check Company Code:
  
  Verify that you are using the correct company code in your transaction. If you are working with multiple company codes, ensure that the G/L account exists in the intended company code.
  
  
  
  Review Account Group Settings:
  
  Check the account group settings to ensure that the G/L account can be used in the specified company code. You can do this by navigating to OBD4 (Define Account Groups) and reviewing the settings.
  
  
  
  Data Migration Review:
  
  If this issue arose after a data migration, review the migration process to ensure that all necessary G/L accounts were created in the target company code.
  
  
  
  Consult with SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  FS00: Create/Change G/L Account Master Record
  OBD4: Define Account Groups
  OBY6: Define Company Code
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on creating G/L accounts and managing company codes.
  Authorization: Ensure that you have the necessary authorizations to create or modify G/L accounts in the system.
  
  By following these steps, you should be able to resolve the error and successfully post your transactions.