Note. For many of the new features in this article you might find that the field is missing from the user interface or dialog box. We have found this is the case both with a new install and an upgrade from MAS 9.1. You will need to run the presentation.mxs file(s); see this IBM Support Tech Note for instructions – https://www.ibm.com/support/pages/presentation-changes-are-not-applied-automatically-when-using-feature-channel

It looks as if this is associated with new features that were delivered as part of the Feature Channel and might be limited to applications using the classic user interface, and not the Maximo Application Framework. In the Maximo Secrets environment I use there were presentation.mxs files for Manage, Service Provider, Transportation and Spatial, but not one for HSE or Optimizer which are also installed.

Addition of PR field to Purchase Orders – Advanced Search

It seems such a small thing and missing from the Advanced Search dialog for years, the ability to search for Purchase Orders based on the PR reference on the PO line. You’ll find this field in the Line Details section, third column below GL Debit Account and GL Credit Account.

If you are using a MAXDEMO database, then you can search with % or PR 1023. The field has no Select Value (it could be a lot of records), but there is a Go To menu to allow you to navigate to the Purchase Requisitions application or one of its industry solution/add-on clones to find the required PR.

Adding Rotating Asset to View Inventory Transactions

In the Inventory application it wasn’t possible previously to see which rotating asset had been transferred, issues or returned, although these details were recorded in MATRECTRANS and MATUSETRANS objects.

The field Rotating AssetA Rotating Asset is an asset that is tracked between operating locations, repair workshops, and can be added to a storeroom ready to be issued again. More has been added to the dialog View Inventory Transactions in three places. For PUMP100 in the CENTRAL storeroom, in the Receipts & Transfers tab you will find the field in the line details, third column.

I’ve used the Issue Current Item to issue Rotating Asset 2077 to a new work order 1205 at APPR state.

Back in the View Inventory Transactions dialog and now on the Issues & Returns tab you’ll find Rotating Asset in the third column of the table details, but it is also in the table window header (not shown).

There is no change in the Adjustments tab.

Prevent Asset Population from Location

In the Work Order applications, the default scenario is that when you enter a Location if the location only has one asset, then the Asset field is also populated. If there are multiple assets at the location, then you need to use the Select Value. In the MAXDEMO database Asset 2077 is populated when you enter Location BOILER, it is the only asset at that location.

Note. The same population of the asset field also works on the Multiple Assets, Locations and CI table, and on the work order tasks.

There is an organization-based setting found in the OrganizationsA structural element of a Maximo database which is used for data sharing. More application and Asset Options dialog in the new section called Asset Autopopulation, there is a checkbox titled Prevent Asset population from Location?

When this is enabled, when you select or enter the Location on the work order it will no longer populate the asset. This is also the case on work order tasks and in the Multiple Assets, Locations and CI table.

Work Order Description derived from Job Plan during PM Generation

When you generate a work order from a PM the PM description is used as the work order’s description. An option has been provided in MAS 9.2 to allow the work order description to use the job plan’s description.

In the MAXDEMO database I am using PM PM-GEN and generating a work order using the Generate Work Orders action with the Use Frequency Criteria field disabled. Before I can generate a work order for PM-GEN I need to make it Active and change the status for asset 11230 to Operating.

The PM record PM-GEN has a description of Generator Overhaul. Its Job Plan JP11210 has a description of Emergency Generator Overhaul.

When I generated work order 1206 its description was – Generator Overhaul – derived from the PM.

In the Organizations application and action PM Options there is a SiteA structural element of a Maximo database that is used for data separation. More level set of settings, the new one is called Use Job Plan Description. I’ve selected this for the BEDFORD site.

The second work order generated from the PM, 1207 had a description of – Emergency Generator Overhaul – derived from the Job Plan.

Work Order Actuals selecting a Rotating Asset populates Storeroom

In previous versions when you are in the Work Order Tracking application and Actuals-Materials tab and you are entering a new row, when you select an Item which is set to Rotating the Rotating Asset field becomes mandatory, but if you select it before entering a storeroom you will receive an error message – BMXAA1818E – Please enter a storeroom location – the Storeroom field is not marked as mandatory.

The Rotating Asset field is at the bottom of the table details (not shown).

In MAS 9.2 a change was made to allow the selection of the Rotating Asset and allow Maximo to populate the Storeroom, it already knows where it is located. The Select Value for the Rotating Asset field is shown. Note that there are Rotating Assets from Storeroom Locations like CENTRAL or GARAGE, but also other types of locationsA physical place where assets exist and where work can be performed. More which are not storerooms. If you select a rotating asset from location REPAIR, for example, you would receive the error BMXAA2660E – Storeroom REPAIR is not a valid inventory location.

Observant readers might also wonder what the Alias field is doing here. That is because I have the Transportation Industry Solution installed on the Maximo Secrets environment.

I’ve selected Rotating Asset 2086 from the CENTRAL storeroom. In MAS 9.2, no error is displayed and the Storeroom field (not shown) has been populated from the selection of the Rotating Asset.

There are also a couple of additions:

• If you try to change the Rotating Asset and it doesn’t align with the Item, Storeroom and Site, then you will receive a new error – Rotating asset 1245 does not match item/storeroom/site. Enter a valid rotating asset. (BMXAA1035).
• If you clear the Site field, the Storeroom and Rotating Asset fields are also cleared. If you now, try to select a Rotating Asset you will receive a different error – BMXAA10356E – Site field cannot be empty. Select a valid site. This is because the Site field is mandatory and it needs to be populated before selecting the Rotating Asset.

PM End of Calendar Month Due Date Calculations

In previous versions of MAS there was a System Property mxe.pm.enforceMaximumDayOfMonthContinuity which when set to 1 would generate PM based work orders with a frequency unit of MONTHS to the last day of that month. This System Property no longer exists and has been replaced by a site level based MAXVARS setting found in the Organizations application and PM Options. The field in the section PM Options is called – Set Due Date to End of Month.

In the Preventive Maintenance application and Frequency – Time Based Frequency tab, there is the same field Set Due Date to End of Month. This field only appears when the Frequency Units is set to MONTHS, but be patient, it is based on a condition, and for me it did not appear immediately, I’d already navigated back to the main tab and later checked the Frequency tab and saw that the field was now displaying.

I’ve created a new PM 1020 with a frequency of 1 MONTHS starting 1-Aug-26, and I’ve now made it Active by using the Change Status action. You need to do this before you create a forecast which will be the easiest way to visualise how Maximo is processing this change.

I’ll generate a forecast for the next year by using the Generate Forecast action, the Forecast Until date is set to 31^st July 2027.

A forecast is generated with the first Forecast Date set to the Estimated Next Due Date 1^st Aug 2026 and monthly thereafter all starting on the 1^st of the month.

I’ve now set the field – Set Due Date to End of Month. At first when I deleted and recreated the forecast it didn’t work, then I quickly realised that the Estimated Next Due Date needs to start at the end of a month. It has now been set for 31^st July 2026.

After deleting and recreating the forecast the forecast dates now start on 31^st July 2026 and are the end days of each month, no leap year for us in 2027.

I did run a test setting the Organizations – PM Options field for the BEDFORD site to check that the default for Set Due Date to End of Month worked for a new PM, it did default as I expected.

The same field has been added to the Master PM application. It doesn’t get defaulted from the value in the Organizations application, I quickly realised this is because Master PMs are defined at the System level. But the field is there for you to set it. I verified that if a PM is associated with a Master PM that the field Set Due Date to End of Month on a PM would be updated when the Master PM action Update Associated PMs is used.