Do you have any question about this error?
Message type: E = Error
Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing
Message number: 126
Message text: No CO version can be determined for ledger &1 in company &2
The G/L ledger configuration should contain an assignment of ledger &v1&
/ company code &v2& to a corresponding CO version. However, no CO
version can be determined for that combination.
Every CO version needs to be assigned to a suitable legder. Otherwise CO
documents cannot be recorded properly.
Please assign all relevant CO versions to a ledger for all company
codes.
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.
FINS_ACDOC_CUST126
- No CO version can be determined for ledger &1 in company &2 ?The SAP error message FINS_ACDOC_CUST126 indicates that the system is unable to determine a controlling (CO) version for a specific ledger in a given company code. This typically occurs during the posting of financial documents when the system tries to find the appropriate CO version for the specified ledger and company code combination.
Cause:
- Missing CO Version Configuration: The CO version for the specified ledger and company code may not be configured in the system.
- Incorrect Ledger Assignment: The ledger may not be correctly assigned to the controlling area or company code.
- Inconsistent Settings: There may be inconsistencies in the settings between the financial accounting (FI) and controlling (CO) modules.
- Data Migration Issues: If data has been migrated from another system, there may be missing configurations or data inconsistencies.
Solution:
Check CO Version Configuration:
- Go to the transaction code OBY6 (or SPRO -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Define Ledger).
- Ensure that the CO version is defined for the specified ledger and company code.
Verify Ledger Assignment:
- Check the assignment of the ledger to the controlling area. You can do this in the transaction code OKB9 (or SPRO -> Controlling -> General Controlling -> Organization -> Assign Company Code to Controlling Area).
- Ensure that the ledger is correctly assigned to the controlling area.
Review CO Settings:
- Ensure that the controlling area settings are consistent with the financial accounting settings. Check the configuration in OKKP (Controlling Area) and ensure that the settings align with the ledger and company code.
Check for Data Migration Issues:
- If the error occurred after a data migration, review the migration process to ensure that all necessary configurations were transferred correctly.
Consult Documentation:
- Review SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
Contact SAP Support:
- If the issue persists after checking the above configurations, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the error message FINS_ACDOC_CUST126.
Get instant SAP help. Start your 7-day free trial now.
FINS_ACDOC_CUST125
CO version &1/&2 is ABC delta version;it can¦t be used in S/4HANA Finance
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_ACDOC_CUST124
Transaction not allowed for CO version &1
What causes this issue? CO version &v1& in CO area &v2& is an Activity-Based Costing (ABC) delta version. The system issues an error ...
FINS_ACDOC_CUST127
You have changed the posting period variant from &3 to &4 (&1/&2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_ACDOC_CUST128
You have changed the fiscal year variant from &3 to &4 (&1/&2)
What causes this issue? You have changed the fiscal year variant from &V3& to &V4& in company code &V1&, ledger &V2&....
Click on this link to search all SAP messages.