In PMTB_JOB_RUN_MASTER The JOB_EXEC_STATUS Status Remains As P And Not As C After Execution.
(Doc ID 2989086.1)
Last updated on NOVEMBER 23, 2023
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
In PMTB_JOB_RUN_MASTER the JOB_EXEC_STATUS status remains as P and not as C after execution.
In Reference to SR 3-34166022681.
Observation Job execution fails with PM-JOB-011 error "External job Scheduling cannot be triggered as job is already running."
EXPECTED BEHAVIOR
-----------------------
Expectation is after successful job execution in PMTB_JOB_RUN_MASTER the JOB_EXEC_STATUS should change from P to C, which is not happening when job is executed from Auto Mode or Manual mode.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. create a Manual Job request from PMDMNJOB screen for a given PM job such as PQDFUVAQ, PMDAENTB
2. Save and authorize the same.
3. after the PM Job is executed for that particular branch, retrigger the same job.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Job execution fails.
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 |