Maximo Open Forum

Hello All,

Job plan tasks didn't get copied to the work order it was attached to .
There are other work orders which have the same Job Plan tasks copied .
Also for the WO in the question, when we remove the job plan and attach the same job plan again then the plans are getting copied.

We also don't have any logic for restricting the plans being copied.

Can any one help me with the approach on how to troubleshoot this issue?

#EverythingMaximo
#WorkManagement

------------------------------
Meghana Siriveli
------------------------------

Is this a reoccurring thing or is this a one time occurrence? If a WO (including tasks) was never approved, tasks can be deleted even if they were copied in via job plan. That means it's possible a user deleted them.

You also mention that you don't have any logic for restricting the plans being copied. Can you confirm that you don't have job plan conditions enabled (under System Settings in the Organizations application) and that the JOBTASK.CONDITIONNUM field is null? I've seen where people have a condition that doesn't evaluate to true here but will evaluate to true on an existing record (because the way the condition is written it queries the database versus getting the in memory record). If this is occurring reliably for a given job plan when done on a background process (such as PM), this is where I'd probably start.

------------------------------
Steven Shull
Projetech Inc.
------------------------------

​I can't work out if this relates to a WO generated from a PM or a manually created work order. 
If PM generated, a way to test this is to manually fire the PM and see what happens (probably using your test environment).
This will answer any questions on whether the work plans were copied or not when the WO was generated.  If that works okay, maybe reset the date and update the PMWOGEN cron to fire it - again this will indicate if it works okay.

Occasionally some data may be missing if there are specific issues with the job plan, but if this normally works manually, its unlikely to be a data error. during creation by the cron.

Do you have auditing turned on for work orders?  If so, and you have tasks, you may want to see if there are any records in A_WORKORDER where the PARENT value = your WO number.  Of course if between the job plan being applied, and the work plan being removed, the WO was never saved this will not help.

------------------------------
Brian Williams
Ineos FPS
------------------------------

Original Message:
Sent: 06-15-2021 08:52
From: Steven Shull
Subject: work plans didn't get copied from job plan attached on a work order

Is this a reoccurring thing or is this a one time occurrence? If a WO (including tasks) was never approved, tasks can be deleted even if they were copied in via job plan. That means it's possible a user deleted them.

You also mention that you don't have any logic for restricting the plans being copied. Can you confirm that you don't have job plan conditions enabled (under System Settings in the Organizations application) and that the JOBTASK.CONDITIONNUM field is null? I've seen where people have a condition that doesn't evaluate to true here but will evaluate to true on an existing record (because the way the condition is written it queries the database versus getting the in memory record). If this is occurring reliably for a given job plan when done on a background process (such as PM), this is where I'd probably start.

------------------------------
Steven Shull
Projetech Inc.
------------------------------

Hello Brian,

Thanks for your response.

This is a Manually created work Order.

Yes we have also checked A_WORKORDER where the PARENT value = our WO number but we couldn't find any records.



------------------------------
Meghana Siriveli
------------------------------

Original Message:
Sent: 06-15-2021 09:27
From: Brian Williams
Subject: work plans didn't get copied from job plan attached on a work order

​I can't work out if this relates to a WO generated from a PM or a manually created work order. 
If PM generated, a way to test this is to manually fire the PM and see what happens (probably using your test environment).
This will answer any questions on whether the work plans were copied or not when the WO was generated.  If that works okay, maybe reset the date and update the PMWOGEN cron to fire it - again this will indicate if it works okay.

Occasionally some data may be missing if there are specific issues with the job plan, but if this normally works manually, its unlikely to be a data error. during creation by the cron.

Do you have auditing turned on for work orders?  If so, and you have tasks, you may want to see if there are any records in A_WORKORDER where the PARENT value = your WO number.  Of course if between the job plan being applied, and the work plan being removed, the WO was never saved this will not help.

------------------------------
Brian Williams
Ineos FPS
------------------------------


Original Message:
Sent: 06-15-2021 08:52
From: Steven Shull
Subject: work plans didn't get copied from job plan attached on a work order

Is this a reoccurring thing or is this a one time occurrence? If a WO (including tasks) was never approved, tasks can be deleted even if they were copied in via job plan. That means it's possible a user deleted them.

You also mention that you don't have any logic for restricting the plans being copied. Can you confirm that you don't have job plan conditions enabled (under System Settings in the Organizations application) and that the JOBTASK.CONDITIONNUM field is null? I've seen where people have a condition that doesn't evaluate to true here but will evaluate to true on an existing record (because the way the condition is written it queries the database versus getting the in memory record). If this is occurring reliably for a given job plan when done on a background process (such as PM), this is where I'd probably start.

------------------------------
Steven Shull
Projetech Inc.