IBM Support

IJ01989: FORECAST DATES ARE NOT CALCULATED CORRECTLY WHEN THE PM HAS SEASONAL DATES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Forecast dates are not calculated correctly when the PM has
    seasonal dates.
    
    STEPS TO REPLICATE:
    1. Create a new PM - assign to it an asset and a job plan
    2. Frequency tab:
    Frequency: 1
    Frequency Units: MONTHS
    Estimated Next Due Date: 8 November 2017
    3. Seasonal Dates tab:
    Active Days -> check the checkboxes for all week days.
    Active Dates:
    Start Month: November
    Start Day: 1
    End Month: November
    End day: 30
    4. Save and activate the PM
    5. Select Action -> Generate Forecast:
    Forecast for (Days): 900
    Result: Forecast tab -> there is only one row for next year,
    when there
    should be at leats 2, one for November 2018 and one for
    November 2019
    as 900 days from now means April 2020.
    
    the client also tried to set the seasonal dates as follows:
    Start Month: JULY
    Start Day: 1
    End Month: AUGUST
    End Day: 31
    and generated the forecast for the next 900 days.
    The result is July 2018, August 2018 and there should be
    entries for
    July 2019 and August 2019 as well.
    
    Maximo 7608
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * FORECAST DATES ARE NOT CALCULATED CORRECTLY WHEN THE PM HAS  *
    * SEASONAL DATES                                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.1.0 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ01989

  • Reported component name

    PREVENTIVE MAIN

  • Reported component ID

    5724R46PM

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-17

  • Closed date

    2018-01-09

  • Last modified date

    2018-01-09

  • 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

    PREVENTIVE MAIN

  • Fixed component ID

    5724R46PM

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Prev Maint

Software version: 760

Reference #: IJ01989

Modified date: 09 January 2018