FSM Location Record

A location identifies where inventory is held in NetSuite. Field Service Management (FSM) uses the standard location record for warehouses, technician vans, and other stock locations. Employee records reference these locations, and records of stock usage and transfers retain the location involved.

Warehouse and van locations are uses of the standard location record. A warehouse holds replenishment stock, and a van location identifies stock carried by a technician. An FSM asset separately represents a service site or machine, with a service address that identifies where work takes place. For more information, see FSM Asset Record.

Record Information

Use the record and field IDs when working with searches, mappings, and integrations. Account labels can differ from the supplied English labels.

Property

Value

Record type

Standard NetSuite

Record name

Location

Record ID

location for SuiteScript, searches, and REST

Record identity

NetSuite Internal ID (internalid)

Display name

Name (name)

For more information about native field identifiers, refer to the Location Records Browser. The Location REST reference uses API names such as mainAddress. These API names can differ from SuiteScript and search field names.

Forms

Maintain locations through the native NetSuite Location page. FSM stores stock location references in fields on employee records rather than in a separate FSM Location form.

The built-in FSM Mobile stock tabs use location choices and inventory data. Selecting a location on the Order or Return tab associates the location with the transaction. The selection doesn't open the location's NetSuite form or change its address or inventory settings. For information about configuring the Order and Return tabs in FSM Mobile, see Configuring FSM Mobile Order and Configuring FSM Mobile Return.

Record Relationships

The following table identifies which record stores each location reference and how FSM uses the relationship. Multiple employee records, consumable records, or transactions can reference the same location.

Related Record

Relationship and Field ID

Purpose

Parent location

The child location stores Sublocation of (parent), a single parent location reference.

Forms the native location hierarchy.

Subsidiary

Location stores Subsidiary (subsidiary).

Identifies its NetSuite company context.

Employee: stock location

Employee stores Field Service Employee Location (custentity_nx_location), a single location selection.

Identifies the van or other location supplying the technician's stock.

Employee: warehouse

Employee stores Field Service Employee Warehouse (custentity_nx_warehouse), a separate single location selection.

Can supply the initial source location for Order or destination location for Return, subject to the allowed location choices.

Consumable

Field Service Consumable stores Location (custrecord_nx_conslocation).

Identifies the location associated with the recorded item usage.

Transfer order

Transfer order stores source Location (location) and destination To Location (transferlocation).

Identifies both ends of a stock transfer.

Sales order

Sales order item lines hold Location (location), or Inventory Location (inventorylocation) in the applicable cross-subsidiary fulfillment path.

Identifies the line's stock location separately from its asset or task link.

Item fulfillment

Fulfillment item lines store Location (location).

Identifies the location issuing stock.

Item receipt

Item receipt stores To Location (location) on the receipt and its item lines.

Identifies the location receiving stock. See the Item Receipt Records Browser.

The Field Service Employee Warehouse value supplies the initial source location for Order or destination location for Return only when that location is allowed. It doesn't restrict all transfers to that warehouse. See FSM Mobile Stock Transfers for transfer direction and selection behavior.

The native location hierarchy is separate from the asset hierarchy. FSM Asset Hierarchy and Inheritance applies to Field Service Assets. A custom link between a location and an asset doesn't automatically add inheritance, FSM Mobile resources, history, reports, or synchronization.

FSM Fields

The following table describes native location fields relevant to FSM. The record relationships table describes the Field Service fields stored on employee records.

Field

Field ID

Purpose

Important Values or Behavior

Name

name

Display identity.

Required. Maximum 60 characters.

Sublocation of

parent

Immediate parent.

Native hierarchy.

Subsidiary

subsidiary

Company context.

Inventory locations in OneWorld belong to one subsidiary.

Location is Inactive

isinactive

Availability in location selection lists.

Inactive locations don't appear in location lists on records and transactions.

Location Type

locationtype

Native classification.

Store, Warehouse, or Undefined. No native Van type.

Make Inventory Available

makeinventoryavailable

Availability for orders.

Controls whether on-hand inventory at the location is available to orders. It doesn't specify the stock quantity.

Use Bins

usebins on the record and usesbins in searches

Bin-management setting.

Bin requirements also depend on the item and enabled inventory features.

Address

addrtext in the native record reference

Location address text.

REST exposes mainAddress and returnAddress separately.

Time Zone

timezone

Native location time zone.

Separate from FSM service Time Zone fields.

Native classifications and address data are described in Creating Locations. Location Type doesn't determine an employee's stock or warehouse location. The Field Service Employee Location and Field Service Employee Warehouse fields identify those locations.

For field inventory, use separate warehouse and technician van locations.

Important: For technician van locations, check the Make Inventory Available box and clear the Use Bins box, even when warehouse locations use bins. Bins add inventory-detail and putaway work that is usually unsuitable for a technician van. See Managing Warehouse and Van Locations for Field Service Management for the FSM setup guidance.

Different bin settings by location require the Advanced Bin / Numbered Inventory Management feature with the Multi-Location Inventory feature. Basic Bin Management doesn't support enabling bins for some locations and disabling them for others. See Bin Management by Location for the native feature distinction.

A location's main or return address is separate from the asset address or task Field Service Address. FSM Service Locations and Geocoding explains service-address sourcing. Selecting a stock location doesn't make its address the service site.

Used by FSM Features

The following table shows how FSM features use location records. For selection, processing, and transaction results, see the linked feature topics.

Feature

How the Record Is Used

FSM Mobile Stock Transfers

Identifies the source and destination of requests, returns, and incoming stock.

FSM Consumable Processing

Retains the location of recorded usage for sales order and fulfillment processing.

FSM Mobile Sales Order Management

Uses stock choices and line locations for eligible fulfillment.

Record Constraints and Data Requirements

Native location validation and account permissions apply. Name and Time Zone are required fields in the native record reference. Feature prerequisites and FSM Mobile input requirements apply to specific workflows, rather than every location record.

The supplied Field Service Employee Location and Field Service Employee Warehouse fields are optional in their field definitions and have no supplied selection default. Their selectors require Make Inventory Available. For FSM inventory use, the selected location's subsidiary must match the employee's subsidiary. See Managing FSM Employee Records and the relevant stock feature for operational requirements.

Assigning a location to an employee doesn't add stock to that location. NetSuite inventory transactions determine inventory balances and movements. Stock at a parent location, warehouse, or another van doesn't establish availability at the selected location. Inventory data loaded in FSM Mobile also doesn't reserve stock. See Inventory Section in FSM Mobile for shared choices and refresh behavior.

Additional Information

Related Topics

General Notices