Warehouse Inventory Movement
Overview
This section describes the Warehouse Inventory Movement process enabled through the mobile scanner application. The functionality supports end‑to‑end stock handling using new work order actions: Pick, Pack, Ship, and Deliver.
This process is used for a customer use case and focuses on enabling inventory movement orders driven by work orders.
Business Purpose
The objective of this module is to:
- Enable controlled movement of inventory within a warehouse
- Support operational workflows using mobile devices
- Track stock lifecycle from picking to final delivery
- Ensure traceability of inventory actions against work orders
High-Level Process Flow
- A Work Order is created for inventory movement
- Warehouse staff receive the work order on the mobile scanner application
- Inventory progresses through the following actions:
- Pick
- Pack
- Ship
- Deliver
- Each action updates the work order and inventory status
- The process completes once Delivery is confirmed
Mobile Scanner Application Context
The process is executed primarily via the mobile scanner app.
Inventory Movement Use Case
The Warehouse Scenario:
- A warehouse receives a work order to move stock
- The work order instructs staff to:
- Pick specific inventory items
- Pack them for shipment
- Ship the items
- Confirm delivery
This aligns with standard warehouse logistics workflows.
Work Order Lifecycle in Inventory Movement
A work order goes through a defined action cycle:
- Pick – Inventory is physically collected from storage
- Pack – Picked inventory is packaged for shipment
- Ship – Packaged items are dispatched
- Deliver – Items are delivered and receipt is confirmed
Once all actions are completed, the work order has fully progressed through the cycle.
Identification and Tracking
- Inventory items are tracked using identifiers such as:
- Configuration Item (CI)
- Serial Number (where applicable)
Key Notes and Constraints
- Actions are sequential and must follow the defined order
- System behaviour depends on the deployed version
- UI differences in the mobile app and the FSM console do not prevent backend action execution
- Shipping functionality must be validated
Example scenario on the Midtier
Step 1 (Pick Config): Navigate to Midtier Home page then select the Applications list and scroll down to select the FSM Scanner Integration Application then click on the FSM Scanner Workflow Configuration.
Step 2: After being directed to the FSM Scanner Workflow Configuration Click on the “New request” button
Step 3: Once navigated to the new request view. Select the company, of your choice, and add “Pick” on the Scanner Action text Field. The most critical setting on these configurations is to set Update CI to “Yes”, Dataset to “BMC Asset” and Pick Action to “Yes”, The other setting may be left as they are unless a different result is desired.
Step 4: After creating configuring the Scanner workflow you may click on the save button and review it.
Step 5 (Pack Config): After navigating to the Scanner workflow Configuration Request new form, Fill in the Scanner Action field as “Pack” Select the company, of your choice. The most critical setting on these configurations are to set Dataset to “BMC Asset”, and Pack Action to “Yes”.
Step 6: You may configure other setting on the form in the Work Order Information to such Description and/or View Access, in accordance with the desired outcome. Update Create CI Work Log to “Yes”. Then save and review the configuration
Step 7 (Shipping Config): After navigating to the Scanner workflow Configuration Request new form, fill in the Scanner Action field as “Shipping” Select the company, of your choice. The most critical setting on these configurations is to set Dataset to “BMC Asset”, and Shipping Action to “Yes”. The AssetLifeCycle Status of the Original CI should be “Transferred”
Step 8: Navigate to the Worklog information and update the Description and Short Description to “CI was Shipped”
Step 9: Save and review the configuration.