How To Fix 3G357 - Tax indicator could not be read from G/L account

SAP Error Message - Details

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 357

• Message text: Tax indicator could not be read from G/L account

What causes this issue?

The tax indicator for the G/L account could not be determined for one
of the following reasons:
No destination could be determined from the ALE distribution model for
the GeneralLedgerAccount.GetDetail method.
A system or communication error occurred when executing the function
'BAPI_GL_ACC_GETDETAIL' in the target system.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 3G357 - Tax indicator could not be read from G/L account ?

  The SAP error message 3G357, which states "Tax indicator could not be read from G/L account," typically occurs when the system is unable to retrieve the tax indicator associated with a General Ledger (G/L) account during a transaction that involves tax calculations. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Tax Indicator: The G/L account may not have a tax indicator assigned to it in the master data.
  Incorrect G/L Account Configuration: The G/L account may not be properly configured for tax purposes in the system.
  Inactive G/L Account: The G/L account might be inactive or not available for the current fiscal year.
  Authorization Issues: The user may not have the necessary authorizations to access the G/L account or its tax information.
  Data Consistency Issues: There may be inconsistencies in the data, such as missing or incorrect entries in the tax configuration tables.
  
  Solutions:
  
  
  Check G/L Account Master Data:
  
  Go to the G/L account master data (transaction code FS00) and verify that the tax indicator is correctly assigned to the account.
  Ensure that the account is active and available for the relevant fiscal year.
  
  
  
  Review Tax Configuration:
  
  Check the tax configuration settings in the system (transaction code OB40 for tax codes and OBYZ for tax determination).
  Ensure that the tax codes and indicators are correctly set up and linked to the G/L accounts.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to access the G/L account and perform the transaction.
  Check the user roles and profiles to ensure they include the required permissions.
  
  
  
  Data Consistency Check:
  
  Run data consistency checks to identify any discrepancies in the tax configuration or G/L account settings.
  Use transaction codes like SE16 or SE11 to check relevant tables for inconsistencies.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on tax configuration and G/L account settings.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FS00: G/L Account Master Data
  OB40: Maintain Tax Codes
  OBYZ: Maintain Tax Determination
  SE16/SE11: Data Browser/Table Display
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to this error message.
  
  
  By following these steps, you should be able to identify and resolve the issue related to the SAP error message 3G357.