IBM Support

Maximo Asset Management interim fix 010 released

Technical Blog Post


As with all interim fixes, Maximo Asset Management interim fix 010 is cumulative. It contains all fixes from earlier interim fixes, with the addition of new fixes listed in this post.


Tivoli's process automation engine interim fix 010 is available at Fix Central.


Application Name



Graphical Assignment

In Graphical Assignment (GA) application, when you set up the street level routes cron task to apply SLRs in the background, the cron task looks for GRPASSIGN instead of RLASSIGN. The Select SLR dialog returns empty.


Conditional Expression Manager

In the Conditional Expression Manager application, when you upgrade to Maximo Asset Management Interim Fix 007, SIGOPTION conditions no longer work.



In the Crews application, when you modify the crew availability, all fields in the Modify Crew Availability dialog box show invalid binding.


Cron Task Setup

In the Cron Task Setup application, in a clustered environment, when you set mxe.crontask.donotrun = ALL, and perform a live refresh, an error occurs.


Graphical Scheduling

In the Graphical Assignment application, if you select Move to Today for an assignment or a work order that is not scheduled for the current day or the following day, the assignment or work order is moved to the following day, not to the current day.


Graphical Assignment

In the Graphical Assignment application, on the Dispatch tab, when spatial is selected as the map provider, routes do not work.


Graphical Crew Management

In the Graphical Crew Management application, when you select the Previous Day, Next Day, or Toggle View buttons, an error occurs.


Graphical Scheduling

In the Graphical Scheduling application, when you move a PM, the Save button does not undim and the row does not turn red.


Graphical Scheduling

In the Graphical Scheduling application, when you toggle between scenarios, an error occurs.


Graphical Scheduler

In the Graphical Scheduling application, when you use Next Schedule or Previous Schedule while you view a Schedule, the start of the date ribbon for the subsequent schedules is not used.


Graphical Scheduling

In the Graphical Scheduling application, when you use different time zones, craft availability is displaced by one day for some shifts.



In the Install application, when you run maxinst, an error occurs.


Integration Modules

In the Integration Modules application, the REST API does not return all the FAILURELIST records.


Inventory Usage

In the Inventory Usage application, when you create a new inventory usage record and change the status to complete, the INVRESERVE record for line 1 is deleted.


Inventory Usage

In the Inventory Usage application, you try to issue an item that has two condition codes, an error occurs.



In the Invoices application, when you create invoices from the Maximo UI, the GL Debit Account is not set correctly on the invoice line.


Job Plans

In the Job Plans application, when job plan labor is associated to a contract, it is not possible to revise a job plan and associate it to a valid labor contract.


Job Plans

In the Job Plans application, when you duplicate a job plan and view the status history on the new record, it keeps the status date of the original job plan.


Purchase Orders

In the Purchase Orders application, when the default insert site is not the same is the purchase orders site, revising the purchase order causes an error.



In the Receiving application, when you select return an item to vendor, the CONSIGNMENT field displays 0 when it is 1.


Report Administration

In the Report Administration application, when you use the custom date parameter DISPLAYDATE for a non-base language, the date parameters get corrupted.



In the Report application, rich text fields are vulnerable to cross-site scripting (XSS).



In the Report application, when you run a report with a user ID containing a '\' character, an authentication error occurs.


System User Interface

In the Users application, under Security Restrictions, when over 1000 security restrictions exist, Maximo may encounter errors expanding the UI tree.


Work Order Tracking

In the Work Order Tracking application, when a Work Order exists in multiple sites and you try to set the Labor status to Inactive, an error occurs.


System Object

When the LDAPSYNC cron task runs, it does not sync the home phone number for users who do not have a work number. The following error occurs: BMXAA4129E - The record for Person=YYYYY, Phone=XXX-XXX-XXX, Type=HOME already exists.


Create Requisition

In the Create Requisition application, when you use the select value lookup from either the Requested By or Request For fields, an error occurs. 


Object Structures

In the Object Structures application, when you import ASSETSPEC data, the imported NUMVALUE value is rounded.

IBM Control Desk uses Tivoli's process automation engine This interim fix can be applied to Control Desk

For product compatibility, see Control Desk, Maximo and Tivoli's process automation engine version compatibility.

To install, see Installing an Interim Fix in Maximo 7.6.

[{"Business Unit":{"code":"BU005","label":"IoT"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""},{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"SSWT9A","label":"Control Desk"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]