FSM Sales Order Record

A sales order records items and services ordered by a customer. Field Service Management (FSM) uses the standard NetSuite sales order transaction and adds relationships to service work. These relationships include cases, customer relationship management (CRM) tasks, project tasks, and assets.

An order can contain lines entered directly in FSM Mobile or added from separate consumable records. Item fulfillments and invoices record subsequent fulfillment and billing results. Saving the sales order doesn't establish either result.

Record Information

Use these identifiers when working with record mappings, searches, and integrations. Field labels can differ by account or form.

Property	Value
Record type	Standard NetSuite
Record name	Sales Order
Record ID	salesorder
Record identity	Internal ID (internalid). Order # (tranid) is the visible transaction number.
FSM record model	models/salesorder, inheriting models/transaction
Standard FSM Mobile resource	salesorder
Supplied FSM form	Field Service Sales Order (custform_nx_sales_order)

salesorder is the record type used by SuiteScript and FSM. SALESORDER in the supplied form definition identifies the form's transaction type. Transaction searches can use SalesOrd and status values with that prefix, such as SalesOrd:G. SalesOrd and its prefixed status values are search identifiers for the same record. See the NetSuite Sales Order reference.

Forms

The supplied Field Service Sales Order form presents native Customer and Project fields, FSM service relationships, and Task, Project Task, Asset, Case, and Consumable item columns. Its supplied definition is not marked preferred. An account can use its own customized sales order form. Native form and role preferences affect initial form selection. See Defining Preferred Forms.

NetSuite always stores the custom form with a sales order and uses the stored form when the transaction is reopened. Store Form with Record is not an optional checkbox for this transaction type. See Storing Custom Forms with Transactions.

The FSM sales order model doesn't define a default custom-form ID. A default configured for record creation applies to operations that use this model. This default doesn't change the form on existing orders. See Custom Forms for Record Creation.

The standard Sales Order tab in FSM Mobile defines its own elements and mappings. It doesn't generate its fields from the stored NetSuite sales order form. Its required fields and initial values therefore have a separate source. For supported FSM Mobile setup, see Configuring FSM Mobile Sales Order Management. For general form-generated element behavior, see Form Properties.

Record Relationships

Header relationships describe the order's service context. Item-line relationships identify the work or asset associated with an individual charge. They are separate stored values.

Header and Related-Record Links

These links are native NetSuite relationships or supplied FSM fields. The table identifies the record holding each reference.

Related record	Relationship and field ID	Purpose
Customer	Sales order native Customer (entity) and Field Service Customer (custbody_nx_customer)	Retains the service customer separately from a project. FSM synchronizes these values with the applicable transaction entity context.
Project	With Project Management, the native Project (job) field identifies the project. Without Project Management, the native entity field can identify the project.	Associates the order with the Project. There is no separate supplied FSM Project body field for this relationship.
Asset	Sales order Field Service Asset (custbody_nx_asset) references an FSM asset	Identifies the header asset. The associated CRM task or project task can supply this value.
Case	Sales order Field Service Case (custbody_nx_case) references a case	Associates this order with service work. Several orders can reference the same case.
Selected Case transaction	Case Field Service Transaction (custevent_nx_case_transaction) references a transaction	Selects one transaction on the case, including a potential sales order source for case invoicing. This reference is stored on the case.
CRM Task	Sales order Field Service Task (custbody_nx_task) references a CRM task	Identifies the order's CRM task context.
Project Task	Sales order Field Service Project Task (custbody_nx_projecttask) references a project task	Identifies the separate project task context. The standard mapping depends on Project Management.
Source Estimate or other supported source	Sales order native Created From (createdfrom) references the source transaction	Identifies a transformation source, including an estimate converted to an order.
Item Fulfillment or Invoice	The downstream transaction's native Created From (createdfrom) references the sales order	Connects fulfillment or billing results to the order. More than one downstream transaction can reference an order.
Consumable	Consumable Billing Transaction (custrecord_nx_constransaction) references the sales order	Records the order associated with processed usage. The originating consumable remains a separate FSM record.

The sales order's Case link and the case's selected Transaction are different relationships. Setting custbody_nx_case through the standard Sales Order tab in FSM Mobile doesn't automatically select that order in custevent_nx_case_transaction. Consumable processing can populate an empty Field Service Transaction field on the case. Transforming the case's selected source transaction into a sales order can replace that selection. See FSM Consumable Processing and FSM Mobile Quote Management.

For Customer, Project, and task-derived Asset sourcing, see FSM Customer and Asset Selection.

