How To Fix FINS_ACDOC_CUST102 - Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 102

• Message text: Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2

What causes this issue?

In the customizing of the real-time integration of CO-FI the ledger
group &V1& is used.

System Response

The ledger group &V1& doesn't contain leading ledger &V2&.
This means that the leading ledger can't act as ledger for CO data for
all company codes.
Background:
In SAP S/4HANA Finance FI and CO share the same persistence for storing
postings: In other words, CO has to store its data in a G/L ledger. This
G/L ledger must be the leading ledger.
The customizing migration program evaluates the customizing of the
real-time integration of CO-FI in order to check whether the leading
ledger contains all CO postings: That is, primary postings from FI and
secondary postings from CO (such as repostings and allocations between
cost centers).
<ZH>After the migration, the secondary postings from CO will also be
posted into the leading ledger</>.

How to fix this error?

Keep in mind that these additional postings into the leading ledger will
affect the data displayed in financial reports.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_ACDOC_CUST102 - Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2 ?

  The SAP error message FINS_ACDOC_CUST102 indicates an issue related to the integration between Controlling (CO) and Financial Accounting (FI) in real-time postings. Specifically, the error states that the specified ledger group does not contain the leading ledger.
  Cause:
  This error typically occurs when:
  
  The ledger group specified in the posting does not include the leading ledger that is required for the integration between CO and FI.
  The configuration of the ledger groups in the system is incorrect or incomplete.
  The document being posted is trying to use a ledger that is not part of the specified ledger group.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  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.
  Verify that the ledger group specified in the error message includes the leading ledger. If it does not, you may need to add the leading ledger to the group.
  
  
  
  Check Document Posting:
  
  Review the document you are trying to post and ensure that it is using the correct ledger and ledger group.
  Make sure that the document is being posted to a ledger that is part of the specified ledger group.
  
  
  
  Consult with Configuration Team:
  
  If you are not able to resolve the issue, consult with your SAP configuration team or a functional consultant who specializes in FI/CO integration. They can help verify the settings and make necessary adjustments.
  
  
  
  Testing:
  
  After making changes, perform a test posting to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Leading Ledger: In SAP, the leading ledger is the primary ledger used for financial reporting. It is essential for the integration of CO and FI.
  Ledger Groups: Ledger groups are used to define which ledgers are included in a particular reporting structure. They are crucial for ensuring that the correct data is available for reporting and analysis.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  OB22: To configure ledger groups.
  FB50: To post documents in the general ledger.
  KSB1: To view CO line items.
  
  
  
  By following these steps and understanding the underlying concepts, you should be able to resolve the FINS_ACDOC_CUST102 error effectively.