Fix Readme
Abstract
This document lists APARs and Known Issues fixed in the Maximo Manage 9.2.x Feature Channel April Release. In addition to the new fixes listed here, all fixes from earlier Maximo Manage 9.2.x FC releases are included.
Content
The Operator version is 9.2.0-pre.stable.21956.
This patch updates Manage to version 9.2.167
This release uses graphite version 3.2.632
With the release of Manage Operator Suite 9.2.x FC, the following industry solutions and add-ons now support architecture IBM Power® (ppc64le) to use existing Red Hat® OpenShift® capabilities through the Red Hat OpenShift Container Platform for scalability and resilience:
• IBM Maximo Asset Configuration Manager
• IBM Maximo IT
• IBM Maximo Reliability Strategies
For Industry Solutions Patches, go to:
IBM Maximo Asset Configuration Manager 9.2 FC
IBM Maximo Asset Investment Planning 9.2 FC
IBM Maximo for Aviation 9.2 FC
IBM Maximo Civil Infrastructure 9.2.12 FC
IBM Maximo for Oil & Gas 9.2 FC
IBM Maximo for Nuclear Power 9.2 FC
IBM Maximo for Health, Safety and Environment 9.2 FC
IBM Maximo for Service Providers 9.2 FC
IBM Maximo for Transportation 9.2 FC
IBM Maximo for Health 9.2 FC
IBM Maximo Asset Investment Planning 9.2 FC
IBM Maximo for Aviation 9.2 FC
IBM Maximo Civil Infrastructure 9.2.12 FC
IBM Maximo for Oil & Gas 9.2 FC
IBM Maximo for Nuclear Power 9.2 FC
IBM Maximo for Health, Safety and Environment 9.2 FC
IBM Maximo for Service Providers 9.2 FC
IBM Maximo for Transportation 9.2 FC
IBM Maximo for Health 9.2 FC
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 Behaviour Changes section for information.
When an APAR or Known Issue has Database Change in the first column, click the link or go to the Database Change Details section for information.
| APAR | Application Name | Description |
|---|---|---|
| DT397733 | UI | MAS Manage translation in Norwegian, Portuguese and Chinese language required for Logout Option and Warning Message |
| DT442276 | Known Issue | Increasing the length of the CURVALFORMULA attribute in the AHDRIVERLIB object is not supported in Maximo. |
| DT450803 | Mobile | Mobile application: First option is pre-selected upon viewing MVI photo analysis results |
| DT454581 | System (Object) | In the Users application, filtering by 'Locked' status for users who have entered incorrect passwords multiple times is unavailable. |
| DT455987 | Scheduler/Crew | In Scheduler/Crew applications (WPLABOR, ASSIGNMENTS, LABTRANS), the 'Qualification Met' field incorrectly displays as PARTIAL when no labor is assigned or when the assigned labor partially meets the qualification requirements. |
| DT456578 | Mobile | In the Technician application of the Mobile version, creating a new Quick Report Work Order results in an error that includes details from a previous Quick Report Work Order. |
| DT458077 | Preventive maintenance | Preventive maintenance: Creating reservations for condition code enabled items without corresponding inventory balances, despite receiving BMXAA4590E and BMXAA1894E error messages. |
| DT458163 Behaviour Change | Purchase orders | When creating a Purchase Order with Condition Code-enabled items in Purchase Requisition, the 'Condition Code' field is not marked as required, leading to error BMXAA1895E. |
| DT458418 | System (Object) | Name field in MASUSER application remains empty when creating a new user from an existing Person. |
| DT458878 | Mobile | Selecting an Asset record from within the Maximo Inspection application on Android devices is not possible. |
| DT459359 | Applications | Dates with truncated years beyond 2050 default to 1950 instead of the intended year in Applications. |
| DT459575 | Mobile | Mobile Inventory Counting: Count Book Line records do not appear in 'Counted' list after Save, when the Count Book is added post 'Refresh for Updates', instead of upon initial login. |
| DT459820 | Scheduler/Crew | Graphical Work Week's Calendar export fails for work orders with special characters '_' in their descriptions, within the Scheduler/Crew application. |
| DT459905 | Mobile | Inspection App's Mobile version: Chevron in table columns or lookups causes the app to display a blank page. |
| DT459958 | Reports | Cognos reports containing Japanese characters fail to open from Maximo Manage. |
| DT460429 | Mobile | Inspection form domain values display incorrectly in the Inspections application compared to Preview mode. |
| DT460733 | Condition Monitoring | Condition Monitoring fails to generate Work Orders when action limits are enabled and no Measurement data is entered. |
| DT460779 | System (Object) | Restricting system API wsmethods causes UI malfunction |
| DT461298 | Preventive maintenance | Meter-based Preventive Maintenance Work Orders fail to generate correctly, resulting in updated Meter Frequency data despite missing or invalid values elsewhere. |
| DT461374 | System (Object) | In Users application, the 'Last Modified By' field displays a parameter value instead of the actual user name. |
| DT461636 | Asset templates | Asset Templates application lacks the Date Value column in the Specifications tab, as the DATEVALUE attribute is absent from the PLUSCTPSPEC object. |
| DT461731 | Mobile | Mobile Inspections display an incorrect count of required questions following the clearance of answers for required questions. |
| DT461905 | Preventive maintenance | Creating a PM-based work order results in BMXAT0318W warning, disregarding the unchecked 'Always prompt when a service address changes' option in Service Address Options. |
| DT462065 | Mobile | Mobile application displays duplicate 'Save or discard changes?' dialog upon leaving Report Time drawer. |
| DT462160 | Mobile | In Mobile, when a new Work Order is created for a newly added Asset, the system incorrectly displays meter reading values from a previous Work Order. |
| DT462308 | Scheduler/Crew | Rolling Schedule fails to update dates when switching Offset from Negative to Positive during cron execution. Validation is suppressed in rolling cron, causing discrepancy between manual and automated roll. |
| DT462526 | Mobile | Inspection form conditionals do not respond consistently in the Maximo Mobile application, causing target sections to not show or highlight. |
| DT462691 Behaviour Change | Preventive maintenance | Floating meter-based Preventive Maintenance work orders generate incorrect warning BMXAA9342W when 'Use Last Work Order's Start Date' is disabled and Slack equals 0. |
| DT462699 | Mobile | View Meter Readings button in Asset Manager Mobile App results in error BMXAA9105E due to invalid OSLC order by identifier sequence. |
| DT462712 | Mobile | In Maximo Mobile, rapidly clicking the Labor lookup chevron in the Report Labor Time drawer causes a system error message instead of opening the lookup dialog, displaying: 'Cannot read properties of undefined (reading 'laborcraftrate')'. |
| DT462849 | ACM | BDI logs contain excessive garbage collection output due to a recent change in Websphere Liberty (wlp) with IBM Semeru JREs. To avoid polluting pod logs, redirect garbage collection output to files using the JVM parameter '-Xverbosegclog:logs/verbosegc.%Y%m%d.%H%M%S.%pid.txt,10,1024'. |
| DT462925 | Mobile | In Mobile, retrieving Reserved Items records incorrect quantities for non‑rotating items. The system applies the quantity from the first reserved item to all items instead of using each item’s reserved quantity. |
| DT462962 | Mobile | In the Mobile Technician application, creating and saving a new Labor Time entry without selecting a Labor through lookup causes the resulting LABTRANS record to display the Labor Code instead of the Labor Display Name. |
| DT463110 | Invoices | Invoice Line unit cost changes cause Purchase Order receipt status to be incorrect |
| DT463143 | Desktop Requisitions | When creating a Material Requisition (MR) and adding an Item line, the STORELOC field does not accept input on the initial attempt. |
| DT463267 | Mobile | Mobile Technician application: Assignment status does not update to 'COMPLETED' upon completion of a work order. |
| DT463425 | UI | In Manage, unsaved changes are lost and users are redirected to the Start Center without warning when session timeout is exceeded. |
| DT463453 | Mobile | Published changes to the Navigator are not showing in Maximo Mobile |
| DT463524 | Labor | In the Labor application, when a user's default site differs from the Work Site, the Work Location Extended Drilldown dialog displays locations related to the user's site instead of the defined Work Site. |
| DT463533 | Mobile | Asset functions in Datasheets on Mobile application do not sort sequentially. |
| DT463548 | Desktop Requisitions | Decommissioned assets can be used initially on a Material Requisition |
| DT463634 | Mobile | The Classification creation process does not utilize the system property sr.default.classstructureid, resulting in a null Classification and preventing assignment of Service Requests to Owner Groups via associated Ticket Templates. |
| DT463640 | Known Issue | Azure SAS Key–Based Attachment Upload Fails in Manage with URL Validation Error. |
| DT463677 | Assets | Linear asset relationships in Maximo Manage lack consistent validation. Saving the first relationship skips measure validation, but adding a second triggers an error BMXAA6307E for missing sourcestart and sourceend measures. |
| DT463679 | UI | Inspection application's X-MAF headers are empty, potentially causing firewall issues. |
| DT463703 | UI | Mobile application icons are misaligned to the right in MAS, causing reduced visibility on devices. Alignment should match the layout of version 7.6. |
| DT463827 | Mobile | Linking a work order to an inspection in the Mobile application results in multiple requests to MXAPIINSPECTIONRES, causing the Inspection Data progress to restart and display the spinning wheel. |
| DT463844 | UI | Reachover icon overlaps asset number in list view assets, should be at the end of the field. |
| DT463938 | Preventive maintenance | Preventive maintenance hierarchy causes endless work order generation when using 'Use this PM to Trigger PM Hierarchy?' option on a child PM in Maximo Asset Management .3 at iFix level IF036. |
| DT463970 | UI | Horizontal scroll bar does not reach the end of pages with multiple wide Result Set portlets in Maximo Manage. |
| DT464065 | Mobile | When editing an LABTRANS record and changing the associated Labor, saving the record results in error BMXAA2634E due to mismatched labor, craft, skill level, vendor, and contract. |
| DT464075 | System (Object) | Maximo Objects on update not publishing messages to Outbound Queue |
| DT464184 | System (Object) | Continuous Push Notification queue writes result in BMXAA1360E error: 'An outbound transaction could not be written to the queue. |
| DT464251 | Mobile | Multi Asset & Location record count does not update correctly in My Schedule application. After marking a record as 'In Progress', the count resets to 50 even when more than 50 records are present and no filter is applied. |
| DT464266 | Mobile | Mobile navigation: Leaving Asset Details from a Technician Work Order does not return to the originating Technician Work Order detail view, instead navigates to the Asset list page in the Assets application. |
| DT464288 | Assets | Classification Search filter persists but does not reapply upon changing classification tree node in Assets application. |
| DT464319 | UI | In the Mobile/Role-Based Technician application, the last value in the Classification hierarchy lookup is truncated. |
| DT464417 | Mobile | In Mobile Operational Dashboard, selecting an Inspection Record from a work queue card does not open the chosen record. |
| DT464434 | Applications | The 'Move/Modify Asset' confirmation email is sent in English regardless of locale and language settings within the Assets application. |
| DT464597 | Scheduler/Crew | After upgrading to MAS 9.1.x, the OpenShift Console displays an extra API deployment |
| DT464658 | System (Object) | The WFASSIGNMENT database table causes UpdateDB errors during language updates, resulting in failed processes. |
| DT464659 | Mobile | TECHMOBILE's MXAPIALNDOMAIN call lacks a filter for ORGID/SITEID, affecting data retrieval. |
| DT464675 | Applications | Error when importing MATRECTRANS BMXAA6228E - The GL Account number on a receipt must be the same as those on the purchase order. |
| DT464761 | UI | Launching Cognos Analytics from the Analytics menu within UI fails, resulting in no response. |
| DT464903 | Mobile | Location meter readings addition in Mobile Technician app fails with BMXAA4214E, causing an unknown error. The error message suggests that 'encodedId' is null, which occurs specifically during location meter reading submissions. |
| DT464951 | Mobile | ‘Apply template’ option for a Mobile application in Security Groups does not grant access to all relevant Object Structures automatically |
| DT464974 | Scheduler/Crew | Craft Allocation Chart Displays Incorrect Over-Allocation After Optimization. |
| DT465015 | Mobile | Mobile application: Work Detail Data Service (WoDetailDS) initiates full sync upon opening a work order assigned to labor, causing unnecessary data synchronization for all work orders. |
| DT465155 | UI | Date picker in SR Details View lacks hidden label, causing accessibility issues for users with screen readers. |
| DT465309 | Inventory | Slow Performance When Navigating to Inventory from Inventory Usage or Receiving Application |
| DT465327 | Service requests | Work order save failure due to incorrect validation of SR(Service Request) view Relationships Against TICKET Object in Maximo. |
| DT465357 | System (Object) | Incorrect hierarchy generation in Object Structures for Work Order and LocationMeter branches leads to BMXAA5588E error. |
| DT465387 | Mobile | In Mobile MVI, deleting a non-analyzed photo after analyzing another causes the analysis status of the analyzed photo to disappear. |
| DT465388 | Mobile | Reusing signature responses from previous inspections when creating new ones while offline in Mobile application. |
| DT465447 | Scheduler/Crew | Recurring Cron in Scheduler/Crew does not account for Offset when Start Week Day is Monday, causing incorrect roll schedule dates. |
| DT465513 | Mobile | Mobile app fails to delete related data when using a unique object structure for a Maximo business object compared to structures used by other apps. |
| DT465646 | UI | Role-Based Applications' URL path sensitivity causes failure to load when lowercase. |
| DT465685 | Desktop Requisitions | Long Description field persists in Desktop Requisitions after item selection |
| DT465704 | UI | Redirecting back to list view instead of last opened record |
| DT465716 | Mobile | SRMobile displays 'Save or discard changes?' dialog after creating three Service Requests consecutively |
| DT465754 | System (Object) | Message reprocessing in CQOUT persists in an ERROR state even after DELETEFLAG becomes 2, causing the message tracking record to remain in error despite successful reprocessing. |
| DT465930 | Mobile | Mobile application: Creating a Work Order fails when the preload database lacks required data. |
| DT466015 | UI | White space appears on the left side in mobile versions of Maximo applications post-9.1 upgrade, reducing usable screen area and requiring horizontal scrolling. |
| DT466071 | Mobile | In Mobile Technician Application, entered remarks on the Meter Readings page persist after changes are discarded. |
| DT466100 | UI | Operational Dashboard Quick Actions card fails, returning to the same record or a blank screen after launching a second action. |
| DT466354 | UI | Start center displays site names in UNICODE characters instead of standard text. |
| DT466399 | UI | Count functionality for Work Queues in OP Dashboard causes prolonged loading times after applying APAR DT458763. |
| DT466401 | UI | Creating a new Work Queue results in a system hang due to an excessive SQL query (select * from workqueue, potentially including the itemcount attribute) when there are numerous work orders. |
| DT466534 | Mobile | Mobile sync fails to complete transactional data after network disconnection during initial sync. |
| DT466551 | Scheduler/Crew | Adding indexes to improve Scheduler performance |
| DT466731 | UI | Manual date entry fails in the date field of an Inspection Form within the Maximo UI application on Windows. |
| DT466881 | Mobile | Activating or opening the Inspection form triggers an action on the INSPECTIONRESULT table, which was not previously associated with this function. |
| DT466980 | System (Object) | Security Groups table filtering fails in Users application for Independent, Module Count, and License Impact columns, returning errors: 'The specified value is not a valid Yes or No value', 'Cannot query on field MODULESCOUNT', and 'Cannot invoke "psdi.mbo.MboValueInfo.getName()" because "mboAttrInfo" is null'. |
| DT467227 | UI | Double encoding occurs for url attachments if the url is already encoded when calling FileNet |
| DT467283 | UI | In Maximo Manage, when 'Edit Profile' window is open, opening other windows like 'Default Information' places them in the background. This behavior hinders usability by obscuring the active workflow. |
| APAR | Change details |
|---|---|
The condition code field is a required field on po (poline), thus when a PO is generated from PR or RFQ and the condition code is missing on the PRline or QuotationLine as it is not required there, the condition code will be set to default on PO. | |
The warning BMXAA9342W is intended for time-based PMs when the next due date cannot be determined. However, for meter-based PMs (frequency = 0) where a meter is associated, the next WO generation date may come from meter readings instead of the time-based nextdate field. Therefore, display the warning only when: "Use Last WO Start Date" is disabled, AND nextdate (time-based next due date) is null, AND PM has generated at least one WO (pmcounter > 0), AND Either no meter is associated OR time-based frequency is configured. If a meter is associated and frequency = 0 (pure meter-based PM), suppress the warning because the next generation date may be derived from meter readings instead of nextdate. |
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hB0QAAU","label":"Manage"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.2.0"}]
Was this topic helpful?
Document Information
Modified date:
30 April 2026
UID
ibm17270986