IBM Support

IJ03973: COSTS ARE ADDED FOR DIFFERENT SITE IN SCHEDULER WHEN SERVICE PROVIDER APPLICATIONS ARE USED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment :
    
    App Server  IBM WebSphere Application Server 8.5.5.4
    Version  Tivoli's process automation engine 7.6.0.7 Build
    20170215-0100
    DB Build V7607-14IBM TPAE Integration Framework 7.6.0.7 Build
    20170130-
    1250 DB Build V7607-03IBM Maximo for Service Providers 7.6.3.0
    Build
    20170221-2101 DB Build V7630-21IBM Maximo Asset Management
    Scheduler
    7.6.4.0 Build 20170215-0100 DB Build V7640-53IBM Maximo Asset
    Management Work Centers 7.6.0.1 Build 20161104-1046 DB Build
    V7601-
    41IBM Maximo Asset Management 7.6.0.7 Build 20170215-0100 DB
    Build
    V7604-01
    Server OS  Windows 6.3
    Server DB  DB2/NT64 10.5 (SQL10054)
    
    ACTION TAKEN :
    
    Problem Description :
    ===
    It looks like Planning and Scheduling module has a problem with
    multisite. I will show you how to repeat the problem in
    Graphical
    Scheduling application but please double check if this king of
    problem doesn t exists in other applications like: Graphical
    Assignment, Graphical Assignment-Repair, Graphical Crew
    Management
    ===
    
    Replication Steps:
    
    1. Go Work Order Tracking (SP) application and create a new
    workorder
    in site BEDFORD
    1.1 Work Order Details Tab
    Work Order: 1596
    Class: WORKORDER
    Scheduled Start: 22.11.2017 19:28
    Scheduled Finish: 23.11.2017 15:28
    Duration: 5:00
    1.2 Go to Plans Tab and add a new Labor
    Craft: CARP
    Skill Level: FIRSTCLASS
    Quantity: 1
    Regular Hours: 5
    Rate: 18,00
    1.3. Change work order status to APPR.
    1.4 Go To Actuals tab and add a new labor
    Labor: ADAMS
    Craft: CARP
    Skill Level: FIRSTCLASS
    Start Date: 23.11.2017
    Regular Hours: 10
    GL Debit Account: 6000-100-000
    GL Credit Account: 6000-100-000
    
    2. Go To Graphical Scheduling application and create New
    Schedule
    Type: WORK
    Start Dat
    e: 22.11.2015 0:00
    End date: 11.10.2019 0:00
    Rolling Project: Uncheck
    Calendar: DAY
    Shift: DAY
    Organization: EAGLENA
    2.1 Add Work Queries
    Data Source: WORKORDER
    Query Name: TEST
    Where condition (please observe that in the sql condition we
    have wonum
    that was created):
    wonum = '1596' and (woclass = 'WORKORDER' or woclass =
    'ACTIVITY') and
    (status = 'APPR' or status = 'INPRG') and historyflag = 0 and
    siteid =
    'BEDFORD' and istask = 0
    2.2 Go To Work Cost tab and press calculate cost. Check that
    the cost
    from work order that was created for BEDFORD side is there.
    
    3 Go To Work Order Tracking (SP) application and create WO but
    this time for MCLEAN site. Double check that you have the same
    value in WONUM for both sites.
    (default insert site will be changed)
    3.1 Work Order Details Tab
    Work Order: 1596
    Class: WORKORDER
    Scheduled Start: 22.11.2016 19:28
    Scheduled Finish: 23.11.2016 15:28
    Duration: 5:00
     Go to Plans Tab and add a new Labor
    Craft: CARP
    Skill Level: FIRSTCLASS
    Quantity: 1
    Regular Hours: 5
    Rate: 18,00
    Line Cost: 90
    3.2 Change work order status to APPR.
    3.3 Go To Actuals tab and add a new labor
    Labor: ADAMS
    Craft: CARP
    Skill Level: FIRSTCLASS
    Start Date: 23.11.2016
    Regular Hours: 10
    GL Debit Account: 6000-100-000
    GL Credit Account: 6000-100-000
    
    4. Go To Graphical Scheduling that was created in step 4 and
    select Refresh Schedule  option.
    4.1 Go To Work Cost tab and press  Calculate Cost  button. You
    will see
    that cost from MCLEAN site was added and this is a bug
    according to the
    client.
    
    Exoectation :
    ---
    Expectation is that when you are working with BEDFORD site in
    Planning and Scheduling module then you shouldn't see data from
    other sites (for example from MCLEAN).
    ---
    
    
    We think that it should work this way because we added siteid
    attribute
    in sql query in where condition.
    ---
    
    (Scheduler, Service Providers and TPAE involved)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * maximo scheduler users                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Actual COSTS ARE ADDED FOR DIFFERENT SITE IN SCHEDULER WHEN  *
    * SERVICE                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fix has been made to fix....The fix for this APAR is contained
    in the following maintenance package:
    		 | release\fix pack\interim fix for  Release 7.6.1.0 of Base
    Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ03973

  • Reported component name

    SERVICE PROVIDE

  • Reported component ID

    5724R46SV

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-07

  • Closed date

    2018-03-22

  • Last modified date

    2018-03-22

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

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

Fix information

  • Fixed component name

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
22 March 2018