My Oracle Support Banner

E1:34: Deleting Newly Created P3411 Record Before Saving Deletes Pegging F3412 Records (Doc ID 2552540.1)

Last updated on JANUARY 10, 2020

Applies to:

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

Symptoms

EnterpriseOne 9.1
When adding a new message in the Detail Message Review (P3411) but deleting it before accepting the message, the system deletes records from the Pegging Inquiry File (F3412).

The suspicion is that the "Delete Grid Rec Verify-After" event rule has bad logic that tries to cleanup data in F3412 based on the data it thinks the user is deleting from F3411. The problem is that if the user doesn't click Save after adding the new row, then it doesn't get a UKID Value. When the event logic in Line 2 runs, it gets all the F3412 records where the Pegging Record Link (PLNK) = 0, because the GC UKID is blank. Then lines 3-7 delete all records in F3412 where PLNK=0.

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.