IBM Support

IBM Maximo Application Suite - Manage Operator patch 9.0.25

Fix Readme


Abstract

On 30 April 2026, IBM released IBM® Maximo® Application Suite Manage Operator patch 9.0.25. As with all patches, it is cumulative. In addition to the new fixes listed here, all fixes from earlier patches for this version are included.

Content

This patch updates Manage to version 9.0.298
This patch uses Graphite 2.13.666
 
For Industry Solutions Patches, go to:

*Not updated from Operator Patch 9.0.24 in this release. 


Manage and Mobile 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 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.
APARApplication NameDescription
DT382340 IntegrationReceiving Rotating Items in Bulk option fails to process large quantities (1000+ records) through the PLUSDMXRCVROTITMInterface Enterprise Service, resulting in an error BMXAA4176E for an invalid attribute METER1001.
DT449787 MobileMobile application fails to approve Material Requests, resulting in BMXAA10013E error: 'Invalid URI for updating resource. The URI needs to end with the resource REST id'.
DT455057 MobileIn Maximo Mobile Inventory Counting, some Count Book lines display incorrect due dates compared to the database query results.
DT456578 MobileIn 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.
DT457827 OIL&GASMAXEVERONE security group is ignored by Oil & Gas scripts in the MAS9 upgrade.
DT459347 SpatialSpatial: Map Layer visibility issue in Map Manager application
DT459575 MobileMobile 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/CrewGraphical Work Week's Calendar export fails for work orders with special characters '_' in their descriptions, within the Scheduler/Crew application.
DT459836 MobileTechnician App Start timer method not picking up the start date
DT460429 MobileInspection form domain values display incorrectly in the Inspections application compared to Preview mode.
DT460733 Manual Change Behaviour ChangeCondition MonitoringCondition 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
DT460805 SpatialSpatial application: Custom sub-layer labels not displayed in Identify Operation Pop-Up in Map View
DT460895 MobileWhen a task has an Inspection Form with a counter meter that includes prior readings, completing the inspection in Maximo Mobile fails if the user enters a reading lower than the previous value. The application briefly displays error BMXAA0642E and then returns the user to the Tasks page without allowing inspection completion.
DT461298 Preventive maintenanceMeter-based Preventive Maintenance Work Orders fail to generate correctly, resulting in updated Meter Frequency data despite missing or invalid values elsewhere.
DT461636 Manual ChangeAsset templatesAsset Templates application lacks the Date Value column in the Specifications tab, as the DATEVALUE attribute is absent from the PLUSCTPSPEC object.
DT461947 SpatialWindows Mobile apps cannot load maps when Proxy is enabled in Map Manager, resulting in error 'Error 500'.
DT462065 MobileMobile application displays duplicate 'Save or discard changes?' dialog upon leaving Report Time drawer.
DT462691 Behaviour ChangePreventive maintenanceFloating meter-based Preventive Maintenance work orders generate incorrect warning BMXAA9342W when 'Use Last Work Order's Start Date' is disabled and Slack equals 0.
DT462849 ACMBDI 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'.
DT463031 HSERevising multiple Consequences with same Consequence ID fails with error "BMXAO0568E - Consequence TEST cannot be revised because it is not the latest revision. You can revise only the latest revision of an active consequence.".
DT463092 UIAfter applying custom CSS to an application page, the system briefly render the page with the default theme before the custom CSS loads, causing a visible flash of default styling.
DT463143 Desktop RequisitionsWhen creating a Material Requisition (MR) and adding an Item line, the STORELOC field does not accept input on the initial attempt.
DT463425 UIIn Manage, unsaved changes are lost and users are redirected to the Start Center without warning when session timeout is exceeded.
DT463524 LaborIn 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.
DT463634 MobileThe 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.
DT463548 Desktop RequisitionsDecommissioned assets can be used initially on a Material Requisition
DT463677 AssetsLinear 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.
DT463938 Preventive maintenancePreventive 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.
DT464050 SpatialIn the Work Order Tracking Map tab, navigating between records using the next and previous arrows updates the record but does not update the map marker coordinates, so the marker remains at the prior location.
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.
DT464288 AssetsClassification Search filter persists but does not reapply upon changing classification tree node in Assets application.
DT464319 UIIn the Mobile/Role-Based Technician application, the last value in the Classification hierarchy lookup is truncated.
DT464434 AssetsThe 'Move/Modify Asset' confirmation email is sent in English regardless of locale and language settings within the Assets application.
DT464659 MobileTECHMOBILE's MXAPIALNDOMAIN call lacks a filter for ORGID/SITEID, affecting data retrieval.
DT464658 System (Object)The WFASSIGNMENT database table causes UpdateDB errors during language updates, resulting in failed processes.
DT464729 MobileTasks Not Displayed in Technician Application Labor Entry When Work Order Is Set to Custom Status Mapped to INPRG
DT464951 Mobile‘Apply template’ option for a Mobile application in Security Groups does not grant access to all relevant Object Structures automatically
DT464974 Scheduler/CrewCraft Allocation Chart Displays Incorrect Over-Allocation After Optimization.
DT462826 AssetsWhen a user creates two identical relationships in the same session before saving and those relationships do not exist in the database, the system does not validate the duplicates and allows both records to be saved.
DT465155 UIDate picker in SR Details View lacks hidden label, causing accessibility issues for users with screen readers.
DT465290 InvoicesInvoices approval failure occurs after a receive, return, and re-receive cycle on the same PO line due to missing matching receipts.
DT465309 InventorySlow Performance When Navigating to Inventory from Inventory Usage or Receiving Application
DT465327 Service requestsWork order save failure due to incorrect validation of SR(Service Request) view Relationships Against TICKET Object in Maximo.
DT465487 Manual ChangeInventory usageTransfer Details section in Inventory Usage application is improperly aligned, resulting in poor readability.
DT442276 Database ConfigurationIncreasing the length of the CURVALFORMULA attribute in the AHDRIVERLIB object is not supported in Maximo.
DT465685 Desktop RequisitionsLong Description field persists in Desktop Requisitions after item selection
DT465704 UIRedirecting back to list view instead of last opened record
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 MobileMobile application: Creating a Work Order fails when the preload database lacks required data.
DT465734 SpatialSpatial app: Filtering on the Asset list does not apply when opening maps from VPTK files in the Mobile app.
DT466535 MobileMobile application fails to download work order descriptions, returning aliases instead of actual descriptions.
DT466752 Manual ChangeFailure codesChanging the format and the content of the REST API error messages.
DT466876 MobileMobile application fails to download Supporting Data due to a null 'rsCount' error when using bind variables on listwhereclause for a table domain.
DT467557 MobileIn Technician (RBA) application, setting labor actual Hours to zero prevents the End Time from being automatically populated, contrary to expectation.
DT458163 Behaviour ChangePurchase OrdersError BMXAA1895E in Purchase Requisition while creating a Purchase Order with Condition Code-enabled item

