I would like to auto-populate persistent classification level columns in the WORKORDER table - via the WO classification.

• WOL1
• WOL2
• WOL3
• WOL4
• (these are OOB WORKORDER columns)

Is it possible to auto-populate level columns via a crossover domain (and OOB relationships)?
Or would this require the use of Maximo formulas or an autoscript?

An OOB solution would be preferred over an autoscript, since OOB is more likely to be accepted by my technical team.
Thank you.
7.6.1.2
#Maximo
#AssetandFacilitiesManagement

#AssetandFacilitiesManagement
#Maximo

Nowadays, I would do this with Automation Script as it is a lot more flexible and easier to deploy and easier to keep track of source code changes with source control. But if Crossover is what your client prefer, try the following steps:

1. Go to DB Config, set all WOL1,L2,L3,L4 to ALN (100) as OOTB they have different data types.
2. Open ClassStructure object, add the following two relationships:
   - Relationship1:
      + Name: GPARENT
      + Child Obj: ClassStructure
      + Where: classstructureid = (select parent from classstructure where classstructureid=:parent)
   - Relationship 2:
      + Name: GGPARENT
      + Child Obj: ClassStructure
      + Where: classstructureid = (select parent from classstructure where classstructureid = (select parent from classstructure where classstructureid= '1336'))
3. Create a CrossOver Domain:
   - DomainID: ZZWOCLASSSTRUCT
   - Object: ClassStructure
   - Add the following Crossover Field mappings:
      + Source: Description - Destination: WOL1   
      + Source: PARENT.Description - Destination: WOL2
      + Source: GPARENT.Description - Destination: WOL3
      + Source: GGPARENT.Description - Destination: WOL4
4. Associate that ZZWOCLASSSTRUCT to the ClassStructureID field of the Work Order Object.

The data will be copied every time the user changes Classification.

Couple of notes:
- Not sure if the WOL1,2,3,4 are OOTB cross-over in Java (i.e. in certain scenarios, for example, associate Asset, Location, or generate from PM, there are some OOTB logic that copy certain fields from these sources to Work Order. If that's the case, you'll have to choose different custom fields)
- If you want it to work with Task, you may need to set the cross over to WOACTIVITY view too





------------------------------
Viet Tran
------------------------------

Related:

Parse out values from a custom persistent hierarchy path column (using SQL & registered expressions):

classl1 = trim(regexp_substr(hierarchypath, '[^\]+', 1, 1)),

classl2 = trim(regexp_substr(hierarchypath, '[^\]+', 1, 2)),

classl3 = trim(regexp_substr(hierarchypath, '[^\]+', 1, 3)),

classl4 = trim(regexp_substr(hierarchypath, '[^\]+', 1, 4));


More info here:
Parse delimited string via Oracle SQL/regex (example: parse GL)

#AssetandFacilitiesManagement
#Maximo