IJ07356: PM HIERARCHY CHILD PM MOVE TO NEXT DAY NOT REFLECTED IN GRAPHICAL SCHEDULING RESOURCES

APAR status

• Closed as program error.

Error description

• When a PM with a PM hierarchy is forecasted, the resources from
  the PMs in the hierarchy are not updated and the start and end
  date are incorrect.
  
  STEPS TO REPRODUCE:
  
  1. We will first need 3 job plan records, each job plan should
  be for a different craft (this makes it easier when in GS) for
  the job plans use labor hours of 4, 1 and 3 on each job plan.
  
  2. We will now create 3 PM records, attach 1 job plan created
  earlier to each PM. Update the frequency as needed for each.
  Decide which of the 3 will be the parent and under the
  hierarchy tab add the other 2 remaining PMs. From the parent
  record approve the PM and make sure to roll the changes down to
  all the records.
  
  4. Forecast the PM out for 60 days.
  
  5. In the Graphical Scheduling application create a new
  schedule, add the calendar shift, under the work queries
  section add a new row and change the data source to PM.
  
  6. Add the parent PM number we ran the forecast on earlier.
  Move the Gantt view tab, change the date to one day ahead of
  what is listed there. Notice that the parent has a new start
  date but the end date remains the same, check the child
  record and notice that none of those dates changed when they
  should have.
  
  
  PRODUCT VERSION:  Maximo 7.6.0.9 with Scheduler 7.6.7
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of Graphical Scheduling in Scheduler 7.6.7.            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PM HIERARCHY CHILD PM MOVE TO NEXT DAY NOT REFLECTED         *
  * INGRAPHICAL SCHEDULING RESOURCES                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A code fix has been delivered.
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO SCHEDULE

• Fixed component ID

  5724R46SE

Applicable component levels