ANSI X12 855 in Bound 4010

CDW Corporation

June 15, 2006

ANSI X12 855 In Bound 4010

Guidelines

June 15, 2006

Revision History

Date / Number / Description
9/15/2000 / 1.0 / First Draft
06/15/2006 / 1.1 / Added Revision History and segment and element usage. Documented use of estimated delivery date.

The following pages are the guidelines for implementing the ANSI X12 855 document with CDW. The segments listed below are a subset of the 855 document. This represents all the segments that CDW is capable of receiving.

The column labeled "Usage” is used to communicate CDW’s business requirements to properly process the data.

For segments identified as "CDW Required" partners must send segments and need to follow the ANSI X12 conventions.
For the segments identified as “Used” partners must send data if there is a “CDW Note” that denotes special conditions, or may send the data if available.

Segment and Element Detail:

The column labeled “Usage” is used to communicate CDW’s business requirements to properly process the data.

For elements identified as “CDW Required” partners must send elements and need to follow the ANSI X12 conventions for conditional and paired relationships.
For elements identified as “Used” partners may send data if available or otherwise required by the ANSI X12 conventions.

The element, segment, and transaction descriptions identified by "CDW Note" or enclosed in [] illustrate CDW's business usage and interpretation.

Segment / Max. / Loop
ID / Name / Req / Use /

Repeat

Usage

(Header)
ST / Transaction Set Header / M / 1 / Required
BAK / Beginning Segment for Purchase Order Acknowledgment / M / 1 / Required
REF / Reference Numbers / O / >1 / Used
FOB / F.O.B. Related Instructions / O / >1 / Used
N1 / loop / O / Used
N1 / Name / O / 1 / Used
N3 / Address Information / O / 2 / Used
N4 / Geographic Location / O / 1 / Used
Segment / Max. / Loop
ID / Name / Req / Use /

Repeat

(Detail)
PO1 / loop / 100,000
PO1 / Baseline Item Data / O / 1 / CDW Required
REF / Reference Numbers / O / >1 / Used
DTM / Date/Time Reference / O / 10 / Used
ACK / Loop / O / 104
ACK / Line Item Acknowledgment / O / 1 / CDW Required
DTM / Date/Time Reference / O / 1 / Used
Segment / Max. / Loop
ID / Name / Req / Use /

Repeat

(Trailer)
CTT / Transactions Totals / M / 1
SE / Transaction Set Trailer / M / 1

Here is an example of an inbound 855 document:

ST~855~5730001

BAK~00~AC~1047023~20001003

FOB~FO~OR

N1~ST~CDW COMPUTER CENTERS, INC.~92~DS

PO1~000000~1~EA~9817.92~~VP~C7834A#ABA~BP~217220~UP~88698919064

ACK~IH~1~EA~~~0001059436

PO1~000000~1~EA~.01~~VP~C7834S~BP~221780

ACK~IA~1~EA~017~20060623~0001059436

DTM~068~20060616

CTT~1

SE~11~5730001

Please note that the segment terminators are not shown.

The following is a guide to the notation that is used to present the specifications:

Req - Required or Usage

CConditional

MMandatory

OOptional

XRelational

TP - Element Type

ANAlpha Numeric

DTDate, in the form of CCYYMMDD

IDIdentifier or Qualifier

NxNumeric, where ‘x’ is the number of decimal positions

RDecimal, with the decimal point included

TMTime, in the form of HHMM

Header

ST - Transaction Set Header

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max / Usage
ST01 / 143 / Transaction Set Identifier / 855 – Purchase Order Acknowledgment / M / ID / 3/3 / Used
ST02 / 329 / Transaction Set Control Number / Sequential #
(Same as SE02) / M / AN / 4/9 / Used

BAK - Beginning Segment for Purchase Order Acknowledgment

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
BAK01 / 353 / Transaction Set Purpose Code / ‘00’ – Original / M / ID / 2/2 / Used
BAK02 / 587 / Acknowledgment Type / See note / M / ID / 2/2 / CDW Req
BAK03 / 324 / Purchase Order Number / From the 850 PO / M / AN / 1/22 / CDW Req
BAK04 / 373 / Date / CCYYMMDD, purchase order date / M / DT / 8/8 / CDW Req
BAK05 / 328 / Release Number / O / AN / 1/30 / Not used
BAK07 / 367 / Contract Number / O / AN / 1/30 / Not used
BAK09 / 373 / Date / O / DT / 8/8 / Not used

CDW Note: The following BAK02 codes indicate the order was accepted without errors and will be shipped:

AT-Accepted (requested code)

AD-Acknowledged With Detail, no change

AK-Acknowledged No detail or change

AP-Acknowledged Product Replenishment

NA-No Acknowledgment Needed

CDW Note: The following BAK02 codes indicate at least one item on the order had an error and the order will not ship:

RJ-Rejected

RD-Rejected with Detail

Any other code not listed in the “accepted” codes

REF – Reference Numbers

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
REF01 / 128 / Reference Number Qualifier / Any valid code / M / ID / 2/3 / Used
REF02 / 127 / Reference Number / X / AN / 1/30 / Used
REF03 / 352 / Description / X / AN / 1/80 / Used

