Inter-location transfers
Dispatch exact unrestricted stock into in-transit custody and require a different destination operator to scan and reconcile the handoff.
Screen orientation
Location creation, dispatch and receipt depend on separate Inventory authorities. Source balances and destinations are filtered by assigned site, classification, stock state and the user’s role.
The page can define an authorised storage location or dispatch a transfer. The in-transit queue then exposes receive/reconcile only to an eligible user other than the dispatcher.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Site / Location code / Location name | Select and text | Required when adding a location. | Create a location only within the assigned site and use its physical controlled code and recognisable name. | Defines a destination identity; it creates no stock. |
| Storage type / Storage clearance | Selects | Required when adding a location. | Choose the actual storage function and highest permitted classification. Clearance is a location rule, not a user permission. | Controls later eligibility for stock movement. |
| Capacity (optional) | Decimal | Optional; positive when present. | Record the approved capacity in the applicable quantity model. Leave blank when no governed capacity is defined. | Adds a destination constraint without creating inventory. |
| Exact unrestricted balance | Select | Required for dispatch. | Select the exact item revision, source, batch/serial/container, ownership and available quantity. | Pins the source balance that will leave custody. |
| Planned MRP transfer request (optional) | Select | Optional for a planning-generated transfer. | Select a pending request only when dispatching its exact planned item revision, quantity, ownership and locations; the form locks those values and the server revalidates them. | Links physical custody execution to the retained MRP run and proposal without creating a second posting. |
| Destination location | Select | Required. | Choose only the intended controlled destination offered after source scope and classification checks. | Pins the receiving location. |
| Quantity | Decimal | Required; positive and no greater than the selected unrestricted balance. | Enter the physical amount dispatched, preserving serial/container whole-identity rules. | Creates the exact in-transit quantity when confirmed. |
| Movement authorization | Text | Required. | Cite the approved transfer authority or request; do not use the transfer number itself. | Retains attributable movement provenance. |
| Dispatch and custody notes | Long text | Required. | Record package condition and authorised purpose at handoff. | Becomes immutable dispatch evidence. |
| Scanned transfer / source / destination | Scanner or text | Required for receipt reconciliation. | Scan all three physical references and confirm they match the dispatched record. | Prevents a different transfer or location from being received. |
| Package or security seal / Receipt reconciliation notes | Text and long text | Required when reconciling receipt. | Record the verified seal and observed quantity/package condition. | Completes attributable destination custody evidence. |
Actions and effects
When to use: When an authorised physical storage destination must be registered.
What it does: Creates location master data only; no stock is placed there.
When to use: After exact source, destination, quantity and authority are verified.
What it does: Posts source-out and in-transit custody evidence.
When to use: By a different eligible destination operator after all scans match.
What it does: Posts the destination receipt and closes the in-transit handoff.
Lists and states
- In-transit queue: transfer, classification, source→destination, quantity and authority show custody awaiting independent receipt.
- Transfer history retains dispatcher and receiver evidence; it is not editable inventory master data.
Authority boundary
Transfers move existing authorised quantity only. They cannot create or approve stock, bypass blocked/quarantine state, merge serial/container identities or allow the dispatcher to self-receive.