Fix Readme
Abstract
On 30 April 2026, IBM released IBM® Maximo® Application Suite Manage Operator patch 8.7.32. 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 uses Graphite 2.12.465
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 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 |
|---|---|---|
| DT382340 | Integration | Receiving 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. |
| DT435562 | UI | The My Recent Applications option disappears. |
| DT449753 Manual Change | Inventory usage | In Inventory Usage, issuing more than 250 items causes a misleading warning message to appear. |
| DT451764 | Work Order Tracking | Duplicating a Work Order with tasks in Maximo's Work Order Tracking results in an extra blank labor row being added when new entries are made in the Plans > Labor tab. |
| DT455057 | Mobile | In Maximo Mobile Inventory Counting, some Count Book lines display incorrect due dates compared to the database query results. |
| 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. |
| DT457263 | Work Order Tracking | Work Order Tracking: Updating WO Assignment record with ID XXXX (error BMXAA8229W) occurs during deletion of Work Order Assignments. |
| DT460733 Manual Change Behaviour Change | Condition Monitoring | Condition Monitoring fails to generate Work Orders when action limits are enabled and no Measurement data is entered. |
| 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. |
| DT461636 Manual Change | Asset templates | Asset Templates application lacks the Date Value column in the Specifications tab, as the DATEVALUE attribute is absent from the PLUSCTPSPEC object. |
| 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. |
| 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'. |
| DT463110 | Purchase orders | 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. |
| 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. |
| DT463548 | Desktop Requisitions | Decommissioned assets can be used initially on a Material Requisition |
| 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. |
| 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. |
| DT464075 | System (Object) | Maximo Objects on update not publishing messages to Outbound Queue |
| DT464288 | Assets | Classification Search filter persists but does not reapply upon changing classification tree node in Assets application. |
| DT464434 | Assets | The 'Move/Modify Asset' confirmation email is sent in English regardless of locale and language settings within the Assets application. |
| DT462826 | Assets | When 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. |
| DT465290 | Invoices | Invoices approval failure occurs after a receive, return, and re-receive cycle on the same PO line due to missing matching receipts. |
| 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. |
| DT465487 Manual Change | Inventory usage | Transfer Details section in Inventory Usage application is improperly aligned, resulting in poor readability. |
| DT465685 | Desktop Requisitions | Long Description field persists in Desktop Requisitions after item selection |
| DT466752 Manual Change | Failure codes | Changing the format and the content of the REST API error messages. |
| APAR | Change details |
|---|---|
To modify 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 filter icon Search the Search the message group: inventory message key: MaxInvUseLineLimitExceeded press enter click view details icon edit the value details add new value :The maximum number of \{0} inventory usage lines has been entered for the current record. You can delete lines or add them to a new inventory usage record. When finished, click OK. | |
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> elementsOnly indentation/placement will change due to wrapping. Add the following AFTER the original section closing tag </section>:</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. |
| 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. | |
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. |
Related Information
[{"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":"8.7.0"}]
Was this topic helpful?
Document Information
Modified date:
29 April 2026
UID
ibm17270969