Configuring FSM Consumable Processing

Configure how FSM Mobile records item usage and how background processing adds that usage to sales orders and fulfills eligible items. This topic brings together the Consumables tab setup and processing controls. For the processing lifecycle and transaction effects, see FSM Consumable Processing.

This topic includes the following sections:

• Before You Begin

• Processing Controls and Defaults

• Configure Mobile Recording and Inventory Selection

• Configure Billable Selection and Pricing

• Customization Boundaries

• When Processing Settings Apply

• Disabling Processing

Before You Begin

Prepare the records and access required for your scenario:

• Use standard NetSuite CRM tasks linked to cases. Consumables do not support project tasks. For that scenario, see FSM Mobile Sales Order Management.

• Give the person changing the configuration access to Field Service > Administration > Configuration and the relevant employee, item, location, and transaction records. User access and subsidiary restrictions apply. See Managing FSM Employee Records.

• On the Field Service subtab of the technician's employee record, check the Field Service Mobile User box. For stock usage, set Field Service Employee Location (custentity_nx_location) on the Field Service subtab to the inventory location the technician uses. Ensure the intended stock is available there.

• On items intended for selection in FSM Mobile, check the Field Service Show On Mobile box (custitem_nx_show_on_mobile). By default, the box is not checked. See Setting Up Items for Field Service Management.

• For automatic fulfillment, enable the Locations feature on the Enable Features page. Supply the location and any bin, lot, or serial information required by the item. With Inventory Status enabled, use manual fulfillment for consumables by setting consumable.fulfill to false. The Consumables path does not supply Inventory Status assignments.

The product-supplied Field Service Scheduled : Consumable deployment (customdeploy_nx_consumable) performs background processing. Retain the supplied consumable record validation and task completion processing. Deployment settings and monitoring belong in FSM Script Reference. Changing these processing switches does not require creating a new deployment.

Important:

Billing processing selects cases with unlinked consumables on CRM tasks that have a status of Completed. It then collects all unlinked consumables for each selected case, including entries from unfinished tasks. Consider this behavior when a case contains several tasks.

Processing Controls and Defaults

Edit the root consumable object in the Field Service Configuration record. Both properties accept JSON Boolean values, true or false. The supplied schema defaults are true. If you omit a custom property, FSM retains its inherited value.

Setting	Default	Effect
consumable.bill	true	Selects eligible cases for adding unlinked consumables to an existing or new sales order.
consumable.fulfill	true	Selects eligible consumable sales order lines for automatic fulfillment when Locations is enabled.

Choose the combination that matches the intended outcome.

bill	fulfill	Outcome
true	true	Add consumables to sales orders and automatically fulfill eligible lines.
true	false	Add consumables to sales orders and fulfill those lines manually. Use this combination for Inventory Status.
false	true	Stop selecting new consumables for sales order addition. Existing eligible consumable lines can still be fulfilled.
false	false	Stop selecting new billing and fulfillment work. Recording in FSM Mobile and completion of missing transaction links remain available.

The switches do not change a consumable's Billable field. A nonbillable consumable still becomes a sales order line, with a zero rate, when billing processing is enabled. It can still be fulfilled when its item qualifies. Neither switch prevents the processor from completing missing case or consumable sales order links.

Configure Sales Order Processing with Manual Fulfillment

Configure Sales Order Processing with Manual Fulfillment

1. Use an inactive copy of the current configuration and retain the previous version.

2. Set consumable.bill to true and consumable.fulfill to false in the revised configuration, as shown in the following example.

                       {
     "consumable": {
       "bill": true,
       "fulfill": false
     }
   } 
   
                     

3. Follow Updating and Validating FSM Configuration for validation and activation.

This fragment permits sales order addition and leaves fulfillment to the manual process. To retain automatic fulfillment, use "fulfill": true after confirming its prerequisites. To stop new billing selection, use "bill": false and choose the fulfillment value separately.

Standard default JSON for these properties:

              {
  "consumable": {
    "bill": true,
    "fulfill": true
  }
} 

            

Configure Mobile Recording and Inventory Selection

Under "routes/mobile", the consumables resource defines the tab and inventory supplies shared item options. For placement and loading rules, see Where Mobile Resources Are Configured.

