Price and Availability
Price and Availability|
Note:
Users can also use the PriceList transaction as an
alternative to Price and Availability. PriceList returns the
same data as this transaction along with all possible pricing options available as well as promotion details. |
The following DTD defines the Price and Availability Submit document:
|
Note:
XML should be used as a supplement to the Product Catalog found on Tech Data’s Web
site. The Product Catalog is updated every business day and the download can be automated with
the getprod.exe utility. The Product Catalog is also available via an EDI 832
transaction. XML should
not
be used for updating your entire electronic catalog database. Tech Data reserves the
right to restrict access to the XML service for customers who do not use this service appropriately.
|
|
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 | ||||||||||||||||||||||||||||||||||||||||
| TransControlID | O | Unique tracking identifier assigned by the customer for each Price and Availability document submitted | A/N | 100 | ||||||||||||||||||||||||||||||||||||||||
| ResponseVersion | O |
Designates the Response DTD version that will be returned.
|
A/N | 20 | ||||||||||||||||||||||||||||||||||||||||
| Detail | R | |||||||||||||||||||||||||||||||||||||||||||
| LineInfo | R | Minimum of 1 per Price and Availability submit document is required, but multiple are allowed | ||||||||||||||||||||||||||||||||||||||||||
| AssignedID | O | Unique tracking identifier assigned by the customer for each detail line (item) requested within the Price and Availability submit document | A/N | 100 | ||||||||||||||||||||||||||||||||||||||||
| OrderLevel | O |
This element is only used when Government or Education pricing is desired.
|
A | 2 | ||||||||||||||||||||||||||||||||||||||||
| RefIDQual | R |
Two character code identifying the part number type that was contained in the Price and Availability submit
document. It identifies the part number type that is contained in the proceeding <RefID> element.
|
A | 2 | ||||||||||||||||||||||||||||||||||||||||
| RefID | R | The item number | A/N | 20 | ||||||||||||||||||||||||||||||||||||||||
| PromoAcceptInd | O | A Y/N value which indicates whether or not promotions will be accepted | A | 1 | ||||||||||||||||||||||||||||||||||||||||
| PromoAppliedShowInd | O | A Y/N value which indicates whether or not the response will show where promotions have been applied, (using the PromoAppliedInd) | A | 1 | ||||||||||||||||||||||||||||||||||||||||
| Summary | O | Obsolete, no longer needed | ||||||||||||||||||||||||||||||||||||||||||
| NbrOfSegments | R | Obsolete (being phased out), disregard this value | ||||||||||||||||||||||||||||||||||||||||||
| The actual maximum length is not documented. Include on each XML document submitted the UserName and Password values assigned by your Master/Admin user. |
|
Element Name
|
Optional
Required |
Description
|
Data
Type |
Max Len
|
||||||||||||
| Header | ||||||||||||||||
| TransSetIDCode | R | Fixed value of ‘846REC’ | A/N | 6 | ||||||||||||
| TransControlID | O | Unique tracking identifier assigned by the customer for each Price and Availability submit 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 | A/N | 20 | ||||||||||||
| Detail | ||||||||||||||||
| LineInfo | R | For each item number (<RefID>) submitted, one LineInfo node will be returned | ||||||||||||||
| AssignedID | O | Unique tracking identifier assigned by the customer for each detail line (item) requested within the Price and Availability document. The content of the element sent by the customer within the XML message is returned as is to the customer within the Response document. The purpose of this element is for tracking purposes. | A/N | 100 | ||||||||||||
| RefIDQual1 | O |
Two character code identifying the part number type that was contained in the Price and Availability submit
document. It identifies the part number type that is contained in the following <RefID1> element.
|
A | 2 | ||||||||||||
| RefID1 | O | The item number | A/N | 20 | ||||||||||||
| RefIDQual2 | O | Two character code identifying the part number type that was contained in the Price and Availability submit
document. It identifies the part number type that is contained in the following <RefID2> element.
|
A | 2 | ||||||||||||
| RefID2 | O | This element will contain the manufacturer’s part number when preceded by a <RefIDQual2> value of ‘MG’ | A/N | 20 | ||||||||||||
| RefIDQual4 | O |
Two character code identifying the part number type that was contained in the Price and Availability submit
document. It identifies the part number type that is contained in the following <RefID4> element.
• ResponseVersion of 1.3 or higher
|
A | 2 | ||||||||||||
| RefID4 | O | Alternate part number for which an availability request is being submitted. • ResponseVersion of 1.3 or higher |
A/N | 20 | ||||||||||||
| ProductDesc | O | Description of requested item | A/N | 50 | ||||||||||||
| PriceIDCode1 | O | A fixed value of ‘CON’ | A | 3 | ||||||||||||
| UnitPrice1 | O | Customer’s price | N | 15(2) | ||||||||||||
| PriceIDCode2 | O | A fixed value of ‘MSR’ | A | 3 | ||||||||||||
| UnitPrice2 | O | Manufacturer’s Suggested Retail Price | N | 15(2) | ||||||||||||
| RequiredEndUserInfo | O | A Y/N value which indicates if end user information would be required or not when an order for
this item is submitted. This element is ALWAYS populated.
• ResponseVersion of 1.3 or higher |
A | 1 | ||||||||||||
| RequiredLicenseInfo | O | A Y/N value which indicates if end user license information would be required or not when an order for this item is submitted.
• ResponseVersion of 1.3 or higher |
A | 1 | ||||||||||||
| PromoAppliedInd | O | A Y/N value which indicates whether or not promotions were applied • ResponseVersion of 1.3 or higher |
A | 1 | ||||||||||||
| ProductWeight | O | Weight of the requested item • ResponseVersion of 1.3 or higher |
N | 9 | ||||||||||||
| ItemStatus | O |
Tech Data status of the requested item. Possible values include:
• ResponseVersion of 1.3 or higher
|
A | 6 | ||||||||||||
| WhseInfo | O | |||||||||||||||
| IDCode | R | Warehouse location name, i.e. MIAMI, FL, NORCROSS, GA, etc. For a complete list of Tech Data’s logistic centers, refer to the Warehouse Codes heading found in the Order submit section. | A/N | 25 | ||||||||||||
| WhseCode | O | Tech Data warehouse identifier. For a complete list of Tech Data’s logistic centers, refer
to the Warehouse Codes heading found in the Order submit section of this document. • ResponseVersion of 1.4 or higher |
A/N | 2 | ||||||||||||
| Qty | O |
Quantity of item in the warehouse.
|
N | 15 | ||||||||||||
| TotalOnOrderQty | O | The total number on order for the warehouse. • ResponseVersion of 1.3 or higher |
N | 12 | ||||||||||||
| OnOrderQty | O | The earliest Expected-To-Arrive quantity for the warehouse. Is a sub-set of TotalOnOrderQty. • ResponseVersion of 1.3 or higher |
N | 10 | ||||||||||||
| OnOrderETADate | O | The earliest Expected-To-Arrive date for the warehouse. (format mm/dd/yy) • ResponseVersion of 1.3 or higher |
A/N | 8 | ||||||||||||
| ErrorInfo | ||||||||||||||||
| RefIDQual3 | O | A fixed value of ‘1Q’ | A/N | 2 | ||||||||||||
| RefID3 | O | A fixed value of ‘0’ | N | 1 | ||||||||||||
| ErrorDesc | O | Error description | A/N | 250 | ||||||||||||
| Summary | ||||||||||||||||
| NbrOfSegments | R | Obsolete, disregard this value |
| 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. |
| ©2005 Tech Data Corporation. All Rights Reserved. |
|
Tech Data proprietary and confidential |
