E1: UBE: Few UBE Jobs Get Stuck at P (Processing) Status in Submitted Job Search (P986110B) (WSJ application) and Remain in P status Even After the PDF Output is Created Successfully
(Doc ID 2962420.1)
Last updated on JULY 25, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Out of many UBE Batch Jobs which are submitted on server, few of them remain in P(Processing) status and never advance to D(Done) status as expected, when viewed in WSJ- Submitted Job Search P986110B Application. When checking the UBE outputs in printqueue folder, it is observed that the PDF output files are created successfully. Issue affects multiple environments, such as production and prototype environment.
Issue may be replicated using below steps :
- Login to production or prototype environment in JDE web client.
- Type BV in fast path to Open Batch Versions application (P98305W)
- Find the UBE job known to be getting stuck in P status.
- Select the desired versions and submit the Job on Server.
- Type WSJ In fast path to open Submitted Jobs Search application (P986110B).
- Monitor the record for the job submitted in step 4 and notice that once the job goes to P status , it never gets changed to D status as expected.
- Navigate to the printqueue folder on enterprise server.
- Notice that the corresponding PDF output file for the job number that was stuck in P status is created successfully.
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 |
Cause |
Solution |
References |