How To Fix FINS_RECON735 - COSS_BAK exists but not COSS - &1 &2 &3

FINS_RECON735 - Overview

• Message type: E = Error

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

• Message number: 735

• Message text: COSS_BAK exists but not COSS - &1 &2 &3

What causes this issue?

There is a mismatch between view COSS and the former totals table,
stored in 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 or COSS_BAK. Please check
corresponding detailed messages FINS_RECON 712/717 (Empty field
COEP-BUKRS, Empty field 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_RECON735 - COSS_BAK exists but not COSS - &1 &2 &3 ?

  The SAP error message FINS_RECON735 with the description "COSS_BAK exists but not COSS - &1 &2 &3" typically occurs in the context of financial reconciliation processes, particularly when dealing with cost accounting and controlling (CO) documents. This error indicates that there is a discrepancy between the backup (COSS_BAK) and the actual cost object (COSS) records in the system.
  
  Cause:
  
  Data Inconsistency: The error usually arises when there is a mismatch or inconsistency in the data between the backup records (COSS_BAK) and the actual records (COSS). This can happen due to incomplete postings, data corruption, or issues during data migration.
  Missing Entries: The COSS table, which contains actual cost line items, may not have been updated correctly, leading to the absence of expected entries.
  Incorrect Configuration: There may be configuration issues in the controlling module that lead to improper handling of cost objects.
  
  
  Solution:
  
  Check for Missing Entries: Investigate the COSS table to see if the expected