Item-Line Links

Each field in the following table is stored on an individual sales order item line. The supplied English column labels include '(trans)' where shown. Forms can use shorter labels.

Field	Field ID	Relationship and meaning
Field Service Task (trans)	custcol_nx_task	References the CRM task associated with this line. The standard editing rules in FSM Mobile use the current task relationship.
Field Service Project Task (trans)	custcol_nx_projecttask	References the project task associated with this line through a separate link from the CRM task.
Field Service Asset (trans)	custcol_nx_asset	References the asset associated with this charge. The supplied field can source from the line's CRM task Asset.
Field Service Case (trans)	custcol_nx_case	References the line's Case. The supplied field sources from the line's CRM task Case. It is separate from the header Case link.
Field Service Consumable	custcol_nx_consumable	References the originating consumable added by consumable processing. It doesn't mean that the line has been fulfilled or invoiced.

The standard direct sales order path in FSM Mobile supplies task and asset defaults for item entries. These defaults don't allocate each charge to a child asset automatically. Consumable processing supplies the recorded usage's task, asset, and consumable references when it appends a line. For details about direct entry, see FSM Mobile Sales Order Management. For consumable processing, see FSM Consumable Processing.

An account-created relationship remains a customization. Adding a field that links an order or line to another record doesn't automatically include that record in FSM Mobile, inheritance, history, reports, or synchronization.

FSM Fields

The relationship fields in Record Relationships and the following data help you interpret an FSM sales order. Native fields are identified as standard. The two additional Field Service body fields are supplied by FSM.

Transaction and Item Data

These values describe the order and its lines. Initial values and input rules depend on the creation source.

Field	Field ID	Meaning and important values
Date (standard)	trandate	Transaction date. The standard direct path in FSM Mobile defaults it from the task date. A new consumable-generated order uses the first collected consumable's creation date.
PO # (standard)	otherrefnum	Customer's purchase-order reference text, not a link to a NetSuite purchase order. When an order is created from case details, it can receive the case's PO reference.
Item and Quantity (standard, item line)	item, quantity	Item and Quantity are required for standard item entries in FSM Mobile. Quantity has an initial value of 1 and accepts whole numbers of at least 1. FSM Mobile configuration defines these requirements.
Price Level, Unit Price, and Amount (standard, item line)	price, rate, amount	Line pricing and calculated amount. Consumable processing can supply Price Level and sets rate to 0 for nonbillable usage. The direct sales order path in FSM Mobile doesn't apply FSM Billing Rules.
Location / Inventory Location (standard, item line)	location, inventorylocation	Stock-processing location, distinct from the customer's service address. FSM uses Inventory Location when Intercompany Cross-Subsidiary Fulfillment applies.
Inventory Detail (standard, item line)	inventorydetail	Bin and numbered-stock assignments when advanced inventory management applies. Other enabled inventory features use their applicable native fields.
Total (standard)	total	NetSuite transaction total. It can include charges outside the standard item table in FSM Mobile.
Field Service Customer Signature	custbody_nx_customer_signature	Rich-text signature content. The standard Sales Order tab doesn't provide a signature-entry control. Signed conversion on the Quote tab is a separate operation on an estimate.

For item and pricing support, inventory assignments and their limits, see FSM Mobile Sales Order Management and FSM Consumable Processing. Native field definitions are available in the Sales Order Records Browser.

Business State and Result Indicators

Order status, line quantities, and identifiers used during creation describe different facts. They are not scheduled-script execution states.

Field or value	Field ID	Meaning
Status (standard)	status and native order status field orderstatus	Saved order business state. The FSM model and standard direct creation path in FSM Mobile supply initial orderstatus: "B" (Pending Fulfillment). Account approval and other processes can change the saved result.
Fulfilled and Invoiced (standard, item line)	quantityfulfilled, quantitybilled	Separate quantities fulfilled and billed for that line. Use related transactions to establish the intended result.
Amount Unbilled (standard search value)	amountunbilled	Native order-level unbilled amount used by the case summary calculation. The calculation includes orders linked through header Field Service Case, even when they are not the case's selected Transaction.
External ID (standard)	externalid	Standard creation in FSM Mobile uses an External ID with the fsm_ prefix to recognize repeated requests. This ID is separate from Order # and doesn't indicate business completion.
Field Service Idempotency Key	custbody_nx_idempotency_key	Older custom identity field retained for compatibility and visibility. Standard creation in FSM Mobile uses External ID instead.

