Maximo Open Forum

 View Only
  • 1.  Crossover domain from Route Stop to WO

    Posted 10-09-2023 04:51

    Hi,

    I'm trying to setup a crossover domain to copy certain field from Route Stop to WO when generating WO from a PM which has a Route attached, but it doesn't work. Any help or suggestion would be highly appreciated. Maximo version is 7.6.1.3.

    Here is what I did:

    • Created a Route RT1 with three stops which will become Child Work Orders
    • Attached the Route RT1 to a PM, PM1
    • Created a Crossover Domain RT2WO with the following setup:
      • Object: ROUTE_STOP
      • Validation Where Clause:
        route = :route and siteid = :siteid and routestopid = :routestopid
      • Source Field = DESCRIPTION (from ROUTE_STOP)
      • Destination Field = WORKTYPE (to WO)
    • Attached the Crossover Domain RT2WO to the field ROUTESTOPID in table WORKORDER and applied configuration changes
    • Tried to generate WO from PM1 I get the message "BMXAA4196E - Attribute Route must be set before Route Stop can be set."

    Any idea what I'm doing wrong?

    Thank you,
    Dragos


    #EverythingMaximo

    ------------------------------
    Dragos Chitu
    EL
    ------------------------------


  • 2.  RE: Crossover domain from Route Stop to WO

    Posted 10-10-2023 20:08

    Hi Dragos,

    I'm missing the bit as to what you're trying to achieve.  I have this information

    • The route is going to have x number of stops
    • Each stop will be a child work order
    • On each stop, you have entered the value which is the worktype.
    • For each child route work order, you want to copy from the new field to the WORKORDER.WORKTYPE field

    Firstly, please do not use the description field for the worktype. Instead, use one of the spare crossover fields which are still around such as ROUTE_STOP.RTS1 goes to WORKORDER.WORTS1.  You should attach a lookup to the ROUTE_STOP.RTS1 so the values are aligned to the worktype.

    I'm going to guess that the error is because the timing of the work order creation.  If you move to the existing crossover, then conceptually it can only be populated when the child work order has been created.

    Hopefully, that simple change will work for you.



    ------------------------------
    Regards,
    Craig Kokay
    ISW
    Maximo Practice Manager
    eMail: ckokay@isw.net.au
    Phone: +61-411-682-040

    #IBMChampion2023
    ------------------------------



  • 3.  RE: Crossover domain from Route Stop to WO

    Posted 10-11-2023 01:42

    Hi Craig,

    Thank you for your reply! I think you got it right: for each child work order I'm trying to have a different work type.

    I agree with you that the description field is not the right one for holding work type info, but I wanted just to make a test. In the end I would need to have information from multiple fields from the ROUTE_STOP table copied over to fields in WORKORDER table at the time of work order creation. And the information regarding work type won't be put in the description. But before creating more fields in ROOUTE_STOP table I wanted to see that it's working at least with one.

    Now, it's not clear for me where I have to attach the crossover domain that I've created. To ROUTE_STOP.RTS1 field? Could you please clarify?

    On the other hand, I do not understood what should I move, to which existing crossover. Could you please clarify as well?

    Thank you,

    Dragos



    ------------------------------
    Dragos Chitu
    EL
    ------------------------------



  • 4.  RE: Crossover domain from Route Stop to WO

    Posted 10-12-2023 19:19

    Hi Dragos

    ROUTE_STOP.RTS1 goes to WORKORDER.WORTS1.  For this to happen you just have to add the data to the route stop, then add the route to the work order where the crossover will occur.  Now the second part of using this technique will be to have a crossover on WORKORDER.WORTS1 to WORKORDER.WORKTYPE.

    Of course, the alternative is to create an automation script



    ------------------------------
    Regards,
    Craig Kokay
    ISW
    Maximo Practice Manager
    eMail: ckokay@isw.net.au
    Phone: +61-411-682-040

    #IBMChampion2023
    ------------------------------



  • 5.  RE: Crossover domain from Route Stop to WO

    Posted 10-13-2023 10:37

    Hi Craig,

    Thank you for the clarifications!

    Tried the solution that you proposed, but I was not yet successful: 

    Here is what I did:

    • added field RTS1 to Route application (to make RTS1 visible and editable);
    • populated RTS1 field with work type values;
    • changed Crossover Domain RT2WO with the following setup:
      • Object: WORKORDER
      • Validation Where Clause:
        wonum = :wonum and siteid = :siteid
      • Source Field = WORTS1
      • Destination Field = WORKTYPE
    • attached the Crossover Domain RT2WO to the field ROUTESTOPID in table WORKORDER (I'm not sure if this is correct), and applied configuration changes
    • tried to generate work orders from PM, I get the error message: 
      • BMXAA4191E - The value 1 is not valid for Route Stop. Specify a valid value for Route Stop.

    I even tried to edit Lookup Map of the field ROUTESTOPID in the table WORKORDER as follows:

    • Target Attribute: ROUTESTOPID
    • Source Object: ROUTE_STOP
    • Source Key: ROUTESTOPID

    Still, no luck. When trying to generate the WOs I'm getting the same error message: 

      • BMXAA4191E - The value 1 is not valid for Route Stop. Specify a valid value for Route Stop.

    Any idea what I'm doing wrong? Should I attach the RT2WO domain to other field?

    Thank you,

    Dragos



    ------------------------------
    Dragos Chitu
    EL
    ------------------------------