How To Fix FINS_ACDOC_UTIL002 - Different CO versions assigned to ledgers for cocode &1 and &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_UTIL - Messages for package FINS_ACDOC_UTIL

• Message number: 002

• Message text: Different CO versions assigned to ledgers for cocode &1 and &2

What causes this issue?

You are posting across multiple companies. For the involved ledgers, the
valuation view assignment is different between at least two companies.

System Response

The posting is prohibited by the system - it would lead to documents
that are incomplete from a business viewpoint.

How to fix this error?

Depending on your configuration of accounting principles and valuation
groups and their assignment to ledgers, you can either restrict the
involved ledgers by specifying a ledger group for the posting or you can
post to more ledgers by omitting the ledger group or using a ledger
group that includes more ledgers.
Either way, the set of valuation views being posted to has to be same
for all companies involved in the transaction.

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_UTIL002 - Different CO versions assigned to ledgers for cocode &1 and &2 ?

  The SAP error message FINS_ACDOC_UTIL002 indicates that there is a mismatch in the controlling (CO) versions assigned to different ledgers for the specified company codes. This typically occurs when you are trying to perform a financial operation that involves multiple company codes, and the system detects that the CO versions configured for these company codes are not the same.
  Cause:
  
  Different CO Versions: The primary cause of this error is that the company codes involved have different CO versions assigned to their respective ledgers. This can happen if the configuration for controlling areas is not consistent across the company codes.
  Configuration Issues: It may also arise from incorrect or incomplete configuration in the controlling area settings, where the CO versions are defined for different ledgers.
  
  Solution:
  To resolve this error, you need to ensure that the same CO version is assigned to the ledgers for the company codes involved. Here are the steps to do this:
  
  
  Check CO Version Assignment:
  
  Go to the SAP transaction code OBY6 (or SPRO -> Financial Accounting -> General Ledger -> Master Data -> G/L Account -> Prepare for Migration -> Assign Company Codes to CO Versions).
  Verify the CO version assigned to each company code and ledger.
  
  
  
  Align CO Versions:
  
  If you find that the CO versions are different, you will need to align them. This may involve changing the CO version for one of the company codes to match the other.
  Make sure that the CO version you choose is appropriate for the financial reporting and controlling needs of the company codes.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the controlling area to ensure that they are set up correctly and consistently across all relevant company codes.
  If necessary, consult with your SAP configuration team or a functional consultant to ensure that the settings are appropriate.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs and that the financial operations can be completed successfully.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, SPRO, and OKKP (for controlling area settings).
  Documentation: Review SAP documentation or help files related to financial accounting and controlling area configuration for more detailed guidance.
  Support: If the issue persists after checking the configurations, consider reaching out to SAP support or your internal SAP helpdesk for further assistance.
  
  By following these steps, you should be able to resolve the FINS_ACDOC_UTIL002 error and ensure that your company codes are properly configured for financial transactions.