FSM Asset Processing from Item Fulfillments

Field Service Management (FSM) can create or update assets from item fulfillments for sales orders. The Create/Update Assets sublist shows the asset rows to process. When you save the fulfillment, FSM requests background processing for those rows.

How It Works

This section explains the records and rules involved in the feature.

Asset Creation and Updates

FSM includes an item in asset processing only if the Field Service Asset (custitem_nx_asset) box is checked on the item record. FSM prepares one asset row per unit selected for fulfillment.

FSM uses the configured asset matching rules to check each row against existing assets. Matching rows identify existing assets to update, and unmatched rows identify assets to create.

When you select or clear an item line for fulfillment, FSM refreshes the Create/Update Assets sublist. FSM checks for matching assets for the current selection. Asset rows are added or removed after these checks complete. Changing fulfillment quantities, using Mark All or Unmark All, and changing inventory detail also refreshes the sublist. A refresh can replace manual changes to asset rows.

On an editable sales-order fulfillment, FSM also prepares the sublist before the page is displayed. When the NetSuite Default Items to Zero Received/Fulfilled preference is not set, items start at their default fulfillment quantities. FSM prepares asset rows and checks for matching assets for the selected eligible items during page loading. A large number of eligible items or units can therefore delay the initial page display.

When the preference is set, quantities start at zero, and asset rows are prepared when items are selected for fulfillment. For the preference's behavior, see Order Management Accounting Preferences. For the observed timeout limitation, see Fulfillment Volume and Timeouts.

The sublist is available on an editable form with the configured transaction tab. Saving a fulfillment with no asset rows doesn't request asset creation or updates.

Key Behaviors

This section describes how the feature responds to different conditions and actions.

Asset Row Columns and Validation

The default sublist contains the following visible columns:

Item - Identifies the item from the fulfillment line. The column is required and can't be edited.
Serial Number - Identifies the asset's serial number. The column is required and can be edited.
Asset - Identifies a matching existing asset. FSM fills this column, which can't be edited.
Address - Displays the address text prepared from the fulfillment's shipping address. The column can't be edited.

For serialized items, FSM fills the Serial Number column from fulfillment inventory detail when Advanced Bin/Numbered Inventory Management is enabled. For nonserialized items, FSM doesn't automatically fill the Serial Number column.

FSM prevents you from saving the fulfillment if an asset row is missing a required value. When you edit an asset row, FSM also checks for a matching row elsewhere in the sublist. If an asset row matches another row in the list, FSM displays an error and prevents you from saving the row. If the row matches an existing asset record, FSM links the row to that asset.

Record Interactions

This section describes the records and field values used in asset processing.

Records Used in Asset Processing

The following table shows how FSM uses records in this feature.

Record	Use in Asset Processing
Item	Identifies items for asset processing when the Field Service Asset (`custitem_nx_asset`) box is checked.
Item fulfillment	Supplies item quantities, asset-row values, and the transaction reference stored on the asset.
Field service asset	Stores values from an asset row during creation or an update.

Record

Use in Asset Processing

Item

Identifies items for asset processing when the Field Service Asset (custitem_nx_asset) box is checked.

Item fulfillment

Supplies item quantities, asset-row values, and the transaction reference stored on the asset.

Field service asset

Stores values from an asset row during creation or an update.

By default, FSM populates each asset row's customer value from the fulfillment's Field Service Customer field. FSM sources the address selection and address text from the shipping address. If the fulfillment uses a custom address or an address text override, FSM clears the address selection in the asset row.

FSM uses the fulfillment's Field Service Asset field to populate the parent asset in each row. By default, assets with a parent inherit Customer, Address Select, Address, and Region from that parent. These inherited values take precedence over the corresponding values supplied in the asset row. For details, see FSM Asset Hierarchy and Inheritance.

Processing Model and Lifecycle

This section explains when processing occurs and what can affect its progress and results.

Background Asset Processing

Field Service User Event (customscript_nx_userevent) requests asset processing when an item fulfillment that contains asset rows is created or edited. Field Service Scheduled (customscript_nx_scheduled) creates or updates the assets in the background. The item fulfillment deployment for the user event script is customdeploy_nx_itemfulfill_userevent.

This processing uses the asset rows submitted with the fulfillment. It is separate from the background inheritance processing for existing child assets described in FSM Asset Hierarchy and Inheritance.

Saving the fulfillment doesn't confirm that all asset records have been created or updated. An error during asset processing can stop the scheduled run before all rows are processed.

The following messages on the fulfillment page include New Assets in the message text:

Pending Processes - Appears when the related script run is pending or processing. The message alone doesn't show whether processing has started.
Failed Processes - Appears when the related script run has failed.

To confirm the outcome, check that the expected asset records were created or updated with the correct field values.

For associated script and deployment details and execution monitoring, see FSM Script Reference.

Configuration

The asset-matching configuration determines whether a row identifies an existing asset. The default matching template uses the item and serial number, or the item and address text if the serial number is empty. This fallback doesn't make the Serial Number column optional on the standard fulfillment sublist.

Account configuration can change the matching rules and the Create/Update Assets sublist requirements. Matching rules affect whether a row creates or updates an asset. Sublist requirements affect whether the row or fulfillment can be saved.

Important:

Changing matching rules can change which existing assets are updated. Keep the matching definitions consistent and preserve the asset identity fields and validation dependencies when customizing the sublist.

For feature setup, see Configuring FSM Asset Processing from Item Fulfillments. For matching definitions, see FSM Record Model Configuration. For Create/Update Assets form controls and requirements, see FSM NetSuite View Configuration.

Limitations and Constraints

This section describes fulfillment volume and timeout observations.

Fulfillment Volume and Timeouts

Loading an item fulfillment can time out when FSM prepares and matches a large number of asset rows. Timeouts have been observed particularly when Default Items to Zero Received/Fulfilled is not set and many eligible items are selected when the page first loads.

Timeouts have been observed on fulfillments that would create around 380 assets. This figure refers to the number of assets generated from the fulfilled quantities, not the number of item lines. It is an indicative observation: the actual timeout point varies and is not a fixed product limit.