Manage transfer order
Summarize
Summary of Manage transfer order
The Asset Management application in ServiceNow enables asset managers to efficiently manage the transfer of assets between company stockrooms using transfer orders. This process supports both consumable and non-consumable assets, with consumables tracked by quantity and non-consumables handled as single entities.
Show less
Transfer orders and their detailed components—transfer order lines—facilitate tracking, processing, and movement of multiple assets within one order. The application includes workflows and tasks to manage and monitor these transfers accurately.
Key Features
- Transfer Order Lines: Allow multiple assets to be transferred in one order, with shipment preparation and other actions managed at the line level. Pre-allocated assets can be included but must be transferred in full quantity. Business rules prevent duplicate transfers of the same asset simultaneously.
- Workflows: Transfer order line processing is managed by workflows that depend on installed plugins like Service Management Core or Field Service Management. These workflows automate the stages of asset transfer.
- Transfer Order Line Tasks: Automatically created based on asset model categories, these tasks guide the transfer order line through various stages (e.g., fulfillment, shipment). Closing tasks progresses the transfer and updates asset statuses (e.g., from available to reserved).
- Template Tasks and Customization: Default template tasks are available by model category and cannot be altered, but organizations can create customized template tasks and subtasks for greater flexibility and alignment with their processes.
- Subtasks: Enable detailed tracking within each transfer order line task. Subtasks must be completed to close the parent task, supporting granular control (e.g., imaging a computer before shipment).
- Transfer Order Flow: Provides a visual and editable workflow in Workflow Studio to tailor the asset transfer process to organizational requirements.
Key Outcomes
- Efficient and controlled movement of assets between stockrooms with clear tracking of asset status changes throughout the transfer process.
- Prevention of asset transfer conflicts through business rules that restrict duplicate transfers.
- Automated task generation and progression streamline the transfer order lifecycle and improve visibility into transfer stages and service levels.
- Customization capabilities allow alignment of transfer workflows and tasks with specific organizational needs, enhancing process flexibility and compliance.
- Improved asset status accuracy via automatic updates tied to task completion, reducing manual errors and administrative overhead.
Manage the asset movement from one stockroom to the other using transfer order.
The Asset Management application enables asset managers to create transfer orders for moving assets between company stockrooms.
Consumable assets and non-consumable assets can be transferred as follows:
- If an asset is consumable, it can be transferred and the quantity can be greater than one. Consumable parts are tracked by the system qualitatively.
- If an asset is non-consumable, it must be transferred as a single entity with a quantity of one. Non-consumable parts correspond to assets defined in the system.
- If the Service Management Core plugin is activated, the Transfer Order Line SM core workflow manages the processing of the transfer order lines.
- If the Field Service Management plugin (com.snc.work_management) is activated, the Transfer Order Line SMCore workflow manages the processing of the transfer order lines.
Transfer order lines
Transfer order line tasks
When you create a transfer order line, based on the model category specified in the asset, a transfer order line task is automatically created. Transfer order line tasks are created to move transfer order lines from one stage to the other. Transfer order line tasks also help you to track service levels and the time frame needed to complete a transfer order.
Default template tasks are available with the Asset Management application. The template tasks are based on model categories. Default template tasks cannot be deleted or modified. If required, you can also create your own customized template tasks. For more information, see Create a customized template task. When you create a transfer order line and select an asset, that asset corresponds to a model category. If a customized template task exists for that model category then that template task is added to the transfer order line as a transfer order line task. If no customized template task match is found for the asset you selected, then the default template task is added as a transfer order line task.
If you skip a transfer order line task and select Closed Skipped, the asset is not updated automatically. Once the asset is received or delivered, you can make the update manually.
If you are upgrading from any previous release to the New York release, and you have an open transfer order line that is still being processed, all the transfer order line tasks associated with that transfer order line are simultaneously created and displayed in the transfer order line form layout. Based on the stage of the transfer order line, the tasks that still need to be processed will be open; all the other tasks that have already been completed will be closed. Based on the order, if you close a later transfer order line task, all the previous tasks, which are currently open, automatically will be Closed Skipped.
Transfer order line subtasks
To further add granularity and efficiency to the process, you can also create subtasks for each transfer order line task. Each transfer order line task can have multiple subtasks. For example, before preparing for shipment, for a computer, you may want to create subtasks for imaging the computer or adding additional software. If subtasks have been defined for a particular transfer order line task, then the subtasks are automatically added to the transfer order line task. Once all the subtasks are closed, the transfer order line task is automatically closed. For more information, see Create a template subtask.