How To Fix E2195 - Foreign key applied from the include

SAP Error Message - Details

• Message type: E = Error

• Message class: E2 - DE Data Dictionary

• Message number: 195

• Message text: Foreign key applied from the include

What causes this issue?

You set the 'Inherited from include' flag. This passes the attributes
of the foreign key from the included table or structure to the
including table or structure. The foreign key therefore depends on the
definition of the included table or structure.

System Response

Only for information.

How to fix this error?

No action required.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message E2195 - Foreign key applied from the include ?

  The SAP error message E2195, which states "Foreign key applied from the include," typically occurs in the context of data consistency checks in SAP, particularly when dealing with foreign key relationships in database tables. This error indicates that there is an issue with the foreign key constraints defined in the database, often due to missing or inconsistent data.
  Cause:
  
  Missing Data: The foreign key constraint is violated because the referenced record in the parent table does not exist. This can happen if a record was deleted or if the data was not properly entered.
  Inconsistent Data: The data in the child table does not match the expected values in the parent table, leading to a violation of the foreign key constraint.
  Include Structure Issues: If the error arises from an include structure, it may indicate that the foreign key relationship defined in the include is not being satisfied by the data in the main table.
  
  Solution:
  
  Check Data Integrity: Verify that all records in the child table have corresponding records in the parent table. You can do this by running SQL queries or using transaction codes like SE11 (Data Dictionary) to check the table relationships.
  Correct Data Entries: If you find missing or incorrect entries, you will need to either add the missing records to the parent table or correct the entries in the child table to ensure they match the foreign key constraints.
  Review Include Structures: If the error is related to an include structure, check the definitions in the include and ensure that the foreign key relationships are correctly defined and that the data adheres to these definitions.
  Use Transaction Codes: Utilize transaction codes like SE14 (Database Utility) to check and repair inconsistencies in the database tables.
  Consult Documentation: Review SAP documentation or notes related to the specific tables and foreign key relationships to understand any specific requirements or constraints.
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SE14 (Database Utility), SE37 (Function Module), SE80 (Object Navigator).
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific tables or foreign key constraints you are working with.
  Debugging: If you have access to debugging tools, you can trace the program execution to identify where the foreign key violation is occurring.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or development team for further analysis and resolution.