Availability
Availability
|
Element Name
|
Optional
Required |
Description
|
Data
Type |
Max Len
|
||||||||||
| Header | R | |||||||||||||
| UserName | R | EC logon ID assigned by Tech Data | A/N | Note 1 | ||||||||||
| Password | R | Password assigned by Tech Data | A/N | Note 1 | ||||||||||
| TransSetIDCode | R | Value must be ‘846SEND’ | A/N | 7 | ||||||||||
| TransControlID | R | Unique tracking identifier assigned by the customer for each Availability request document submitted. | A/N | 100 | ||||||||||
| ResponseVersion | O |
Designates the Response DTD version that will be returned.
|
A/N | 20 | ||||||||||
| Detail | R | |||||||||||||
| LineInfo | Minimum of 1 per Availability request document, but multiple are allowed | |||||||||||||
| AssignedID | R | Unique tracking identifier assigned by the customer for each detail line (item) requested within the Availability document | A/N | 100 | ||||||||||
| RefIDQual | R |
Two character code identifying the part number type that was contained in the Availability
request document. It identifies the part number type that is contained in
the proceeding <RefID> element.
|
A | 2 | ||||||||||
| RefID | R | The part number for which an availability request is being submitted | A/N | 20 | ||||||||||
| Summary | R | |||||||||||||
| NbrOfSegments | R | Obsolete , no value is required |
| The actual maximum length is not documented. Include on each XML document submitted the UserName and Password values assigned by your Master/Admin user. | |
| If Buyer Part numbers are to be submitted, contact your Tech Data Sales team to have your Buyer Part number to Tech Data Item number cross-reference established on our system. |
The following is an example of an Availability Response document:
|
Element Name
|
Optional
Required |
Description
|
Data
Type |
Max Len
|
||||||||||
| Header | R | |||||||||||||
| TransSetIDCode | R | Value will be ‘846REC’ | A/N | 6 | ||||||||||
| TransControlID | R | Unique tracking identifier assigned by the customer for each Availability request document submitted. The content of the element sent by the customer within the XML document is returned as is to the customer within the Response document. The primary function of these types of elements is for tracking purposes. | A/N | 100 | ||||||||||
| ResponseVersion | O |
Designates the Response DTD version
• ResponseVersion 1.3 or higher
|
A/N | 20 | ||||||||||
| Detail | R | |||||||||||||
| LineInfo | R | Minimum of 1 per Availability response document, but multiple could occur. | ||||||||||||
| AssignedID | R | Unique tracking identifier assigned by the customer for each detail line (item) requested within the Availability document. The content of the element sent by the customer within the XML document is returned as is to the customer within the Response document. The primary function of these types of elements is for tracking purposes. | A/N | 100 | ||||||||||
| RefIDQual1 | R |
Two character code identifying the part number type that was contained in the Availability
request document. It identifies the part number type that is contained in
the following <RefID1> element.
|
A | 2 | ||||||||||
| RefID1 | R | The part number being inquired | A/N | 20 | ||||||||||
| RefIDQual2 | O |
Two character code identifying the part number type that was contained in the Availability
request document. It identifies the part number type that is contained in
the following <RefID2> element.
|
A | 2 | ||||||||||
| RefID2 | O | Alternate part number being inquired | A/N | 20 | ||||||||||
| RefIDQual4 | O |
Two character code identifying the part number type that was contained in the Availability
request document. It identifies the part number type that is contained in
the following <RefID4> element.
• ResponseVersion 1.3 or higher
|
N/A | 2 | ||||||||||
| RefID4 | O |
Alternate part number for which an availability request is being submitted.
• ResponseVersion 1.3 or higher
|
N/A | 20 | ||||||||||
| ProductWeight | O |
Weight of the requested item.
• ResponseVersion 1.3 or higher
|
N | 9 | ||||||||||
| ItemStatus | O |
Tech Data status of the requested item. Possible values include:
• ResponseVersion 1.3 or higher
|
A/N | 14 | ||||||||||
| WhseInfo | ||||||||||||||
| IDCode | R | Warehouse name, e.g. SUWANEE, GA; SWEDESBORO, NJ; etc. For a complete list of Tech Data’s logistic centers, refer to Warehouse Codes in the Order submit section | A/N | 16 | ||||||||||
| WhseCode | O |
Tech Data warehouse identifier. For a complete list of Tech Data’s logistic
centers, refer to Warehouse Codes
in the Order submit section.
• ResponseVersion 1.4 or higher
|
A/N | 4 | ||||||||||
| Qty | R | Quantity of item in the warehouse. | N | 15 | ||||||||||
| TotalOnOrderQty | O |
The total number on order for the warehouse.
• ResponseVersion 1.3 or higher
|
N | 12 | ||||||||||
| OnOrderQty | O |
The earliest Expected-To-Arrive quantity for the warehouse. Is a sub-set of TotalOnOrderQty.
• ResponseVersion 1.3 or higher
|
N | 10 | ||||||||||
| OnOrderETADate | O |
The earliest Expected-To-Arrive date for the warehouse. (format mm/dd/yy)
• ResponseVersion 1.3 or higher
|
A/N | 8 | ||||||||||
| ErrorInfo | ||||||||||||||
| RefIDQual3 | O | Will contain ‘1Q’ | A/N | 2 | ||||||||||
| RefID3 | O | Will contain ‘0’ | N | 1 | ||||||||||
| ErrorDesc | O | Error description | A/N | 250 | ||||||||||
| Summary | R | Obsolete, disregard this value | ||||||||||||
| NbrOfSegments | R | Obsolete, disregard this value | N | 9 |
| ©2015 Tech Data Corporation. All Rights Reserved. |
|
Tech Data proprietary and confidential |