Fix Readme
Abstract
On 30 December 2022, IBM released IBM® Maximo® Asset Management 7.6.1.2 interim fix 028. As with all interim fixes, it is cumulative. In addition to the new fixes listed here, all fixes from earlier interim fix releases for this Feature Pack are included.
Content
Tivoli's process automation engine 7.6.1.2 interim fix 028 is available at Fix Central.
| APAR | Application Name | Description |
| IJ44376 | Install / Upgrade | In Maximo Asset Management 7.6.1.3, if base language is not English, UpdateDB fails. |
| IJ43820 | Work Order Tracking | Receiving a payload to update MATUSETRANS when the Maximo property 'mxe.app.inventor.updateReservations' is set to 1, results in error BMXAA8229W - "Record INVRESERVE: has been updated by another user. Your changes have not been saved. Refresh the record and try again." |
| IJ44151 | Graphical Assignment | In Spatial Scheduling Scenario dat files, the parameter "Allow Secondary Work Zone Assignment" is always false and the parameter "Match Work Zone" is always true. |
| IJ44163 | Map Manager (Spatial) | Username and Password login window displays opening Map in Maximo with an external url. |
| IJ44243 | Work Supervision | Setting the zoom percentage to 70% or smaller creates a blank section to appear following the Record page in the Work Supervision work center. |
| IJ44123 | Work Order Tracking | Data is not reflected correctly in Assignments updating from Crafts to Crew. |
| IJ43951 Manual change correction |
Security | For more information about a security vulnerability, see IBM X-Force Exchange. |
| IJ44070 | Work Order Tracking | WOMATSTATUSSYNC creates an entry with user's default insert org instead of the record's org. |
| IJ44014 | Graphical Scheduling | In Graphic scheduling, rescheduling a Work Order, the UPDATEWPMATREQDATE setting is ignored, resulting in no change to the Material's Required Date. |
| IJ43912 | System UI | Users receive error BMXAA4214E filtering on the Print column in the View Attachments dialog. |
| IJ43789 | Inventory usage | In the Inventory Usage application, returning an item can incorrectly result in error BMXAA7704E - "The inventory usage lines 1, relate to a deleted inventory reservation. Do you want to proceed with the status change for these lines?". |
| IJ42077 | System Object | Technician application's query for MXAPIINVBAL Object Structure is incorrect. |
| IJ42062 | Assets | Map Manager's Edit tool does not work on layers with an ID greater than 1000. |
| IJ41841 | Conduct an Inspection | Unable to use an inspection form where there is only a location associated with a work order. |
| IJ41701 | Inventory usage | Items that are marked as both Consigned and Capitalized are showing a nonzero cost on Inventory Usage and Work Order Actuals. |
| IJ41510 | Drilldown | Work Order Tracking Drilldown selects the wrong Asset. |
| IJ41230 | Security | For more information about a security vulnerability, see IBM X-Force Exchange. |
| IJ41050 | Preventive maintenance | In Condition Monitoring from PMNUM fields, Go To Preventive Maintenance doesn't find PM if priority on MEASUREPOINT differs from PM priority. The same issue exists with the JPNUM fields and Job Plans. |
| IJ41130 | System properties | Cannot save imglib to S3 Storage. |
| IJ40875 | Integration | When the Status is changed using MIF, and CHANGEBY information is sent, Maximo does not use the value sent in the transaction to fill the CHANGEBY field in the WORKORDER and WOSTATUS tables. It uses the logged-in user who sent the transaction. |
| IJ40729 | Receiving | In the Receiving application, changing the inspection status of an Item causes the GL Debit Account field (MATRECTRANS.GLDEBITACCT) to be different from the Account number in the GL Debit Account field in Purchase Orders (POLINE.GLDEBITACCT). |
| IJ40848 | Report | BIRT Reports display blank output when emojis are present in description. |
| IJ40524 | Create Requisition | Duplicating a Purchase Requisition, the Issue on Receipt? checkbox is cleared even though there is a value in Work Order field. |
| IJ40167 | Crews | Requirement Status shows NOT QUALIFIED when there are more assigned labor that has the qualification than the required quantity. |
| IJ39803 | Crews | Crew assignment status for a tool assignment shows OK when the asset is decommissioned. |
| IJ38843 | Database configuration | Wrong relationship in ASSET table on INSPECTIONRESULT. |
| IJ38929 | Graphical Work Week | In the Graphical Work Week application, assigning a task that has no Planned Labor results in the error BMXAT1118W - "This labor is assigned to a crew and not available". |
| IJ38063 | Budget Monitoring | In an environment with a very large number of Work Order and LABTRANS records, updating Budget Lines causes error "BMXAA7387E - While attempting to retrieve 100001 of LABTRANS, the operation was terminated because the preset limit of 10000 was exceeded for retrieving LABTRANS into a single set. Reduce the number of selected objects for the operation.". |
| IJ37813 | Cron Task Setup | Error messages are written to reorder logs for multiple instances of the ReorderCronTask for Direct Issue reorders. |
| IJ37563 | Inventory usage | Performing a reconciliation on a Staged item results in an incorrect total balance. |
| IJ37704 | Database configuration | The where clause for relationship QUERY.MAXUSER finds the MAXUSER record for the current user, but the description says it finds the owner of the query. |
| IJ37247 | Report | In MEASUREMENT table when multiple records are present with same POINTNUM but different sites, measurement information from different site appears in report. |
| IJ37519 | Assets | Receiving error BMXAA6713E changing a rotating item in Asset application. |
| IJ37278 | Shipment Receiving | The wrong usage line is automatically brought up in Shipment Receiving. |
| IJ36443 | Work Order Tracking | Completing an assignment in the Work Order Tracking application returns error BMXAA8229W. |
| IJ34793 | Conditional Expression manager | Sig Options were not being evaluated correctly on table rows resulting in error BMXAA2256E - "Field Value is read-only.". |
| IJ32864 | System UI | Double quotation marks at the beginning of an error message display incorrectly as duplicated double quotation mark. |
| IJ32109 | Graphical Scheduling | In Graphical Scheduling, filtering resources a second time causes Work Orders records not to display. |
| IJ22118 | Inventory | Upgrading Maximo 7.6.0.8 environment to Maximo 7.6.1.1 increases the length of data attribute INVENTORY.NEWCOSTTYPE from 16 to 23. |
Correction to manual change instructions for APAR IJ43951
<filter-mapping>
<filter-name>ReportRequestFilter</filter-name>
<url-pattern>/report/*</url-pattern>
</filter-mapping>
Just after
<filter-mapping>
<filter-name>ReportRequestFilter</filter-name>
<url-pattern>/output/*</url-pattern>
</filter-mapping>
Files to change:Interim fix 016 for Maximo Integration Framework 7.6.1.2 is also available at Fix Central.
| APAR | Application Name | Description |
| IJ42743 | Integration | Message tracking incorrectly reports unprocessed messages in RECEIVED status. |
| IJ41320 | Integration | HTTP query fails when synchronous message tracking is enabled. |
| Security bulletins first remediated in this interim fix |
The most recent Maximo Integration Framework 7.6.1.2 interim fix is MIF interim fix 016.
IBM Control Desk 7.6.1.2 uses Tivoli's process automation engine 7.6.1.1. Apply interim fixes for Maximo Asset Management 7.6.1.1 to IBM Control Desk 7.6.1.1.
IBM Control Desk 7.6.1.3 and 7.6.1.4 use Tivoli's process automation engine 7.6.1.2. This interim fix can be applied to IBM Control Desk 7.6.1.3 and 7.6.1.4.
Related Information
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
ibm16852245