Error Running PM Loop Schedule With Mixed Criteria
(Doc ID 2494532.1)
Last updated on NOVEMBER 23, 2019
Applies to:PeopleSoft Enterprise FIN Maintenance Management - Version 9.2 and later
Information in this document applies to any platform.
On : 9.2 version, Preventive Maintenance
Error running PM Loop Schedule with mixed criteria
In Image 29 Demo, error received when running Preventative Maintenance for a Loop Schedule with Meter and Date criteria. Error occurs when only some assets meet the Date criteria at time of run but all assets meet the Meter criteria. Error message is generated in logs. Only work order for asset meeting Date based criteria is created. Asset(s) meeting Meter criteria only are ignored. Replication steps attached.
SQL error. Function: SQLExec Error Position: 0
Return: 805 - ORA-00001: unique constraint (SYSADM.PS_WM)PM_ACT_INST) violated statement: INSERT INTO PS_WM_PM_ACT_INST (RUNDTTM, INTFC_ID, TO INTFC_ID, RUNDATE) VALUES (CAST(S YSTIMESTAMP AS TIMESTAMP), :1 , :2, TO_DATE(TO_CHAR(CHAR(SYSDATE, 'YYYY-MM- DD'), 'YYYY-MM-DD')) Original Statement: INSERT INTO PS_WM_PM_ACT_INST (RUNDTTM, INTFC_ID, TO_INTFC_ID, RUNDATE) VALUE S (%CURRENTDATETIMEIN, :1 , :1, %CURRENTDATEIN)
The issue can be reproduced at will with the following steps:
1. Create test Loop with two assets
2. Assign to and create Loop Schedule. Schedule has Meter and Date based criteria. Schedule is set up so that only one asset meets Date based criteria but both assets meet Meter based criteria
3. Run Preventative Maintenance for this Schedule only. Error is displayed in logs
4. Only Work Order for asset meeting Date based criteria is created. Since both assets met Meter criteria, two Work Orders should have been created:
< Internal Only
Internal Only >
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