Hi guys, we have a GL Account structure with four components, and Components 1 and 2 are marked as 'Required'.

However, Maximo is allowing a GL Account to be created at the Location level without a Component 2 value.

Question here is at what point does Maximo enforce the 'Required' components of a GL Account?

------------------------------
Tom M
------------------------------

Hi Tom,

GL-segment required flag is taken into consideration only at the time, when full or partial GL-account validation triggers.
This is applicable mainly to the GL-accounts on financial transactions (LABTRANS, MATUSETRANS, MATRECTRANS, POs and INVOICEs) but only when validation options are enabled.
You can read more about this in @Andrew Jeffery's Maximo Secrets - Chart of Accounts – Validation Options.

------------------------------
Andrzej Więcław
Maximo Technical SME
Naviam
Wrocław, Poland

If this post was helpful, please click the Like button to let others know.
------------------------------

Hi Tom,

The "Required" components are not required when a GL field is only going through Partial GL Validation as is the case with Locations.GLAccount.  If you lookup that attribute in Database Configuration, you will see that the Class on that attribute is "psdi.app.financial.FldPartialGLAccount" as is also the case on the GLAccount attribute on other objects such as Asset and WorkOrder.

The Required attribute means that the component must be populated before the transactions is sent to the Financial System - General Ledger.  The non-required components are typically at the end of the GL Account.  For example, some companies use the last GL Component as a Project field and require it for capital charges but not for O&M charges.

The reason the GL Account fields on objects like Assets, Locations, and WorkOrder only go through Partial GL Validation is that there is logic in the system to merge components from different sources into a single GL Account.  For example, when a WO is created with an Asset and a Location, the system will default the GL Account on the WO to the GL Account on the Asset, but if there are any unspecified components of the GL Account on the Asset, it will replace those components with the corresponding components from the Location's GL Account if they are specified.

Additionally, most companies have a component of the GL Account that identifies a Resource/Expense Type such as Labor, Storeroom Material, Direct Purchase Material, etc.  That component is typically left unspecified on WOs because the same WO my have several different types of resources/expenses charge to it.  For instance, if a WO is entered on an ISSUE transaction, the GL Debit Account defaults to the value of the GL Account on the InvCost record for the Item / Storeroom / Condition combination and then any unspecified components are replaced with the corresponding components from the WO's GL Account if they are specified.  If any required components are still unspecified after the merge (and GL Validation is enabled), an error will occur when you try to save the transaction because the MatUseTrans.GLDebitAcct goes through Full GL Validation.  (Note: The GLAccount on the InvCost record is defaulted from the GLDefault attribute on the AccountDefaults record for the Commodity Group on the Item as specified on the Resource Codes dialog in the Chart of Accounts application.)

------------------------------
Julio Hernandez
Ergonare, Inc.
Phoenix AZ
480-759-9870
------------------------------

Thanks Julio and @Andrzej Więcław; that makes it all clear.

------------------------------
Tom M
------------------------------

Original Message:
Sent: Wed March 04, 2026 02:24 PM
From: Julio Hernandez
Subject: Required component on a GL Account

Hi Tom,

The "Required" components are not required when a GL field is only going through Partial GL Validation as is the case with Locations.GLAccount.  If you lookup that attribute in Database Configuration, you will see that the Class on that attribute is "psdi.app.financial.FldPartialGLAccount" as is also the case on the GLAccount attribute on other objects such as Asset and WorkOrder.

The Required attribute means that the component must be populated before the transactions is sent to the Financial System - General Ledger.  The non-required components are typically at the end of the GL Account.  For example, some companies use the last GL Component as a Project field and require it for capital charges but not for O&M charges.

The reason the GL Account fields on objects like Assets, Locations, and WorkOrder only go through Partial GL Validation is that there is logic in the system to merge components from different sources into a single GL Account.  For example, when a WO is created with an Asset and a Location, the system will default the GL Account on the WO to the GL Account on the Asset, but if there are any unspecified components of the GL Account on the Asset, it will replace those components with the corresponding components from the Location's GL Account if they are specified.

Additionally, most companies have a component of the GL Account that identifies a Resource/Expense Type such as Labor, Storeroom Material, Direct Purchase Material, etc.  That component is typically left unspecified on WOs because the same WO my have several different types of resources/expenses charge to it.  For instance, if a WO is entered on an ISSUE transaction, the GL Debit Account defaults to the value of the GL Account on the InvCost record for the Item / Storeroom / Condition combination and then any unspecified components are replaced with the corresponding components from the WO's GL Account if they are specified.  If any required components are still unspecified after the merge (and GL Validation is enabled), an error will occur when you try to save the transaction because the MatUseTrans.GLDebitAcct goes through Full GL Validation.  (Note: The GLAccount on the InvCost record is defaulted from the GLDefault attribute on the AccountDefaults record for the Commodity Group on the Item as specified on the Resource Codes dialog in the Chart of Accounts application.)

------------------------------
Julio Hernandez
Ergonare, Inc.
Phoenix AZ
480-759-9870
------------------------------