How To Fix FINS_RECON738 - COSS_BAK differs from COSS in attrib.- &1 &2 &3

FINS_RECON738 - Overview

• Message type: E = Error

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

• Message number: 738

• Message text: COSS_BAK differs from COSS in attrib.- &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_RECON738 - COSS_BAK differs from COSS in attrib.- &1 &2 &3 ?

  The SAP error message FINS_RECON738 with the description "COSS_BAK differs from COSS in attrib.- &1 &2 &3" typically relates to inconsistencies in the cost accounting data, specifically between the original cost object (COSS) and the backup cost object (COSS_BAK). This error often arises during reconciliation processes or when trying to post transactions that involve cost objects.
  
  Cause:
  
  Data Inconsistency: The primary cause of this error is that the attributes of the backup cost object (COSS_BAK) do not match those of the original cost object (COSS). This can happen due to manual changes, incorrect postings, or data corruption.
  
  Configuration Issues: There may be configuration issues in the cost accounting module that lead to discrepancies in how cost objects are defined or processed.
  System Updates or Changes: Changes in the system, such as updates or migrations, can sometimes lead to inconsistencies in the data.
  
  
  Solution:
  
  Check Data Consistency: Use transaction codes like KSB1 (Cost Centers: Actual Line Items)