FSM Consumable Transaction Field Mapping

Field Service Management (FSM) uses consumable values to add sales-order lines, prepare fulfillment, and complete transaction links. The following tables describe those transaction effects. For the overall processing flow and prerequisites, see FSM Consumable Processing. For record definitions, see FSM Consumable Record.

From Consumable Fields to Sales-Order and Fulfillment Lines

The Field Service Consumable record (customrecord_nx_consumable) preserves the recorded usage. The table describes what the supplied processing path does with each relevant value. It does not describe additional account scripts or workflows.

Consumable Value	Sales-Order Effect	Fulfillment or Linking Effect
Consumable internal ID	Write the line's Field Service Consumable reference (`custcol_nx_consumable`).	Match the originating usage to an order line and complete missing transaction links.
Item (`custrecord_nx_consitem`)	Write Item (`item`).	The transformed order supplies the item. Its characteristics related to fulfillment, serial or lot numbers, and bins determine eligibility and assignment requirements.
Quantity (`custrecord_nx_consqty`)	Write Quantity (`quantity`).	Supply the recorded quantity for the matched line. Lines that require numbered inventory or bin details use the sum of retained assignment quantities.
CRM Task (`custrecord_nx_constask`)	Write line Field Service Task (`custcol_nx_task`) when supplied. Case billing does not explicitly supply an order-body Task from the consumables.	Group work by task and location. Write the fulfillment's Field Service Task (`custbody_nx_task`).
Case (`custrecord_nx_conscase`)	Select the case and its transaction. A newly created order receives Field Service Case (`custbody_nx_case`).	Complete the case's Field Service Transaction (`custevent_nx_case_transaction`) link to the order. The bundled Consumable Case field sources from its CRM Task.
Asset (`custrecord_nx_consasset`)	Write Field Service Asset on the line (`custcol_nx_asset`) when supplied.	The transformed line supplies its asset relationship. This can identify a child asset separately from the order's body asset.
Employee (`custrecord_nx_consemployee`)	No employee line field is explicitly written by this addition path.	Used in the standard FSM Mobile list/default. Fulfillment collection is by task and location, without an employee filter.
Location (`custrecord_nx_conslocation`)	Write line Location (`location`), or line Inventory Location (`inventorylocation`) when Intercompany Cross-Subsidiary Fulfillment is enabled.	Assess using the corresponding order-line location, match consumables by task and location, and use that location to initialize the fulfillment.
Billable (`custrecord_nx_consbillable`)	Control Rate (`rate`). When the Billable box is cleared, FSM explicitly supplies 0. No separate consumable Billable field is written to the order line.	Does not exclude the line from fulfillment.
Price Level (`custrecord_nx_consprice_level`)	With Multiple Prices, supply Price Level (`price`) for ordinary items. A blank level becomes Custom (-1). No price level is supplied for item groups.	Pricing selection does not supply inventory assignments.
Serial or lot value (`custrecord_nx_conserial`)	Write Issue Inventory Number (`issueinventorynumber`) in advanced Inventory Detail, or Serial/Lot Numbers (`serialnumbers`) in basic management.	Classify the selected value as a serial number for a serialized item or as a lot number otherwise. Supply that inventory assignment.
Serial or lot label (`custrecord_nx_conseriallabel`)	No separate label field is explicitly copied to the line.	Supports FSM Mobile display. The stored number value is used for assignments. Advanced management uses inventory-number IDs. Basic management uses the number representation required by its fields.
Bin (`custrecord_nx_conbin`)	Write Inventory Detail Bin Number (`binnumber`) with advanced management. No direct bin write with basic management.	Supply the selected bin in advanced Inventory Detail or basic Bin Numbers (`binnumbers`).
Billing Transaction (`custrecord_nx_constransaction`)	A blank value permits collection for sales-order addition.	Set to the sales order during link completion. It identifies the order, rather than an invoice or fulfillment.

Consumable Value

Sales-Order Effect

Fulfillment or Linking Effect

Consumable internal ID

Write the line's Field Service Consumable reference (custcol_nx_consumable).

Match the originating usage to an order line and complete missing transaction links.

Item (custrecord_nx_consitem)

Write Item (item).

The transformed order supplies the item. Its characteristics related to fulfillment, serial or lot numbers, and bins determine eligibility and assignment requirements.

Quantity (custrecord_nx_consqty)

Write Quantity (quantity).

Supply the recorded quantity for the matched line. Lines that require numbered inventory or bin details use the sum of retained assignment quantities.

CRM Task (custrecord_nx_constask)

Write line Field Service Task (custcol_nx_task) when supplied. Case billing does not explicitly supply an order-body Task from the consumables.

Group work by task and location. Write the fulfillment's Field Service Task (custbody_nx_task).

Case (custrecord_nx_conscase)

Select the case and its transaction. A newly created order receives Field Service Case (custbody_nx_case).

Complete the case's Field Service Transaction (custevent_nx_case_transaction) link to the order. The bundled Consumable Case field sources from its CRM Task.

