CMRO Loop Definition For Maintenance Requirement Is Not Working As Expected
(Doc ID 2682923.1)
Last updated on JUNE 24, 2020
Applies to:Oracle Complex Maintenance, Repair, & Overhaul - Version 12.2.5 and later
Information in this document applies to any platform.
Loop definition for MR is not working as expected
Expect that the Loop definition for MR works fine as expected.
Following is the loop functionality in MR loop definition.
a) The scenario we have is that, as per the new directive the existing 4 Checks are to be done in a sequence.
b) All the 4 MRs are revised and loop defined. There was no forecast. Revised again with copy accomplishment as 'NO' and the forecast was generated.
c) Added each MR to visit and signed off based on the actual accomplishment date.
d) However after accomplishing check 1, check2, check3 and check 4 the due date of check1 is going back as over due. Its not considering the accomplishment date of check4, rather it consider only the accomplishment
date of check 1 itself and generates due date back dated. This will not help us to use loop functionality.
a) Take 4 existing MRs (interval 180 days/600 Hrs) and define them in Loop with copy accomplishment as 'NO'.
b) Add first MR to visit and sign off as 16-Aug-2018 and run BUE
c) Then add second due MR and sign off as 05 Feb 2019 and run BUE
d) Add third MR and sign off as 23 Aug 2019 and run BUE
e) Add fourth MR and sign off as 17 feb and run BUE. After this in UMP the
First MR is shown as over due with due date 12 feb 2019.
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