IBM Support

IJ32076: ISSUE WITH ASSETS WITH THE SAME ASSETNUM

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When there are two assets with the same ASSETNUM, but different
    SITEID, the assets have associated the same meter and a work
    worder is generated from a PM with meter based frequency for
    one of the assets, the WOMETER table is populated with meter
    reading reference for the other asset.
    STEPS TO
    REPRODUCE:
    1.	Open the Assets application and create a new
    asset for site BEDFORD:
    a.	Asset: TESTASSET, Test asset
    Bedford
    b.	Click on tab Meters and add the meter RUNHOURS. Fill
    in the mandatory attributes than save
    c.	Change status to
    OPERATING
    2.	Click on Profile>Default Information and change
    Default Insert Site: MCLEAN, Storeroom Site for Self-Service
    Requisitions: MCLEAN
    3.	Create a new asset for site
    MCLEAN:
    a.	Asset: TESTASSET, Test asset MCLEAN
    b.	Click on tab
    Meters and add the meter RUNHOURS. Fill in the mandatory
    attributes than save
    c.	Change status to OPERATING
    4.	Open the
    Preventive Maintenance application and create a new
    PM:
    a.	Asset: TESTASSET, Test asset MCLEAN
    b.	Click on tab
    Frequency, sub-tab Meter Based Frequency
    c.	Click on New Row,
    enter the meter RUNHOURS, Frequency:100
    d.	Save
    5.	Change
    status to Active
    6.	Open the assets application and the open
    the asset TESTASSET, Test asset Bedford
    7.	Click on tab Meters
    and enter a meter reading of 100 hours
    8.	In SQL run a SELECT
    statement against table METERREADING for ASSETNUM=TESTASSET and
    SITEID=BEDFORD. Take a note of the field:
    METERREADINGID
    9.	Open the Preventive Maintenance application
    and open the PM Test asset MCLEAN
    10.	Click on Generate Work
    Orders
    11.	Uncheck Use Frequency Criteria?, then click
    OK
    12.	Take a note of the work order generated for the asset
    from the site MCLEAN
    13.	Run a SQL SELECT statement for table
    WORKORDER, WONUM= with the WO number created
    14.	Notice that
    the METERREADINGID matches the METERREADINGID for the asset
    from the Bedford site
    RESULT:
    The workorder table is populated
    with data for a different asset
    EXPECTED RESULT:
    The workorder
    table should populated with data for the asset from the
    PM
    REPORTED IN VERSION:
    Tivoli's process automation engine
    7.6.1.1
    

Local fix

  • Go into Database Configuration, open the record for PMMeter,
    and change the relationship "METERREADING" (from PMMeter to
    MeterReading) to "assetnum=:assetnum and metername=:metername
    and siteid=:siteid".
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ISSUE WITH ASSETS WITH THE SAME ASSETNUM                     *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ32076

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-13

  • Closed date

    2021-06-21

  • Last modified date

    2021-06-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 ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
22 June 2021