How To Fix FINS_RECON734 - COSP_BAK differs from COSP in attrib.- &1 &2 &3

FINS_RECON734 - Overview

• Message type: E = Error

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

• Message number: 734

• Message text: COSP_BAK differs from COSP in attrib.- &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_RECON734 - COSP_BAK differs from COSP in attrib.- &1 &2 &3 ?

  The SAP error message FINS_RECON734 indicates that there is a discrepancy between the values in the COSP (CO Object: Cost Line Items) and COSP_BAK (Backup of CO Object: Cost Line Items) tables. This typically occurs during the reconciliation process in the Controlling (CO) module, where the system checks for consistency between these two tables.
  
  Cause:
  The error can arise due to several reasons, including:
  
  Data Inconsistency: There may be inconsistencies in the data between the COSP and COSP_BAK tables, possibly due to incomplete postings, errors during data transfer, or issues during the closing process.
  Custom Developments: If there are custom programs or enhancements that manipulate CO data, they might lead to discrepancies.
  System Errors: Bugs or issues in the SAP system or during a system upgrade can also lead to this error.
  Manual Changes: Manual changes to the data in the COSP table without corresponding updates to the COSP_BAK table can cause this issue.
  
  
  Solution:
  To resolve the