/GSINS/INSH_MSG086 - Cannot determine GL account for post.area/chart.accts/maintr/subt &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /GSINS/INSH_MSG -

• Message number: 086

• Message text: Cannot determine GL account for post.area/chart.accts/maintr/subt &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.

AnswerBot

• What is the cause and solution for SAP error message /GSINS/INSH_MSG086 - Cannot determine GL account for post.area/chart.accts/maintr/subt &1 ?

  The SAP error message /GSINS/INSH_MSG086 indicates that the system is unable to determine the General Ledger (GL) account for a specific posting area, chart of accounts, maintenance type, or subtype. This error typically arises in the context of asset accounting or inventory management when the system is trying to post a transaction but cannot find the appropriate GL account mapping.
  Causes:
  
  Missing Configuration: The GL account may not be configured for the specific combination of posting area, chart of accounts, and maintenance type/subtype.
  Incorrect Settings: There may be incorrect settings in the configuration of the asset accounting or inventory management module.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that prevent the system from determining the correct GL account.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the required configuration or master data.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the configuration settings for the relevant module (e.g., Asset Accounting or Inventory Management).
  Ensure that the GL accounts are correctly defined for the relevant posting area and chart of accounts.
  Use transaction codes like OBY6 (for chart of accounts) or OAOA (for asset accounting) to review the settings.
  
  
  
  Review Master Data:
  
  Check the master data for the asset or inventory item involved in the transaction.
  Ensure that all necessary fields are filled out correctly and that the relevant GL accounts are assigned.
  
  
  
  Transaction Analysis:
  
  Analyze the transaction that triggered the error. Look for any missing or incorrect data that could lead to the inability to determine the GL account.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on the specific configuration settings required for your scenario.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to access the relevant configuration and master data.
  
  
  
  Testing:
  
  After making changes, perform a test transaction to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, OAOA, OABT, and others that pertain to GL account configuration and asset management.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.