How To Fix E2190 - Foreign key does not exist in include and will be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: E2 - DE Data Dictionary

• Message number: 190

• Message text: Foreign key does not exist in include and will be deleted

What causes this issue?

You created a foreign key for a field in an include, but set the
'Inherited from include' flag. The system tries to copy the definition
of the foregin key from the include, but the foreign key is not defined
in the include.

System Response

The foreign key was deleted.

How to fix this error?

You may not set the 'Inherited from include' flag when creating the
foreign key for this field.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message E2190 - Foreign key does not exist in include and will be deleted ?

  The SAP error message E2190, which states "Foreign key does not exist in include and will be deleted," typically occurs during the activation of a data dictionary object, such as a table or a view, when there is a foreign key relationship defined that does not correspond to an existing primary key in the referenced table or include structure.
  Cause:
  
  Missing Foreign Key Definition: The foreign key defined in the table does not point to a valid primary key in the referenced table or include.
  Changes in Table Structure: If the structure of the referenced table has changed (e.g., the primary key was removed or modified), the foreign key relationship may become invalid.
  Inconsistent Data Dictionary: There may be inconsistencies in the data dictionary where the foreign key is defined but not properly linked to an existing primary key.
  
  Solution:
  
  Check Foreign Key Definition: Go to the table definition where the error occurs and check the foreign key settings. Ensure that the foreign key is correctly defined and points to an existing primary key in the referenced table.
  Verify Referenced Table: Check the structure of the referenced table or include to ensure that the primary key exists and is correctly defined.
  Adjust or Remove Foreign Key: If the foreign key is no longer valid, you may need to either adjust it to point to a valid primary key or remove it if it is not needed.
  Re-activate the Object: After making the necessary changes, try to activate the data dictionary object again to see if the error persists.
  Transport Requests: If this issue arises in a transport request, ensure that all related objects are included in the transport to maintain consistency.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like SE11 (Data Dictionary) to view and modify table definitions and foreign key relationships.
  Documentation: Refer to SAP documentation for detailed information on data dictionary objects and foreign key constraints.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be specific fixes or recommendations provided by SAP.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or ABAP team for further investigation and resolution.