Thanks to Julio for this very comprehensive explanation of what Maximo actually does in this case.
I am guessing that now User1971 is asking how to prevent users from taking the actions as described in Craig's post if this indeed will cause these issues.
The first thing that comes to mind is to make the Job Plan field read only if the ISTASK is =1 - this should prevent a job plan being applied.
Secondly do a similar thing with the New Row button on the tasks table if the parent work order ISTASK=1
Julio, If the task work order does not currently have any transactions associated e.g. PRLINE, POLINE, MATUSETRANS etc would allowing these actions still be an issue?
In all cases it may be easier/safer to just prevent these actions and if a task on a work order cannot be completed and you need to perform this work at a later date then using the follow up work order process would be the best option.
------------------------------
Steve Lee
Maximo Technical Sales Specialist
IBM
Leeds
------------------------------
Original Message:
Sent: Fri October 16, 2020 01:57 PM
From: Julio Hernandez
Subject: Convert task to child work order?
Trying to "promote" a Task to a Child WO by simply changing IsTask from 1 to 0 is dangerous. When a Task is "promoted" by adding a Task directly or through a Job Plan, the IsTask value is not the only thing that changes. The TaskID will be NULLed out and the WOGroup, which is set to the Parent when IsTask is 1, will be changed to the WONum. And as already pointed out by someone, the WOClass will remain WOACTIVITY. That means that the WO will continue to appear in the "Activities and Tasks" application.
Allowing Tasks to be promoted is a bad idea in any case. It will create problems if records such as PRLine, LabTrans, MatUseTrans, etc. have been already been created with the EnteredAsTask flag set to 1. These types of records store the WONum of the WO that is being charged in a RefWO fields. The screens that display these types of records look up the WorkOrder record for the RefWO and populate the non-persistent WONum and TaskID fields based on the EnteredAsTask value. When creating one of these records, the EnteredAsTask is set to 1 if a value is entered in the TaskID field and the RefWO is set to the WONum of the WorkOrder records where the Parent and TaskID match the values entered in the non-persistent WONum and TaskID fields. When displaying an existing record with EnteredAsTask set to 1, the system will set the non-persistent WONum and TaskID fields to the Parent and TaskID of the Reference WO respectively. If the Task was promoted after the record was created, the Task on the Reference WO will be NULL making it appear as if the transaction was charging the Parent WO.
For this reason, I strongly discourage clients from allowing Tasks to be promoted. Doing so is also a prerequisite if the client wants to implement intelligent WONum for Tasks where the WONum is the Parent + "-" + TaskID which makes integration with other applications much easier.
#AssetandFacilitiesManagement
#Maximo