How To Fix FINS_ACDOC_CUST346 - Use leading ledger &4 as compatibility view ledger for CoCode &1 / &2

FINS_ACDOC_CUST346 - Overview

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 346

• Message text: Use leading ledger &4 as compatibility view ledger for CoCode &1 / &2

What causes this issue?

In the Customizing settings for
<DS:SIMG.V_FCML_MLCO_COFI>Multiple Accounting Principles in Controlling
(COGM)</>, you entered ledger &V3& as compatibility view ledger for
Controlling for company code &V1&, accounting principle &V2&, and
<LS>Excl. Update</> = '1'.

System Response

How to fix this error?

For <LS>Excl. Update</> = '1', you must use leading ledger &V4& instead
of &V3&.

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_CUST346 - Use leading ledger &4 as compatibility view ledger for CoCode &1 / &2 ?

  The SAP error message FINS_ACDOC_CUST346 indicates that there is an issue with the configuration of the leading ledger in the context of the Universal Journal (ACDOCA) in SAP S/4HANA. This error typically arises when there is a mismatch or misconfiguration related to the compatibility view ledger for a company code.
  
  Cause:
  
  Leading Ledger Configuration: The error suggests that the system is expecting a specific leading ledger to be used as a compatibility view ledger for the specified company code. If the leading ledger is not properly configured or if the company code is not assigned to the correct leading ledger, this error can occur.
  Missing Assignments: The company code may not be assigned to the leading ledger in the configuration settings.
  Inconsistent Data: There may be inconsistencies in the data related to the ledgers and company codes in the system.
  
  
  Solution:
  
  
  Check Ledger Configuration:
  
  Go to the transaction code OB22 (or the relevant configuration path) to check