IJ05580: GA - WHEN THE MXE.SKD.SYNCWODATES IS SET TO 1 THE SCHEDULE END DATE NOT MOVING WHEN ASSIGNMENT ADDED WITH A DATE PAST DATE

APAR status

• Closed as program error.

Error description

• PROBLEM: When the mxe.skd.syncwodates is set to 1 the Schedule
  end date not moving when assignment added with a date past
  existing sched end date
  STEPS TO REPRODUCE:
  Pre Conditions
  - create a WO - planned labor of 4 hours - not interruptible
  - move to assignment tab
  - change the assignment to 2 hours and assign a labor -
  assignment date tomorrow 7 am
  - create a new assignment same labor 2 hours - but assign on
  the next day
  - notice the sched start/end dates adjust as you add dates
  Steps To Reproduce
  -  create another WO for 4 hours
   - go to GA - create a work list for this one WO
    - drag and drop assignment to Finley - split in half
  and assign second half the next day
    - Save
    - go back to WOT and notice that the sched end has not
  changed as it should
  CURRENT ERRONEOUS RESULT:  : The Schedule End dates did't
  changed at the Work Order - Assignment as we expected
  EXPECT Result: The hours should be sync with the Assignments.
  ADDITIONAL INFO: NO
  ENVIRONMENT (SYSTEM INFO):
  App Server Weblogic Application Server 12.1.1.0
  Version
  Tivoli's process automation engine 7.6.0.9-IFIX20180330-1643
  Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-04
  IBM TPAE Integration Framework 7.6.0.9 Build 20171127-2330 DB
  Build V7609-32
  IBM Maximo Asset Management Scheduler Plus 7.6.7.0 Build
  20171127-0100 DB Build V7670-01
  IBM Maximo Asset Management Scheduler 7.6.7.0 Build
  20171127-0100 DB Build V7670-56 HFDB Build HF7670-12
  IBM Maximo Asset Management Work Centers 7.6.0.3 Build
  20171121-0723 DB Build V7603-175
  Server OS Windows Server 2012 R2 6.3
  Server DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
  Release 11.2.0.3.0 - 64bit Production With the Partitioning,
  OLAP, Data Mining and Real Application Testing options)
  (c) Copyright IBM Corp. 2017
  LOCAL FIX: N/A
  SECURITY IMPACT (Y/N): N
  

Local fix

• Disable the mxe.skd.syncwodates property
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * maximo scheduler users                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When the mxe.skd.syncwodates is set to 1 the Schedule        *
  * end date not moving when assignment added with a date past   *
  * existing sched end date                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixpack  Release 7.6.1.0 of Base Services (Scheduler   *
  * 7671)or request an interim fix                               *
  ****************************************************************
  

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(Scheduler 7671)
  

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

• R767 PSY

     UP