IBM Support

IBM Maximo Application Suite - Manage Operator patch 9.0.13

Fix Readme


Abstract

On 5 May 2025, IBM released IBM® Maximo® Application Suite Manage Operator patch 9.0.13. 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.93.

For Industry Solutions Patches, go to:
*Not updated from Operator Patch 9.0.11 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 Behavioral 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 Change instructions
To solve this issue, a unique index might need to be created on the ponum, revisionnum, polinenum, and siteid columns.
 
Steps to be Performed Before Creating the Unique Index:
 
Step 1: Remove Duplicate Records
1. Ensure that there are no duplicate entries for ponum, revisionnum, polinenum, and siteid.
2. Run the following query to check for duplicates: 
SELECT
	ponum,
	revisionnum,
	polinenum,
	siteid,
	count(*)
FROM
	poline
GROUP BY
	ponum,
	revisionnum,
	polinenum,
	siteid
having
	count(*) > 1;
3. If this query returns any records, manually address the duplicates (either by deleting or correcting them) before proceeding. This ensures that data integrity is maintained before the index is enforced.

Step 2: Check for Existing Index
1. Run the following query to check if an index already exists on these columns. Alternatively, go to Database Configuration, search for POLINE Object and check the list of Indexes on the Index tab to verify if any such index already exists on POLINE object.
Note: The out-of-the-box POLINE_NDX10 index exists on these columns but is not unique.

Query to Find Existing Index (SQL Server):
SELECT
	i.name AS IndexName,
	i.is_unique AS IsUnique
FROM
	sys.indexes i
JOIN sys.index_columns ic ON
	i.index_id = ic.index_id
	AND i.object_id = ic.object_id
JOIN sys.columns c ON
	ic.column_id = c.column_id
	AND ic.object_id = c.object_id
WHERE
	i.object_id = OBJECT_ID('dbo.poline')
	AND c.name IN ('ponum', 'revisionnum', 'polinenum', 'siteid')
GROUP BY
	i.name,
	i.is_unique
HAVING
	COUNT(c.name) = 4;

Query to Find Existing Index (Oracle database):
SELECT
	i.index_name,
	i.uniqueness AS IsUnique
FROM
	user_indexes i
JOIN user_ind_columns c ON
	i.index_name = c.index_name
WHERE
	i.table_name = 'POLINE'
	AND c.column_name IN ('PONUM', 'REVISIONNUM', 'POLINENUM', 'SITEID')
GROUP BY
	i.index_name,
	i.uniqueness
HAVING
	COUNT(c.column_name) = 4;

Query to Find Existing Index (Db2):
SELECT
	i.NAME AS IndexName,
	i.UNIQUERULE AS IsUnique
FROM
	MAXIMO.MAXSYSINDEXES i
JOIN MAXIMO.MAXSYSKEYS k ON
	i.NAME = k.IXNAME
WHERE
	i.TBNAME = 'POLINE'
	AND k.COLNAME IN ('PONUM', 'REVISIONNUM', 'POLINENUM', 'SITEID')
GROUP BY
	i.NAME,
	i.UNIQUERULE
HAVING
	COUNT(DISTINCT k.COLNAME) = 4;


3. If the result of the above query is not empty. Check if a unique index already exists on the same four columns. If it is already a unique index, the user might not need to create a new unique index.

Step 3: Handling Non-Unique Index
1. If the index is not unique, take note of the index (for example out-of-box non-unique index, POLINE_NDX10), which might be the existing non-unique index.
2. Go to Database Configuration Application and Remove the non-unique index from the Alternate Index field for the POLINE object on the Object tab.
3. Go to the Index Tab, and delete the non-unique index (POLINE_NDX10).
4. Save the record.

Step 4: Create a New Unique Index
1. Go to Database Configuration Application > Go to the Index Tab > Add a new index
2. Index name: UNIQUE_POLINE_NDX10
3. Storage Partition: MAXINDEX
4. Enforce Uniqueness? Yes
5. Add columns in the following order - PONUM, REVISIONNUM, POLINENUM, SITEID
6. Set the newly created UNIQUE_POLINE_NDX10 index as the alternate index (MAXOBJECTCFG.ALTIXNAME) for the POLINE object from the Database Configuration Application on the Object tab.
7. Save and apply the configuration changes. Be sure to take a database backup and perform the changes in Admin Mode.
 
DT424145
1. Open Application Designer.
2. Click Export System XML.
3. Click the icon next to LIBRARY. Save the file as library.xml.
4. Search for 'tablecol id="classspec_table_tablebody_4"'.
5. Remove the entire line it is in.
6. In its place, add the line 
<tablecol id="classspec_table_tablebody_4" dataattribute="SPECVALUE" sortable="false" lookup="" smartfilloff="true"/>
7. Search for 'tablecol id="searchAttributeItem_table_tablebody_7"'.
8. Remove the entire line it is in.
9. In its place, add the line 
<tablecol id="searchAttributeItem_table_tablebody_7" dataattribute="specvalue" lookup="" label="Search Value" smartfilloff="true"/>
10. Search for 'tablecol id="SEARCHATTR_table_tablebody_7"'.
11. Remove the entire line it is in.
12. In its place, add the line 
<tablecol id="SEARCHATTR_table_tablebody_7" dataattribute="specvalue" lookup="" label="Search Value" smartfilloff="true"/>
13. Save the modified library.xml file.
14. In Application Designer, import the modified library.xml file.
15 Save changes.
DT397288
A. Database Configuration
Add a date value attribute for the FEATURESPEC and ASSETFEATURESPEC objects. For example:
1. Open Database Configuration.
2. Filter for the FEATURESPEC application.
3. Click the Attributes tab.
4. Add a date value attribute:
  • Attribute: DATEVALUE
  • Type: DATE
  • Title: Date Value
  • Description:- Date Value
  • Length: 4
  • Leave the Persistent? toggle on
