My Oracle Support Banner

E1: UBE: UBE Submitted Through RUNUBE With Batch Mode or Through RUNUBEXML, Ends in Error When It Is Submitted by a Specific User (Doc ID 2930986.1)

Last updated on MARCH 16, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 1_9.2 64-bit and later
Information in this document applies to any platform.

Symptoms

On tools release 9.2.5 or later, when a specific user submits any UBE through RUNUBE with Batch Mode as argument or through RUNUBEXML, the UBE ends in error. The UBE output can be set in P98617 to either database or filesystem or both.
When the same UBE is submitted from menu or from Batch Versions or using RUNUBE with Interactive Mode as argument, the UBE is launched and executed successfully.

When the UBE ends in error the Queue Kernel records the following message in the log:

Steps to replicate:

  1. Create a copy of F986110R in some other data source
  2. Add an OCM mapping for F986110R for a specific user in System and Server Map data sources.
  3. Submit an UBE through RUNUBE using "Batch" flag (e.g. RUNUBE <E1_USER> <PASSWORD> <ENV> *ALL R0008P XJDE0001 QBATCH B H D) or submit an UBE through RUNUBEXML.
  4. Check the status in WSJ and notice that the job status is E.

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.