Fix Readme
Abstract
On 31 January 2023, IBM released IBM® Maximo® Asset Management 7.6.1.3 interim fix 0043. 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.3 interim fix 004 is available at Fix Central.
| APAR | Application Name | Description |
| IJ44620 | Database configuration | Users with Language and Locale in Maximo set to non-English receive an error downloading delta Lookup Data only in Anywhere Technician. |
| IJ44274 | Desktop Requisitions | Users encounter error BMXAA1758E in the Inventory Usage application. |
| IJ43547 | Logging | Loggers fail to write log entry for automation scripts after log4j upgrade. |
| IJ44572 | Logging | Maximo logging does not take inheritance into account. It logs to one valid appender, not all valid appenders in the hierarchy. |
| IJ44370 | Work Order Tracking | "Change Work Order status in background" does not work as expected for non-English languages. |
| IJ44453 | Inventory | The Maximo-x Manage Inventory application does not display entries in the Storerooms Counts when the Domain is updated with a new synonym. |
| IJ43818 | Work Order Tracking | An Automation Script with attribute launch point does not execute when the value for Long_description field is cleared. |
| IJ44504 | Routes | Can't navigate beyond the first 20 Assets from the route (Multi Asset Location section) referenced on a WO viewing the WO in Work Execution Work Centers Multi Asset section. |
| IJ39223 | Work Packages | "Duplicate Work Order Hierarchy" does not copy the safety plans for child work orders. |
| IJ44255 | Purchase orders | Attempting to approve a Purchase Order results in errors BMXAA3279E - "Could not change PO status to APPR" and BMXAA4146E - "Not a valid GL account". |
| IJ32864 | System UI | Double quotation marks at the beginning of an error message display incorrectly as duplicated double quotation mark. |
| IJ40848 | Report | BIRT Reports display blank output when emojis are present in description. |
| IJ37934 | Preventive maintenance | A Preventive Maintenance record's status can be changed despite missing UI required data (Estimated Next Due Date), leading to erroneous Work Order generation. |
| IJ40660 | Condition Codes | Adding a LIFOFIFO condition enabled item on a Job Plan, the condition code value list lookup is not populating the values. |
| 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. |
| IJ36443 | Work Order Tracking | Completing an assignment in the Work Order Tracking application returns error BMXAA8229W. |
| IJ40095 | Ticket Templates | If the DATATYPE Domain is a duplicate, the 'Submit a Service Request' Work Center does not load some Specifications from Ticket Template after an upgrade |
| IJ41699 | Assets | Shipment releases Asset with Ancestor but without Parent. |
| IJ35277 | Report | Two reports were accidentally included in Maximo: budgetprint_2axes.rptdesign and contrpurch_print_act.rptdesign. |
| IJ43387 | Inspection | Conduct an Inspection pulls incorrect Location when WONUM and MULTIID are the same. |
| IJ42549 | Graphical Resource View | The calendar view in Graphical Resource View is not auto populated correctly. |
| IJ41701 | Inventory usage | Items that are marked as both Consigned and Capitalized are showing a nonzero cost on Inventory Usage and Work Order Actuals. |
| IJ41252 | Purchase Contracts | The default table data storeroom price is used instead of the purchase contract price. |
| 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). |
| IJ40524 | Create Requisition | Duplicating a Purchase Requisition leaves the "Issue on Receipt?" checkbox cleared, even though there is a value in Work Order field. |
| IJ40313 | Work Center | A script with an attribute launch point on INSPFIELDRESULT.NUMRESPONSE is not displaying a message when the value entered on the inspection field is out of range. |
| IJ40183 | Escalations | In the Escalations application, the SQL Expression Builder displays more classifications that necessary. |
| IJ38131 | Work Order Tracking | In the Inventory application, Unit/Actual Cost fields are incorrect when information is changed before the record is saved for Actuals/Material on a work order. |
| IJ37877 | Inspection | Inspection form for the wrong organization is attached to Work Order. |
| IJ24576 | Database configuration | The default index Maximo created for a new Object is created on the Maximo data tablespace, not the Index tablespace. |
| IJ39858 | System UI | When the focus is changed to a different tab by using the left and right arrow keys, the contrast between the text and background does not meet usability standards. |
| IJ43397 | Work Order Tracking | Work Order can be changed to an incorrect status by the WOMaterialStatusUpdateCronTask or the Update Material Status button. |
| IJ41841 | Conduct an Inspection | Unable to use an inspection form where there is only a location associated with a work order. |
| IJ39803 | Crews | Crew assignment status for a tool assignment shows OK when the asset is decommissioned. |
| IJ36062 | Service Request | The GL Account option at the Service Request Work Center doesn't go to the Location associated with the Ticket. |
| IJ39018 | Manage Inventory | When a user with a locale of en_CA creates a Pick List in Manage Inventory Work Center, they receive error BMXAA4144E - "The date/time format is not valid". |
All Maximo Integration Framework fixes are incorporated into Maximo Asset Management 7.6.1.2 interim fixes.
IBM Control Desk 7.6.1.3 and 7.6.1.4 use Tivoli's process automation engine 7.6.1.2. Apply interim fixes for Maximo Asset Management 7.6.1.2 to IBM Control Desk 7.6.1.3 and 7.6.1.4.
IBM Control Desk 7.6.1.5 uses Tivoli's process automation engine 7.6.1.3. This interim fix can be applied to IBM Control Desk 7.6.1.5.
Related Information
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m50000000CbP7AAK","label":"Install-\u003EFixpack"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1"},{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"ARM Category":[{"code":"a8m500000008b3TAAQ","label":"Miscellaneous Category (Portal, UI, Maximo, Install)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1"}]
Was this topic helpful?
Document Information
Modified date:
19 February 2024
UID
ibm16891147