My Oracle Support Banner

E1: UBE: Logging Of ER Code, Placed After Synchronous Report Interconnect Child UBE Launched Via Business Function, Is Not Captured in Parent UBE JDEDEBUG Log (Doc ID 2665526.1)

Last updated on MAY 06, 2020

Applies to:

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

Symptoms

Parent UBE has ER code after call to ER BSFN which launch synchronous Child UBE Report Interconnect via API jdeLaunchUBEEx/jdeLaunchUBEEx2.

When UBE is submitted with UBE Logging Level 6 to server, logging of the ER code after the synchronous report interconnect launched via ER BSFN is not captured in Parent UBE jdedebug log.

If ER BSFN call is replaced with ER synchronous Report Interconnect, the logging of the ER code after ER synchronous report interconnect is captured in Parent UBE jdedebug log.

 

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.