Radial Integration | 2016

Store Fulfillment > Store Fulfillment Feeds > Order Cancels

Order Cancels

Store Fulfillment to Retailer

Column Description

# Tag Req Max Len Occurs Type Nest Level Parent Tag Description SFS ISPU STS TYPE
1 <CustomerServiceUpdate> Yes 0 1/Doc Node 0 None Root tag indicating the beginning of a customer service document. Y Y Y S
2 <CustomerService> Yes 0 1+ Node 1 <CustomerServiceUpdate> Node indicating the beginning of a customer service action. Y Y Y S
3 <Header> Yes 0 1 Node 2 <CustomerService> Node containing header elements. Y Y Y S
4 <VendorNumber> Yes 10 1 String 3 <Header> Code representing the fulfillment location of the order. Y Y Y S
5 <OrderNumber> Yes 20 1 String 3 <Header> The original OMS order number plus any suffix added in Store Fulfillment for split orders Y Y Y S
6 <HostOrderNumber> Yes 20 1 String 2 <Header> The original OMS order number. Y Y Y S
7 <OrderType> Yes 8 1 String 3 <Header> "DropShip" for Store Fulfillment or DropShip. "Stock" for StockPO. Y Y Y S
8 <Company> No 4 1 String 3 <Header> Code associating the order to a company. Y Y Y S
9 <Division> No 4 1 String 3 <Header> Code associating the order to a division within the company. Y Y Y S
10 <Department> No 4 1 String 3 <Header> Code associating the order to a department within the division. Y Y Y S
11 <CustomerPO> No 20 1 String 3 <Header> End customer purchase order number. Y Y Y S
12 <LotNumber> No 10 1 String 3 <Header> Number or code representing the order processing picking lot of the order. May be used as a pass through field to store header-level data for printed documents or host updates. Y Y Y S
13 <JobNumber> No 16 1 String 3 <Header> Number or code representing the processing job that processed the order. May be used as a pass through field to store header-level data for printed documents or host updates. Y Y Y S
14 <EntryOperator> No 30 1 String 3 <Header> Name of the entry operator who placed the order. May be used as a pass through field to store header-level data for printed or host update documents. Y Y Y S
15 <SourceCode> No 16 1 String 3 <Header> Offer or Catalog Code of the order. May be used as a pass through field to store header-level data for printed documents or host updates. Y Y Y S
16 </Header> Yes 0 1 Node 2 <CustomerService> Tag indicating end of the header Node. Y Y Y S
17 <CancelInfo> No 0 1 Node 2 <CustomerService>   Y Y Y S
18 <CancelAllProducts> Yes 3 1 String 3 <CancelInfo> “Yes” or “No” indicating whether or not all products on the order are being cancelled.Ignore this tag for Store Fulfillment as this flag represents only the portion of an order assigned to a single store. This would not represent the complete order if an order was split across stores. Y Y Y S
19 <ReasonCode> No 10 1 String 3 <CancelInfo> Code indicating the reason for the cancellation. Y Y Y S
20 <CancelDate> Yes 8 1 String 3 <CancelInfo> Cancel date (yyyyMMdd) Y Y Y S
21 <CancelTime> Yes 6 1 String 3 <CancelInfo> Cancel time (HHmmss) Y Y Y S
22 <ShipMethCode> No 20 1 String 3 <CancelInfo>   Y Y Y S
23 </CancelInfo> No 0 1 Node 2 <CustomerService>   Y Y Y S
24 <CancelProduct> Yes 0 1+ Node 2 <CustomerService>   Y Y Y S
25 <LineNumber> Yes 9 1 Num 3 <CancelProduct>   Y Y Y S
26 <SKU> Yes 30 1 String 3 <CancelProduct> Advertised SKU number. Y Y Y S
27 <VendorSKU> No 30 1 String 3 <CancelProduct> Vendor SKU number. Y Y Y S
28 <ExternalID> No 10 1 String 3 <CancelProduct> Internal host SKU identifier. Y Y Y S
29 <UPCCode> No 14 1 Num 3 <CancelProduct> UPC, EAN, or GTIN. Y Y Y S
30 <CancelledQuantity> Yes 14 1 Num 3 <CancelProduct> Maximum 4 decimal positions. Y Y Y S
31 </CancelProduct> No 0 1+ Node 2 <CustomerService> Tag indicating end of the CancelProduct Node. Y Y Y S
32 </CustomerService> Yes 0 1+ Node 1 <CustomerServiceUpdate> Tag indicating the end of a customer service action. Y Y Y S
33 </CustomerServiceUpdate> Yes 0 1/Doc Node 0 None Tag indicating the end of a customer service document. Y Y Y S

 

Copyright © 2017 Radial. All rights reserved.