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

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 736

• Message text: COSS exists but not COSS_BAK - &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_RECON736 - COSS exists but not COSS_BAK - &1 &2 &3 ?

  The SAP error message FINS_RECON736 indicates that there is a discrepancy in the reconciliation process related to Cost of Sales Accounting (COSS) entries. Specifically, the error states that a COSS entry exists, but the corresponding COSS_BAK (backup) entry does not. This can occur during the reconciliation of cost accounting and financial accounting data.
  Cause:
  
  
  Data Inconsistency: The primary cause of this error is often due to inconsistencies in the data between the COSS and COSS_BAK tables. This can happen if:
  
  A COSS entry was created but the corresponding COSS_BAK entry was not generated due to a system error or interruption.
  There were manual changes or deletions in the database that led to missing entries.
  Issues during the posting process that prevented the backup entry from being created.
  
  
  
  Configuration Issues: Incorrect configuration settings in the system can also lead to this error, particularly if the settings for cost accounting and financial accounting are not aligned.
  
  
  System Bugs: Occasionally, bugs in the SAP system or specific patches may lead to this type of error.
  
  
  Solution:
  
  
  Check for Missing Entries: 
  
  Use transaction codes like SE16 or SE11 to check the COSS and COSS_BAK tables for the specific entries mentioned in the error message (indicated by &1, &2, &3).
  Identify the missing COSS_BAK entries for the corresponding COSS entries.
  
  
  
  Recreate Missing Entries: 
  
  If you find that COSS_BAK entries are indeed missing, you may need to recreate them. This can often be done by re-running the relevant posting or reconciliation process that should have generated the COSS_BAK entries.
  
  
  
  Run Reconciliation Programs: 
  
  Use SAP standard reconciliation programs or reports to identify and correct inconsistencies. Programs like RKAEP000 (for cost accounting) can help in reconciling the data.
  
  
  
  Check Configuration: 
  
  Review the configuration settings in the controlling (CO) and financial accounting (FI) modules to ensure they are set up correctly. This includes checking the settings for cost element accounting and integration points between CO and FI.
  
  
  
  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 related to this error message.
  
  
  
  Contact SAP Support: 
  
  If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error and the steps you have already taken.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and others that can help you analyze the data.
  Documentation: Review SAP documentation related to Cost of Sales Accounting and reconciliation processes to understand the expected behavior and configurations.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the FINS_RECON736 error effectively.