Special attributes available for crossover domain
QiupingMao 270002GCBJ Comments (3) Visits (13019)
Recently a blog was written for hidden features of crossover domain. This blog talks about a couple of special attributes in Maximo created specifically for crossover domain use. As was mentioned in the earlier blog, the concept of crossover domain is simple. It is a way to trigger something to happen when an attribute is being populated. Do you want to know how you can crossover values from pm to the work order hierarchies which pm generated? How you can crossover additional values from ticket and work order to workview?
How you can crossover values from pm to the work order hierarchies which pm generated?
Maximo’s PM work order generation process sets the PMNum attribute of the generated work order. But, it does not do so for the tasks nor any of the Route/Nested Job Plan children, 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 ( Tpae 7504 and before have this as tasks only and Tpae 7505 and after supports non-tasks like route-stops see APAR IV38979), and therefore it can trigger the crossover domain to happen. Note: this attribute is only filled in during work order creation during PM Work Order Generation. Now rhat you know this special attribute exists, setting up a crossover domain is simple. Let’s say we create a crossover domain PM2WO from PM. The validate where clause should be “(pmnum=:pmnum or pmnu
How can you crossover additional values from ticket and work order to WORKVIEW?
The WORKVIEW table stores information from work order and ticket records, so we cannot simply use record key to crossover values from work order and ticket. To be able to crossover values from work order or ticket, Maximo has two non persistent attributes, ticketid and wonum. The ticketid is set when the workview record is for a ticket, and wonum is set when the workview record is for work order. Unlike the above PM scenario, these values are set on both insert and update of a WORKVIEW record. If client wants to crossover some values from the ticket to WORKVIEW, they can create a crossover domain, let’s say TK2WKVIEW with a validate where clause of “ tick
the domain should be associated with WONUM on WORKVIEW.