1. Field Service Management
  2. FSM Configuration
  3. FSM Configuration Reference
  4. FSM Record Model Configuration
  5. FSM Transfer Order Model Reference

FSM Transfer Order Model Reference

Note:

This reference is intended for administrators and developers who work with Transfer Order model mappings and transaction behavior.

The Transfer Order model represents transferorder and inherits Transaction behavior. Its explicit defaults are empty. It supplies a transfer order ID formula that excludes linked transfer lines. It maps status to orderstatus and the requestor to employee. The mappings are from: "location" and to: "transferlocation". The Item array maps Item and absolute quantity to the Item sublist.

Standard default structure (JSON fragment):

          {
  "models/transferorder": {
    "prototype": {
      "record": "transferorder",
      "map": {
        "id": "*formulatext:case when {line} > 0 and {transferorderitemline} is null then {internalid} end|internalid",
        "type": "formulatext:nvl({recordtype}, lower({type}))",
        "createdfrom": "createdfrom",
        "createdfromtype": "createdfrom.recordtype|",
        "entity": "entity",
        "customer": "custbody_nx_customer",
        "asset": "custbody_nx_asset",
        "case": "custbody_nx_case",
        "task": "custbody_nx_task",
        "status": "status|orderstatus",
        "date": "trandate",
        "email": "email",
        "contact": "contactprimary.internalid|",
        "purchaseorder": "otherrefnum|",
        "paymentmethod": "paymentmethod",
        "firmed": "firmed",
        "employee": "requestor.internalid|employee",
        "from": "location",
        "to": "transferlocation",
        "items": [
          {
            "item": "item|item.item",
            "quantity": "formulanumeric:abs({quantity})|item.quantity"
          }
        ]
      },
      "defaults": {},
      "syncentity": false,
      "inventory": false
    }
  }
}

For the meaning of the inherited syncentity and inventory properties and guidance on changing these properties, see Transaction Mappings and Processing Properties.

The inherited Project and Project Task mappings vary with Project Management. For the inherited mapping values, see FSM Transaction Base Model Reference.

Transfer Order form components use this model. FSM Mobile order, return, and receive resources have separate article definitions and transaction processing. Preserve source and destination locations and the relevant transformation, fulfillment, or receipt path. A model map change doesn't define a complete new FSM Mobile transfer workflow.

Additional Information

Related Topics

General Notices