APARChange details
To add message, follow these steps:
Log into Manage as an administrative user.
Go to the Database Configuration Application (System Configuration -> Platform Configuration -> Database Configuration
In the More Actions section, click Messages.
Click the add new row
Message Group-  measurement
Message Key - noMeasurementAvailable
Display Method-MSGBOX
Message ID Prefix-BMXAA
Message ID Suffix- E
Display ID- checked
Value- Cannot generate a work order as no measurement is available.
Button- OK? Checked
When finished, click OK.
Go to Application Designer Application > search PLUSCTMPLT application > export application definition from Common Actions> update the XML file as below:
Search: <tablecol id="specifications_specifications_table_tablebody_4" dataattribute="assetattribute.datatype" sortable="false" showfilterfield="true" linkedcontrolid="specifications_specifications_table_1_griddetails1_2" />
In immediate next line, add following line: <tablecol id="specifications_specifications_table_tablebody_6a" dataattribute="datevalue" linkedcontrolid="specifications_specifications_table_1_griddetails2_3a" smartfilloff="true"/>
Search: <textbox id="specifications_specifications_table_1_griddetails2_2" dataattribute="alnvalue" lookup="alndomain" smartfilloff="true" />
In immediate above line, add following line: <textbox id="specifications_specifications_table_1_griddetails2_3a" dataattribute="datevalue" lookup="datelookup" smartfilloff="true"/>
Save the xml.
Import the application definition.
To update xml file, follow these steps:
Log into Manage as an administrative user.
Go to the Application Designer (System Configuration -> Platform Configuration -> Application Designer)
Search for “invusage”, and open that record
Under common actions section, click Export Application Definition.
Download the file as invusage.xml
Search for below existing section :
<section id="main_invuselinetab_table_1_grid4_sec2" label="Transfer Details" sigoption="TRANSFER">
Add the following wrapper BEFORE the existing section:
<section id="main_invuselinetab_table_1_grid4_sec2">
<sectionrow id="main_invuselinetab_table_1_grid4_row_21">
<sectioncol id="main_invuselinetab_table_1_grid4_sec2_row2_col1">
Modify the existing section tag:
From : <section id="main_invuselinetab_table_1_grid4_sec2" label="Transfer Details" sigoption="TRANSFER">
To : <section id="main_invuselinetab_table_1_grid4_sec2_row1" label="Transfer Details" sigoption="TRANSFER">
Do not modify:
<sectioncol> blocks
<textbox> elements
Only indentation/placement will change due to wrapping.
Add the following AFTER the original section closing tag </section>:
(after </section> for <section id="main_invuselinetab_table_1_grid4_sec2_row1" label="Transfer Details" sigoption="TRANSFER"> add the below closing tag)
</sectioncol>
</sectionrow>
</section>
Go to Database Configuration Application
From More Actions > select Messages
3 Add new messages as follows
Message Group: failure
Message Key: usedinworkorder
Display Method: MSGBOX
Message ID Prefix: BMXAA
Message ID Suffix: E
Display ID: true
Value: Failure code is referenced by a work order and cannot be deleted.
Button: OK?
Message Group: failure
Message Key: usedinasset
Display Method: MSGBOX
Message ID Prefix: BMXAA
Message ID Suffix: E
Display ID: true
Value: Failure code is referenced by an asset and cannot be deleted.
Button: OK?
Message Group: failure
Message Key: usedinlocation
Display Method: MSGBOX
Message ID Prefix: BMXAA
Message ID Suffix: E
Display ID: true
Value: Failure code is referenced by a location and cannot be deleted.
Button: OK?
Message Group: failure
Message Key: usedinfailurereport
Display Method: MSGBOX
Message ID Prefix: BMXAA
Message ID Suffix: E
Display ID: true
Value: Failure code is referenced by a failure report and cannot be deleted.
Button: OK?
Click OK and new messages are now configured.
APARChange details
User will get a error message stating "cannot generate a work order as no measurement is available" when trying to generate work order from condition monitoring application with no measurement available on the meter.
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.
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.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"label":"IBM Maximo Application Suite","code":"SSRHPA"},"ARM Category":[{"code":"a8m3p000000hB0QAAU","label":"Manage"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0.0"}]

Document Information

Modified date:
29 April 2026

UID

ibm17270970