How To Fix FINS_RECON739 - COSP_BAK/COSS_BAK differs from COSP/COSS - &1 &2 &3 &4

FINS_RECON739 - Overview

• Message type: E = Error

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

• Message number: 739

• Message text: COSP_BAK/COSS_BAK differs from COSP/COSS - &1 &2 &3 &4

What causes this issue?

There is a mismatch between view COSP/COSS and the former totals table,
stored in COSP_BAK/COSS_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, COSP_BAK or COSS_BAK. Please
check corresponding detailed messages FINS_RECON 712/717/718 (Empty
field COEP-BUKRS, Empty field COSP_BAK/COSS_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_RECON739 - COSP_BAK/COSS_BAK differs from COSP/COSS - &1 &2 &3 &4 ?

  The SAP error message FINS_RECON739 indicates a discrepancy between the actual cost line items in the COSP (Cost Object: Actual Line Items) and COSS (Cost Object: Actual Line Items for Statistical Key Figures) tables and their backup tables COSP_BAK and COSS_BAK. This error typically arises during the reconciliation process, particularly when there are inconsistencies in the data that should be synchronized between these tables.
  Causes:
  
  
  Data Inconsistency: The most common cause is that the data in the backup tables (COSP_BAK and COSS_BAK) does not match the data in the main tables (COSP and COSS). This can happen due to incomplete updates, failed transactions, or manual data manipulation.
  
  
  System Errors: Issues during data processing, such as system crashes or transaction rollbacks, can lead to inconsistencies.
  
  
  Custom Developments: If there are custom programs or enhancements that manipulate cost data, they may inadvertently cause discrepancies.
  
  
  Transport Issues: If changes were transported between systems (e.g., from development to production),