Receiving Detail Feed
The Receiving Detail Feed provides Radial’s WMS systems with information on inbound shipments to Radial DCs in order to prepare for and perform merchandise receiving in the warehouse. Incoming feeds can be marked as an Advance Shipping Notice (ASN) or Purchase Order (PO) file type (Field 2).
There are both XML and flat file versions of this feed.
Exchange frequency
As available.
Timing
Not a scheduled feed.
Sender/Receiver
From the Merchant to Radial
File Formats
XML
Flat file, Pipe (|) Delimited
XML Schema
The XML version of the Receiving Detail feed follows the schema: Receiving_Detail.xsd.
Additional data element definitions are in the following flat file table.
XML Example
Flat File Name
eircdtyyyymmddhhmmss.rdl
Flat File Receipt Acknowledgement
Optional; File Name: eircdtrecackyyyymmddhhmmss.rdl
Exception Reporting
An email containing an attached spreadsheet of errors will be sent to the Business Management Team and/or partner when errors occur.
Flat File Example
Flat File Data Format
|
ID |
Field |
Description |
Type |
Length |
Req. |
Comments |
|---|---|---|---|---|---|---|
|
1 |
RadialStore Number |
Store number that is assigned by Radial to represent the JDA Store Number. |
Character |
5 |
Yes |
This value can be found in the Launch Credentials document referred to as ‘JDA Store Number’ |
|
2 |
Receiving Type |
Purchase Order or ASN. P=Purchase Order A=Advance Shipping Notice
|
Character |
1 |
Yes |
Values: A, P
|
|
3 |
Partner’s Shipment Number |
Partner’s purchase order number. |
Character |
15 |
Yes |
Only required if field 2 = P (PO).
** If Logpro, length and type is 10 Numeric
|
|
4 |
Order Date |
Date of Purchase Order YYMMDD
|
Numeric |
6,0 |
No |
Identifies when the Partner placed the order with the vendor for products. |
|
5 |
Shipment Receipt Date |
Date the shipment is expected to arrive at Radial’s Warehouse YYMMDD |
Numeric |
6,0 |
Yes |
|
|
6 |
Shipper’s Name |
Name of shipper sending goods to Radial’s Warehouse
|
Character |
30 |
Yes |
If goods are shipped from the Partner then the name of the Partner’s Warehouse needs to be populated. If goods are shipped directly from vendor then vendor name should be populated Note: only the first 15 characters will be used |
|
7 |
Partner Item Number |
Partner’s item number for products in Radial Item Master. |
Character |
15 |
Yes |
Same value sent in the item master as ‘ClientItemId’ |
|
8 |
Quantity Shipped |
Quantity, in units, shipped to the Radial Warehouse |
Numeric |
6,0 |
Yes |
|
|
9 |
Item Cost |
Item cost per unit |
Numeric |
8.2 |
No |
This value should not be greater than 99999.99 |
|
10 |
Shipping Comments |
Miscellaneous comments about the shipment or items within the shipment. |
Character |
100 |
No |
|
|
11 |
Trailer Number |
Identifies the trailer at the Radial Warehouse. |
Character |
25 |
No |
|
|
12 |
Carton ID |
Identifies the carton. |
Numeric |
20,0 |
No |
To be used for ASNs only. |
|
13 |
ASN Number |
Partner ASN Identifier |
Character |
15 |
No |
To be used for ASNs only. |
|
14 |
Date/Time Stamp |
Date and Time in which the file was generated. Format yyyy-mm-dd-hh.mm.ss |
Character |
19 |
Yes |
|
|
15 |
Warehouse Number |
The Radial Warehouse that is expected to receive the products.
|
Numeric |
3,0 |
Yes |
This value can be found in the Launch Credentials document referred to as ‘Warehouse Number’ |
|
16 |
Lot ID |
The Lot ID associated with the product. |
Character |
20 |
No |
Lot ID can only be sent for items that have been flagged as ‘Lot Controlled’ in the item master. |
|
17 |
Future Use |
Future Use |
Character |
10 |
No |
Future use |
|
18 |
Segment ID |
The segment ID associated with this item. |
Character |
30 |
No |
If applicable, the Radial assigned segment ID associated with the item. |
Flat File Trailer Record
|
ID |
Field Name |
Field Description |
Field Type |
Field Length |
Req |
Comments |
|---|---|---|---|---|---|---|
|
1 |
Record Identifier |
Record Identifier |
Character |
10 |
Yes |
Value: “TRAILER” (all caps) |
|
2 |
# of total records |
Total number of records in the file including Trailer |
Numeric |
7,0 |
Yes |
|
|
3 |
Batch ID# |
Batch Number |
Numeric |
9,0 |
Yes |
Sequential number |
ASN error messages
(subject to change; this may not be a complete list)
** Unless otherwise noted, if there is an error, the line where the exception occurred will not be processed and will need to be corrected and resent.
|
ID |
Error Message |
Comments |
|---|---|---|
|
1 |
Error parsing delimited data. |
File needs to be corrected & resent. |
|
2 |
No Trailer found |
Trailer record missing. File needs to be corrected & resent. |
|
3 |
Total of xx <> xx The record count control total does not match the number of records processed in the file xxxx for Store xxx. |
Total number of records does not match the trailer. File needs to be corrected & resent. |
|
4 |
Batch ID received is invalid. |
Batch id must be between 0 and 999999999. File needs to be corrected & resent. |
|
5 |
Partner ID is invalid. |
|
|
6 |
Shipment Number is blank. |
Shipment # is Required for PO.
|
|
7 |
Shipment Number should be equal to or less than 15 characters. |
PO #: Shipment Number should be equal to or less than 15 characters. |
|
8 |
Order Date is invalid. |
|
|
9 |
Shipment Receipt Date is invalid. |
|
|
10 |
Shipper Name is blank. |
|
|
11 |
Shipper Name should be equal to or less than 30 characters. |
|
|
12 |
Quantity shipped is invalid. |
If quantity is zeros or greater than 999999. |
|
13 |
Item Cost is invalid. |
If item cost less than zero or greater than 99999999. |
|
14 |
Shipping comments should be equal to or less than 100 characters. |
|
|
15 |
Trailer Number should be equal to or less than 25 characters. |
|
|
16 |
Carton ID should be equal to or less than 25 characters. |
|
|
17 |
Carton ID is missing. |
If ASN, carton ID is required. |
|
18 |
Partner ASN identifier is Blank. |
If ASN, ASN is required. |
|
19 |
ASN Number should be equal to or less than 25 characters. |
If ASN, ASN number needs to be 25 characters or less. |
|
20 |
Fulfillment Center number is invalid. |
If fulfilment center is less than 1 or greater than 99999. |
|
21 |
Fulfillment Center number is not setup in PFFCFG File for ASN. |
The fulfilment center sent is not set up for the partner. |
|
22 |
Partner Item Number is blank. |
|
|
23 |
Partner Item# is invalid. Please send the Item Master for this Vendor part#. Do not send the ASN record again for this SKU. It will be processed after the Item Master is processed. |
Item does not exist in JDA. |
|
24 |
Corresponding GSI SKU# not found in TFITM. Don't have to send this record again. Will be processed when the feed program run again. |
|
|
25 |
Receiving Type is invalid. It should be "A" or "P". |
|
|
26 |
Default Record Not setup for Record Type. |
Receiving Type is blank and there is no default set up. |
Receipt Acknowledgment
The Receipt Acknowledgment file, when required, provides the partner or vendor file acknowledgment information for those files received by Radial. It is provided by the partner or vendor for files that are sent by Radial.
Exchange Frequency
Generated in response to Receiving Detail feed
Sender/Receiver
Radial to Partner/Vendor
File Name
FeedPrefixFeedAckNameyyyymmddhhmmss.xxx
• FeedPrefix = the Feed prefix of the file being acknowledged
• FeedAckName = the Feed Acknowledgement Name of the file being acknowledged (i.e., recack)
• xxx is the extension from the original file being acknowledged
File Format
Pipe (|) delimited
Data Format
|
ID |
Field |
Description |
Type |
Length |
Required |
Comments |
|---|---|---|---|---|---|---|
|
1 |
File Name |
File Name sent or received for processing |
Character |
50 |
Yes
|
The name of the file being acknowledged (including original date/time stamp) |
|
2 |
Number of Records |
Total number of records in the file (Number of records DOES NOT include the trailer record) |
Numeric |
5.0 |
Yes |
Does not include trailer record. |
|
3 |
Date/Time Processed |
YYYYMMDDHHMMSS |
Numeric |
14,0 |
Yes |
|
|
4 |
Batch ID# |
Batch Number |
Numeric |
9,0 |
Yes |
Batch number of the file being acknowledged |