FSM Consumable Record

In Field Service Management (FSM), a consumable records an item and quantity used during a customer relationship management (CRM) task. It connects the usage to the technician, the asset being serviced, and, where applicable, the stock location, bin, and serial or lot number.

FSM uses the custom Field Service Consumable record to retain usage separately from the task and its transactions. Associated processing can add the usage to a sales order and fulfill eligible items. Recording a consumable doesn't itself establish a stock movement, invoice, or completed fulfillment. For information about the processing lifecycle, see FSM Consumable Processing.

Record Information

Use these identifiers for searches, mappings, and integrations. Field labels can vary by account or form.

Property	Value
Record type	FSM custom record
Record name	Field Service Consumable
Record ID	customrecord_nx_consumable
Record identity	NetSuite Internal ID (internalid)
FSM record model	models/consumable
Standard FSM Mobile resource	consumables, labeled Inventory

The record type ID is also used in FSM record searches. The mapped model attributes quantity and transaction are not additional stored field IDs. The supplied record doesn't use a Name field or automatic record numbering as its identity.

Forms

The standard FSM Mobile Inventory tab defines its fields directly in the consumables resource. It doesn't load a NetSuite custom form to generate those fields. The selected inventory option supplies the Item, Location, Bin, and serial or lot details, which appear as read-only values. Quantity is a required whole-number input of at least 1. The resource supplies the current Task, current employee, and selected child Asset or Task Asset when creating the NetSuite record.

A NetSuite Consumable form presents the same underlying record fields. An account can have customized forms with layouts, preferred-form choices, and additional requirements that are separate from the standard FSM Mobile resource. For an applicable custom entry form, Store Form with Record retains that form for later viewing and editing instead of using the preferred form. Available form properties depend on the form type. See Custom Entry Form Properties.

For FSM Mobile field definitions and supported customization, see Configuring FSM Consumable Processing. If an account uses form-generated FSM Mobile fields, see Form Properties for the shared loading and override rules. Loading a form to generate FSM Mobile fields is separate from storing a UI form with a Consumable.

Record Relationships

The Consumable stores the references in the following table unless the table identifies another record as the owner. Several consumable records can reference the same Task, Case, Asset, employee, Item, or stock location.

Related record	Relationship and field ID	Purpose
CRM Task	Consumable Task (custrecord_nx_constask) references native task.	Required link to the visit. It is a supplied parent-record relationship, allowing related Consumables to appear on the Task. The supplied FSM Task form includes this sublist.
Case	Consumable Case (custrecord_nx_conscase) references supportcase.	Associates usage with the service request. Its supplied field sourcing uses the selected Task's native Case relationship.
Asset	Consumable Asset (custrecord_nx_consasset) references customrecord_nx_asset.	Identifies the equipment or site associated with this usage. NetSuite field sourcing uses Task Asset (custevent_nx_task_asset). FSM Mobile can supply the selected child Asset instead.
Employee	Consumable Employee (custrecord_nx_consemployee) references employee.	Identifies the technician associated with the usage. Standard FSM Mobile supplies the current employee, which can differ from the task's assignee.
Item	Consumable Item (custrecord_nx_consitem) references item.	Identifies the item used. The Item being consumed is separate from the Item represented by the serviced asset.
Location	Consumable Location (custrecord_nx_conslocation) references location.	Identifies the stock location from which the item was used. It is separate from the customer's address or service location.
Bin	Consumable Bin (custrecord_nx_conbin) references the native Bin record.	Identifies the selected stock bin, where applicable.
Price Level	Consumable Price Level (custrecord_nx_consprice_level) references a NetSuite price level.	Provides pricing context when Multiple Prices is enabled.
Billing transaction	Consumable Billing Transaction (custrecord_nx_constransaction) references a transaction.	FSM Consumable Processing maintains this as the associated sales order reference. It is a transaction link, not an invoice or fulfillment status.
Sales order line	The line's Field Service Consumable (custcol_nx_consumable) references the Consumable.	Connects the transaction line to its originating usage. The line separately stores Task (custcol_nx_task) and Asset (custcol_nx_asset) references.

