Maximo PM work order generation process does not set the PMNUM attribute for its tasks nor any of the child Work orders created by Route/Nested Job Plan.
We are therefore not able to use PMNUM to crossover values from PM to all levels of work orders the PM generated.
But, PMs can have routes and a job plan, and routes can have route-stops, and job plans can have nested job plans, etc.
To be able to crossover values from PM attributes all the way down to PM generated work order hierarchies, Maximo has a special, non persistent attribute called NewTaskParentPMNum which is associated with WORKORDER and it’s views WOACTIVITY, WOCHANGE and WORELEASE.
This attribute is set to PMNUM on all work orders generated by PM.
Solution:
1. Create a new cross over domain similar to PM2WO and set the condition as "pmnum=:NewTaskParentPMNum and siteid=:siteid and orgid=:orgid”.
Map PM.PMNUM to WORKORDER.PM in this domain.
2. Attach it to attribute WORKORDER.NEWTASKPARENTPMNUM
3. When child task workorders are generated by PM, it will set PMNUM from the parent PM
An extract from below link:
https://goo.gl/Tuvk6U
We are therefore not able to use PMNUM to crossover values from PM to all levels of work orders the PM generated.
But, PMs can have routes and a job plan, and routes can have route-stops, and job plans can have nested job plans, etc.
To be able to crossover values from PM attributes all the way down to PM generated work order hierarchies, Maximo has a special, non persistent attribute called NewTaskParentPMNum which is associated with WORKORDER and it’s views WOACTIVITY, WOCHANGE and WORELEASE.
This attribute is set to PMNUM on all work orders generated by PM.
Solution:
1. Create a new cross over domain similar to PM2WO and set the condition as "pmnum=:NewTaskParentPMNum and siteid=:siteid and orgid=:orgid”.
Map PM.PMNUM to WORKORDER.PM in this domain.
2. Attach it to attribute WORKORDER.NEWTASKPARENTPMNUM
3. When child task workorders are generated by PM, it will set PMNUM from the parent PM
An extract from below link:
https://goo.gl/Tuvk6U
Hi,
ReplyDeleteWe are unable to generate child workorders from PM when we select a route having route stops as child workorders instead of task workorders.
Getting below error:
BMXAA4191E - The value TEST is not valid for parent pmnum. Specify a valid value.
Task workorders are generating fine from PM.
Can you please suggest something.
As noted in the reference link, the error may be related to APAR IV38979. Can you please try the same thing in version 7.5.0.5
DeleteHi,
ReplyDeleteMy client is using maximo 7.1.1.7 base version and we are trying to implement the same scenario. We have 4 custom fields in PM which needs to carry over to parent and then to child work orders created from PM Routes. The above example is for higher version, could you please suggest me any other work around for this.
Appreciate your help.
Thanks in advance.
Please customize your mbo s for your requirement.
Delete