Description |
As soon as a delivery is arrived by the DC on SEKO360, this method will push the delivery information to the Hub. |
Available formats
Entity Relationships
This diagram shows the high level relationship between the entities detailed in the Field Level Details section of this page.
Field level details
DeliveryArrive | ||
Field | Description | Data Type |
ArrivedDate | Goods that the DC has marked the goods as arrived. The goods are in the building to be processed | datetime |
DCCode | SEKO created code that uniquely identifies the DC from other SEKO DC's. This code is supplied by SEKO. | nvarchar(100) |
DeliveryNumber | This field is linked to the ASN number specified in the Load Receipt message. If the return has been raised by the DC against the sales order number, this will be an incremental value. | nvarchar(100) |
HBRef | This field is linked to the HB_Ref field in the Load Receipts message. For returns raised by the DC against the sales order number, this field will contain the original sales order number the goods were dispatched on. | nvarchar(50) |
IntegrationId | This is determined by SEKO360 and is the client unique identifier. This will be a consistent unique value per client. Example: CCIND | nvarchar(100) |
InterfaceRecordId | This is the SEKO360 Globally Unique Identifier. If the GUID is not provided in the Load message, this will be automatically generated by the system. System generated example: a99645dc-5b45-4917-890c-4b02c68ac342. | varchar(100) |
RMA | This data is generated only on a return raised by the DC against the sales order number. Of the Push GRN message, you also have the HB Ref and Delivery Number fields. This RMA field is a conjunction of both these fields. For example: Delivery Number: 000219, HB Ref: 200117-1, RMA: 200117-1.000219 | nvarchar(50) |
ReturnService | Placeholder | nvarchar(100) |
SequenceNumber | This is determined by SEKO360. Every push message will increment by 1 for each service selected | int |
...