Description
| Excerpt |
|---|
Collects a tote-ID for an Order Line. In a Planned Function. |
See also
...
Advantages
Tote is Pre-defined step with unique functionality.
Requirements
- Order List Mobile Configuration must have the TotePicking-tag defined, i.e. <TotePicking>true</TotePicking>
- Order Line must have the Destination-tag defined, i.e. <Destination>Customer1234</Destination>
Flow
Collects
A tote/bag/pallet/carrier -identification, for the current order line being registered.
Typical use
Part of the Standard Workflow on Planned Functions.
Tote is used to group related lines, i.e. lines going to the same Place or belonging to the same Document etc.
...
The Destination-
...
attribute defines which Customer/Order/Whse.Document the line belongs to.
Flow
- Registering the first line belonging to a Tote, the app will ask for a Tote ID.
- Registering the next line belonging the same Tote, the app will ask for Validation of the Tote ID from step 1
- Optionally: Should the Tote be physically full, you can start a new Tote.
Notes
- Requirements
- Order List Mobile Configuration must have the TotePicking-attribute=true.
...
...
- See Order List GetOrders Response
- Order Line must have the Destination-attribute defined, i.e. <Destination>Customer1234</Destination> See Order Lines GetOrderLines Response
- See also: How to use Tote- Picking and Shipping
See Step Configuration Matrix for details.
Examples
eFilter by label (Content by label) showLabels false max 155 spaces TFSK showSpace false sort title type page cql label = "example" and label = "totestep" and space = "TFSK" labels Mobile