Do you have any question about this error?
Message type: E = Error
Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing
Message number: 262
Message text: No co area assigned to co code &3, but global curr in ledger &2.
There is no controlling area assigned to company code &V3& or no
currency type configured in the controlling area. Therefore the currency
type of the global currency (KSL) must be empty for all ledgers.
In Ledger &V2& there is currency type &V1& configured. This is a data
inconsistency.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please contact SAP.
Error message extract from SAP system. Copyright SAP SE.
FINS_ACDOC_CUST262
- No co area assigned to co code &3, but global curr in ledger &2. ?The SAP error message FINS_ACDOC_CUST262 indicates that there is no controlling area assigned to the company code specified in the error message, but a global currency is present in the ledger. This typically occurs in the context of financial accounting and controlling when there is a mismatch in the configuration settings.
Cause:
- Missing Assignment: The company code (CO code) does not have a controlling area assigned to it in the system.
- Configuration Issues: The ledger is configured to use a global currency, but the necessary controlling area settings are not in place.
- Data Inconsistency: There may be inconsistencies in the master data or configuration settings that prevent the system from recognizing the relationship between the company code and the controlling area.
Solution:
To resolve this error, you can follow these steps:
Check Company Code Assignment:
- Go to the transaction code OBY6 (or navigate through the menu: SPRO > Financial Accounting > General Settings > Company Code > Assign Company Code to Controlling Area).
- Ensure that the company code in question is assigned to a controlling area.
Verify Controlling Area Settings:
- Use transaction code OKKP to check the settings of the controlling area.
- Ensure that the controlling area is properly configured and that it is linked to the correct company codes.
Check Ledger Configuration:
- Go to transaction code OB22 to check the ledger settings.
- Ensure that the ledger is correctly configured to use the global currency and that it aligns with the controlling area settings.
Review Master Data:
- Check the master data for the company code and controlling area to ensure there are no inconsistencies or missing entries.
Transport Requests:
- If changes were made in a development environment, ensure that the transport requests are properly moved to the production environment.
Consult Documentation:
- Review SAP documentation or consult with your SAP Basis or functional team for any specific configurations that may be required for your organization.
Related Information:
By following these steps, you should be able to identify and resolve the underlying cause of the error message FINS_ACDOC_CUST262.
Get instant SAP help. Start your 7-day free trial now.
FINS_ACDOC_CUST261
Global currency field must use currency type &1 in ledger &3 / cocode &4
What causes this issue? If a valuation is assigned to a ledger, then the currency type of the global currency field (KSL) must contain accordingly th...
FINS_ACDOC_CUST260
Company code &2 does not exist
What causes this issue? The company code &V2& is assigned to ledger &V1&, see transaction <DS:TRAN.FINSC_LEDGER>FINSC_LEDGER.&l...
FINS_ACDOC_CUST263
Company code &1 is assigned to CO area &2, which does not exist
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_CUST264
Enter currency type
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.