Maximo Open Forum

 View Only

 Why Does POLINE.ORDERUNIT Default Value Not Populate on New PO Line in PO Screen?

  • Administration
  • Maximo Application Suite
  • Procurement
Jared Schrag's profile image
Jared Schrag posted 02-27-2026 10:09

In our MAS v9.1.5 system, in Database Configuration for the POLINE object, for the ORDERUNIT attribute, we have a Default Value "EA" specified. However, when in the PO screen, on a new PO, in the PO Lines tab, when I click New Row, the Order Unit field is not populated with the default value. What am I missing here? I've confirmed that we have no Automation Scripts that set the value of the POLINE.ORDERUNIT attribute. What else should I be checking?

Here is the Database Configuration for POLINE.ORDERUNIT:

image

Here is an example of clicking New Row on the PO Lines tab in the PO applicaiotn screen:

image
Steven Shull's profile image
Steven Shull posted 03-02-2026 10:18

This is one of the difficult scenarios of defaulting where the MBO logic overrides the database default values. What happens is the linetype being set to ITEM triggers a clearFields() method on the attribute class that clears the orderunit. Since this executes after the database default, your database default should trigger and then get set back to null. 

I don't love application defaults (because they only impact a single application and won't handle mobile or the new UI framework) but these defaults fire after MBO defaults so it might work. Or you can try to tie an attribute launch point automation script on linetype to set orderunit to EA if orderunit is null. 

Related Content