My Oracle Support Banner

E1: UBE: Synchronous Interconnect Jobs and Issues with Audit Tables F986114/F986114A (Doc ID 2572539.1)

Last updated on MAY 04, 2020

Applies to:

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

Symptoms

When synchronous report interconnect jobs are in running status, the F986110 will only have one record for the main job, but in the F986114 there will be more records.

When the main job is terminated, the corresponding (job#) F986114 record will be set to status 'E' but the other F986114 records (synchronous children with same PIDs but with different job#) will remain in status 'P'. 
Since there is no F986110 record corresponding to those child synchronous records in F986114, there is no way to change the status to 'E' as well and the user will have no clue that there are F986114 records with status 'P'.   
  
Once there is a F986114 record with status 'P' and the same process ID occurs again by the Enterprise Server operating system, that creates blocking issues for subsequent jobs and wrong execution details might be pulled from the old record.

The P986110B will check the F986114 based on process ID, host (server name) and status 'P'.

Since there are old records in the table still with status 'P', sometimes there will be the same process ID resulting in incorrect records shown in the P986114A form W986114AB (Work With Synchronous Jobs). 
  
Also, when jobs records involving Synchronous interconnect children are deleted from WSJ, only the matching Job# records are deleted from Audit Header/ Detail tables (F986114/F986114A). 

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.