Ansicht
Dokumentation

CPI32B8 - Secondary referential constraint defined but not established. ( OS/400 )

CPI32B8 - Secondary referential constraint defined but not established. ( OS/400 )

CPI1466 during Backup   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by IBM.
SAP E-Book


Message : CPI32B8
Secondary referential constraint defined but not established.

Message Long Text :

Cause . . . . . : Referential Constraint &13 is defined but cannot be established for dependent file &1 in library &2, The parent file &5 in library &6 has a delete rule of &11 and update rule of &12. The reason code is &8. The constraint state is &7. The defined status is &9.
When a unique constraint or a primary key constraint is added to a file that is a parent file in a defined referential constraint with a dependent file, then the referential constraint of the dependent file is known as a secondary referential constraint. The referential constraint is regarded as secondary processing because the primary request is for the processing of the unique constraint or the primary key constraint.

The reason codes are:
01 - The parent file does not exist.
02 - The parent or dependent file does not have a member.
03 - A mismatch exists between the parent key and foreign key
for the field attributes.

The constraint states are as follows:
01 - Defined and enabled.
02 - Defined and disabled.

The defined status is:
01 - Defined valid.
02 - Defined not valid. See previous messages.


Message File : QCPFMSG
Library Message File : QSYS2924


SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3273 Date: 20240329 Time: 002434     sap01-206 ( 2 ms )