How To Fix FINS_RECON739 - COSP_BAK/COSS_BAK differs from COSP/COSS - &1 &2 &3 &4

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 739

• Message text: COSP_BAK/COSS_BAK differs from COSP/COSS - &1 &2 &3 &4

What causes this issue?

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

  The SAP error message FINS_RECON739 indicates a discrepancy between the actual cost line items in the COSP (Cost Object: Actual Line Items) and COSS (Cost Object: Actual Line Items for Statistical Key Figures) tables and their backup tables COSP_BAK and COSS_BAK. This error typically arises during the reconciliation process, particularly when there are inconsistencies in the data that should be synchronized between these tables.
  Causes:
  
  
  Data Inconsistency: The most common cause is that the data in the backup tables (COSP_BAK and COSS_BAK) does not match the data in the main tables (COSP and COSS). This can happen due to incomplete updates, failed transactions, or manual data manipulation.
  
  
  System Errors: Issues during data processing, such as system crashes or transaction rollbacks, can lead to inconsistencies.
  
  
  Custom Developments: If there are custom programs or enhancements that manipulate cost data, they may inadvertently cause discrepancies.
  
  
  Transport Issues: If changes were transported between systems (e.g., from development to production), inconsistencies may arise if the transport was not executed correctly.
  
  
  Solutions:
  
  
  Data Reconciliation: 
  
  Use transaction codes like KAH3 (Display Cost Object) or KAH2 (Change Cost Object) to check the data in both tables and identify discrepancies.
  Compare the records in COSP and COSP_BAK, as well as COSS and COSS_BAK, to find the differences.
  
  
  
  Rebuild Backup Tables: 
  
  If the discrepancies are significant, you may need to rebuild the backup tables. This can often be done through specific SAP programs or transactions designed for data consistency checks.
  
  
  
  Check for Custom Code: 
  
  Review any custom developments that may affect cost accounting and ensure they are functioning correctly.
  
  
  
  System Logs: 
  
  Check system logs for any errors or warnings that occurred during the time the discrepancies were created. This can provide insight into what went wrong.
  
  
  
  SAP Notes: 
  
  Search for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  
  
  
  Consult SAP Support: 
  
  If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to cost accounting, such as KSB1 (Cost Centers: Actual Line Items) and KOB1 (Order: Actual Line Items).
  Backup Tables: Understand the purpose of backup tables in SAP and how they are used for data integrity and recovery.
  Cost Object Accounting: A solid understanding of how cost object accounting works in SAP can help in diagnosing and resolving issues related to cost discrepancies.
  
  By following these steps, you should be able to identify the cause of the FINS_RECON739 error and implement a solution to resolve it.