IBM Support

IJ08473: PM FORECAST DOES NOT CONSIDER THE VALUE OF PMFORECAST.NEWDATE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Adding a new date in case of Forecast Date the report should
    consider the New Date and should give the desired output. After
    generating the Forecast you can see that the report only takes
    the value of the Forecast Date.
    STEPS TO REPLICATE:
    Prerequiste steps.
    Go to Report Administration application and bring up the report
    projected_pm_labor.rptdesign
    Enable tickbox on radio button on  field: "Use Both Parameter
    Options?"
    Save and Generate Report Request Pages
    1. Create Job Plan 10219 and saved the record
    2. Add Craft : LINEMEK and Labor : BABERG and give hours as
    1.00 and 2.00 respectively. Change the Status to Active.
    3. Create a new PM : 21291 and add the Job Plan into it.
    4. On Frequenct tab, add Frequency as 6 MONTHS and add
    estimated Next Due Date as 03/08/2018.
    5.Change the status to ACTIVE.
    6. From Action menu, select Generate Forecast and set Forecast
    for 350 days in the "Forecast for (Days)" field. The Forecast
    Unit will auto populate with a date: 17/07/19
    Once you submit the request a dialog messasge will be displayed:
    "BMXAT0019l - Forcasting for PM 21291 in site BEDFORD
    successful."
    On the Forecast tab the following is displayed
    Forecast Details
    ================
    Forecast Date | Job Plan
    --------------|---------
    01/08/18      | 10219
    --------------|---------
    01/02/19      | 10219
    7. Run the report projected_pm_labor.rptdesign from Run Reports
    under More Actions
    8. On the Request Page, Parameters, enter 50 days in * Number
    of Weeks field.
    This gives the results expected.
    Projected PM Labor Requirements
    Number of Weeks: 50
    One Graph is displayed:
    PM Forecast by Week
    Labor Hours: 3.00
    Week 25
    Clicking next page arrow displays the following:
    Projected PM Labor Requirements
    Number of Weeks: 50
    Week: 25
    Total Hours: 3
    Line 1:
    Craft: ELECT
    Skill Level: FIRSTCLASS
    Hours: 2.00
    Line 2:
    Labor: WILSON
    Hours: 1.00
    9. Close the report and go back to Forecast tab in PM
    application
    Now we need to change the Forecast Date and add New Date as
    14/08/2018.
    10. Focus cursor into the New Date field on the first line in
    Forecast Details section for Forecast Date: 01/08/18
    11. Change the Forecast Date and add New Date as 14/08/2018.
    Forecast Details
    ================
    Forecast Date | Job Plan New Date
    --------------|---------|-----------
    01/08/18      | 10219   |14/08/2018
    --------------|---------|-----------
    01/02/19      | 10219
    12. Run the report projected_pm_labor.rptdesign same a step 8.
    Unexpected Results:
    Comparing the previous report run to this second run, the
    reports are both identical with same result as seen after step
    8.
    The second run of the report does not reflect any changes, i.e.
     it has not taken into
    consideration the New Date and the report showed the same
    result.
    Expected Results:
    The second report run should not show anything extra as the gap
    is 6 months to generate the next forecast.
    The Graph entry for "PM Forecast by Week" should be empty and
    their should be no Line entries for Craft and Labor.
    Environment:
    Tivoli's process automation engine 7.6.0.9-IFIX20180227-1319
    Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-02
    

Local fix

  • Dev to provide fix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Projected PM Report users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * NEWDATE in PM Forecasting not taken into account for         *
    * reporting purposes.                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Import latest report design.                                 *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IJ08473

  • Reported component name

    BIRT INTEG-REPO

  • Reported component ID

    5724R46B1

  • Reported release

    760

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-15

  • Closed date

    2018-11-14

  • Last modified date

    2018-11-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
BIRT

Software version: 7.6

Reference #: IJ08473

Modified date: 14 November 2018