Fix Readme
Abstract
On 31 August 2023, IBM released IBM® Maximo® Asset Management 7.6.1.3 interim fix 011. 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 011 is available at Fix Central.
APAR | Application Name | Description |
IJ47848 | Install/Upgrade | After successfully installing Maximo 7.6.1.3 interim fix to a functioning Maximo Multi-Tenancy 7.6.1.3, Maximo does not start. The error is BMXAA6425E - "The server was not deleted from the Maxsession table MXServer. Log out and then log in again to refresh your database connection.". |
IJ45265 | Assets | If the Location is in a Primary System, then it cannot have more than one Rotating Asset based on Rotating Item mentioned in the Rotating Item field in the Location record. If a user tries to associate more than one Asset with the Location, the message BMXAA0137E - "Location XXXXX is currently occupied by Asset YYYYY" appears. The same is not true for non-Primary Location, which can have more than one Rotating Assets. |
IJ46845 | Crafts | Creating a craft in the Crafts application results in error BMXAA2528E. |
IJ47446 | Receiving | If multiple receipts for a Pay On receipt PO are voided, multiple total and tax Invoice Transactions are created. |
IJ47442 | Graphical Scheduling | In Graphical Scheduling, the Priority column displays "0" instead of an empty value for Work Orders where the Duration is NULL (empty field). |
IJ46539 | Domains | Physical Count Adjustment dialog box shows all records, rather than the ones selected in the List tab. |
IJ44633 | System UI | Scenario: The user has an extra-wide display. Running a BIRT report with the SiteID field results in error BMXAA3556E - "SiteID is a required field.". |
IJ47339 | Service Request | In the Service Request application, selecting "Update Field with Current Value" on the Result Set dialog box does not populate Service Address values in the TKSERVICEADDRESS Maximo Business Object (mbo). |
IJ47336 | System UI | Cannot generate Warranty Claims from Work Order Tracking. |
DT216046 | Work Order Tracking | Duplicating a Work Order with its Hierarchy, when SAFETYPLANID field has a value in all Work Orders in the Hierarchy, results in error BMXAA4211E - "Database error number -803 has occurred when operating on WOSAFETYPLAN.". |
IJ44342 | Integration | Revising a Purchase Order by using the Maximo Integration Framework (MIF) removes RFQ references on PO Lines. |
IJ44466 | Preventive maintenance | After removing a Feature from an Asset, Feature data remains in the Preventive Maintenance record. |
IJ46628 Behavioral Change |
System Object | Maximo does not support IBMJCEPlus FIPS. |
IJ46747 | Inventory usage | In the Inventory Usage application, changing the Status to Shipped results in error BMXAA4195E - "A value is required for the Packing Slip field on the SHIPMENT object.". |
IJ46227 | Purchase Contracts | The next Purchase Contract Revision cannot be created if the previous Revision is in a custom status of Canceled (CAN), and this status is not set up as default in Domain status. |
IJ46408 | System UI | For more information, see IBM X-Force Exchange. |
IJ45639 | Database configuration | See the Maximo Fix Pack 7.6.1.3 upgrade failure due to missing class FldIoTMappingProperty techdoc. |
IJ45588 | Purchase requisitions | If the Default Vendor is not used creating a Purchase Requisition for a Consignment Item, the PRLINE is not added. |
IJ45847 | Graphical Scheduling | In the Graphical View of the Graphical Scheduling application, the white bars corresponding to the Maintenance Schedule of the Asset are not visible. |
IJ42754 | Work Order Tracking | Error ORA-01722 occurs when InspectionResult records exist with non-numeric value in ReferenceObjectID. |
IJ44695 | Database configuration | Using Database configuration to increase the DESCRIPTION attribute length in the WORKORDER object does not work. Entering and saving text longer than 100 characters results in error BMXAA4049E. |
IJ39616 | Work Order Tracking | Moving an Asset across sites in the Work Order Tracking application results in error BMXAA0154E - "Open Work Order exists for the Asset XXXXX. Close/Cancel the Work Order XXXX before moving the asset and its assemblies.". |
IJ40623 | People | "Modify Person Availability" results in error BMXAA3089E - "Start time, end time, work hours, and reason code are required to modify availability." even when required values are entered. |
IJ32490 | Work Order Tracking | On a Work Order with multiple Hazards, deleting one hazard, saving, then deleting or modifying a tag-out on another Hazard error causes the error message BMXAA4650E to be displayed upon saving the record. |
Behavioral change with fix to IJ46628
This fix adds a new System Property mxe.security.app.session.keylength property. The default value is 1024. Modify the application session keylength when longer values are called for; for example, after modifying the WebSphere java.security file security.provider for FIPS to com.ibm.crypto.plus.provider.IBMJCEPlus.
All Maximo Integration Framework fixes are incorporated into Maximo Asset Management 7.6.1.3 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
Was this topic helpful?
Document Information
Modified date:
19 February 2024
UID
ibm17030670