Do you have any question about this error?
Message type: E = Error
Message class: FH - General ledger module messages
Message number: 220
Message text: Account &1 already exists up to &2 in controlling area &3
You attempted to create the controlling-area-specific area for a G/L
account. This area already exists, however, albeit with restricted
validity.
This can occur in particular if a cost element has already lost its
validity before the current fiscal year at the time of migration.
The system prevents you from saving.
A controlling-area-specific area for a G/L account with restricted
validity cannot be changed.
If this situation was not intentional, refer to SAP Note 2223514.
Error message extract from SAP system. Copyright SAP SE.
FH220
- Account &1 already exists up to &2 in controlling area &3 ?The SAP error message FH220 indicates that an account already exists in the specified controlling area. This error typically arises when you attempt to create or modify a cost element or account in the Controlling (CO) module, and the system finds that an account with the same number already exists.
Cause:
- Duplicate Account Creation: You are trying to create a cost element or account that already exists in the specified controlling area.
- Incorrect Account Number: The account number you are trying to use may have been entered incorrectly, leading to a conflict with an existing account.
- Data Migration Issues: If you are migrating data from another system or performing a mass upload, there may be duplicates in the data being imported.
Solution:
- Check Existing Accounts: Verify if the account you are trying to create already exists in the controlling area. You can do this by navigating to the relevant transaction (e.g., transaction code
KS01
for creating cost elements) and checking the account list.- Use a Different Account Number: If the account already exists, consider using a different account number that does not conflict with existing accounts.
- Review Data Migration: If this error occurred during a data migration process, review the data being imported to ensure there are no duplicates. Clean up the data before re-importing.
- Consult Documentation: Refer to SAP documentation or your organization's guidelines for creating accounts in the CO module to ensure compliance with naming conventions and account structures.
Related Information:
KS01
- Create Cost ElementKS02
- Change Cost ElementKS03
- Display Cost ElementIf the problem persists after checking these aspects, it may be beneficial to consult with your SAP support team or refer to SAP's support portal for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FH219
Results analysis for orders/projects only possible without CoCd data (&3)
What causes this issue? For account &V2& in controlling area &V1&, you have selected cost element category 31 (Order/Project Results ...
FH218
You are not authorized to lock secondary cost elements in CO area &1
What causes this issue? You are not authorized to lock secondary cost elements in controlling area &V1&. INCLUDE NA_AUTH_K_CSKB OBJECT DOKU I...
FH221
Cost element category must not be changed for primary cost elements
What causes this issue? You have tried to change the cost element category for a primary cost element although postings already exist for it. A warni...
FH222
Cost element category must not be changed for secondary cost elements
What causes this issue? You have tried to change the cost element category for a secondary cost element although postings already exist for it. An er...
Click on this link to search all SAP messages.