How To Fix FMCE613 - Duplicate cover group number &1, copied from &2, found during BAdI call

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCE - Cover Eligibility Messages

• Message number: 613

• Message text: Duplicate cover group number &1, copied from &2, found during BAdI call

What causes this issue?

You have changed the cover group number using a BAdI implementation, but
the changed cover group number is identical with the cover group number
to be used in the target.

System Response

The cover group cannot be copied to the target.

How to fix this error?

Contact your system administrator to change the BAdI implementation in
the IMG activity <DS:SIMG.FMCE_COVER_GROUP>BAdI:Enhance Cover
Groups/Cover Rules</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMCE613 - Duplicate cover group number &1, copied from &2, found during BAdI call ?

  The SAP error message FMCE613 indicates that there is a duplicate cover group number in the system. This error typically occurs during the execution of a Business Add-In (BAdI) when the system detects that a cover group number being processed already exists in the system, which violates the uniqueness constraint for cover group numbers.
  Cause:
  
  Duplicate Entry: The most common cause of this error is that there are two or more entries in the system with the same cover group number. This can happen due to data entry errors, incorrect data migration, or issues in the configuration.
  BAdI Implementation: If the BAdI implementation is incorrectly handling the cover group numbers, it may inadvertently attempt to create or process a duplicate entry.
  Data Consistency Issues: There may be inconsistencies in the data that lead to the same cover group number being referenced multiple times.
  
  Solution:
  
  
  Check for Duplicates: 
  
  Use transaction codes like SE16 or SE11 to check the relevant database tables (e.g., FMCE) for existing cover group numbers. Look for duplicates and resolve them by either deleting or modifying the entries.
  
  
  
  Review BAdI Implementation: 
  
  If you have custom logic in the BAdI implementation, review the code to ensure that it correctly handles cover group numbers and does not create duplicates.
  
  
  
  Data Cleanup: 
  
  If duplicates are found, you may need to clean up the data. This could involve deleting or merging duplicate entries, depending on your business requirements.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to the specific BAdI you are using to see if there are any known issues or additional configuration steps required.
  
  
  
  Testing: 
  
  After making changes, thoroughly test the system to ensure that the error no longer occurs and that the functionality works as expected.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and SE80 (Object Navigator) for checking and modifying data.
  SAP Notes: Check SAP Notes for any updates or patches related to the BAdI or the error message. This can provide insights into known issues and fixes.
  Support: If the issue persists after troubleshooting, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the FMCE613 error and implement a solution to resolve it.