Items Packed
In some cases, commissioners prepare a trip upfront by packing itemsPlanned before the mobile worker (driver) starts the trip. When using OMD Pick & Pack, packed quantities are aggregated and confirmed in the app. Aggregated items and their quantities are then stored in a separate attachment with subtype itemsPacked attached to the trip.
| Attribute | Description | Optional | Example |
|---|---|---|---|
| attachmentType | The type of this attachment. Needs to be 6, which means delivery | no | 6 |
| subType | The sub-type of this attachment, being itemsControlled | no | itemsPacked |
| reference | For the main aggregation level, the product category the aggregated item belongs to. For drilldown, a hash of the subgroup determined by the picknpackSubGroupingTemplate process flow preference. |
no | main: Jackets; drilldown: a1b2c3d4 |
| content | The description of the aggregated item | no | Billy |
| quantity | The packed quantity of the aggregated item, possibly deviating from the planned quantity | no | 9 |
| size | The planned quantity of the aggregated item | no | 10 |
| format | The aggregation level, being main or drilldown |
yes | main |
| processFlow | The reason provided when deviating from the planned quantity | yes | Not available |
| extra | Additional XML data using the <Data> and <Scan> layout documented in the scancode attachment |
yes | see scancode attachment |
The extra field may use - among other information - the same <Data> element layout as the scancode attachment, including its <Scan> elements and attributes. Unlike the scancode attachment, itemsPacked is a trip attachment: the extra scan data is associated with the trip and not with an individual task.