Fix Readme
Abstract
On 31 December 2024, IBM released IBM® Maximo® Asset Management 7.6.1.3 interim fix 027. 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 027 is available at Fix Central.
Maximo Asset Management 7.6.1.3 interim fixes incorporate Maximo Integration Framework fixes which were formerly released in a separate IBM Installation Manager package.
| APAR | Application Name | Description |
| DT276997 | Graphical Scheduling | "The system is taking too long to process your query" error in Graphical View on Graphical Scheduling application. |
| DT365479 | Graphical Work Week | Moving Assignments several times does not always update the scheduled Start and Finish dates in the Work Order. |
| DT392650 | Item Master | In Item Master, fetching a record that is part of an Item Assembly Structure with many Items takes longer than expected. |
| DT392986 | Count Book | Error in the Count Books application adding multiple BINs to a record. |
| DT393366 | Manage Inventory | The Inspection application only loads an Inspection Form when the site matches the user's SITEID. |
| DT394004 | Count Book | In the Count Books application, a user updating the Physical Count for multiple records at the same time causes the warning BMXAA8229W - "Record COUNTBOOKLINE : Site=BEDFORD Count Book Number=XXXX Bin=A1 Batch= Condition Code= Item=XXXX Asset= has been updated by another user.". to appear. |
| DT394743 | Purchase orders | Scenario: A user performs an Inspection one or more days after the Receipt date, but the Inspection Status date is the Receipt date. |
| DT395756 | Technician | In the Technician role-base application, using Quick Reporting to create a new Work Order against a Linear Asset causes an unexpected error. |
| DT395872 | Asset templates | Loading PLUSCTPASSET causes error BMXAA4176E - "Attribute LOCATION does not exist.". |
| DT395974 | Work Order Tracking | In Work Order tracking, entering an incorrect value in the Crew Work Group field causes the error BMXAA4176E - "Attribute AMCREWTYPE does not exist. Gather the logs from the directory and determine the process or app referencing the invalid attribute.". |
| DT396348 | Purchase requisitions | The Unit Cost on PRs created by Inventory Reorder is incorrect. |
| DT396836 | Purchase orders | A user approving a PO revision even though the revised PO no longer has a line for the obsolete item causes the message BMXAA5609I - "This action is not allowed since the item XXX is in Pending or Obsolete status at Item/Organization level." to display. |
| DT397378 | Failure codes | Selecting the Duplicate Failure Code action in the Failure Codes application does not use the Autokey value for the new Failure Code. |
| DT397488 | Assets | In the Assets application inside the Item Assembly Structure, when a user deletes an Item, clicking Autonumber All generates Asset numbers, but the Asset is still populated on the Spare Parts tab. |
| DT398133 | System UI | When a user Attaches a document that contains a double byte character in the file name, the error "The server has encountered an unknown error. Reload the application and try again. If the problem persists, contact your system administrator." displays. |
| DT398364 | Desktop Requisitions | In the Create Requisition application, the "Required Date" field in the MRLine object shows an incorrect time that doesn't align with the user's timezone. |
| DT399749 | Item Master | In Item Master, filtering records and no records are returned causes a DB connection leak in the psdi.app.item.Item canToggleRotating class. |
| DT399896 | Asset templates | Assets created from Asset Templates with Classification do not have values copied from the CLASSSPEC.CS01 attribute to the ASSETSPEC.ES01 attribute. |
| DT399996 | Purchase orders | When you create a purchase order revision with the Maximo Integration Framework and the line quantity is less than the received quantity, an error occurs. |
| DT400488 | Service requests | The record hover dialog for the Asset field in the Service Requests application does not show Asset Details when the record is saved, unless you specifically hover over the Asset Field first, before saving the record. |
| DT406925 | Scheduler | In Graphical Assignment , clicking Publish Scenario displays error BMXAA4214E - "An unknown error has occurred. Please contact your system administrator for assistance. Gather the logs from the |
| DT406953 | System Object | The swagger file is not valid when the parameter includeactions=1 is used to create it. |
| DT416547 | Job Plans | The default Job Plan status is not being used causing the Job Plan to not be displayed. |
| DT416585 | Preventive maintenance | In the Preventive Maintenance application, using the Set Reading At Last WO action to add New Reading values more than twice, the updated value will not be populated in the Meter Reading field. |
| IJ41708 | Integrity Checker | Running Integrity Checker in repair mode throws an exception due to auto-commit. |
| IJ47954 | Item Master | Importing data using the .xml file type does not work when the Maximum count in Object Structure is set to 0. |
| IJ50644 | Work Order Tracking | In Work Order Tracking, opening the Reference Points lookup for a Linear Asset with a large number of Asset features set up as reference points takes longer than expected. |
| IJ50702 | Assets | Loading the Asset list after clicking the drilldown function is slower than expected. |
| IJ50724 | Item Master | To Store Location Information is different when Rotating items is received and voided, before assets are created It is expected that void receipt line has the same to location RECEIVING (type HOLDING) as the initial receipt. |
| IJ50901 | Integration | Using the "$" character as a text qualifier causes import to fail. |
| IJ51328 | Database configuration | Unable to have more than 1012 columns on a DB2 11.5 table. |
IBM Control Desk environment interim fix information
- 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":"BU048","label":"IBM Software"},"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":"BU048","label":"IBM Software"},"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:
09 January 2025
UID
ibm17180489