Customer and Project context comes through the Task and Case. The supplied Consumable has no separate Customer or Project field. The Case's Field Service Transaction (custevent_nx_case_transaction) is another stored relationship, distinct from the Consumable's Billing Transaction.

The Asset link associates the usage with equipment. It doesn't create an Asset hierarchy or establish that every history view or report includes the record. Additional account custom links don't automatically add inheritance, FSM Mobile presentation, reporting, or synchronization behavior.

FSM Fields

These are the supplied Consumable fields and the native identity fields with significant FSM use. Requirements and initial values in the following tables identify their source and scope.

Usage and Stock Details

The stored usage keeps the item, quantity, and stock selections together.

Field	Field ID	Purpose	Important values or behavior
Task	custrecord_nx_constask	CRM Task for the usage.	Required in the supplied record definition. Consumables don't use Project Tasks.
Case	custrecord_nx_conscase	Service Case associated with the usage.	Stored field with sourcing from Task. Not required in the supplied record definition. Case-based processing requires the applicable Case relationship.
Asset	custrecord_nx_consasset	Asset associated with the usage.	Stored separately from Task Asset. Standard FSM Mobile can supply a selected child Asset.
Employee	custrecord_nx_consemployee	Technician associated with the usage.	Standard FSM Mobile supplies the current employee and uses it with Task to select entries.
Item	custrecord_nx_consitem	Item used.	Required in the supplied record definition. Supported tab item types and selection conditions are defined in FSM Consumable Processing.
Quantity	custrecord_nx_consqty	Quantity used.	Decimal numeric field. Required with a minimum of 0.00001 in the supplied record definition. Standard FSM Mobile separately requires whole numbers of at least 1.
Location	custrecord_nx_conslocation	Stock source.	Standard FSM Mobile obtains it from the inventory option. Processing uses the saved location. An employee location or service address is not a replacement for this stored value.
Bin	custrecord_nx_conbin	Selected bin.	Stock assignments must match the item and location. Basic and advanced bin management use this selection differently during transaction processing.
Serial	custrecord_nx_conserial	Selected serial or lot identifier used by processing.	Stored as text. Standard FSM Mobile writes the selected inventory-number ID here, despite the label Serial. It is separate from Serial Label.
Serial Label	custrecord_nx_conseriallabel	Display text for the selected serial or lot.	Standard FSM Mobile stores the inventory option's number label here. The display label doesn't replace the identifier used for processing.

There is no separate Units field on the supplied Consumable record. When adding usage to a sales order, FSM writes Quantity without explicitly setting the line's Units (units). NetSuite transaction sourcing and account behavior determine the units. The recorded quantity and required inventory assignments must be valid for those transaction units. A decimal record field doesn't establish fractional input or unit conversion in the standard FSM Mobile tab.

A standard FSM Mobile entry can store one selected inventory number and one bin, when applicable. For the effects on serialized, lot-numbered, and bin-managed stock, see Inventory-Assignment Scenarios.

Billing and Transaction Data

Billable and Price Level describe pricing inputs. Billing Transaction records an association created by separate transaction processing.

Field	Field ID	Purpose	Important values or behavior
Billable	custrecord_nx_consbillable	Indicates whether usage is billable for pricing.	Checked by default in the supplied field definition. Applicable Task Billing Rule validation can replace the entered value. If the Billable box is cleared after validation, FSM sets the sales order line's rate to 0 when adding the usage. It doesn't prevent line creation or eligible fulfillment.
Price Level	custrecord_nx_consprice_level	Pricing level for the usage.	With Multiple Prices enabled, validation can set Price Level from a rule, customer pricing, or the default price level.
Billing Transaction	custrecord_nx_constransaction	Associated billing transaction.	Maintained as a sales order link by Consumable Processing. A populated value excludes the Consumable from new billing collection. It doesn't establish fulfillment or invoicing.

A Custom price level is stored as blank. For ordinary items, the consumable model interprets a blank level as Custom (-1). For item groups, consumable collection supplies no price level. A blank field doesn't mean that pricing is omitted.

