IBM Support

IJ33550: ERROR ON CALCULATE PM COST WHEN PREVENTIVE MAINTENANCE RECORDS WITH SAME NUMBER EXIST IN 2 DIFFERENT SITES

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

  • An error is displayed when trying to use "Calculate PM Cost"
    action in "Graphical Scheduling" application. This is happening
    when two Preventive Maintenance records with the same name exist
    in two different sites.
    
    STEPS TO REPRODUCE:
    1. Go to Preventive Maintenance application
    2. Create one Preventive Maintenance record on the BEDFORD site
    3. Create one Preventive Maintenance record on the HARTFORD site
    
    4. Generate a forecast for 2 years for both Preventive
    Maintenance records
    5. Go to Graphical Scheduling application.
    6. Create a schedule for the Preventive Maintenance record in
    BEDFORD site
    7. Go to Cost and Usage tab and PM Forecast Cost sub-tab
    8. Click on Calculate PM Cost
    
    RESULT:
    
    Error is displayed
    BMXAT0048E - The activities did not populate. For more
    information, check the Maximo log file (in your application
    server directory)
    or contact your system administrator. One or more values in the
    INSERT statement, UPDATE statement, or foreign key update caused
    by a DELETE statement are not valid because the primary key,
    unique constraint or unique index identified by "2" constrains
    table "MAXIMO.SKDPMFOCOSTTEMP" from having duplicate values for
    the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.26.14
    
    EXPECTED RESULT:
    
    Cost to be calculated
    
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenancepackage:
    Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ33550

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-07-01

  • Closed date

    2021-07-20

  • Last modified date

    2021-07-20

  • 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

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

Document Information

Modified date:
21 July 2021