With Advanced Shipping, fulfillment and billing are separate. The following states help interpret an order. Without Advanced Shipping, native status meanings differ.

Status	Meaning with Advanced Shipping
Pending Approval	Approval is outstanding.
Pending Fulfillment	Approved and awaiting shipment.
Partially Fulfilled	Partly shipped. This state alone doesn't identify billing completion.
Pending Billing	Billing remains outstanding.
Pending Billing/Partially Fulfilled	Billing remains outstanding, and the order is partially fulfilled.
Billed	Fully shipped and invoiced.
Closed	The order is closed to further fulfillment and billing.
Canceled	The order is canceled.

See Viewing the Status of Sales Orders for native status meanings. A Shipped item fulfillment describes the lines and quantities on that fulfillment, not every line on the order.

Case invoicing separately checks the case's selected sales order, its billing status, and payment method. An unbilled amount or a case link alone doesn't establish invoice eligibility or exact invoice lines. See FSM Case Invoicing and FSM Case Unbilled Amount Calculation.

The supplied sales order fields have no general FSM processing-complete checkbox. A saved order, technical identity, or completed execution doesn't establish that fulfillment, invoicing, or related asset processing succeeded. For technical identity behavior, see FSM Mobile Duplicate Creation Protection.

Creation and Update Sources

The following sources can create or update an order. Their operations and subsequent results have different timing.

Source	Effect on the record
NetSuite entry, import, or integration	Creates or changes the native sales order and available FSM fields, subject to the operation's permissions and validation.
Direct FSM Mobile Sales Order tab	Creates or updates the order during synchronization. Its optional automatic fulfillment is part of that FSM Mobile save path. A local save doesn't confirm a NetSuite write.
FSM Mobile Quote conversion	Transforms an existing estimate following a signed update. Creates a separate sales order without the direct Sales Order tab's automatic fulfillment.
FSM Consumable Processing	Appends unlinked usage to the case's existing order, transforms a supported selected source, or creates an order from case details. Completing links and fulfilling items are separate background stages.
Case-related background updates	Can update the selected transaction's Project and Case links following case creation or a Company change. Saving the case doesn't establish completion of the order update.
Native fulfillment and billing	Related item fulfillments and billing transactions change the order's resulting status and quantities. They are separate records.

Sales order record handling uses Field Service User Event (customscript_nx_userevent, customdeploy_nx_salesorder_userevent) and Field Service Client (customscript_nx_client, customdeploy_nx_salesorder_client). Consumable and unbilled processing use their separate Scheduled deployments. See FSM Script Reference for execution and deployment details.

Used by FSM Features

The following topics explain how FSM features use sales order data.

Feature	How the record is used
FSM Mobile Sales Order Management	Direct order entry, task-related line editing, and optional fulfillment during synchronization.
FSM Mobile Quote Management	Sales order creation from a signed update to an existing estimate.
FSM Consumable Processing	Order lines and transaction links for separately recorded usage.
FSM Customer and Asset Selection	Native entity and FSM Customer and Asset selection and sourcing.
FSM Related Service Work	Case-related updates to the selected transaction's service context.
FSM Case Invoicing	An eligible selected order can supply invoice item lines.
FSM Case Unbilled Amount Calculation	Case-linked orders supply unbilled sales amounts.
FSM Asset Processing from Item Fulfillments	The order supplies the source for a fulfillment. Submitted fulfillment Asset rows drive separate Asset processing.

Record Constraints and Data Requirements

The supplied FSM sales order body and item-line fields are not required in their field definitions. A case, asset, CRM task, or project task link is therefore not a universal requirement on every native sales order. Features and account forms can require the relationships needed for their own operations.

The supplied sales order form requires native Customer, Date, and Status, along with Custom Form. Transaction validation in NetSuite and enabled features can impose additional requirements. Standard item and quantity requirements in FSM Mobile are separate from form requirements. Changing form requirements doesn't automatically change FSM Mobile element validation.

A header Task or shared Project doesn't mean you can edit every order line in FSM Mobile. Line relationships and standard editing protections determine which lines you can edit. Stock assignments and saved transaction quantities must also remain valid. For limits on partial fulfillment and existing transactions, see FSM Mobile Sales Order Management and FSM Consumable Processing.

Additional Information

• FSM Mobile Quote Management
• FSM Mobile Sales Order Management
• FSM Consumable Processing
• FSM Case Invoicing

Related Topics

• FSM Records
• FSM Consumable Record
• FSM Estimate Record
• FSM Invoice Record
• FSM Item Fulfillment Record

General Notices