Fix Readme
Abstract
On 29 December 2023, IBM released IBM® Maximo® Asset Management 7.6.1.2 interim fix 040. 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
Interim fix 040 is the final interim fix released for Maximo 7.6.1.2.
Tivoli's process automation engine 7.6.1.2 interim fix 040 is available at Fix Central.
| APAR | Application Name | Description |
| IJ49454 | Integration | IBM Maximo Asset Management is vulnerable to Information Disclosure. |
| IJ49218 | Assets | Specification Attributes are doubled when an Asset is duplicated. |
| IJ49199 | Inventory usage | Auto Split is not working as expected for a Rotating Item of cost type Asset. |
| IJ48910 | Purchase orders | When the quantity in the PO/PR line is set to 0, the Unit cost and line cost are changed to 0. However, the tax value, loaded cost, and header cost values (pretaxtotal) are not updated. |
| IJ49065 | Scheduling Alternate Resources | In Scheduling Alternate Resources, attempting to delete an unused resource results in error BMXAT1066E - "The default alternate availability cannot be removed.". |
| IJ48905 | Assets | When you issue a Rotating Tool to a Work Order at a different Site, then return it to the originating storeroom but into a different bin, Maximo does not update the Asset bin correctly. |
| IJ48723 | Assets | A user cannot change an Asset status from Inactive to Decommissioned. |
| IJ48640 | Data Sheets | The Date Sheet look-up in the "Attach Datasheets" dialog box displays a description, but the description field is blank selecting it. |
| IJ48283 | Item Master | Adding an item results in errors BMXAA7136E - "Validation failed when the database default values were set. See the associated message for more information." and BMXAA7831I - "Do you want to apply the tax-exempt status to the organization level for the item, and to the vendor level for the item?". |
| IJ48261 | Work Order Tracking | When a user exits Edit Mode with unsaved changes, the user is redirected to the List tab and the result list is cleared. |
| IJ47261 | Work Order Tracking | Adding a Material with insufficient quantity to a Work Order's does not update Task Status. |
| IJ47112 | Inventory usage | In Inventory Usage lines, tabbing to the New Physical Count field and clicking Enter sets the value to 0.00. |
| IJ46151 | Integration | Using MIF or Application Import to update serialnum field for assets that have a groupname results in error BMXAA8665W - "Do you want to allow sequence number duplication?". |
| IJ45613 | Location | Changing a Location within the hierarchy to an Ancestor above it in the hierarchy and when that Ancestor is a Facility causes missing records in the LOCANACESTOR table. |
| IJ45327 | System UI | Forcing an error during the Add New Attachment operation with a .zip files results with the file uploaded, even if the operation is cancelled. |
| IJ45093 | System UI | In a UNC Path configuration, Doclinks are not working. |
| IJ44914 | Scheduler | In Graphical Scheduling, "Select All Tree Grid" doesn't work as expected. |
| IJ44663 | Drilldown | When Extended drill-down is enabled, the Location drill-down does not work correctly in the Service Request application. |
| IJ43913 | System UI | It is difficult for Maximo users with red/green color blindness to tell that long description boxes have more information. |
| IJ39810 | System UI | Popup modals are not handled correctly in Screen Reader. |
| IJ36219 | Database configuration | Increasing the number of Tax types in Database Configuration when audit is enabled for that object results in error BMXAA0596E - "A row cannot be added because this object is not editable.". |
| IJ35144 | Login | After a user logs out of the Service Request Work Center when LDAP is enabled, a blank screen appears |
| IJ33268 | UpdateDB Utility | drop_app dbc script is not deleting records from CTRLGROUP and SIGOPTFLAG. |
The final Maximo Integration Framework 7.6.1.2 interim fix is MIF interim fix 023.
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
[{"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"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1","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","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
29 December 2023
UID
ibm17103639