Incorrect PM Master No is displayed in the WO Message in the PM Cycle batch job log, after a PM is Superseded.
(Doc ID 1331916.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Utilities Work and Asset Management - Version 1.8.1 and later
Information in this document applies to any platform.
The incorrect PM Master No is displayed in the WO Message in PM Cycle batch job log,
after a PM is Superseded.
The WO generated is for a different PM Master record but the batch job log
shows the wrong PM Master number.
### Steps to Reproduce ###
1.Setup 2 PM's with one superseding the the other as defined by adding one of
them to the PM Group of the other. Let's say 000954 and 0009555.
2. List 000954 as a PM in the PM Group 0009555.
3.Setup a third PM (000956) that has a schedule date that coincides with the
first 2 PMs.
4.Run PM_Cycle()batch Job. Two messages will appear, one indicating that PM
000954 was superseded by PM 0009555.The next message displays in the format
'WO was created: 01/PM No./Forecast cycle number/Forecast date: WO:
and would show in this scenario of the problem as 'WO was created
01/000954/Forecast cycle number/06-JAN-2011: 01121.
5.All the information proceeding the WO 01121 is for the PM that was
superseded not for PM 000956 for which the WO was actually created.
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