How To Fix /ACCGO/CAS_MSG356 - Cannot determine G/L account for account key

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_MSG -

• Message number: 356

• Message text: Cannot determine G/L account for account key

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_MSG356 - Cannot determine G/L account for account key ?

  The SAP error message /ACCGO/CAS_MSG356 Cannot determine G/L account for account key typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with account assignments and cost elements. This error indicates that the system is unable to find a General Ledger (G/L) account associated with a specific account key.
  Causes:
  
  Missing Configuration: The account key may not be properly configured in the system. This can happen if the account key is not linked to a G/L account in the configuration settings.
  Incorrect Account Key: The account key being used may be incorrect or not valid for the transaction being processed.
  Missing G/L Account: The G/L account that should be associated with the account key may not exist or may have been deleted.
  Authorization Issues: There may be authorization issues preventing the system from accessing the necessary configuration or G/L accounts.
  Data Inconsistencies: There may be inconsistencies in the master data or configuration settings that lead to this error.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the configuration settings for the account key in the SAP system. This can typically be found in the SPRO transaction under Controlling -> Cost Element Accounting -> Master Data -> Cost Elements -> Define Cost Elements.
  Ensure that the account key is correctly linked to a valid G/L account.
  
  
  
  Verify Account Key:
  
  Check the account key being used in the transaction. Make sure it is the correct one and is valid for the type of transaction you are processing.
  
  
  
  Create or Update G/L Account:
  
  If the G/L account does not exist, create it in the G/L account master data. Use transaction code FS00 to create or modify G/L accounts.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the configuration and G/L accounts. This may require coordination with your SAP security team.
  
  
  
  Review Master Data:
  
  Check for any inconsistencies in the master data related to cost elements and account assignments. Ensure that all necessary data is correctly maintained.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 (G/L Account Master), OBY6 (G/L Account Determination), and SPRO (SAP Reference IMG).
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal for any patches or updates that may address the issue.
  Testing: After making changes, perform tests to ensure that the error no longer occurs and that the system behaves as expected.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.