How To Fix 8N1108 - Posting to A/L account & is not allowed for G/L document type &

SAP Error Message - Details

• Message type: E = Error

• Message class: 8N1 - Messages for Accounting (Greek Localization)

• Message number: 108

• Message text: Posting to A/L account & is not allowed for G/L document type &

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 8N1108 - Posting to A/L account & is not allowed for G/L document type & ?

  The SAP error message 8N1108 indicates that there is an issue with posting to an Asset/Liability (A/L) account that is not allowed for the specified General Ledger (G/L) document type. This error typically arises when the system is configured to restrict certain types of postings based on the document type being used.
  Cause:
  
  Document Type Restrictions: The G/L document type you are using may not be configured to allow postings to the specified A/L account. Each document type in SAP can have specific settings that determine which accounts can be posted to.
  Account Type Configuration: The A/L account may be set up in a way that restricts it from being used with the current document type. This could be due to settings in the account's master data or in the configuration of the document type itself.
  Posting Period Issues: If the posting period is closed or restricted for certain types of transactions, this could also lead to this error.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for the document type in transaction code OBY6 (for document types) or OBD2 (for document type settings).
  Ensure that the document type you are using is allowed to post to the A/L account in question.
  
  
  
  Review Account Master Data:
  
  Check the master data of the A/L account (transaction code FS00) to see if there are any restrictions or settings that prevent it from being used with the current document type.
  Ensure that the account is set up correctly for the type of transactions you are trying to post.
  
  
  
  Posting Period:
  
  Verify that the posting period is open for the type of transaction you are trying to execute. You can check this in transaction code OB52.
  
  
  
  Consult with SAP Basis or Configuration Team:
  
  If you are unsure about the configuration settings, it may be helpful to consult with your SAP Basis or configuration team to ensure that everything is set up correctly.
  
  
  
  Testing:
  
  After making any changes, try to post the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OBY6: Document Type Configuration
  OBD2: Document Type Settings
  FS00: G/L Account Master Data
  OB52: Posting Periods
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  Documentation: Review SAP documentation related to G/L account postings and document types for further understanding of the configuration and restrictions.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.