Fix Readme
Abstract
On 25 June 2024, IBM released IBM® Maximo® Application Suite Manage Component patch 8.6.15.
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 |
DT238874 | Install/Upgrade | In an upgrade environment that has a table with a column of data type CRYPTO, and one or more records in that table has data in the CRYPTO field, the upgrade fails in ValidateCrypto. |
DT247243 | Mobile | In the Mobile Technician application, work completes without displaying the "Labor Approval?" pop up. |
DT253536 | Users | The CognosUserSyncCronTask does not synchronize Users from MAS Core to Cognos if they were already synchronized from MAS Manage to MAS Core. |
DT257950 | Mobile | Adding a description with 255 characters causes error BMXAA4049E. |
DT258311 Manual Change |
Inventory Counting | Count Book Lines show the wrong serial number for Assets. |
DT259279 | Mobile | In Maximo Mobile, adding a Gauge Meter Reading of 0 (zero) may cause the Reading and its time not to display properly. The previously added 0 Reading may be pre-filled when adding a new reading. |
DT261549 | Assets | In Assets, entering unavailable hours outside the Shift Period causes Asset Downtime to be incorrect. |
DT365033 | Inventory | Transferring a Kit between Storerooms results in error BMXAA3496E - "Trouble processing item NNNN. Cause: The balance in the bin will become negative as a result of this transaction.". |
DT379209 | System UI | The Mouse Over label display does not work for the Help and Profile Menu icons. |
DT380456 | Mobile | Maximo Mobile application crashes with OOM error. |
DT380837 | Graphical Assignment | In environments where the System Property mxe.map.showMarkersOnRouteError is set to 1, the Graphical Assignment map displays no Work Order markers for routes. |
DT381844 | Mobile | In the Technician application, users cannot open follow-up Work Orders. |
DT381849 | System Object | In a Manage environment with Japanese as the base language, accessing Manage from the Maximo Application Suite Navigator page causes error BMXAA4024E - "The synonym value REACT is not valid for the domain CUSTAPPTYPE. Specify a valid synonym value. You can find a list of valid values using the Domain application.". |
DT381883 | Mobile | The Failure Class and Problem do not display after the user fills in the Failure report. |
DT381946 | Mobile | Updating the Cause and Remedy of a Failure Report results in error BMXAA0018I - "The report is complete.". |
DT382232 | Mobile | In the Mobile Technician application, Route Stops are not ordered by Sequence. |
DT382276 | Mobile | In the Mobile Technician application, setting the Start Time in a Work Order to more than 3 hours displays "Start time cannot be in the future" message even though Future Labor Transaction Tolerance in Hours is set to longer than that. The user cannot save the Actual Labor. |
DT382297 | Mobile | Mobile application allows fields in closed Work Orders to be edited. |
DT383069 | Mobile | Closing a Work Order when the timer was not stopped before placing the Work Order in a Completed state on the Mobile app results in error BMXAA4042E - "The status cannot be changed for the selected records.". |
DT383276 | Mobile | Clicking on a Work Order number in Mobile Inspections application displays the wrong Work Order. |
DT385969 | System UI | In the Maximo Mobile Technician application, the cs-switch text translations are not published. |
DT386109 | Mobile | For a user that has a Japanese locale, downloading the supporting data download fails with the error BMXAA9757E - "Error executing the request. Check the request parameters to verify parameter value format." |
DT386200 | Mobile | A user cannot create a follow-up Work Order when the parent Work Order does not belong to the list specified in the Security Group condition. |
DT386333 | Mobile | In the Technician role-based application, reporting Labor does not display the Labor Name. |
DT386478 | Integration | The results from exporting a JSON Swagger are missing Query Parameters and Headers. |
DT386939 | Mobile | The Start-End times for a LABTRANS record display incorrectly in the Labor section on a mobile device after a 'Refresh for Updates'. |
IJ49991 | System UI | In Preventive Maintenance, adding column controls with conditions to the PR Lines section causes unexpected read-only conditions and system messages. |
IJ50215 | Database configuration | The Formulas Duration function does not work for ALN type attributes. |
IJ50792 | Assets | Changing an Asset's status to a synonym of Decommissioned, then changing the status of its Location to a synonym of Decommissioned causes duplicate lines to be written to the Asset Status History. |
IJ51008 | System Object | Maximo generates DEBUG level log entries for some objects, bypassing the Maximo Logger's application settings. |
IJ51035 | Inventory usage | Clicking the action "Create Remaining Usage Lines" does not populate the GL Debit Account. |
IJ51043 | Tools | In the Tools application, checking the "Rotating Item" checkbox results in error BMXAA9922 - "This item is active and has been added to a storeroom. It cannot be made rotating.". |
IJ51199 | Inspection | In the "Conduct an Inspection" Work Center, the action "Generate Work Order for items" results in error BMXAA7837E - "An error occurred that prevented the OSACTION.MXAPIINSPRESULT.CREATEWO script for the null launch point from running. AttributeError: 'NoneType' object has no attribute 'createWorkorder' in script at line number 33.". |
IJ51220 | Work Order Tracking | In the Work Order Tracking application, the View Costs dialog displays an incorrect value for Estimate Internal Labor Hours. |
Manual Changes
APAR | Change instructions |
---|---|
1. Go to the Database Configuration Application
2. Query for "COUNTBOOKLINE" object and move to Relationship tab 3. Search for a Relationship called ASSET 4. Update the where clause from itemnum=:itemnum
to
itemnum = :itemnum and assetnum=:assetnum and siteid=:siteid and orgid=:orgid
5. Click Save |
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.15
- Click Save.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"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:
25 June 2024
UID
ibm17157396