FSM Transfer Order Record

A transfer order records a planned movement of inventory between two NetSuite locations. In NetSuite Field Service Management (FSM), a transfer order can request stock for a technician's van. It can also record stock being returned from the technician's location to another location.

FSM uses the standard NetSuite transfer order transaction. Its header identifies the source, destination, and service-work context. Its item lines identify the requested items and quantities. Related item fulfillments record shipment, and item receipts record receipt. A saved transfer order alone doesn't establish either result.

Record Information

Use these identifiers when working with searches, field mappings, and integrations. Account labels can differ from the labels shown here.

Property	Value
Record type	Standard NetSuite transaction
Record name	Transfer Order
Record ID	transferorder
Record identity	Internal ID (internalid) identifies the record. Order # / Transaction Number (tranid) identifies the order in the interface.
FSM record model	models/transferorder
Standard FSM Mobile resources	order and return use transfer orders. receive uses item receipts.

The TrnfrOrd prefix in transaction-search status values identifies transfer orders. It is not the record ID used for record creation. For the native record, see Transfer Order.

Forms

You can use standard transfer order forms or forms customized for your NetSuite account. Form choice controls presentation and can impose form-specific requirements. It doesn't change the underlying field IDs.

Custom transfer order forms support Store Form with Record. When Store Form with Record is checked, transactions created with the custom form retain its form reference. NetSuite displays the stored form when you view or edit a transaction, even if that form isn't enabled for your role. For more information about stored forms and role-related implications, see Storing Custom Forms with Transactions.

The standard FSM Mobile Order and Return tabs define their elements directly instead of generating the elements from a configured NetSuite form. FSM Mobile configuration therefore determines the initial values and required inputs. Selecting a NetSuite UI form is separate from defining FSM Mobile fields. For information about supported loading and override rules for resources that use form-generated elements, see Form Properties.

Record Relationships

The transfer order holds the location and service-work references in the following table. Shipment and receipt links are held on the related transactions.

Related record	Relationship and field ID	Purpose
Source Location	Transfer order From Location (location) references one location.	Identifies the location supplying the stock.
Destination Location	Transfer order To Location (transferlocation) references one location.	Identifies the location receiving the stock.
Employee	Transfer order Employee (employee). Read through requestor.internalid in FSM searches.	Identifies the employee associated with the request. This is separate from the technician assigned to the service task.
Customer	Transfer order Field Service Customer (custbody_nx_customer) references one customer.	Associates the movement with its service customer. It is not a stock destination.
Case	Transfer order Field Service Case (custbody_nx_case) references one case (supportcase).	Associates the order with the service request.
CRM Task	Transfer order Field Service Task (custbody_nx_task) references one CRM task (task).	Associates the movement with a service visit.
Project Task	Transfer order Field Service Project Task (custbody_nx_projecttask) references one project task (projecttask).	Provides the separate project task relationship.
Asset	Transfer order Field Service Asset (custbody_nx_asset) references one FSM asset (customrecord_nx_asset).	Stores equipment or service-site context, separate from the transferred item.
Item	Each row of the native item sublist references an item through item.item.	Identifies the stock requested on that line.
Item Fulfillment	Item fulfillment Created From (createdfrom) references the transfer order.	Records stock shipped against the order. An order can have more than one fulfillment.
Item Receipt	Item receipt Created From (createdfrom) references the transfer order. Where a receipt is matched to a fulfillment, FSM searches use the receipt's appliedtotransaction relationship.	Records stock received and identifies the related shipment where applicable. An order can have more than one receipt.

The service-work links are supplied FSM body fields. The locations, item sublist, and transaction links are native NetSuite relationships. The employee's Field Service Location (custentity_nx_location) supplies FSM Mobile location context. Field Service Warehouse (custentity_nx_warehouse) can supply the other location's initial choice. These fields are stored on the employee, not the transfer order.

Adding a different custom relationship doesn't automatically include the linked record in FSM Mobile selection, history, reports, inheritance, or synchronization. See the relevant Configuration topic for supported additions.

FSM Fields

The following tables list selected native transaction fields used by FSM and the supplied FSM body fields.

Header and Item Data

The record stores requested movement data separately from the shipment and receipt results.

Field	Field ID	Purpose	Important values or behavior
Order # / Transaction Number	tranid	User-facing transaction identity.	Separate from internalid. Standard stock tabs display the saved number without writing it.
From Location	location	Source of the stock movement.	Standard FSM Mobile Return defaults this field to the employee's location. These are FSM Mobile defaults, not universal record defaults.
To Location	transferlocation	Destination of the stock movement.	Standard FSM Mobile Order defaults this field to the employee's location. These are FSM Mobile defaults, not universal record defaults.
Employee	employee (search join requestor.internalid)	Employee associated with the order.	Standard FSM Mobile Order and Return supply the current employee when creating an order.
Subsidiary	subsidiary	Subsidiary context in OneWorld.	Standard FSM Mobile creation supplies the user's subsidiary context.
Date	trandate	Transaction date.	Standard FSM Mobile Order and Return supply the event date. Native form initialization can supply a different initial date.
Item	item.item	Item reference on the native item sublist.	The FSM Mobile choice list doesn't establish that an item is valid for a transfer order.
Quantity	item.quantity (search column quantity)	Quantity requested on an item line.	FSM reads the absolute search quantity. Requested quantity is separate from shipped or received quantity.
Item line identity	item.line (search column line)	Identifies an existing item line.	Standard FSM Mobile Order and Return retain line identity when loading and saving item rows.
Quantity Shipped (search value)	transferorderquantityshipped	Shipped quantity on a transfer order line.	Used by one incoming-stock search branch. It doesn't mean that the destination has received the stock.

