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

SAP Error Message - Details

• 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 FINS_RECON734 error, you can follow these steps:
  
  
  Check for Inconsistencies:
  
  Use transaction codes like KAH3 (Display Cost Center) or KSB1 (Cost Centers: Actual Line Items) to review the data in both COSP and COSP_BAK tables.
  Compare the entries in both tables to identify discrepancies.
  
  
  
  Reconcile Data:
  
  If discrepancies are found, you may need to reconcile the data. This could involve correcting entries in the COSP table or reprocessing the relevant transactions.
  You can use the KSV5 transaction to perform a reconciliation.
  
  
  
  Run Consistency Checks:
  
  Use the transaction KALC (Cost Object Controlling: Consistency Check) to run consistency checks on the CO data.
  This can help identify and correct inconsistencies automatically.
  
  
  
  Review Custom Code:
  
  If there are custom developments, review the code to ensure it correctly handles updates to both COSP and COSP_BAK tables.
  
  
  
  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 resolve known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSB1, KAH3, KALC, and KSV5 for monitoring and reconciling CO data.
  Backup Tables: Understand the role of backup tables like COSP_BAK in maintaining data integrity and consistency.
  Documentation: Review SAP documentation related to Controlling and reconciliation processes for best practices and troubleshooting tips.
  
  By following these steps, you should be able to identify the cause of the FINS_RECON734 error and implement a solution to resolve it.