Do you have any question about this error?
Message type: E = Error
Message class: FAGL_MIG - Migration to New General Ledger Accounting
Message number: 124
Message text: Document splitting information already exists
The document splitting tables already contained information for the
selected item.
This could have the following causes:
The information was provided by program <ZK>FAGL_MIG_RPITEMS_CRESPLIT</>
. This is particularly likely in the case of multiple migration plans
with non-calendar fiscal year variants because the item occurs in the
worklist of the documents to be posted subsequently as well as in the
worklist of old open items.
An error occurred during parallel processing. In this case, the package
with errors is restarted by the program. There is also the possibility
that items of the package have already been written successfully to the
database. Since these items cannot be processed again with a restart,
the system issues a message for these items explaining that the items
already exist in the database.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check whether the item was generated correctly in tables
<ZK>FAGL_SPLINFO</> and <ZK>FAGL_SPLINFO_VAL</>. No other activities
need be performed because document splitting has already occurred.
Error message extract from SAP system. Copyright SAP SE.
FAGL_MIG124
- Document splitting information already exists ?The SAP error message FAGL_MIG124, which states "Document splitting information already exists," typically occurs during the migration of financial data, particularly when using the New General Ledger (New GL) functionality. This error indicates that the system has detected that document splitting information for a particular document already exists in the database, which can lead to conflicts during the migration process.
Causes:
- Duplicate Document Splitting Entries: The error often arises when there are attempts to migrate or post documents that already have document splitting information associated with them.
- Incorrect Migration Settings: If the migration settings or parameters are not correctly configured, it can lead to attempts to create duplicate entries.
- Data Consistency Issues: There may be inconsistencies in the data being migrated, such as missing or incorrect entries that lead to the system trying to create duplicate splitting information.
Solutions:
Check Existing Document Splitting Information: Before migrating, check if the document splitting information already exists for the documents in question. You can do this by querying the relevant tables (e.g., ACDOCA for the Universal Journal).
Adjust Migration Parameters: Review and adjust the migration parameters to ensure that they are set correctly. This may involve changing settings in the migration tool or ensuring that the source data is clean and does not contain duplicates.
Data Cleansing: Perform data cleansing on the source data to remove any duplicates or inconsistencies. This may involve checking for duplicate entries in the source system or ensuring that all necessary fields are populated correctly.
Use Transaction Codes: Utilize transaction codes like
FB03
to display the document and check for existing splitting information. You can also useFAGL_MIGRATION
to manage migration processes.Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
Testing in a Sandbox Environment: If possible, replicate the migration process in a sandbox environment to identify the exact cause of the error without affecting production data.
Engage SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for assistance. They can provide more specific guidance based on your system configuration and the details of the error.
Related Information:
By addressing the underlying causes and following the suggested solutions, you should be able to resolve the FAGL_MIG124 error effectively.
Get instant SAP help. Start your 7-day free trial now.
FAGL_MIG123
Document splitting information for &1 &2 &3 &4 already exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_MIG122
Special period &1 &2 is still open for company code &3, account type &4
What causes this issue? Not all special periods in the fiscal year preceding the migration date are closed.System Response The system issues an erro...
FAGL_MIG125
An entry with other values already exists: &1 &2 &3
What causes this issue? You have made an entry for a document. There are already entries with the same values in the <ZK>Reference Transaction ...
FAGL_MIG126
The documents listed have been included in the Customizing table
What causes this issue? The listed documents have been included in the Customizing table for maintaining document-specific business transaction assig...
Click on this link to search all SAP messages.