Service-Work and Synchronization Data

The service relationships in the following table are stored on the transfer order header. The supplied field definitions don't require these references on every transfer order.

Field	Field ID	Purpose	Important values or behavior
Field Service Customer	custbody_nx_customer	Customer associated with the service work.	Standard FSM Mobile Order and Return creation supply available event customer context.
Field Service Case	custbody_nx_case	Related case.	Standard FSM Mobile creation supplies available event case context. The field definition also specifies sourcing from the selected CRM task's case.
Field Service Task	custbody_nx_task	Related CRM task.	Distinct from the project task reference.
Field Service Project Task	custbody_nx_projecttask	Related project task.	Distinct from the CRM task reference.
Field Service Asset	custbody_nx_asset	Related equipment or service-site asset.	No explicit asset default is supplied in the standard FSM Mobile Order or Return creation defaults.
External ID (native)	externalid	Technical identity used by standard FSM Mobile creation synchronization.	FSM stores creation identity with the fsm_ prefix. It is separate from the order number and shipment status.
Field Service Idempotency Key	custbody_nx_idempotency_key	Custom field for creation identity retained for compatibility.	Current standard FSM Mobile record creation uses External ID. This field is not a fulfillment, receipt, or recurrence-completion indicator.

For creation identity and retry behavior, see FSM Mobile Duplicate Creation Protection.

Status and Transfer Controls

These native values describe the order and its transfer settings. An FSM script's execution state is separate.

Field or indicator	Field ID	Meaning and important values
Status	Record field orderstatus (search field status)	Native transaction state. Standard FSM Mobile Return creation supplies Pending Fulfillment (B). Standard FSM Mobile Order creation doesn't specify an order-status default.
Pending receipt states (search values)	TrnfrOrd:F, TrnfrOrd:E	Pending Receipt and Pending Receipt/Partially Fulfilled. The standard incoming-stock searches use these states together with location, shipment, and transfer-cost conditions.
Firmed	firmed	When Firmed is checked, line items remain committed to the order and cannot be reallocated. Firmed transfer orders cannot be rescheduled or canceled. It is separate from fulfillment or receipt completion. See Entering a Transfer Order for its native effect.
Use Item Cost as Transfer Cost	istransferpricecosting	Native transfer-cost choice. FSM uses it to distinguish incoming choices based on transfer order lines from choices based on individual item fulfillments.
Initial Open label in FSM Mobile	No saved status field represented by this initial label	Display text for a local Order or Return entry before it is saved in NetSuite. The Open label doesn't indicate a saved transaction or its status.

A saved order or a pending-receipt state doesn't establish that all requested items have arrived. The related fulfillment and receipt transactions provide the shipment and receipt data. For selection and processing consequences, see FSM Mobile Stock Transfers.

Creation and Update Sources

The creation source determines which initial values are supplied. Related transactions remain separate records.

Source	Effect on the record
NetSuite entry or supported import/integration	Creates or updates the native transfer order, subject to NetSuite validation, permissions, and form requirements.
FSM Mobile Order	Creates or edits a stock request destined for the employee's location, with available employee, service-work, and date context.
FSM Mobile Return	Creates or edits an outgoing order from the employee's location. Automatic fulfillment can create or replace related item fulfillments.
Native fulfillment and receipt processing	Creates related shipment and receipt transactions and changes the order's native quantities/status as appropriate.
FSM Mobile Receive	Creates an item receipt from the selected transfer order, using its related fulfillment where applicable.

Order, Return, and Receive have distinct selection and synchronization rules. For details about selection, synchronization, fulfillment replacement in Return, and receipt processing in Receive, see FSM Mobile Stock Transfers.

Used by FSM Features

The following Features explain how the stored data is used.

Feature	How the record is used
FSM Mobile Stock Transfers	Stores requested and returned movements and supplies the source transaction for incoming receipts.
FSM Mobile Duplicate Creation Protection	Uses technical creation identity during standard FSM Mobile record synchronization.

Record Constraints and Data Requirements

Transfer orders require the Multi-Location Inventory feature. Native transfer orders require a destination location. A source location is required before approval and fulfillment, even where native entry permits it to be omitted initially. Native transfer order items are Inventory or Assembly items. See Entering a Transfer Order for standard entry, units, and inventory requirements.

The standard FSM Mobile Order and Return tabs additionally require the selected other location, an item table, an Item, and a positive whole-number Quantity. Return initializes Quantity to 1. These are FSM Mobile element rules. They don't establish a universal NetSuite restriction to whole-number quantities.

The supplied FSM service-work body fields are optional in their field definitions. Task, employee, and location conditions used to load orders in FSM Mobile are feature-specific selection rules. A native transfer order can exist without satisfying those conditions.

Additional Information

• FSM Mobile Stock Transfers
• Transfer Order Tab in FSM Mobile
• Receive Tab in FSM Mobile

Related Topics

• FSM Records
• FSM Item Fulfillment Record
• FSM Item Receipt Record
• FSM Item Record
• FSM Location Record

General Notices