How To Fix DI792 - Secondary table & bound to incorrect foreign key type using join

DI792 - Overview

• Message type: E = Error

• Message class: DI - Dictionary messages: Indexes

• Message number: 792

• Message text: Secondary table & bound to incorrect foreign key type using join

What causes this issue?

Each secondary table of a lock object must be connected to a base table
above it in the hierarchy with a join condition. This join condition
must be implemented via a foreign key. This foreign key must have the
secondary table as foreign key table and the base table above it in the
hierarchy as check table.
The join condition for the secondary table named is the other way
around: the secondary table is the check table and the base table
higher in the hierarchy is the foreign key table of the relevant
foreign key.

System Response

The action is cancelled.

How to fix this error?

Build the hierarchy of the lock object correctly. Observe the
<DS:TX.DDDOK_ENQU_REQUIREMENTS>requirements for the join conditions of
a lock object</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DI792 - Secondary table & bound to incorrect foreign key type using join ?

  The SAP error message DI792 indicates that there is a mismatch in the foreign key relationship between tables in a join operation. This typically occurs when a secondary table is bound to a foreign key that does not match the expected data type or structure. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  
  Cause:
  
  
  Data Type Mismatch: The foreign key in the secondary table may have a different data type than the primary key it is supposed to reference. For example, if the primary key is an integer and the foreign key is a string, this will lead to the error.
  
  
  Incorrect Join Conditions: The join condition may not be correctly defined, leading to an incorrect binding of the secondary table to the primary table.
  
  
  Modeling Issues: In the data model, the relationships between tables may not be correctly defined, leading to inconsistencies in how the tables are