How To Fix >0357 - G/L account is missing for company code &1 tax flag &2 transaction &3

>0357 - Overview

• Message type: E = Error

• Message class: >0 - General Basis texts

• Message number: 357

• Message text: G/L account is missing for company code &1 tax flag &2 transaction &3

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 >0357 - G/L account is missing for company code &1 tax flag &2 transaction &3 ?

  The SAP error message 0357 indicates that a General Ledger (G/L) account is missing for a specific company code, tax flag, and transaction type. This error typically arises during financial transactions when the system cannot find the appropriate G/L account to post the transaction due to missing configuration.
  
  Cause:
  
  Missing G/L Account Configuration: The G/L account for the specified company code and tax flag has not been defined in the system.
  Incorrect Tax Configuration: The tax settings for the transaction may not be properly configured, leading to the system being unable to determine the correct G/L account.
  Transaction Type Issues: The transaction type being used may not have a corresponding G/L account set up in the system.
  
  
  Solution:
  
  
  Check G/L Account Configuration:
  
  Go to the transaction code OBY6 (or FS00) to check if the G/L account exists for the specified company code.
  If it does not exist, create the G/L account using the appropriate account type and settings.
  
  
  
  Review