Hi all.
Could someone please clarify the logical of the valid from field in pm action?
My situation is:
I have a pm action tha was created 09/08/2020 with the same valid from date.
The pm action is using a work task template.
Now, the user has created another revision of the work task template and set the valid from date to the same as before 09/08/2020.
Hi all.
Could someone please clarify the logical of the valid from field in pm action?
My situation is:
I have a pm action that was created 09/08/2020 with the same valid from date.
The pm action is using a work task template.
The pm action is in interval 180 days. Considering the performed date based: Yes
Now, the user has created another revision of the work task template and set the valid from date to the same as before 09/08/2020.
After activate and Replace Obsolete Revision on PM Actions, the valid from field of the new revision on pm action has assumed the actual sysdate (11/10/2021), not the valid from date that has been set in the work task template.
The problem is, with the actual date in valid from, the maintenance plan has changed the due date.
E.g.:
My last maintenance done was 05/21/2021.
The next one should be in 11/21/2021.
But the system has calculated the next one to 04/29/2022 considering the new valid from date 11/10/2021.
If I uncheck the revision control and change the valid from date of the pm action to 09/08/2020, the maintenance plan goes back the correct due date.
I thing the system must assume the valid from date of the work task template since the replace obsolete function is used.
Hope was clear with explanation.
Tks a lot.
After activate and Replace Obsolete Revision on PM Actions, the valid from field of the new revision on pm action has assumed the actual sysdate, not the the that has been set in the work task template.
The problem is, with the actual date in valid from, the maintenance plan has changed the due date.
E.g.:
My last done maintenance was
Hope was clear with explantion.
Best answer by Dilani
View original
