AI-generated Key Takeaways
-
This document outlines the required data elements for outbound order transactions, including details like order numbers, shipment IDs, timestamps, and location codes.
-
The data encompasses outbound orders from the past hour and any records not previously included.
-
Two fields are mandatory:
outbound_order_numberandwarehouse_shipment_id, along with location codes and data extraction timestamp. -
Most fields are optional but have validation rules, especially date/time fields adhering to ISO 8601 format and string fields with maximum length limits.
-
Status fields,
last_wms_order_statusandnext_wms_order_status, refer to a separate document for valid values.
Include all the Outbound Order transactions for the previous 1 hour and all the records not included in the previous file.
| Data element name | Description | Type | Required (Yes/No) | Validation rules |
|---|---|---|---|---|
| outbound_order_number | Outbound order number for the warehouse from SAP | String | Yes | Max Length: 50 |
| warehouse_shipment_id | Unique identifier for this shipment issued by the shipping partner. | String | Yes | Max Length: 50 |
| execution_order_id | The reference to the Google execution order. | String | No | Max Length: 50 |
| tracking_number | Carrier Tracking Number of the Inbound order received. | String | No | Max Length: 50 |
| google_transport_load_id | Reference to the Transport Load planned by Google's Transportation Management System (TMS) for this shipment, when applicable. | String | No | Max Length: 50 |
| trailer_number | Physical Trailer Number. Systemic trailer number the order is received on, which should match the physical trailer number. | String | No | Max Length: 50 |
| dock_door_number | Dock door the trailer is docked at and the material is unloaded from. | String | No | Max Length: 50 |
| last_wms_order_status | Status based on the last step in the operational process flow that has been completed. | String | No | List of valid values |
| next_wms_order_status | Status based on the next step in the operational process flow that is yet to be completed, regardless of whether that step has begun or not. | String | No | List of valid values |
| released_date_time_utc | Date time the material was allocated to the order and confirmed release and the pick work can start in the WMS. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| pick_start_date_time_utc | Date time of the first pick. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| pick_end_date_time_utc | Date time of the last pick. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| stage_start_date_time_utc | Date time the first completed unit (pallet, carton, etc) of material for the order is located in the staging lane. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| stage_end_date_time_utc | Date time the last completed unit (pallet, carton, etc) of material for the order is located in the staging lane. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| load_start_date_time_utc | Date time the first completed unit (pallet, carton, etc) of material for the order is loaded on the trailer. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| load_end_date_time_utc | Date time the last completed unit (pallet, carton, etc) of material for the order is loaded on the trailer. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| hold_start_datetime_utc | Date time the hold for the order is initiated (CI-Hold, DG Review, etc). | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| hold_end_datetime_utc | Date time the hold for the order is released (CI-Hold, DG Review, etc). | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| dispatched_date_time_utc | Date time the trailer is closed and dispatched from the dock door. | Datetime | No | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |
| source_google_location_code | The code of location where the items are shipped from. | String | Yes | Max Length: 50 |
| destination_google_location_code | The code of location where the items are shipped to. | String | Yes | Max Length: 50 |
| data_extract_datetime_utc | Date time the report/data was generated from the 3PL system. | Datetime | Yes | Format: yyyy-mm-ddThh:mm:ssZ (ISO 8601) |