IBM Support

IV87861: 7604-PREVENTIVE MAINTENANCE JOB PLAN SEQUENCE COUNTER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:
    
    Maximo Asset Management Version 7.6.0.4 on Windows 6.3 Server
    OS,
    Microsoft SQL Server 11.00.2100.
    
    When I generate work orders for a number of days in advance
    that uses
    multiple different job plan sequences, the counter advances by
    only 1.
    The correct job plans are used, and the correct number of work
    orders
    are generated, but the counter does not display correctly until
    I go
    back to the list view, refresh the list, and return to the PM.
    At that
    point the sequence number is correct, but it should display
    correctly
    immediately after generating the work orders.
    
    
    PERFORMANCE ISSUE: NO
    
    STEPS TO REPRODUCE:
    
    Steps to replicate in the OOB Utilities 7.6.0.4
    
    1) Create a new PM Record.
    2) Include an asset.
    3) Include a jobplan.
    4) Go to tab Frequency ans set frequency = 1, frequency Units =
    DAYS,Estimated Next Due date = Today .
    5) Save the record.Change Status to ACTIVE.
    6) Go to More Actions / Generate Workorder
    7) In the genaration Workorder BoX set Generate WOs Due Today
    Plus This
    Number of Days = 10, Check the box "Use Frequency
    Criteria?" to yes. Then Click Ok.
    
    Result: Maximo will Generate 11 workorders, and the filed
    Counter is
    updated to 8.
    
    If you copy the Pm number, go to List View, Select again the Pm
    record.
    The field Counter will be updated from correct value 11.
    
    CURRENT ERRONEOUS RESULT:
    Maximo  PM Generated 11 workorders, and the filed Counter is
    updated to 8.
    If you copy the Pm number, go to List View, Select again the Pm
    record.
    The field Counter will be updated from correct value 11.
    
    
    EXPECTED RESULT:
    Maximo  PM Generated 11 workorders, and the filed Counter is
    updated to 11 automatically.
    
    ENVIRONMENT (SYSTEM INFO):
    
    App Server IBM WebSphere Application Server 8.5.5.3
    IBM Maximo Asset Management 7.6.0.4 Build 20160316 DB Build
    V7605-37
    IBM TPAE Integration Framework 7.6.0.4 Build 20160313-2330 DB
    Build
    V7604-22
    IBM Maximo Spatial Asset mangement 7.6.0.0 Build 20160311 0241
    DB Build
    7600-61
    Tivoli's process automation engine 7.6.0.4 BUild 20160310-1641
    DB Build
    v7604 -01
    
    Server OS Windows 6.3
    Server DB Microsoft SQL Server 11.0 (11.00.2100)
    
    (c) Copyright IBM Corp.2015
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users using PMWoGen to generate multiple future work orders. *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When "Generate Work Orders" is executed, the UI is not       *
    * correctly refreshed upon closing of the dialog box.          *
    * PM.Counter and PM.NextDueDate will display incorrect values  *
    * until the record is refetched.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                          | Release 7.6.0.7 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV87861

  • 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

    2016-08-11

  • Closed date

    2016-10-26

  • Last modified date

    2016-10-26

  • 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

  • R750 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCHPN7","label":"Prev Maint"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":""}]

Document Information

Modified date:
26 October 2016