wave
Represents a collection or batch of orders processed together in logistics and fulfillment workflows.
Columns
| Name | Type | References | Description |
| completeddate | Date | The date when the wave process was completed. This marks the finalization of picking and allocation tasks associated with the wave. | |
| createdby | String | The identifier of the user or system that created the wave. This helps track who initiated the wave processing. | |
| createddate | Datetime | The timestamp indicating when the wave was created. This is useful for auditing and tracking wave lifecycle stages. | |
| externalid | String | A unique external identifier used for integration with third-party systems. This can help cross-reference waves with external records. | |
| location | String | The warehouse or fulfillment center where this wave is being processed. This determines where picking and shipping activities take place. | |
| name | String | The name or reference code assigned to this wave. This can be used for tracking and reporting on wave processing. | |
| newwavestatus | String | The current status of the wave in the system. This status indicates whether the wave is in progress, completed, or awaiting processing. | |
| picktype | String | The method or strategy used for picking items in the wave, such as batch picking, zone picking, or discrete picking. | |
| priority | String | The priority level assigned to the wave, which determines its processing urgency relative to other waves. | |
| releaseddate | Date | The date when the wave was officially released for picking. Once released, warehouse staff can begin executing tasks associated with this wave. | |
| searchtemplateid | String | The identifier for the search template used to generate the wave. This template helps define criteria for selecting orders and inventory. | |
| status | String | The overall status of the wave, indicating whether it is pending, in progress, completed, or canceled. | |
| subsidiary | String | The business entity or subsidiary associated with this wave. This is relevant for companies operating in multiple regions or divisions. | |
| totalassigned | Integer | The total number of order lines assigned to pickers within this wave. This reflects the workload distribution among pickers. | |
| totalorderlines | Integer | The total number of order lines included in this wave. This helps in assessing the size and complexity of the wave. | |
| totalorderlinesfailed | Integer | The number of order lines that failed to process within this wave. Failures could be due to inventory shortages or system errors. | |
| totalorderlinesreleased | Integer | The number of order lines successfully released for picking within this wave. This reflects progress in the fulfillment process. | |
| totalpicktasks | Integer | The total number of pick tasks generated by this wave. Each task represents an individual picking action required for order fulfillment. | |
| totalunassigned | Integer | The number of order lines that have not yet been assigned to pickers. This can indicate pending work that needs distribution. | |
| waveorderlimit | String | The maximum number of orders that can be included in this wave. This limit is typically defined based on operational constraints. | |
| wavetype | String | The category of wave, such as regular, priority, or replenishment. This classification helps optimize warehouse operations. |