IBM Support

IV93038: GRAPHICAL ASSIGNMENT - DISPATCH TAB DOESN'T SHOW WORK ORDERS ON THE MAP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Graphical Assignment - Dispatch Tab doesn't show work orders on
    the map
    Tivoli's process automation engine 7.6.0.6 Build 20161019-0100
    DB Build V7606-50
    IBM TPAE Integration Framework 7.6.0.6 Build 20161014-1504 DB
    Build V7606-24
    IBM Maximo Asset Management Scheduler 7.6.4.0 Build
    20161019-0100 DB Build V7640-51
    
    The steps to replicate.
    1) In Map Manager,  configure a bing Map.
    2) Create 3 service addresses for testing.
    - 1001
    Formatted address:  250 York St, London, ON N6B 1P8, Canada
    Latitude : 42.9833900000
    Longitude : -81.2330400000
    make sure that location is shown in the map.
    -SASTART
    Formatted address: 1116 Mahogany Rd, London, ON N6H 5C3, Canada
    Latitude : 42.9657019899
    Longitude :-81.3139343192
    - SAEND
    Formatted address: 1554 Allen Pl, London, ON N5W 2V8, Canada
    Latitude : 42.9975832509
    Longitude -81.1944580008
    3) Go to the Work Zones application.
    create a work zone (WZ1) with ZONE1 work zone type.
    save
    4) Go to the locations application
    create a location : TESTLOC1
    set service address : 1001
    In work zones tab, add WZ1 work zone.
    make sure that location is shown in the map.
    create a location : STARTLOC
    set service address : SASTART
    In work zones tab, add WZ1 work zone.
    make sure that location is shown in the map.
    create a location : ENDLOC
    set service address : SAEND
    In work zones tab, add WZ1 work zone.
    make sure that location is shown in the map.
    5) Go to the Asset application
    create an asset : TESTAS1 with TESTLOC1
    set service address : 1001
    Calendar : DAY
    Shift : DAY
    make sure that asset location is shown in the map.
    6) Go to the Labor applicaiotn.
    Open   BARRY, BARRY2
    calendar/shift : day/day
    start location : TESTLOC1
    end location : TESTLOC1
    Save Location with Work Order? : checked.
    In work zones tab, add WZ1 work zone.
    7) Go to the WOTRACK application
    create a new WO  : RH2
    Location : TESTLOC1
    asset : TESTAS1
    service address :1001
    Target Start/Sched Start date : 02/02/17 9:00 AM
    Duration : 8
    In Plans/Labor tab, add new line
    - Craft : MECH
    - Skill Level ; FIRSTCLASS
    - Quantity : 1
    - Regular Hours : 8
    In Assignments Tab,   set Laborcode with BARRY.
    Save
    create a new WO  : RH3
    Location : TESTLOC1
    asset : TESTAS1
    service address :1001
    Target Start/Sched Start date : 02/02/17 9:00 AM
    Duration : 8
    In Plans/Labor tab, add new line
    - Craft : MECH
    - Skill Level ; FIRSTCLASS
    - Quantity : 1
    - Regular Hours : 8
    In Assignments Tab,   set Laborcode with BARRY2.
    Save
    8) Go to Graphical assignment application
    Create a new Work Order list
    work list : TESTWL5
    Calendar/Shift : DAY/DAY
    In Work Queries,  set Data source as WORKORDER.
    - where condition -> wonum in ( 'RH2','RH3')
    In Resource :   set data source as LABOR
    - where condition ->  laborcode in ( 'BARRY','BARRY2')
    save
    Click  more actions/ Apply Street Level Routes
    Then, Click Dispatch Tab,
    You may be able to see WO's location in the map. But. sometimes
    not.
    2/2/17 0:57:57:528 EST] 00149c8c SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] Dispatch: loadProject:
    project: 15, addShift: false, resObj: null, resKey: null
    [2/2/17 0:57:57:528 EST] 00149c8c SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] Dispatch: loadProject(15),
    using cached model
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] Resource LABOR:BARRY
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] range start: Thu Feb 02
    09:00:00 EST 2017
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] range end  : Thu Feb 02
    12:00:00 EST 2017
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] shifts 2
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] , Wed Feb 01 07:00:00 EST
    2017-Wed Feb 01 15:00:00 EST 2017
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] , Thu Feb 02 07:00:00 EST
    2017-Thu Feb 02 15:00:00 EST 2017
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] []
    NO INTERVAL
    [2/2/17 0:57:57:528 EST] 00000842 SystemOut     O 02 Feb 2017
    00:57:57:528 [DEBUG] [MAXIMO] [] No shift info for LABOR:BARRY
    in this time interval
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo Scheduler users on 764 Release on Graphical           *
    * Assignment application.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Work Orders are not shown on the Map of the Dispatch View in *
    * the Graphical Assignment application.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix has been delivered to correct the observed issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV93038

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    764

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-02

  • Closed date

    2017-02-14

  • Last modified date

    2017-02-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

  • R764 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"764","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
14 February 2017