Do you have any question about this error?
Message type: E = Error
Message class: FAGL_MIG - Migration to New General Ledger Accounting
Message number: 402
Message text: Postings already made in company code &1 with transaction FBCB
For the migration to new General Ledger Accounting, you have already
used transaction <AB>FBCB</> in company code &V1& to post data in period
0 of fiscal year &V2& in new General Ledger Accounting.
Repeat execution of balance carryforward would overwrite the
carryforward period of the fiscal year.
Processing is terminated.
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.
FAGL_MIG402
- Postings already made in company code &1 with transaction FBCB ?The SAP error message FAGL_MIG402 indicates that there are already postings made in the specified company code using the transaction FBCB (which is typically used for the migration of balances in the General Ledger). This error usually occurs during the migration process when you attempt to post balances or perform a migration that conflicts with existing postings.
Cause:
- Existing Postings: The primary cause of this error is that there are already financial postings in the specified company code that have been made using the FBCB transaction. This could be due to prior migration activities or regular postings that were made after the migration process was initiated.
- Incorrect Migration Process: The migration process may not have been executed correctly, or there may have been an attempt to re-run the migration without clearing previous postings.
Solution:
- Check Existing Postings: Review the postings made in the company code using transaction FBCB. You can do this by checking the relevant tables (like BSIK, BSAK, etc.) or using transaction codes like FB03 to view document details.
- Clear Existing Postings: If the existing postings are not needed, you may need to reverse or delete them. Ensure that you have the necessary authorizations and that this action complies with your organization's policies.
- Adjust Migration Process: If the existing postings are valid and should remain, you may need to adjust your migration process. This could involve:
- Ensuring that the migration is only run once.
- Using a different approach for migrating balances that does not conflict with existing postings.
- Consult Documentation: Review SAP documentation or notes related to the FAGL_MIG402 error for any specific guidance or recommendations.
- Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to identify the cause of the FAGL_MIG402 error and take appropriate actions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FAGL_MIG401
Balance carryforward is not possible; GLT0 update is not active
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_MIG400
Bal. carryfwrd for ledger &1 CoCode &2 not possible (migration to New GL)
What causes this issue? For company code &V2& in ledger &V1&, there is a migration plan for new General Ledger Accounting with migrat...
FAGL_MIG403
Bal. carryfrwd for company code &1 is not possible (migration to New G/L)
What causes this issue? You have started balance carryforward in classic General Ledger Accounting for company code &V1&. However, this compa...
FAGL_MIG500
Migration to new General Ledger Accounting not released; see long text
What causes this issue? You want to create a <DS:GLOS.D5BDBECA49D92A44BBE18822B23D801E>migration plan</> for the migration to new General...
Click on this link to search all SAP messages.