Description |
Once a delivery is confirmed by the DC on SupplyStream, this method will push the delivery information to the Hub. |
System behaviours
- Service supports the situation where the DC add or remove SKU's from a receipt in SS. The removed lines would not be returned in the Push GRN (no 0 quantity). The added lines would be added to the Push GRN.
- Multiple lots of the same product code will show across multiple line items. These lots will be separated by GRNLineItem entities, and will contain the original Line Number specified on upload. For example:
- SKU 123 with a Line Number 1 with a total quantity of 10
- SKU 234 with a Line Number 2 with a quantity of 5
- is received with quantities as follows:
- Lot Number 23 of SKU 123 has a quantity of 6 and returns Line Number 1 in Push GRN
- Lot Number 67 of SKU 123 has a quantity of 4 and returns Line Number 1 in Push GRN
- Lot Number 7 of SKU 234 has a quantity of 5 and returns Line Number 2 in Push GRN
- Received stock may have been processed into a locationType other than AvailableStock. This service provides confirmed GRN quantities, not the final stock location type. Please refer to the stock report for available stock levels as this service does not specify received locationType.
A single XML/CSV GRN file can contain both Standard and Return GRN’s.
- In the case of when stock is "putaway" (i.e. a movement following a GRN) in it's final location (for example: QC to Available), one SKU may be done in multiple batches. For example a GRN of SKU 123 has a quantity of 100. This could be done in two movements of 50. The same SKU may also have stock put away across multiple location types, i.e. Quarantine, Available Stock, Query.
This message could be generated whenever:
...
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
GRN | ||
Field | Description | Data Type |
MessageGroupId | Placeholder | nvarchar(100) |
MessagePart | This is the message part of the total number of messages. API only. | int |
MessageTotal | This is the total number of messages. API only. | int |
IntegrationId | This is determined by SupplyStream and is the client unique identifier. This will be a consistent unique value per client. Example: CCIND | nvarchar(100) |
SequenceNumber | This is determined by SupplyStream. Every push message will increment by 1 for each service selected | int |
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: | nvarchar(50) |
ReceiptReason | Placeholder. | nvarchar(50) |
InterfaceRecordId | This is the SupplyStream 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) |
DeliveryNumber | This is the delivery reference number. An ASN Number provided in the Load Receipts message will show here. If the return was raised by the DC against the sales order number, this will be an incremental value. | nvarchar(100) |
HBRef | The HB_Ref provided in the Load Receipts message will show here. 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) |
ArrivedDate | The date that the DC has marked the ASN as arrived. | datetime |
ReceivingStartDate | The date that the DC started receiving the ASN | datetime |
ConfirmedDate | The date that the DC have confirmed the ASN as put away | datetime |
DCCode | SEKO created code that uniquely identifies the DC from other SEKO DC's. This code is supplied by SEKO. | nvarchar(100) |
ReturnService | Placeholder | nvarchar(100) |
SupplierCode | Supplier code assigned to the ASN | nvarchar(100) |
| DeliveryType | The Type of the delivery, i.e. Standard, Return | nvarchar(100) |
...