Fix Readme
Abstract
On 26 September 2023, IBM released IBM® Maximo® Application Suite Manage Component patch 8.6.5.
Content
APAR and Known Issue Fixes
When an APAR or Known Issue has Manual Change in the first column, click the link or go to the Manual Changes section for directions.
When an APAR or Known Issue has Behavior Change in the first column, click the link or go to the Behavioral Changes section for information.
When an APAR or Known Issue has Behavior Change in the first column, click the link or go to the Behavioral Changes section for information.
| APAR | Application Name | Description |
| DT196079 | System UI | In the Budget Monitoring application, Budget Lines shows "Labor Amounts" as a horizontal label while other labels are vertical. |
| DT198206 | System UI | User created a Work Order in the Quick Insert portal. Problem: The user cannot navigate to the List View. |
| DT198335 | Technician | Creating a work order when the device is in offline mode causes errors BMXAA4590E and BMXAA4673E. |
| DT214326 | Technician | Work orders created while offline do not get set to INPRG when timer starts |
| 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.". |
| DT222698 | Crafts | Changing the Craft on a Work Order results in error BMXAA0019I - "The Resource Lock field is either read only or part of the primary key. You cannot edit this field.". |
| DT224247 | Graphical Scheduling | In the Graphical Scheduling application, the right-click "Change Status" option displays an incorrect list of statuses. |
| DT224287 | Mobile | Maximo Mobile Schema Generation does not check whether app is licensed before generating the schema. |
| DT228268 | Conduct an Inspection | When a user attempts to complete an Inspection on a new Work Order task when all other tasks’ inspections are done, Error BMXAA0032E occurs. This fix requires a Maximo Asset Management 7.6.1.3 interim fix 012, Manage 8.7.1, Manage 8.6.5, Manage 8.5.9, or post-Manage 8.7.0 or later environment. |
| DT228331 | Technician | Maximo Mobile physical signature not prompting correctly |
| DT228619 | Technician | In Work Order Tracking, the HASFOLLOWUPWORK field is not flagged for new Follow-Up Work Orders in Mobile. |
| DT228712 | Mobile | A searchable attribute with an alias in a related datasource causes a schema generation error. |
| DT228965 | System UI | In the Work Order application, when the length of the ASSETNUM field is large, the Hover Over icon merges with the data displayed in the text box. |
| DT233278 | Preventive maintenance | In Configuration Manager, a forecast generated for a PM with Time-Based Frequency Iterations is incorrect. This fix is needed to address the problem reported in APAR IJ47812. |
| DT237037 | Mobile | Role Based Service Requests App does not allow SRs to be created. |
| DT237152 | Spatial | Interactive Map tools do not call the Proxy Service as expected. The token is acquired but not sent to the proxy. This behavior is also seen with WO Edit, Identify, Select & Results & Layers. |
| DT237544 | Technician | Maximo Mobile EAM 8.10 SQL Server - Object structure has queries that contain Oracle Syntax. |
| IJ30815 | Failure codes | A Failure Code's description is not saved. |
| IJ32490 | Work Order Tracking | In 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. |
| IJ34823 | Receiving | The Receiving application does not update the Work Order's "Material Status Last Updated" field when a Direct Issue Item is received. |
| IJ35519 | Work Order Tracking | Moving an asset with the Work Order Tracking application's Move/Swap/Modify dialog results in error BMXAA0154E - "Open Work Order exists for the asset. Close/Cancel the Work Order before moving the asset and its assemblies.". |
| IJ38143 | Condition Codes | Unable to change the Condition Code transferring a Condition-enabled item. |
| IJ38852 | Assets | In the Assets application, the wrong Location is selected from Drilldown dialog. |
| 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.". |
| IJ42754 Manual Change |
Work Order Tracking | Error ORA-01722 occurs when InspectionResult records exist with non-numeric value in ReferenceObjectID. |
| IJ44145 Manual Change |
Purchase orders | Changing the Unit Cost or Quantity of a Revised Purchase Order causes the system to become unresponsive. |
| IJ44342 | Integration | Revising a Purchase Order by using the Maximo Integration Framework (MIF) removes RFQ references on PO Lines. |
| IJ44468 | Routes | In the Routes application, the Inspection Form field allows invalid data to be saved. |
| IJ44545 | Preventive maintenance | Changing status deletes Forecast Data. |
| 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. |
| IJ44871 | Meters | Loading Meter Readings into Maximo with the Maximo Integration Framework (MIF) takes longer than expected and causes high CPU usage. |
| 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. |
| IJ45268 | Assets | Using Issue Current Item action in Inventory for parent/child assets results in incorrect balances for the child items. |
| IJ45433 | Work Order Tracking | Reservation not cleared when Work Order status changed to Complete. |
| IJ45500 | Calibration | Calibration Points can be deleted on WAPPR status, even when "Edit Cal Points" is cleared for WAPPR status. |
| IJ45588 | Purchase requisitions | If the Default Vendor is not used creating a Purchase Requisition for a Consignment Item, the PRLINE is not added. |
| IJ46227 | Purchase Contracts | In Purchase Contracts, the next Purchase Contract Revision cannot be created when the previous Revision is in a custom status of Canceled (CAN), and this status is not the default Domain status. |
| IJ46282 | Inventory usage | When an Item is referenced on multiple Material Plan lines in a Work Order, changing the quantity of the Item can result in error BMXAA4642 - "Error: The quantity cannot be less than what has been already issued.". |
| IJ46284 | Inventory usage | When multiple reservations exist for an Item, changing the Item quantity in a Work Order generates a new reservation with the wrong quantity. |
| IJ46292 | Work Order Tracking | Removing an item from Inventory Usage record results in error BMXAA4631E - "Cannot delete work plan material if an actual material exists for it.". |
| IJ46339 | Install/Upgrade | Upgrade fails with error BMXAA7968E - "A unique key error with index MAXLOOKUPMAP_NDX1 is defined on table maxlookupmap, columns (TARGET, LOOKUPATTR, TARGETATTR, SOURCE).". |
| IJ46398 | Work Order Tracking | Bulk Work Order status change is not refreshing in list view. Selecting one of the records results in error BMXAA4214E. |
| IJ46610 | Report | Downtime report is not calculated correctly when the Shifts overlap. |
| IJ46633 | Application Designer | In Application Designer, adding an attachment from the Library in the Create Communication dialog clears the Template ID field. |
| IJ46642 | Purchase orders | A Purchase Order generated by the "Create PO" action in Purchase Requisition is missing the value from PRLINE.PLIN3. |
| IJ46709 | System UI | In Start Center, Cognos Analytics does not launch from the Favorites Applications Portlet. |
| IJ46737 | Map manager | In the Mobile Service Request application, the Asset or Location is not displayed on the map. An SQL query error appears in the server log. |
| IJ46845 | Crafts | Creating a craft in the Crafts application results in error BMXAA2528E. |
| IJ47415 | Report | Running "importreportsh libraries" fails with error BMXAA7901E - "You cannot log in at this time. Contact the system administrator.". |
| IJ47472 | Message Tracking | Performing a Physical Count adjustment sends a transaction to an external system. |
| IJ47568 | Invoices | The Same As Object and Same As Attribute information is missing from all of the EMITADDRESS attributes on the INVOICE object. |
| IJ47569 | Service Request | In an environment with many Service Requests, creating a Service Request from the More Actions menu reacts more slowly than expected. |
| IJ47799 | Application Designer | Using the 'Return With Value' function from the Work Order Tracking application results in an error. |
| IJ47864 | Item Master | Downloading on a mobile device causes the following error to be written to the logs: BMXAA7135E - "The Boolean value of ITEM.ISKIT cannot be retrieved.". |
| IJ47916 | Inventory Counting | The Inventory Counting role based application allows Physical Counting of an OBSOLETE Item. |
Manual Changes
| APAR | Change instructions |
|---|---|
|
This issue is resolved by changing the INSPECTIONRESULT relationship where the parent is MULTIASSETLOCCI and child is INSPECTIONRESULT.
For SQL Server databases, change the where clause to the following:
referenceobjectid=CONVERT(varchar, :multiid) and referenceobject=''MULTIASSETLOCCI'' and inspformnum=:inspformnum and siteid=:worksiteid and orgid=:orgid For all other databases, change the where clause to the following:
referenceobjectid=TO_CHAR(:multiid) and referenceobject=''MULTIASSETLOCCI'' and inspformnum=:inspformnum and siteid=:worksiteid and orgid=:orgid |
|
| 1. Open Application Designer. 2. Filter PO application and open. 3. Click on PO Lines tab. 4. Under Po Lines table section, select Quantity field and open properties. 5. On Table Column Properties dialog box, click on Advanced tab. 6. Check the ""Always Synchronous?"" check box. 7. Repeat the steps for Unit Cost Field. 8. Save the application. |
Manually Installing the Patch
- Log in to Maximo Application Suite Administration as an administrative user.
- On the left, click Applications.
- From the Action menu, select Update configuration.
- In the dialog box, click the pencil icon on the Components line.
- Under Activation configuration, click your workspace details page link.
- From the Action menu, select Update configuration.
- Under Configurations, click the pencil icon on the Components line.
- In the Maximo Base line, under new version click the down arrow.
- Select Version. Enter 8.6.5
- Click Save.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hB0QAAU","label":"Manage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0"}]
Was this topic helpful?
Document Information
Modified date:
28 December 2023
UID
ibm17034298