Configuration Location	Supplied Behavior
routes/mobile.event.article.task.resources	Selects tabs for CRM task events. Standard configuration supplies an empty rule array. The account's matching rule must include consumables.
routes/mobile.user.employee.resources	Loads supporting user data. Standard configuration includes inventory. Preserve it for tabs that require inventory data.
routes/mobile.inventory.element.consumable.options	Supplies shared consumable.options, using searches selected for the enabled inventory features and technician location.
routes/mobile.consumables.element.inventory	Uses consumable.options for the technician's item selection.
routes/mobile.consumables.element.quantity	Required Integer input, with min: 1 and step: 1.
routes/mobile.consumables.article	Saves to customrecord_nx_consumable. Supplies Task and employee defaults and the selected child asset or task asset.

To make the supplied tab available:

1. Make consumables available for the intended CRM tasks and retain inventory in the matching employee rule. Follow Selecting Resources for both resource lists.

2. Retain the supplied Task and employee article filters and defaults. The supplied settings select the current task's entries for the current employee. Retain the asset default and filter when recording usage against child assets.

3. Retain the selected option's item, location, bin, and serial or lot mappings. The tab displays item and inventory details as read-only and stores the inventory number ID separately from its label.

4. Retain the article's read-only mapping for existing entries whose CRM task is Completed.

Standard stock searches require active items marked for FSM Mobile, available quantity, and the applicable location and inventory conditions. Item groups are also loaded when marked for FSM Mobile, without checking every component's stock at the technician location. Their presence in the list does not establish that the group can be fully fulfilled.

Inventory options are cached until FSM Mobile refreshes. Refresh after saving stock or item changes in NetSuite. Use the account's current Preview when changing searches: enabled inventory features determine which searches and mappings apply. Changes to consumable.options can also affect the Sales Order and Return tabs.

Inventory Search Overrides and Processing Risks

Changing the default inventory searches, including removing available-quantity conditions, can expose stock choices that the supplied searches would omit. Changes to quantity, location, bin, serial, or lot mappings can affect subsequent sales order and fulfillment processing. Inconsistent values entered directly on consumable records can also affect that processing. An override can work correctly. Its presence alone does not establish a failure. Consider these changes alongside the intended billing and fulfillment design, item requirements, and NetSuite account rules. Inventory selection does not reserve stock or guarantee that it remains available when processing runs.

With automatic fulfillment enabled, invalid or unavailable stock assignments can cause fulfillment failures. An active, unrecovered error for this deployment can exclude a case from later assessment. The error can be on the case, a related sales order, or a related consumable. Other consumables on that Case can remain awaiting linking, billing, or fulfillment while unrelated work continues. Earlier transaction changes can remain saved. These record exclusions do not expire with time, and the supplied consumable actions have no automatic retry rule.

Setting consumable.fulfill to false is the supported choice when fulfillment is to be performed manually. Billing and completion of missing transaction links remain governed by their separate rules, and consumable and NetSuite validation still apply. The setting does not repair existing transactions or partial results, remove stored error exclusions, or establish that a search override is safe. See FSM Consumable Processing for processing outcomes and Field Service Scheduled in FSM Script Reference for exclusion and recovery behavior.

Add Selected Service Items

Additional searches can supply supported noninventory, service, and other charge items for sale or resale. Purchase-only subtypes and Kit/Package items are not supported on the Consumables tab. See Supported Item Types on the Consumables Tab.

This fragment adds a search to the existing shared options object.

Add Selected Service Items

1. Replace 12345 and 12346 with verified internal IDs of active service items for sale or resale that do not require inventory fulfillment.

2. Check the Field Service Show On Mobile box on those items.

3. Merge this addition without replacing existing stock searches.

                       {
     "routes/mobile": {
       "inventory": {
         "element": {
           "consumable": {
             "options": {
               "services": {
                 "all": true,
                 "record": "item",
                 "filters": [
                   ["isinactive", "is", "F"],
                   "and",
                   ["type", "anyof", "Service"],
                   "and",
                   ["custitem_nx_show_on_mobile", "is", "T"],
                   "and",
                   ["internalid", "anyof", [12345, 12346]]
                 ],
                 "map": {
                   "id": "formulatext:'item-'||{internalid}||'---'",
                   "label": "itemid",
                   "item": {
                     "id": "internalid",
                     "label": "itemid"
                   }
                 }
               }
             }
           }
         }
       }
     }
   } 
   
                     

