How To Fix FINS_ACDOC_POST017 - Combination of ledgers assigned to ledger group & not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_POST - FIN UDoc posting: Message from posting

• Message number: 017

• Message text: Combination of ledgers assigned to ledger group & not permitted

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 FINS_ACDOC_POST017 - Combination of ledgers assigned to ledger group & not permitted ?

  The SAP error message FINS_ACDOC_POST017 indicates that there is an issue with the combination of ledgers assigned to a ledger group that is not permitted. This typically occurs during the posting of financial documents when the system detects that the configuration of ledgers does not align with the rules set in the system.
  Cause:
  
  Incorrect Ledger Group Configuration: The ledger group may not be configured correctly to allow the combination of ledgers being used in the transaction.
  Posting Period Issues: The posting period may not be open for the specific ledger or ledger group.
  Inconsistent Ledger Assignments: The ledgers assigned to the company code or the document type may not match the expected configuration for the ledger group.
  Customizing Settings: There may be specific customizing settings in the Financial Accounting (FI) module that restrict the use of certain ledgers together.
  
  Solution:
  
  
  Check Ledger Group Configuration:
  
  Go to the configuration settings in SAP (Transaction Code: SPRO).
  Navigate to Financial Accounting (New) > General Ledger Accounting (New) > Ledger > Define Ledger Groups.
  Ensure that the ledgers you are trying to post to are correctly assigned to the appropriate ledger group.
  
  
  
  Review Posting Periods:
  
  Check if the posting period is open for the ledgers involved. You can do this via Transaction Code: OB52.
  Ensure that the posting period is open for all relevant ledgers.
  
  
  
  Verify Document Type and Company Code Settings:
  
  Ensure that the document type being used is compatible with the ledger group and ledgers.
  Check the company code settings to ensure that the correct ledgers are assigned.
  
  
  
  Consult with Configuration Team:
  
  If you are unsure about the configuration, consult with your SAP FI configuration team to review the settings and ensure they align with your business requirements.
  
  
  
  Check for Custom Code:
  
  If there are any custom developments or enhancements in your SAP system, check if they might be affecting the posting logic.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO (to access configuration settings)
  OB52 (to check and manage posting periods)
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  Documentation: Review SAP documentation related to Financial Accounting and General Ledger settings for more detailed guidance on ledger configurations.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it.