My Oracle Support Banner

E1: TDA: Delete Partial Key Does Not Populate Correct Data To Table Trigger Event / Table Event Rule (TER) "After Record is Deleted" (Doc ID 1969260.1)

Last updated on FEBRUARY 05, 2019

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

Tables F5801A and F5801B are defined with same primary keys
Table Trigger Event / Table Event Rule (TER) "After Record is Deleted" is added to F5801A to delete corresponding F5801B record using the primary keys
When F5801A records are deleted using partial primary keys, corresponding F5801B records are not deleted

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.