Additional information for issue #2 Let's check what is referential integrity in the database: WikiPedia: Referential integrity is a property of data stating references within it are valid. In the context of relational databases, it requires every value of one attribute (column) of a relation (table) to exist as a value of another attribute (column) in a different (or the same) relation (table).[1] For referential integrity to hold in a relational database, any column in a base table that is declared a foreign key can contain either a null value, or only values from a parent table's primary key or a candidate key.[2] In other words, when a foreign key value is used it must reference a valid, existing primary key in the parent table. In my case: Parent table it is table with PZINSKEY. Child table it is table with PXINSINDEXEDKEY + reference to Parent table on column PZINSKEY. But this reference can't be validated by database, because record does not exists in Parent table when Pega do insert record into Child table. Must be: Insert record into PARENT/MASTER table (work table) and then Insert record into CHILD table (idx work table) Is it property of Pega engine: insert record into IDX table, and then insert into PARENT table? How to change this order in the Pega?

Please provide the Pega platform version information. And the details of how you are saving. Is it a deferred save operation?

We are having the same issue for GENERATED ALWAYS DB2 columns that can not be nulls. We are using 7.2.2.

Any suggestions?