FOB – F.O.B. Related Instructions

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
FOB01 / 146 / Shipment Payment Method / Any valid code / M / ID / 2/2 / Used
FOB02 / 309 / Location Qualifier / Any valid code / X / ID / 1/2 / Used
FOB03 / 352 / Description / C / AN / 1/80 / Used

N1 – Name

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
N101 / 98 / Type of Organization / ‘ST’-Ship To
‘BT’-Bill To
‘VN’-Vendor
‘EN’-End User / M / ID / 2/3 / Used
N102 / 93 / Name / X / AN / 1/60 / Used
N103 / 66 / ID Code Qualifier / X / ID / 1/2 / Used
N104 / 67 / Identifying Number / X / AN / 2/80 / Used

N2 - Additional Name Information

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
N201 / 93 / Name / M / AN / 1/60 / Used
N202 / 93 / Name / O / AN / 1/60 / Used

N3 - Address Information

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
N301 / 166 / Address Information / M / AN / 1/55 / Used
N302 / 166 / Address Information / O / AN / 1/55 / Used

N4 - Geographic Location

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
N401 / 19 / City Name / O / AN / 2/30 / Used
N402 / 156 / State/Province Code / O / ID / 2/2 / Used
N403 / 116 / Postal Code / O / ID / 3/15 / Used

Detail

PO1 - Baseline Item Data

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
PO101 / 350 / Assigned Identification / From 850 PO1 / O / AN / 1/20 / Used
PO102 / 330 / Quantity Ordered / X / R / 1/15 / CDW req
PO103 / 335 / Unit of Measurement Code / O / ID / 2/2 / Used
PO104 / 212 / Unit Price / Corrected unit price / X / R / 1/17 / CDW req
PO105 / 639 / Basis of Unit Price Code / O / ID / 2/2
PO106 / 235 / Product/Service ID Qualifier / See note, required at least CDW part number / X / ID / 2/2 / CDW req
PO107 / 234 / Product/Service ID / X / AN / 1/48 / CDW req
PO108 / 235 / Product/Service ID Qualifier / X / ID / 2/2 / Used
PO109 / 234 / Product/Service ID / X / AN / 1/48 / Used
PO110 / 235 / Product/Service ID Qualifier / X / ID / 2/2 / Used
PO111 / 234 / Product/Service ID / X / AN / 1/48 / Used

CDW Note: The following product ids can be sent as required.

BP, CB = CDW’s part number

MG = manufacturer’s part number

VP, VC = vendor’s part number

UP = U.P.C. Consumer Package Code

REF - Reference Numbers

Reference

DTM – Date/Time Reference

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
DTM01 / 374 / Date/Time Qualifier / Any valid code / M / ID / 3/3 / Used
DTM02 / 373 / Date / 017 – Estimated Delivery Date 067 – Current Schedule Delivery / X / DT / 8/8 / used

ACK – Date/Time Reference

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/ Max
ACK01 / 668 / Line Item Status Code / See note / M / ID / 2/2 / CDW req
ACK02 / 380 / Quantity / X / R / 1/15 / Used
ACK03 / 355 / Unit of Measurement Code / X / AN / 2/2 / Used
ACK04 / 374 / Date/Time Qualifier / 017 – Estimated Delivery Date 067 – Current Schedule Delivery / O / ID / 3/3 / See note
ACK05 / 373 / Date / CCYYMMDD / X / DT / 8/8 / See note
ACK06 / 326 / Request Reference Number / O / AN / 1/30
ACK07 / 235 / Product/Service ID Qualifier / X / ID / 2/2 / See note
ACK08 / 234 / Product/Service ID / X / AN / 1/48 / See note

CDW Note: The following ACK01 codes indicate the line is fully accepted:

IA-Item Accepted

SP-Item Accepted Scheduled Date Pending

CDW Note: The following ACK01 codes indicate the line was rejected:

IR-Item Rejected

BP-Partial Backordered

DR-Date rescheduled

IB-Item backordered

IC-Changes made

ID-Item deleted

IE-Price pending

IF-Item on hold, incomplete description

IH-Item on hold

IP-Price change

IQ-Quantity change

IS-Item Substituted

Any code not on the “accepted” list

CDW Note: ACK07 / ACK8 can be used to include a reason code. Work with the CDW implementer to determine valid codes.

DTM – Date/Time Reference

Reference

Element / Number / Description / Qual/Def / Req / Type / Min/Max
DTM01 / 374 / Date/Time Qualifier / 017 – Estimated Delivery Date 067 – Current Schedule Delivery / M / ID / 3/3 / See note
DTM02 / 373 / Date / CCYYMMDD / X / DT / 8/8 / See note

CDW Note: An estimated delivery date is required. This can be included in either the ACK or DTM segments.

Trailer

CTT - Transaction Totals

Reference

Element / Number / Description / Qual/Def / Req / Type / Min / Max
CTT01 / 354 / Number of Line Items / Number of PO1 segments used / M / N0 / 1 / 6

SE - Transaction Set Trailer

Reference

Element / Number / Description / Qual/Def / Req / Type / Min / Max
SE01 / 96 / Segments in Transaction / ST and SE included / M / N0 / 1 / 10
SE02 / 329 / Transaction Set Control / Same as ST02 / M / AN / 4 / 9

855_I_40101