The Task's Billing Rule (custevent_nx_billing_type) is stored on the Task, not the Consumable. For information about rule selection, recalculation, and pricing precedence, see FSM Billing Rules. The standard FSM Mobile tab has no direct rate or amount entry.

Identity and Processing Indicators

The following table distinguishes record identity from transaction associations and processing indicators.

Field or indicator	Field ID	Meaning
Internal ID	internalid	Identifies the saved Consumable. Transaction lines use this identity in their Field Service Consumable reference.
External ID	externalid	Native identity used by standard FSM Mobile synchronization to recognize repeated creation requests, with the fsm_ prefix. It is not a billing or fulfillment status.
Idempotency Key	custrecord_nx_consumable_idempotency_key	Custom field retained for compatibility and visibility. Current standard FSM Mobile creation uses External ID instead. It is not a recurrence or processing-completion indicator.
Billing Transaction	custrecord_nx_constransaction	A sales order association maintained separately from fulfillment. A blank value alone doesn't prove that no sales order line already references the Consumable.

The supplied Consumable has no dedicated pending, running, fulfilled, or error-reference field. Associated Field Service Error records hold their own affected-record and deployment information. For processing consequences, see Processing Visibility and Errors.

A Task's Completed status, a populated Billing Transaction, or a completed script execution doesn't establish that every intended line was priced, fulfilled, or invoiced. Fulfillment results are held on the related transactions. Script execution and monitoring are covered by FSM Script Reference.

Creation and Update Sources

Recording usage, validating its values, and updating transaction links are separate operations.

Source	Effect on the record
FSM Mobile Inventory tab	Saves usage locally, then synchronizes the Consumable to NetSuite with Task, employee, Asset, Item, quantity, and applicable stock details. A local save doesn't itself establish the NetSuite record or transaction result.
NetSuite Consumable entry	Creates or edits the custom record using the selected form, record requirements, and applicable FSM handling.
Supplied field sourcing	Supplies Case and Asset values from the selected Task in the NetSuite record context. FSM Mobile supplies its Asset default separately.
FSM billing validation	Can replace Billable and, with Multiple Prices enabled, Price Level. It doesn't create a sales order by itself.
Consumable transaction-link processing	Finds sales order lines referencing the Consumable and fills its missing Billing Transaction. Sales order addition and fulfillment are separate stages.

Field Service User Event and Field Service Client provide the supplied Consumable record handling. Field Service Scheduled : Consumable performs the background transaction work. Their identities and operational controls belong in FSM Script Reference.

Editing a Consumable after it has been added to a sales order doesn't update its existing sales order line through this processing path. See FSM Consumable Processing for transaction and linking behavior.

Used by FSM Features

The following table shows how FSM features use consumable data.

Feature	How the record is used
FSM Consumable Processing	Uses recorded item usage and Case/Task relationships to add sales order lines, complete transaction links, and fulfill eligible items.
FSM Billing Rules	Uses the linked CRM Task's Billing Rule to determine Billable and applicable Price Level during validation.
FSM Mobile Duplicate Creation Protection	Uses standard creation identity to recognize repeated requests for the same FSM Mobile entry.

Record Constraints and Data Requirements

The supplied record definition requires Task, Item, and Quantity, with Quantity at least 0.00001. Its other custom fields are not marked required. This doesn't make every combination usable for sales-order or inventory processing. FSM Mobile input rules, an account form, and transaction validation can impose additional requirements.

The standard FSM Mobile form requires Item and an integer Quantity of at least 1. It obtains stock details from an inventory option rather than allowing independent entry of those details. Location, bin, and serial or lot requirements depend on the item, enabled inventory features, and transaction being processed.

Case-based billing needs the appropriate Case relationship. The billing collection and fulfillment rules are defined in FSM Consumable Processing. The presence of a valid Consumable alone doesn't establish eligibility or successful processing.

Additional Information

• FSM Consumable Processing
• FSM Consumable Inventory and Fulfillment
• FSM Billing Rules

Related Topics

• FSM Records
• FSM CRM Task Record
• FSM Item Record
• FSM Location Record
• FSM Sales Order Record

General Notices