Could someone explane me why the system is not recalculation the due date after a new revision of a pm action?
Even the PM info is set to performed date based “Yes”. But in new revision, the user set the start value to a future date and the Due date is still considering the last completion work task date.
Souldn’t the system consider the next due date on Feb 2023 (Start Value) and not 11/2022?
The correct way in the case bellow is the next due date should be 02/2023 and not 11/2022, because a new revision has been created.
The bug correction suggested by @wrprabash will unfortunately not solve this.
However we have received exactly this setup as a support issue and after some discussions we have decided to change the current behavior (which is not to take the start value into consideration for a new revision when using Performed Date Based = Yes, but to always calculate based on the the last completion work task date).
The change in functionality will now take into account a change in the start value.
This will be changed with lcs bug 165000 which is planned to be delivered with UPD19.
Could someone explane me why the system is not recalculation the due date after a new revision of a pm action?
Even the PM info is set to performed date based “Yes”. But in new revision, the user set the start value to a future date and the Due date is still considering the last completion work task date.
Souldn’t the system consider the next due date on Feb 2023 (Start Value) and not 11/2022?
The correct way in the case bellow is the next due date should be 02/2023 and not 11/2022, because a new revision has been created.
Thank for attention.
Br.
Lopes
Hi Lopes,
If you are running a system below UPD17, lcs bug 163387 (delivered with UPD17) might have solved this problem. Maybe you can verify this by running the same test in a IFS internal environment.
Could someone explane me why the system is not recalculation the due date after a new revision of a pm action?
Even the PM info is set to performed date based “Yes”. But in new revision, the user set the start value to a future date and the Due date is still considering the last completion work task date.
Souldn’t the system consider the next due date on Feb 2023 (Start Value) and not 11/2022?
The correct way in the case bellow is the next due date should be 02/2023 and not 11/2022, because a new revision has been created.
Thank for attention.
Br.
Lopes
Hi Lopes,
If you are running a system below UPD17, lcs bug 163387 (delivered with UPD17) might have solved this problem. Maybe you can verify this by running the same test in a IFS internal environment.
The bug correction suggested by @wrprabash will unfortunately not solve this.
However we have received exactly this setup as a support issue and after some discussions we have decided to change the current behavior (which is not to take the start value into consideration for a new revision when using Performed Date Based = Yes, but to always calculate based on the the last completion work task date).
The change in functionality will now take into account a change in the start value.
This will be changed with lcs bug 165000 which is planned to be delivered with UPD19.
The bug correction suggested by @wrprabash will unfortunately not solve this.
However we have received exactly this setup as a support issue and after some discussions we have decided to change the current behavior (which is not to take the start value into consideration for a new revision when using Performed Date Based = Yes, but to always calculate based on the the last completion work task date).
The change in functionality will now take into account a change in the start value.
This will be changed with lcs bug 165000 which is planned to be delivered with UPD19.
Make it possible to change Maintenance Plan Start Value on PM Action with Performed Date Based = Yes.
Test plan:
Find PM Action with Performed Date Based = Yes or create a new PM Action with necessary information and set Performed Date Based = Yes.
Add Maintenance Plan data.
Check Maintenance Plan Tab. Verify that upcoming planning lines are planned according to “Last Work Task Completion Date” of the last Finished Work Order. If a new PM Action was created, then Generate a Wo and finish it. Then verify that upcoming planning lines are planned according to “Last Work Task Completion Date” of the last Finished Work Order.
Create new revision.
Goto General Tab and change “Maintenance Plan Start Value”.
Goto Maintenance Tab and verify that planning lines have changed according to “Maintenance Plan Start Value”. Refresh page if necessary.
Expected outcome:
Planning lines should change according to “Maintenance Plan Start Value”.
Make it possible to change Maintenance Plan Start Value on PM Action with Performed Date Based = Yes.
Test plan:
Find PM Action with Performed Date Based = Yes or create a new PM Action with necessary information and set Performed Date Based = Yes.
Add Maintenance Plan data.
Check Maintenance Plan Tab. Verify that upcoming planning lines are planned according to “Last Work Task Completion Date” of the last Finished Work Order. If a new PM Action was created, then Generate a Wo and finish it. Then verify that upcoming planning lines are planned according to “Last Work Task Completion Date” of the last Finished Work Order.
Create new revision.
Goto General Tab and change “Maintenance Plan Start Value”.
Goto Maintenance Tab and verify that planning lines have changed according to “Maintenance Plan Start Value”. Refresh page if necessary.
Expected outcome:
Planning lines should change according to “Maintenance Plan Start Value”.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
