Maximo Asset Management 7.6.0.5 interim fix 014 released

Automation Scripts

In automation scripts, the implicit variable scriptName in log.info, causes an error.

Graphical Assignment

In the Graphical Assignment application, when you use the Mass Modify action, the Start Time, End Time, and Hours fields are also updated.

Graphical Scheduling

In the Graphical Scheduling application, in Gantt view, you can save data even if you do not have save access.

Inventory

In the Inventory application, when you transfer a balance to a new bin, the current balance is doubled.

Invoices

In the Invoices application, you cannot approve a multi-line invoice that is associated to a repair if a rotating asset is in the repair location.

Purchase Orders

In the Purchase Orders application, when you use the Change Vendor from PO action, the tax code from the old purchase order is aplied to an invoice.

Receiving

In the Receiving application, when you create an escalation to update MODELNUM from the MATRECTRANS table to the INVENTORY table, the escalation trigger does not update the MODELNUM attribute.

Work Order Tracking

In the Work Order Tracking application, spatial map control gives erroneous results in the logs.

Report Viewer

Some reports are still listed as running after they have completed their execution.

Cron Task Setup

The parameters for the AsyncScheduledJobCron cron task are not valid.

Cron Task Setup

There are intermittent null pointer exceptions in the system out log.

Graphical Assignment

When the default browser language is set to French, in Gantt view, Maximo prints incorrect reports.

Work Order Tracking

The actual material cost attribute on the work order table is incorrectly calculated.