How To Fix FINS_RECON737 - COSS_BAK differs from COSS in values - &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 737

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

  The SAP error message FINS_RECON737 indicates a discrepancy between the values in the COSS (Cost Object Controlling) and COSS_BAK (Backup) tables. This typically occurs during the reconciliation process in the Controlling (CO) module, particularly when dealing with cost objects such as internal orders, projects, or cost centers.
  Cause:
  The error arises when there is a mismatch between the actual values recorded in the COSS table and the backup values in the COSS_BAK table. This can happen due to several reasons, including:
  
  Data Inconsistencies: Changes made to cost objects after the backup was created can lead to discrepancies.
  Incorrect Posting: Manual postings or adjustments that do not properly update both tables.
  System Errors: Bugs or issues during data processing that prevent proper synchronization between the two tables.
  Transport Issues: If changes were transported between systems (e.g., from development to production), inconsistencies may arise if the transport was not executed correctly.
  
  Solution:
  To resolve the FINS_RECON737 error, you can follow these steps:
  
  
  Analyze the Discrepancy:
  
  Use transaction codes like KOB1 (for displaying actual line items) or COSS and COSS_BAK tables to identify the specific differences in values.
  Check the specific cost object mentioned in the error message (the placeholders &1, &2, &3 will provide details).
  
  
  
  Reconcile the Data:
  
  If the discrepancies are due to incorrect postings, you may need to reverse or adjust the postings to ensure that both tables reflect the same values.
  If the backup table is outdated, consider re-running the relevant processes to refresh the data.
  
  
  
  Use SAP Reports:
  
  Utilize standard SAP reports for reconciliation, such as S_ALR_87013611 (for cost center reports) or S_ALR_87013612 (for internal orders) to help identify and correct discrepancies.
  
  
  
  Check for System Notes:
  
  Review SAP Notes related to this error message. SAP frequently releases notes that address known issues and provide solutions or workarounds.
  
  
  
  Consult with SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP Support for assistance. They can provide insights based on the specific version of your SAP system and any known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in the CO module, such as KSB1 (for cost center reports) and KOB1 (for order reports).
  SAP Notes: Regularly check the SAP Support Portal for notes related to FINS_RECON737 or general CO module issues.
  Documentation: Review SAP documentation on Cost Object Controlling for a better understanding of how COSS and COSS_BAK tables function and how to manage them effectively.
  
  By following these steps, you should be able to identify the cause of the discrepancy and implement a solution to resolve the FINS_RECON737 error.