How To Fix FINS_ACDOC_CUST225 - Only CO versions with transfer prices (&1/&2) allowed in FINSC_VERSN_LD

FINS_ACDOC_CUST225 - Overview

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 225

• Message text: Only CO versions with transfer prices (&1/&2) allowed in FINSC_VERSN_LD

What causes this issue?

In the customizing activity <DS:SIMG.FINSV_VERSN_LD>Define Ledger for CO
Version</>, you have entered the CO version &V1&. In controlling area
&V2& this version has valuation view &V3&, but only legal, group and
profit center valuation are allowed in this customizing activity.

System Response

Check the valuation view of the CO version with transaction
<DS:TRAN.OKEVN>OKEVN</>.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_ACDOC_CUST225 - Only CO versions with transfer prices (&1/&2) allowed in FINSC_VERSN_LD ?

  The SAP error message FINS_ACDOC_CUST225 indicates that there is an issue with the configuration of controlling (CO) versions in relation to transfer pricing. This error typically arises when you are trying to post a document that involves transfer pricing, but the CO versions specified do not meet the required criteria.
  
  Cause:
  The error occurs due to one of the following reasons:
  
  Incorrect CO Version: The CO versions specified in the transaction do not match the versions allowed for transfer pricing in the configuration.
  
  Configuration Issues: The configuration in the system for the CO versions may not be set up correctly to allow for transfer pricing.
  Missing or Incorrect Settings: The settings in the table FINSC_VERSN_LD may not include the CO versions you are trying to use for the transfer pricing.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check CO Versions:
  
  Verify the CO versions you are using in your transaction. Ensure that they are the