It uses the standard option-ID pattern for an item without a location, bin, or inventory number. It also retains the tab's nested item reference. Other tabs using the same shared options are also affected. For search and mapping syntax, see FSM Searches and Field Mapping.

Configure Billable Selection and Pricing

Billing rules and transaction-processing switches serve different purposes. billing.consumable evaluates billability when the consumable has an item and task and the task has a Billing Rule (custevent_nx_billing_type). The supplied rule makes billing types 5, 6, 7, and 8 nonbillable. In the standard configuration, billing.task is []. Automatic Task Billing Rule selection requires account rules.

With Multiple Prices enabled, validation can also set Price Level. A numeric billing result can supply a price level. Otherwise, validation uses customer or default pricing. Validation can replace entered Billable and Price Level values. The standard FSM Mobile tab has no direct rate-entry field.

Use Configuring FSM Billing Rules for task rule selection and price-level rules. A task-wide rule also affects related time and expenses. Do not use it as an individual consumable exception without checking those effects.

Let Technicians Choose Billable

The following fragment replaces the existing billing.consumable rule for all consumables. Use it only when that is the intended billing policy.

Let Technicians Choose Billable

1. To make the entered Billable value authoritative for consumables, add the Billable box and its article mapping and change the consumable billing rule together. Preserve other billing properties.

                       {
     "billing": {
       "consumable": "${ consumable.billable }"
     },
     "routes/mobile": {
       "consumables": {
         "element": {
           "billable": {
             "type": "checkbox",
             "label": "Billable",
             "value": true
           }
         },
         "article": {
           "map": {
             "billable": "custrecord_nx_consbillable[boolean]"
           }
         }
       }
     }
   } 
   
                     

The Billable box is checked by default for new entries. The single template tag returns the consumable's Boolean value during server validation. It supplies no numeric price-level result, so the pricing fallback still applies when Multiple Prices is enabled. Without changing an existing billing rule that reapplies billability, the Billable box alone may not retain the technician's choice.

For template-tag behavior, see FSM Expressions and Template Tags.

Customization Boundaries

Modify the existing consumables resource for the supported setup described here. Preserve its record, filters, defaults, and inventory mappings. See FSM Mobile Resource Properties Reference and FSM Mobile Element (Block) Reference for shared definitions.

Follow these customization boundaries:

• You can add custom fields to the consumable record and map those fields into FSM Mobile. Retain the bundled record and fields. Additional fields do not automatically become sales order line fields through configuration.

• The FSM Mobile article saves a consumable custom record. Record validation and background processing provide the subsequent sales order and fulfillment behavior. Matching a copied resource's label or record type does not establish that all required relationships and processing remain intact.

• A case's linked sales order can receive appended consumable lines. Changing a consumable already linked through Billing Transaction does not update its existing sales order line.

• If the case references a transaction other than a sales order, processing attempts a NetSuite transformation. Use a transaction that supports transformation to a sales order. An arbitrary transaction reference is insufficient.

• Keep stock and inventory assignments valid. An item requiring bin, lot, or serial details may be omitted from fulfillment when those assignments are missing. A successful execution does not establish that all requested lines were fulfilled.

When Processing Settings Apply

Processing settings apply to subsequent assessments. These settings do not change sales orders or item fulfillments already produced. Resource and shared-option changes require the affected FSM Mobile configuration and data to be reloaded. See FSM Mobile Resource Selection and Shared Data.

Consumable processing depends on the saved task state in NetSuite. A locally completed FSM Mobile task can still have outstanding synchronization or service-time processing. Unrecovered errors can exclude the affected case from processing. See FSM Consumable Processing, FSM Script Reference, and the Field Service Error Record topic.

For performance measurement and data capture, see FSM Performance and Data Collection.

Consumable references on sales order lines use custcol_nx_consumable. The Case Transaction and Consumable Billing Transaction links identify transaction associations. Neither link establishes fulfillment.

Disabling Processing

Set both consumable.bill and consumable.fulfill to false to stop selecting new billing and fulfillment work. Existing transaction-link completion remains enabled. These switches do not hide the FSM Mobile tab. Its resource-selection rule controls availability.

Removing a custom switch value restores the inherited default and can re-enable processing of outstanding eligible records. It does not cancel an action already assessed or executing, or reverse sales order lines, transaction links, item fulfillments, or inventory movements.

FSM Configuration Reference

FSM Configuration

General Notices