Add fields to user interfaces

You can add fields to the user interfaces in the Maximo® Asset Management work order, purchasing, inventory, and cost management applications.

The following table lists hidden fields that you might need to add to the user interfaces in the Maximo Asset Management work order, purchasing, inventory, and cost management applications. In some cases adding the field is optional, depending on your business practices.

You add these fields through the Application Designer application in the Maximo Asset Management configuration module.

Table 1. Fields to add to windows in Maximo Asset Management
Application	Page	Field	Required or optional
Work Order Tracking	Work Order tab	Project ID Task ID	Required
	Labor subtab of Actuals tab	Expenditure type	See text
	Materials subtab of Actuals tab	Expenditure type Charge organization Non‐labor charge organization	See text
	Tools subtab of Actuals tab	Expenditure type Charge organization Non‐labor charge organization	See text
	Services subtab of Actuals tab	Expenditure type Charge organization Non‐labor charge organization Note: On the Services subtab, the fields are display only	See text
Purchase Requisitions	PR Lines tab	Expenditure type Charge organization	See text
Purchase Orders	PO Lines tab	Expenditure type Charge organization	See text
Receipts	Material receipts tab	Expenditure type Charge organization Non‐labor charge organization	See text
Receipts	Service Receipts tab	Expenditure type Charge organization Non‐labor charge organization	See text
Invoices	Invoice Lines tab	Expenditure type Charge organization	See text
Issues and Transfers	Issue	Expenditure type Charge organization Non‐labor charge organization	See text
Cost Management	Project tab	Budget Cost Burdened Cost Committed Cost Remaining Cost	Optional

You do not have to add the expenditure type field if your business does one of the following:

Uses a single expenditure type for items, a single expenditure type for labor, and a single expenditure type for tools
Uses item number, labor code, and tool code as expenditure types

In these cases, transactions that require these values use the default values in the EXPENDITEM, EXPENDLABOR, and EXPENDTIOOL integration controls, respectively.

In all other cases, add the expenditure type field to the applicable user interfaces.

You do not need to add the charge organization and non‐labor resource organization fields if your business uses a single charge organization and a single non‐labor resource organization for all transactions. Transactions that require these values will use the default values in the CHARGEORG and NLRORG integration controls, respectively.

If your business uses multiple charge or non‐labor resource organizations, add the two fields to the applicable user interfaces.