IBM Support

IJ03904: RESTRICT WORK TO DATES (AND ALSO ROLLING PROJECT) SHOULD NOT CHECK THE TARGET DATES IF THE SCHEDULE DATES EXIST.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Restrict Work To Dates (and also Rolling Project) should not
    check the Target Dates if the Schedule Dates exist but the
    Target Dates are used.
    If Schedule dates exist for a WO, then only those dates should
    be used for deciding if the WO should be included for the
    Restrict Work To Dates checkbox or the Rolling Project
    selection.   If those dates do not exist, then Target dates
    should be checked.   But the Target dates
    are being used even if the Schedule dates exist.
    
    I am not sure about the rules of using other dates on the WO
    such as Actual dates.
    
    Reproduced in 7.6.0.8 and in 7.6.0.9.
    
    STEPS TO REPRODUCE:
    
    1. Make a WO with a Scheduled Start of next Monday, such as
    1/29/18, and a Target Start of 2 Mondays from now, such as
    2/5/18, and a Duration of 4.
    2. Create a new Schedule with a Start Date that is on a day
    inbetween the WO's Schedule Start Date and its Target Start
    Date, such as 2/1/18.
    3. Check the Restrict Work To Dates checkbox.
    4. Give it a Work Query that selects the WO created above.
    5. Save.
    
    At this point you should see the message that there are no WO
    for the Schedule as Restrict Work To Dates should eliminate the
    WO created above based on its Schedule Start date but it does
    not eliminate it, it is looking at the Target Date when it
    should only do that if a Schedule Start date does NOT exist.
    
    The Gantt View will appear and show the WO but it should have
    been eliminated.
    The same is true when using Rolling Project which also selects
    which WO should appear based on the dates of the WO.
    

Local fix

  • (none)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO SCHEDULE USERS                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Restrict Work To Dates (and also Rolling Project) should not *
    * check the Target Dates if the Schedule Dates exist but the   *
    * Target Dates are used.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixpack  Release 7.6.1.0 of Base Services 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
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ03904

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    765

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-05

  • Closed date

    2018-02-21

  • Last modified date

    2018-02-21

  • 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



Document information

More support for: Maximo Asset Management Scheduler

Software version: 765

Reference #: IJ03904

Modified date: 21 February 2018