How To Fix /ACCGO/CAS_STL_LOGIC043 - No GL account maintained in Customizing for accounting type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_STL_LOGIC -

• Message number: 043

• Message text: No GL account maintained in Customizing for accounting type &1

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 /ACCGO/CAS_STL_LOGIC043 - No GL account maintained in Customizing for accounting type &1 ?

  The SAP error message /ACCGO/CAS_STL_LOGIC043 No GL account maintained in Customizing for accounting type &1 typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with the integration of CO with Financial Accounting (FI). This error indicates that there is no General Ledger (GL) account assigned for a specific accounting type in the system configuration.
  Cause:
  The error is caused by the absence of a GL account assignment for the specified accounting type in the Customizing settings. This can happen due to:
  
  Missing Configuration: The required GL account has not been defined in the Customizing settings for the specific accounting type.
  Incorrect Accounting Type: The accounting type being referenced may not be correctly set up or may not exist in the system.
  Transport Issues: If the configuration was recently transported from another system, the GL account assignment may not have been included in the transport.
  
  Solution:
  To resolve this error, you need to ensure that the appropriate GL account is maintained for the specified accounting type. Here are the steps to do this:
  
  
  Access Customizing:
  
  Go to the SAP Easy Access screen and enter transaction code SPRO.
  Navigate to the following path: 
  Controlling -> General Controlling -> Master Data -> Cost Element Accounting -> Define Cost Elements
  
  
  
  
  Check Accounting Type:
  
  Identify the accounting type mentioned in the error message (represented by &1).
  Ensure that the accounting type is correctly defined in the system.
  
  
  
  Maintain GL Account:
  
  For the identified accounting type, check if a GL account is assigned.
  If not, create or assign a GL account to the accounting type. This may involve:
  
  Creating a new cost element if it does not exist.
  Assigning an existing GL account to the cost element.
  
  
  
  
  
  Save Changes:
  
  After making the necessary changes, save your configuration.
  
  
  
  Test the Changes:
  
  Re-run the transaction or process that triggered the error to verify that the issue has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KA01 (Create Primary Cost Element), KA02 (Change Primary Cost Element), and KA03 (Display Primary Cost Element).
  Documentation: Refer to SAP Help documentation for detailed guidance on configuring cost elements and GL accounts.
  Authorization: Ensure you have the necessary authorizations to make changes in the Customizing settings.
  Transport Requests: If changes are made in a development environment, ensure that they are properly transported to the quality and production environments.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Functional team for further investigation.