IJ01902: DIFFERENT TIMEZONE SHOWS DIFFERENT RESULTS FOR THE SAME WO AND RESOURCES IN GRAPHICAL

APAR status

• Closed as program error.

Error description

• PROBLEM:  user timezone affects the calculation of planned
  labor hours
  PERFORMANCE ISSUE: N/A
  STEPS TO REPRODUCE:
  1. Login as a user with timezone set to Australia/Brisbane (GMT
  +10 DST/N) Brisbane
  2. Create a work order in Work Order Tracking application  e.g.
  'RES3'
  3.Set the schedule start date to be tomorrow at 10AM (e.g. 10AM
  falls within the 'DAY' shift)
  duration is 10 hours
  select "interruptible"
  select "DAY" as the interruptible shift
  4. Go to the Plans tab, no task work orders
  Enter 2 planned labor:  3 hours for CATER and 10 hours for MUSIC
  5. Go to Graphical Scheduling application, create a new
  schedule e.g.RES3
  Enter a work query to bring up work order 'DUPRES'
  Go to the "Gantt View" tab.
  Gantt Chart shows the interrupt (dark blue color shows the off
  shift hours)
  6. Go to the Resource tab on the bottom
  The available labor is tomorrow which is next available time
  for the labor (e.g. 'DAY' calendar, 'DAY' shift works Monday -
  Friday, 7AM - 3PM)
  NOTE: craft 'MUSIC' has a load of 10 hours and it didn't get
  split over 2 days (this is INCORRECT)
  7. Go to the "Cost and Usage" tab > "Resource Load and
  Availability" tab
  Planned labor hours show 7 hours for Cater and 14 hours for
  Music
  **  This seems incorrect.
  Planned labor hours should show 3 hours for Cater and 10 hours
  for Music (to be spread over 2 days since it's interrupted.)
  8. If I login as user 'wilson'  , timezone is set to
  Canada/Eastern (GMT - 5 DST/Y) Eastern Standard Time, then
  everything shows up correctly
  Bring  up the same Schedule in the Graphical Scheduling
  application
  Go to the Cost and Usage tab > Resource Load and Availability
  tab
  Planned Labor hours shows 3 hours for Cater
  Planned Labor hours shows 8 hours on Nov 15th and 2 hours on
  Nov 16th
  i.e. the labor hours got split due to the 8 hour shift (as
  expected)
  9. If I login as a user that belongs to the New Zealand
  timezone(GMT +12 DST/Y) Auckland, Wellington
  Go to the Cost and Usage tab > Resource Load and Availability
  tab
  Planned Labor hours shows 2 hours for Cater on Nov 15 and 1
  hour for Nov 16 (this is incorrect!  it should not be splitted
  over 2 days)
  planned labor hours shows 2 hours for Music on Nov 15 and 8
  hours for Music on Nov 16 (this is correct)
  10. If I login as user wilson and check the planned labor hours
  from the Cost and Usage tab > Resource Load and Availability
  tab, it will show Planned Labor hours shows 2 hours for Cater
  on Nov 15 and 1 hour for Nov 16 (this is incorrect!  it should
  not be splitted over 2 days)
  planned labor hours shows 2 hours for Music on Nov 15 and 8
  hours for Music on Nov 16 (this is correct)
  NOTE: the planned labor hours used to be correct previously
  when logged in as user wilson
  with timezone set to (GMT - 5 DST/Y) Eastern Standard Time
  CURRENT ERRONEOUS RESULT:   user timezone affects the
  calculation of planned labor hours
  EXPECTED RESULT: user timezone should NOT affect the
  calculation of planned labor hours
  ADDITIONAL INFO: N/A
  ENVIRONMENT (SYSTEM INFO):  TPAE 7.6.0.8
  LOCAL FIX: N/A
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Users on 7608 or using a specific application         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Users from 7608 experienced odd results when using GS on     *
  * timezones different from current scheduler tz, this behavior *
  * is not verifiable on later releases                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• No changes necessary, the issue is not verifiable on this
  release
  

Temporary fix

Comments

APAR Information

• 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

• R765 PSY

     UP