Technical Blog Post
Abstract
As with all interim fixes, Maximo Asset Management 7.6.0.7 interim fix 009 is cumulative. It contains all fixes from earlier interim fixes, with the addition of new fixes listed in this post.
Body
Tivoli's process automation engine 7.6.0.7 interim fix 009 is available at Fix Central.
| APAR |
Application Name |
Description |
|---|---|---|
| IV92442 |
Assets |
In the Assets application, when you open the Spatial Layer tool, performance is reduced. |
| IJ01119 |
Classifications |
In the Classifications application, when you import a classification that adds or updates the CLASSSPECUSEWITH.DEFAULTTABLEVALUE attribute, the import fails. |
| IV97882 |
Preventive Maintenance |
In the Preventive Maintenance application, when a work order is created from a meter reading, the counter for the PM record is not reset. |
| IV99817 |
Quick Reporting |
In the Quick Reporting application, you cannot enter or add meter readings. |
| IJ00156 |
Receiving |
In the Receiving application, after a purchase order revision, the Received Cost value is incorrect. |
| IV92122 |
Work Order Tracking |
In the Work Order application, child work orders do not inherit the status of their parent work order. |
| IJ02048 |
Database Configuration |
When you import a view that includes a UNION ALL in the where clause into Maximo Database Configuration, attributes are not properly defined, preventing a successful import. |
| IJ02044 |
Assets |
In the Assets application, the Status field on the Select Asset dialog box does not consider your organization. |
To install, see Installing an interim fix in Maximo 7.6.
UID
ibm11113375