How To Fix ACE403 - No follow-up document exists for the legacy data in Accounting

SAP Error Message - Details

• Message type: E = Error

• Message class: ACE - Nachrichten zur Accrual Engine

• Message number: 403

• Message text: No follow-up document exists for the legacy data in Accounting

What causes this issue?

Accrual Engine Customizing for legacy data has been set in such a way
that Accrual Engine documents cannot be posted to Accounting. Legacy
data transfer of Accounting documents takes place in a separate step.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

This means that it is not possible to navigate from Accrual Engine
documents to the corresponding Accounting documents.

How to fix this error?

See the <DS:DE.ACE_LEGACY_TO_ACC_TRANSFER>notes</> on the "Allow
Transfer to Accounting" flag in
<DS:SIMG.FIGL_ACE_LEGACYM_DC>Customizing for legacy data transfer</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACE403 - No follow-up document exists for the legacy data in Accounting ?

  The SAP error message ACE403 ("No follow-up document exists for the legacy data in Accounting") typically occurs when there is an attempt to process or reference legacy data in the system that does not have a corresponding follow-up document. This can happen during various accounting processes, such as during the migration of legacy data into SAP or when trying to perform certain transactions that require a follow-up document.
  Cause:
  
  
  Missing Follow-Up Document: The primary cause of this error is that the system is unable to find a follow-up document that corresponds to the legacy data being referenced. This can occur if the legacy data was not properly migrated or if the follow-up documents were not created during the migration process.
  
  
  Data Migration Issues: If the data migration from a legacy system to SAP was incomplete or incorrect, it may lead to inconsistencies in the data, resulting in this error.
  
  
  Incorrect Document Type: The document type used in the transaction may not be compatible with the legacy data, leading to the inability to find a follow-up document.
  
  
  Solution:
  
  
  Check Migration Data: Review the data migration process to ensure that all necessary follow-up documents were created and that the legacy data was migrated correctly. This may involve checking logs or reports generated during the migration.
  
  
  Verify Document Types: Ensure that the document types used in the transactions are correct and compatible with the legacy data. If necessary, adjust the document types to match the expected formats.
  
  
  Create Missing Documents: If it is determined that follow-up documents are indeed missing, you may need to create them manually or reprocess the migration to include these documents.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance. They can provide guidance based on the specific configuration and setup of your SAP system.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as SE16 (Data Browser) to check the tables involved, or FB03 (Display Document) to view accounting documents.
  
  
  Legacy Data Handling: Understand the processes involved in handling legacy data within SAP, including the use of tools like LSMW (Legacy System Migration Workbench) for data migration.
  
  
  Documentation: Review SAP documentation related to financial accounting and data migration to ensure compliance with best practices.
  
  
  By following these steps, you should be able to identify the root cause of the ACE403 error and implement a solution to resolve it.