How To Fix FINS_RECON731 - COSP_BAK exists but not COSP - &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 731

• Message text: COSP_BAK exists but not COSP - &1 &2 &3

What causes this issue?

There is a mismatch between view COSP and the former totals table,
stored in COSP_BAK.

System Response

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

How to fix this error?

One possible cause of this reconciliation error is missing company code
value (BUKRS) in the source tables COEP or COSP_BAK. Please check
corresponding detailed messages FINS_RECON 712/718 (Empty field
COEP-BUKRS, Empty field COSP_BAK-BUKRS) from the migration activity R22
(Check Enrichment of Transaction Data) via transaction
FINS_MIG_MONITOR_RC2.

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 FINS_RECON731 - COSP_BAK exists but not COSP - &1 &2 &3 ?

  The SAP error message FINS_RECON731 indicates that there is a discrepancy between the CO (Controlling) documents in the COSP (CO Object: Line Item) and COSP_BAK (Backup of CO Object: Line Item) tables. Specifically, it suggests that there are entries in the COSP_BAK table that do not have corresponding entries in the COSP table.
  
  Cause:
  This error typically arises due to one of the following reasons:
  
  Data Inconsistency: There may have been an inconsistency during a data migration or during the execution of a reconciliation process.
  Incomplete Document Processing: Some CO documents may not have been processed completely, leading to entries being created in the backup table without corresponding entries in the main table.
  Custom Development: If there are custom programs or enhancements that manipulate CO data, they may not be handling the data correctly, leading to inconsistencies.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check for Inconsistencies:
  
  Use transaction codes like SE16 or SE11 to check