| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
This service is designed for clients utilizing the Order Pick Pack module which uses Dispatch Cartons, Serial Shipping Container Codes and Retail Compliance.
Push Message
...
Trigger
Trigger: The message is pushed to the client once the uploaded Sales order via Load SO service in iHub has Retail Compliance details available.
Data Included in the message
InterfaceRecordId
SalesOrderNumber
SalesOrderReference
SalesInvoiceNumber
DispatchNumber
DcCode
CarrierName
CarrierService
PrimaryTrackingNumber
PrimaryTrackingUrl
ShipToCompanyCode
ShipToCompanyName
ShipToFirstName
ShipToLastName
DeliveryAddressLine1
DeliveryAddressLine2
DeliveryAddressLine3
DeliveryAddressLine4
DeliveryAddressCity
DeliveryAddressCountyState
DeliveryAddressPostCodeZip
DeliveryAddressCountry
DeliveryPhoneNumber
DeliveryEmailAddress
PickStartDate
PickCompleteDate
PackCompleteDate
DispatchDate
TotalWeightUom
TotalWeight
OrderType
Gs1Prefix
RoutedDate
RoutingId
CartonLineItems:
SsccNumber:
CartonWeightUom:
CartonWeight:
CartonTrackingNumber:
LineNo:
ProductCode:
ProductDescription:
EAN:
StyleCode:
BestBeforeDate:
LotNo:
PackedQty:
BuildKit:
IsComponentSku:
MessageGroupId:
MessagePart:
MessageTotal:
IntegrationId:
SequenceNo:
Configuration Steps
When a client subscribes to the Push Dispatch Carton service, the Development Team or Customer Service will add the necessary service settings in the backend.
The user can then configure the frontend settings on the iHub site by:
Assigning the Service to the Clienthttps://seko.atlassian.net/wiki/spaces/SMAN/pages/2932998161/iHub+-+Client+Setup#Assign-Services
...
Mapping the Service Settingshttps://seko.atlassian.net/wiki/spaces/SMAN/pages/edit-v2/2933030943#Service-Settings
...
Activity Logs
Check iHub Activity Menu for details - Click VIEW button to see message logs
Push via REST
...
Push via FTP
...