FSM Item Record
An item identifies a product, part, service, or charge used in Field Service Management (FSM). FSM uses standard NetSuite item records. Inventory items describe stock, service items identify labor, and other suitable item types represent equipment or charges.
An item and an asset represent different information. The item identifies the product, and an asset identifies a particular piece of equipment or service location. Several assets can reference the same item. A consumable record separately identifies the item and quantity used during a service visit.
Record Information
Use the item's internal ID for record relationships and mappings. Item names, display labels, and search type values serve different purposes.
|
Property |
Value |
|---|---|
|
Record type |
Standard NetSuite item records, including Inventory, Assembly, Non-inventory, Service, and other NetSuite item types |
|
Record name |
Item |
|
Item search ID |
|
|
Record API ID |
Depends on the item type. For example, |
|
Record identity |
Internal ID ( |
|
User-facing identity |
Item Name/Number ( |
item is the common search type used by FSM to retrieve different item types. It is a search-only type, not a general record type for creating or updating items. Use the specific item record type for record API operations. For more information, see Item Search and Inventory Item.
Forms
FSM adds its item fields to the Field Service subtab of applicable item forms. Native forms and account-created custom forms present the same underlying item data. Field availability depends on the item type and form. Changing a field's label or visibility doesn't change its ID or stored meaning.
NetSuite preferred-form settings determine the default entry form. If you check Store Form with Record on a custom entry form, records created with that form retain it. NetSuite uses the stored form when you view or edit those records. The option is cleared by default for custom entry forms. For more information, see Custom Entry Form Properties.
Standard item choices in FSM Mobile use searches rather than the item's stored NetSuite form. The standard Asset tab displays information from the item linked to the asset. Selecting a NetSuite form to generate fields for a configured FSM Mobile resource is a separate mechanism. For more information, see Form Properties.
Record Relationships
Most service relationships are stored on records that reference the item rather than on the item itself.
|
Related Record |
Relationship and Field ID |
Purpose |
|---|---|---|
|
Asset |
Asset Item ( |
Identifies the product represented by the equipment. The supplied Asset Item selector filters for Field Service Asset items. This field is also a native custom-record parent link, allowing related assets to appear beneath the item. |
|
Field Service Project Type |
Item Field Service Project Type ( |
Supplies the classification for a project requested when a new asset is created. It doesn't reference an individual project. |
|
Project created for an asset |
Project Field Service Asset ( |
Holds the resulting service or warranty relationship. The item supplies setup, and the project stores its own type, dates, and asset link. |
|
Consumable |
Consumable Item ( |
Records usage for a service visit. Quantity and stock selections belong to the usage record. |
|
Field Service Task Type |
Task Type Service Time Item ( |
Identifies the service used for automatic time entries for that task type. |
|
Time Bill |
Native Service Item ( |
Identifies the service represented by the recorded hours. |
|
Sales and stock transactions |
Native Item ( |
Identifies what is quoted, sold, fulfilled, transferred, or received. FSM line Asset ( |
|
Kit member items |
A kit's native member definitions identify component items and quantities. Item searches expose these through |
Supplies the component relationships used by the FSM Mobile Sales Order Kit choices. A member relationship doesn't establish available component stock. |
An asset's reference to an item doesn't place the item in the asset hierarchy. The asset's Parent (parent) field defines that hierarchy. See FSM Asset Record.
An account-created link to an item doesn't automatically add the linked record to FSM Mobile, inheritance, history, reports, or synchronization. Those capabilities require their own supported configuration and behavior.
FSM Fields
FSM supplies the following four custom item fields for eligibility and setup. These field values don't indicate whether processing is running or complete.
|
Field |
Field ID |
Meaning |
Supplied Initial Value |
|---|---|---|---|
|
Field Service Asset |
|
Identifies serviceable equipment eligible for asset processing from sales-order item fulfillments. It is a checkbox, not a link to an existing asset. |
Unchecked |
|
Field Service Show On Mobile |
|
Makes the item eligible for FSM Mobile searches that use this checkbox. Other search, stock, location, and feature conditions still determine availability. |
Unchecked |
|
Field Service Project Type |
|
Selects the Field Service Project Type that the standard project lookup uses when an asset is created. The field supports warranty setup and is not limited to a type named Warranty. |
No supplied selection |
|
Field Service Project Duration |
|
In the standard field definition, specifies the project duration as an integer number of months. |
No supplied value |
The supplied field definitions specify these initial values. A form, import, integration, or account customization can supply different values.
The two checkboxes are independent. An equipment item can qualify for asset processing without being offered in FSM Mobile. Making an item available in FSM Mobile doesn't request asset creation.
Item-Type Applicability
The following table shows which item types include each FSM field. Field availability doesn't establish support for every operation in FSM Mobile.
|
NetSuite Item Type |
Field Service Asset, Project Type, and Project Duration |
Field Service Show On Mobile |
|---|---|---|
|
Inventory, including serialized and lot-numbered variants |
Applies |
Applies |
|
Assembly, including serialized and lot-numbered variants |
Applies |
Applies |
|
Non-inventory |
Applies |
Applies |
|
Service |
Doesn't apply |
Applies |
|
Other Charge |
Doesn't apply |
Applies |
|
Item Group |
Doesn't apply |
Applies |
|
Kit/Package |
Doesn't apply |
Applies |
For types with purchase, sale, or resale variants, field applicability doesn't establish transaction support for every variant. Supported item types differ between Consumables, Sales Order, Quote, and stock-transfer workflows. See the applicable feature and configuration topics.
Consumables support inventory usage and, through additional option searches, noninventory, service, and other charge items for sale or resale. Kit/Package and purchase-only variants are unsupported on that tab. Item groups have partial support. A group entry doesn't specify separate bins, serial numbers, or lot numbers for every component. The Sales Order tab provides a separate kit path and has its own item-type and editing limits. The quote capability is intended for noninventory items. See Limitations and Constraints, Limitations and Constraints, and FSM Mobile Quote Management.
Native Item Data Used by FSM
FSM also reads the following native data. Search identifiers are identified where they differ from editable record fields.
|
Field or Data |
Field ID or Search Identifier |
FSM Use |
|---|---|---|
|
Item Name/Number and Display Name/Code |
|
Identifies and labels choices. Shared inventory choices use Display Name when present, otherwise the search Name. |
|
Item type |
Search |
Distinguishes inventory stock, assemblies, and services in searches. These values are not record API IDs. |
|
Inactive |
|
Excludes inactive items from standard item choices in FSM Mobile. |
|
Serialized or lot-numbered item |
|
Distinguishes numbered stock when the corresponding NetSuite features are enabled. Individual numbers and quantities are separate inventory data. |
|
Use Bins |
|
Used in inventory searches and assignments that depend on bins. Location bin settings also matter. |
|
Can Be Fulfilled/Received |
|
Supplies the item's fulfillment eligibility to transaction processing. It doesn't establish available stock or successful fulfillment. |
|
Base Price |
|
Supplies service-item pricing data used by time bill processing. Customer pricing, price levels, and account preferences can affect the resulting rate. |
|
Sales Description |
|
Supplies the description in the shared Quote and Order item list. |
|
Minimum Quantity |
|
Supplies the minimum quantity in the shared orderable list. The list uses |
|
Item description |
Joined item search |
Supplies the standard FSM Mobile Asset tab's read-only description through Asset Item. |
|
Item thumbnail and image |
|
Supply the standard FSM Mobile Asset image through Asset Item, with thumbnail preferred when present. |
|
UPC Code |
|
Supplies barcode text where inventory option data includes it. The standard mappings use UPC Code when that field has a value. If UPC Code is empty, the mappings use Item Name/Number. |
Inventory availability is associated with the relevant stock dimensions. Standard searches can read quantityavailable, locationquantityavailable, or quantities through inventory-number and bin joins. An overall item quantity is not proof of availability at a technician's location, bin, lot, or serial number. See Inventory Section in FSM Mobile.
Creation and Update Sources
Item maintenance and service transactions affect different records.
|
Source |
Effect |
|---|---|
|
NetSuite item entry |
Creates or edits the appropriate native item type and its applicable FSM fields. Form and native item requirements apply. |
|
Item setup for asset and project processing |
Saves eligibility and project setup on the item. Related processing creates or updates assets and can request a project. It doesn't turn the item into either record. |
|
FSM Mobile |
Reads item choices and item-derived information. Standard service tabs save usage, time, or transaction records rather than create or edit the item master. |
|
Inventory transactions |
Change stock associated with the item and its inventory dimensions. Item quantities update in FSM Mobile after changes are saved in NetSuite and FSM Mobile is refreshed. |
Used by FSM Features
The following topics describe selection rules, lifecycles, pricing, and processing outcomes.
|
Feature |
Item Use |
|---|---|
|
Reads Field Service Asset to identify equipment for asset creation or update. |
|
|
Reads Project Type and duration from the new asset's item. |
|
|
Uses the consumed item, quantity, and stock context for sales-order and fulfillment processing. |
|
|
Uses the item with related task and usage/time data to determine billability and applicable pricing. Billing Rule belongs to the task, not the item. |
|
|
Uses the task type's Service Time Item for automatic time bills. Manual time-entry choices use active service items with Field Service Show On Mobile checked. |
|
|
Uses shared item and inventory data for order lines and eligible fulfillment. |
|
|
Uses the shared orderable list for quotes. The supported quote scope is noninventory. A visible inventory choice doesn't extend that scope. |
|
|
Uses item data and stock context for requests, returns, and receiving. Order choices and available stock are separate facts. |
Record Constraints and Data Requirements
None of the four supplied FSM item custom fields is required in its field definition. A specific form or feature can require values for its own operation. Field applicability, item validity, visibility in FSM Mobile, and processing eligibility are separate checks.
Service-time setup uses service items for sale or resale with a base price. See Associating Field Service Task Types With Activity Types. That requirement doesn't make Service Item or Base Price required on every item type.
None of the four FSM item fields indicates processing completion. Checking Field Service Asset or Field Service Show On Mobile doesn't establish that processing produced an asset, project, usage transaction, or fulfillment. Saving the item or completing a script execution doesn't confirm these outcomes either.