Asset (custrecord_nx_consasset)

Write Field Service Asset on the line (custcol_nx_asset) when supplied.

The transformed line supplies its asset relationship. This can identify a child asset separately from the order's body asset.

Employee (custrecord_nx_consemployee)

No employee line field is explicitly written by this addition path.

Used in the standard FSM Mobile list/default. Fulfillment collection is by task and location, without an employee filter.

Location (custrecord_nx_conslocation)

Write line Location (location), or line Inventory Location (inventorylocation) when Intercompany Cross-Subsidiary Fulfillment is enabled.

Assess using the corresponding order-line location, match consumables by task and location, and use that location to initialize the fulfillment.

Billable (custrecord_nx_consbillable)

Control Rate (rate). When the Billable box is cleared, FSM explicitly supplies 0. No separate consumable Billable field is written to the order line.

Does not exclude the line from fulfillment.

Price Level (custrecord_nx_consprice_level)

With Multiple Prices, supply Price Level (price) for ordinary items. A blank level becomes Custom (-1). No price level is supplied for item groups.

Pricing selection does not supply inventory assignments.

Serial or lot value (custrecord_nx_conserial)

Write Issue Inventory Number (issueinventorynumber) in advanced Inventory Detail, or Serial/Lot Numbers (serialnumbers) in basic management.

Classify the selected value as a serial number for a serialized item or as a lot number otherwise. Supply that inventory assignment.

Serial or lot label (custrecord_nx_conseriallabel)

No separate label field is explicitly copied to the line.

Supports FSM Mobile display. The stored number value is used for assignments. Advanced management uses inventory-number IDs. Basic management uses the number representation required by its fields.

Bin (custrecord_nx_conbin)

Write Inventory Detail Bin Number (binnumber) with advanced management. No direct bin write with basic management.

Supply the selected bin in advanced Inventory Detail or basic Bin Numbers (binnumbers).

Billing Transaction (custrecord_nx_constransaction)

A blank value permits collection for sales-order addition.

Set to the sales order during link completion. It identifies the order, rather than an invoice or fulfillment.

Rate and Amount are not copied from consumable price-entry fields. The standard consumable path supplies pricing as described in Billable and Price-Level Scenarios. It does not explicitly set line Amount. Additional custom consumable fields do not become transaction fields automatically through configuration.

Sales-Order Body and Fulfillment Record

For a new order without a linked case transaction, the supplied path uses these body values.

Input or Default	Sales-Order Result
Case customer	Field Service Customer (`custbody_nx_customer`) and customer/entity initialization.
Case company value, supplied as the transaction model's project	Project (`job`) when Project Management is enabled, or the appropriate project/customer Entity (`entity`) representation otherwise.
Case ID and asset	Field Service Case (`custbody_nx_case`) and body Field Service Asset (`custbody_nx_asset`). The line's asset comes from its own consumable.
Case purchase-order reference	PO/Check # (`otherrefnum`).
First collected consumable's creation date	Transaction Date (`trandate`).
Case subsidiary, when Multi-Subsidiary Customer is enabled	Subsidiary initialization for the new order.
Sales-order model defaults	Pending Fulfillment (`orderstatus` = B) and the cross-subsidiary transaction flag (`iscrosssubtransaction` = true).

Input or Default

Sales-Order Result

Case customer

Field Service Customer (custbody_nx_customer) and customer/entity initialization.

Case company value, supplied as the transaction model's project

Project (job) when Project Management is enabled, or the appropriate project/customer Entity (entity) representation otherwise.

Case ID and asset

Field Service Case (custbody_nx_case) and body Field Service Asset (custbody_nx_asset). The line's asset comes from its own consumable.

Case purchase-order reference

PO/Check # (otherrefnum).

First collected consumable's creation date

Transaction Date (trandate).

Case subsidiary, when Multi-Subsidiary Customer is enabled

Subsidiary initialization for the new order.

Sales-order model defaults

Pending Fulfillment (orderstatus = B) and the cross-subsidiary transaction flag (iscrosssubtransaction = true).

Other transaction values follow normal NetSuite sourcing, transformation, and account behavior. These values include currency, tax, shipping, addresses, and item units. This path does not copy these values from consumable usage fields. This addition does not explicitly write Units (units). Quantity and inventory-number requirements must match the transaction's units.

For fulfillment, FSM transforms the selected sales order (createdfrom) and supplies its task and stock location. FSM marks only matched qualifying order lines for fulfillment and supplies quantity and inventory assignments. Order-line identity comes from the transformed transaction. Saved consumable fulfillments receive Shipped status (shipstatus = C).

When sales-order save events run for a case, the sales-order model requests separate processing of unbilled amounts. It sets the case's update indicator (custevent_nx_unbilled_update) and schedules that work. The request is to refresh the case's unbilled amounts. Sales-order addition does not itself create an invoice or establish that recalculation finished. See FSM Case Invoicing for the related billing capability.

From Consumable Fields to Sales-Order and Fulfillment Lines

Sales-Order Body and Fulfillment Record

Related Topics