Repeat for the ASSETFEATURESPEC object.
Follow the steps in the documentation at Adding attributes to objects
 
Modify the ASSETATTRID attribute for FEATURESPEC and ASSETFEATURESPEC objects. For example:
1. Open Database Configuration.
2. Filter for the FEATURESPEC application.
3. Click the Attributes tab.
4. Filter for the ASSETATTRID attribute.
Change the Class name: Class - psdi.app.ticket.FldTKCommonSpecAssetAttrid
Save.
Repeat for the ASSETFEATURESPEC object ASSETATTRID attribute.
Once Database Configuration changes are done, apply them by following the steps in the documentation at Configuring the database in administration mode.

B. Application Designer
Make XML changes required in asset.xml and feature.xml to implement UI changes for the Date Value field.
1. Open Application Designer.
2. Filter for the ASSET application, and click it.
3. Export Application Definition. Save the file as asset.xml
4. Open the asset.xml file in a text editor.
5.1 Search for id "AssetFeature_specifications_table_tablebody_4"
5.2 After that, add the line
<tablecol dataattribute="datevalue" id="AssetFeature_specifications_table_tablebody_date_11" lookup="datelookup"/>
5.3 Search for id "AssetFeature_specifications_table_1_griddetails2_3b"
5.4 After that, add the line
<textbox dataattribute="datevalue" id="AssetFeature_specifications_table_1_griddetails2_date_8" lookup="datelookup" smartfilloff="true"/>
6. Save asset.xml
7. In Application Designer, import the modified asset.xml file.
8. Save changes
 
9. Filter for the FEATURE application, and click it.
10. Export Application Definition. Save the file as feature.xml
11. Open the feature.xml file in a text editor.
12.1 Search for id "specification_featurespectable_tablebody_4"
13.2 After that, add the line
<tablecol id="specification_featurespectable_tablebody_4b" dataattribute="datevalue" lookup="datelookup"/>
13.3 Search for id "specifications_specifications_table_1_griddetails1_row_col2_sec"
13.4 After that, add the line
<textbox id="specification_featurespectable_1_griddetails_date_4b" dataattribute="datevalue" lookup="datelookup" smartfilloff="true"/>
14. Save feature.xml.
15. In Application Designer, import the modified feature.xml file.
16. Save changes.
DT434507 To add new message, follow these steps:
1. Log into Manage as an administrative user.
2. Go to Database Configuration.
3. In the More Actions section, click Messages.
4. Click the New Row icon (plus sign inside a circle)
5. For the new row, enter these details:
  •   Message Group: invoice
  •   Message Key: matchSignOfPOLineCost
  •   Display Method: MSGBOX
  •   Message ID Prefix: BMXAA
  •   Message ID Suffix: E
  •   Display ID?: Checked
  •   Value: The PO Line cost is \{0}. The credited cost against this line must be \{1}.
  •   Button Ok?: Checked
When finished, click OK.
 
IJ38063 Associate the object's classstrucureid to each budget rule for newly added workorder focal points. The attribute should be CLASSSTRUCTUREID, WORKORDER.CLASSSTRUCTUREID, or REFWO to define the appropriate associations against each rule. This is a list of associations for each Rules by object.
  • LABTRANS: WORKORDER.CLASSSTRUCTUREID
  • WPLABOR: WORKORDER.CLASSSTRUCTUREID
  • WPMATERIAL: WORKORDER.CLASSSTRUCTUREID
  • WPSERVICE: WORKORDER.CLASSSTRUCTUREID
  • WPTOOL: WORKORDER.CLASSSTRUCTUREID
  • MATRECTRANS: WORKORDER.CLASSSTRUCTUREID
  • MATUSETRANS: WORKORDER.CLASSSTRUCTUREID
  • POLINE: CLASSSTRUCTUREID
  • PRLINE: CLASSSTRUCTUREID
  • SERVRECTRANS: REFWO
  • TOOLTRANS: REFWO

APAR Change information
To ensure there is no conflict before applying the current fix, it is important to verify that the attribute LASTPMWOGENREADING does not already exist on the WOMETERobject.

APAR Change details
DT434309
The attribute LASTPMWOGENREADING is added on WOMETER object as a part of the fix for this issue to store LASTPMWOGENREAD value on PMMETER while the WO is generated.

[{"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.0.0","Type":"MASTER"}]

Document Information

More support for:
IBM Maximo Application Suite

Component:
Manage

Software version:
9.0.0

Document number:
7231536

Modified date:
20 June 2025

UID

ibm17231536

Manage My Notification Subscriptions

Page Feedback