How To Fix FINS_ACDOC_CUST302 - You have changed the leading ledger from &1 to &2

FINS_ACDOC_CUST302 - Overview

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 302

• Message text: You have changed the leading ledger from &1 to &2

What causes this issue?

You have changed the leading ledger. All company codes have to be
assigned to the leading ledger.

System Response

The system checks that all company codes are assigned to the leading
ledger. If this is not the case, these entries will be created
automatically when you restart the ledger customizing transaction.

How to fix this error?

Save your work, exit the transaction, and restart the transaction. If
the change is possible, the system will add any missing company codes to
the leading ledger.

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_CUST302 - You have changed the leading ledger from &1 to &2 ?

  The SAP error message FINS_ACDOC_CUST302 indicates that there has been a change in the leading ledger configuration in the system. This error typically arises when there is an attempt to post or process financial documents that are associated with a different leading ledger than what is currently configured in the system.
  
  Cause:
  
  Change in Leading Ledger: The leading ledger for a company code has been changed from one ledger (e.g., &1) to another (e.g., &2). This can happen due to configuration changes in the Financial Accounting (FI) module.
  Document Posting: The error may occur when trying to post a document that references the old leading ledger after it has been changed.
  Inconsistent Data: There may be inconsistencies in the data due to the change in the leading ledger, which can lead to issues when processing financial transactions.
  
  
  Solution:
  
  Check Configuration: Verify the configuration settings for the leading ledger in the Financial Accounting settings. Ensure that the