My Oracle Support Banner

E1: RDA: UBE: SCHED: Troubleshooting Report Interconnect Issues (Doc ID 2385088.1)

Last updated on MARCH 22, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 to 9.2 [Release SP24 to 9.2]
Information in this document applies to any platform.


Report Interconnect function in Report Design Aid (RDA) is used when a second report is called from a first report.

This document lists some commonly encountered Report Interconnect issues. This document is created to assist customers in understanding and troubleshooting the different Report Interconnect issues.

Troubleshooting Steps

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
Troubleshooting Steps
 Known Issues
 Issue 1: UBE Report is not run Synchronously as defined in Event Rule Report Interconnect from an Interactive Application
 Issue 2: All Child UBE Reports called by Report Interconnect have Incorrect Spacing
 Issue 3: Child UBE Report fails to launch with error "KNT0000087 - Could not get extended duration token" due to API jdeChdir used to change directory
 Issue 4: Scheduled Job Parameters with Report Interconnect Values gets Corrupted when Passed in to UBE launched from Scheduler
 Issue 5: Data Selection on UBE Version Submitted via Scheduler, Report Interconnect, RUNUBE or RUNUBEXML is Overwritten
 Issue 6: Report called from Report Interconnect ends with "No Data Selected" error
 Issue 7: "Failed to Load Spec" Error on Synchronous Report Interconnect
 Issue 8: Custom UBE stuck in 'P' Processing Status and Triggers Infinite Child UBE Jobs
 Issue 9: Asynchronous Report Interconnect do not work. Report Stays in Processing status but has actually Crashed on the AS400 Server
 8.9x and Previous Releases Known Issues
 Issue 1: OCM Override for Child UBE launched Asynchronously from a Parent UBE does not take effect
 Issue 2: Processing Option Values of Asynchronous Child UBE Report are Blank when Parent UBE Report is Submitted from the Web Client
 Issue 3: Server OCM UBE Override is Ignored on Asynchronous Report Interconnect launched from Server in Parent UBE or Business Function in TR
 Issue 4: Asynchronous Report Interconnect Resets JDEDEBUG.LOG when submitting the Report Locally
 Issue 5: UBE Version is not running in the Job Queue specified in Version Detail for the Child UBE in Synchronous Report Interconnect call in TR 8.94_L1 and Earlier

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