How To Fix CM_EHFND_REQ118 - Client &1: Requirement name "&2" - INSERT statement failed

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_REQ - Messages for Compliance Requirement

• Message number: 118

• Message text: Client &1: Requirement name "&2" - INSERT statement failed

What causes this issue?

The system tried to create a data record for a compliance requirement
name in table <NP>EHFNDD_REQ_NAME</>. However, a database error occurred
during the <ZH>INSERT</> statement.

System Response

INCLUDE R_EHFND_REQ_MIGRATION_NA_TX2 OBJECT DOKU ID TX

How to fix this error?

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

Procedure for System Administrators

INCLUDE R_EHFND_REQ_MIGRATION_NA_TX4 OBJECT DOKU ID TX
INCLUDE R_EHFND_REQ_MIGRATION_NA_TX3 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHFND_REQ118 - Client &1: Requirement name "&2" - INSERT statement failed ?

  The SAP error message CM_EHFND_REQ118 typically indicates that there was an issue with an INSERT statement in the context of a requirement in the SAP system. This error can occur in various scenarios, particularly when working with custom developments, enhancements, or when using the SAP Fiori applications.
  Cause:
  The error message "INSERT statement failed" suggests that the system encountered a problem while trying to insert data into the database. Common causes for this error include:
  
  Data Integrity Issues: The data being inserted may violate database constraints, such as primary key or foreign key constraints.
  Missing Required Fields: The INSERT statement may be missing mandatory fields that are required by the database table.
  Data Type Mismatch: The data types of the values being inserted may not match the expected data types in the database schema.
  Database Locking: The database table may be locked by another transaction, preventing the INSERT operation from completing.
  Authorization Issues: The user executing the operation may not have the necessary permissions to perform the INSERT action on the specified table.
  Custom Logic Errors: If there is custom code or logic involved in the INSERT operation, there may be bugs or logical errors in that code.
  
  Solution:
  To resolve the CM_EHFND_REQ118 error, you can take the following steps:
  
  Check the Error Log: Review the detailed error log or short dump (ST22) to get more information about the specific cause of the failure.
  Validate Data: Ensure that the data being inserted meets all the requirements of the database schema, including data types and mandatory fields.
  Check Constraints: Verify that the data does not violate any primary key or foreign key constraints in the database.
  Review Custom Code: If the error is occurring in custom logic, review the code for any potential issues or bugs that could lead to the failure.
  Database Locks: Check if the table is locked by another transaction. You can use transaction codes like SM12 to view and manage locks.
  Authorization Check: Ensure that the user has the necessary authorizations to perform the INSERT operation.
  Test in Development: If possible, replicate the issue in a development environment to troubleshoot without affecting production data.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), and ST22 (Dump Analysis) to investigate the issue further.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address known issues related to this error message.
  Debugging: If you have access to the ABAP code, consider debugging the program to identify where the INSERT statement is being executed and what data is being passed.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or development team for further assistance.