850 Purchase Order...Purchase Order - 850 ImplememtationGuide850v0.ecs 1 X12V4010 850Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format

850 Purchase OrderX12/V4010/850 : 850 Purchase Order

Version: 1.0 Final

Company: D&H Distributors Publication: 1/28/2015 Modified: 7/18/2019 Current: 7/18/2019

NotesEDI notesThe EDI messages use UTF8/Unicode characters and the field data is limited to the following characters:A through Z (upper or lowercase) (non-English characters are not permitted)0 through 9! “ & ’ ( ) / + , - . : ; = (space) % @ [ ] _ { } # $AllAll messages between trading partners need to meet EDI validation.Upon receiving an EDI message the trading party will validate the message and return a 997 FunctionalAcknowledgment.The sample segments and messages included in this guide use the asterisk as the data element separator. Theseparators used for actual EDI transmissions will be agreed upon with each trading partner.

Shipment of orders is expressly conditioned upon vendor's acceptance the terms defined by the executed PurchaseAgreement between the parties, or by the terms linked below, if no such agreement exists: US Terms and Conditions (https://www.dandh.com/docs/vendor/termsandconditions.pdf) CA Terms and Conditions (https://www.dandh.ca/docs/vendor/termsandconditions.pdf)

Shipment of orders must comply with the current D&H Vendor Guide – Domestic Supplier (“Routing Guide”). Failureto comply will subject vendor to the D&H Non-Compliance Penalties, detailed on page 13 of Routing Guide, linkedbelow: US Routing Guide: (https://www.dandh.com/docs/vendor/US-DomesticSupplierRoutingGuide.pdf) CA Routing Guide: (https://www.dandh.ca/docs/vendor/CA-DomesticSupplierRoutingGuide.pdf)

Purchase Order - 850

ImplememtationGuide850v0.ecs i X12V4010

Table of Contents850 Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BEG Beginning Segment for Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ITD Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N9 Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MSG Message Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO1 Baseline Item Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AMT Monetary Amount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 6. . . . . 8. . . . . 9. . . . 10. . . . 11. . . . 12. . . . 14. . . . 16. . . . 17. . . . 19. . . . 20. . . . 21. . . . 23. . . . 24. . . . 25. . . . 26. . . . 27. . . . 29. . . . 31. . . . 32. . . . 33. . . . 34. . . . 35. . . . 36. . . . 37. . . . 38


ImplememtationGuide850v0.ecs 1 X12V4010

850 Purchase OrderFunctional Group=PO

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to provide for customary and established business and industry practice relative to theplacement of purchase orders for goods and services. This transaction set should not be used to convey purchaseorder changes or purchase order acknowledgment information.

Not Defined:Pos Id Segment Name Req Max Use Repeat Notes Usage

ISA Interchange Control Header M 1 Must useGS Functional Group Header M 1 Must use

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BEG Beginning Segment for

Purchase OrderM 1 Must use

050 REF Reference Identification O >1 Must use060 PER Administrative

Communications ContactO 3 Must use

080 FOB F.O.B. Related Instructions O >1 Must use130 ITD Terms of Sale/Deferred

Terms of SaleO >1 Must use

150 DTM Date/Time Reference O 10 N1/150 Must use240 TD5 Carrier Details (Routing

Sequence/Transit Time)O 12 Must use

LOOP ID - N9 1000 LOOP ID - N9 1000

295 N9 Reference Identification O 1 Used300 MSG Message Text O 1000 Used

LOOP ID - N1 200 LOOP ID - N1 200

310 N1 Name O 1 Must use320 N2 Additional Name

InformationO 2 Used

330 N3 Address Information O 2 Must use340 N4 Geographic Location O >1 Must use350 REF Reference Identification O 12 Used360 PER Administrative

Communications ContactO >1 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - PO1 100000 N2/010L LOOP ID - PO1 100000 N2/010L

010 PO1 Baseline Item Data M 1 N2/010 Must use LOOP ID - PID 1000 LOOP ID - PID 1000

050 PID Product/Item Description O 1 Must use100 REF Reference Identification O >1 Used


Pos Id Segment Name Req Max Use Repeat Notes Usage


210 DTM Date/Time Reference O 10 N2/210 Must use

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - CTT 1 N3/010L LOOP ID - CTT 1 N3/010L

010 CTT Transaction Totals O 1 N3/010 Must use020 AMT Monetary Amount O 1 N3/020 Must use030 SE Transaction Set Trailer M 1 Must use

GE Functional Group Trailer M 1 Must useIEA Interchange Control Trailer M 1 Must use

Notes: 1/150 DTM01 Changed from 010 to 037 4/10/20162/010L PO102 is required.2/010 PO102 is required.2/210 DTM01 Changed From 002 to 037 4/10/20163/010L The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.3/010 The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.3/020 If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction

amount as calculated by the sender.



ISA Interchange Control Header Pos: Max: 1Not Defined - Mandatory

Loop: N/A Elements: 16

User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegments

Element Summary: Ref Id Element Name Req Type Min/Max UsageISA01 I01 Authorization Information Qualifier

Description: Code to identify the type ofinformation in the AuthorizationInformation

M ID 2/2 Must use

CodeList Summary (Total Codes: 7, Included: 1)Code Name00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information

Description: Information used foradditional identification or authorization ofthe interchange sender or the data in theinterchange; the type of information is setby the Authorization Information Qualifier(I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier

Description: Code to identify the type ofinformation in the Security Information

M ID 2/2 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information

Description: This is used for identifyingthe security information about theinterchange sender or the data in theinterchange; the type of information is setby the Security Information Qualifier (I03)

M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier

Description: Qualifier to designate thesystem/method of code structure used todesignate the sender or receiver IDelement being qualifiedD&H Use/Samples: 01-US08-Canada

D&H Use/Samples: 01-US08-Canada

M ID 2/2 Must use

CodeList Summary (Total Codes: 38, Included: 2)



Code Name01 Duns (Dun & Bradstreet)08 UCC EDI Communications ID (Comm ID)

ISA06 I06 Interchange Sender ID

Description: Identification codepublished by the sender for other partiesto use as the receiver ID to route data tothem; the sender always codes this valuein the sender ID elementD&H Use/Samples: 007911209- Production007911209T- Test243337024- Canada243337024- Canada Testing

D&H Use/Samples: 007911209- Production007911209T- Test243337024- Canada243337024- Canada Testing

M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier

Description: Qualifier to designate thesystem/method of code structure used todesignate the sender or receiver IDelement being qualified

M ID 2/2 Must use

CodeList Summary (Total Codes: 38, Included: 4)Code Name01 Duns (Dun & Bradstreet)08 UCC EDI Communications ID (Comm ID)12 Phone (Telephone Companies)ZZ Mutually Defined

ISA08 I07 Interchange Receiver ID

Description: Identification codepublished by the receiver of the data;When sending, it is used by the sender astheir sending ID, thus other partiessending to them will use this as areceiving ID to route data to them

M AN 15/15 Must use

ISA09 I08 Interchange Date

Description: Date of the interchange

M DT 6/6 Must use

ISA10 I09 Interchange Time

Description: Time of the interchange

M TM 4/4 Must use

ISA11 I10 Interchange Control StandardsIdentifier

Description: Code to identify the agencyresponsible for the control standard usedby the message that is enclosed by theinterchange header and trailer

M ID 1/1 Must use

CodeList Summary (Total Codes: 1, Included: 1)Code NameU U.S. EDI Community of ASC X12, TDCC, and UCS



ISA12 I11 Interchange Control Version Number

Description: Code specifying the versionnumber of the interchange controlsegments

M ID 5/5 Must use

CodeList Summary (Total Codes: 14, Included: 1)Code Name00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1997

ISA13 I12 Interchange Control Number

Description: A control number assignedby the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested

Description: Code sent by the sender torequest an interchange acknowledgment(TA1)

M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name0 No Acknowledgment Requested

ISA15 I14 Usage Indicator

Description: Code to indicate whetherdata enclosed by this interchangeenvelope is test, production or information

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 2)Code NameP Production DataT Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; thecomponent element separator is adelimiter and not a data element; this fieldprovides the delimiter used to separatecomponent data elements within acomposite data structure; this value mustbe different than the data elementseparator and the segment terminatorD&H Use/Samples: >D&H Use/Samples: >

M 1/1 Must use

D&H Use/Samples:D&H Use/Samples:ISA*00* *00* *01*007911209 *99*999999999 *160229*1715*U*00401*000001999*0*P*>ISA*00* *00* *01*007911209 *99*999999999 *160229*1715*U*00401*000001999*0*P*>



GS Functional Group Header Pos: Max: 1Not Defined - Mandatory


User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/Max UsageGS01 479 Functional Identifier Code

Description: Code identifying a group ofapplication related transaction sets

M ID 2/2 Must use

CodeList Summary (Total Codes: 240, Included: 1)Code NamePO Purchase Order (850)

GS02 142 Application Sender's Code

Description: Code identifying partysending transmission; codes agreed to bytrading partnersD&H Use/Samples: 007911209- Production007911209T- Test243337024- Canada243337024- Canada Testing

D&H Use/Samples: 007911209- Production007911209T- Test243337024- Canada243337024- Canada Testing

M AN 2/15 Must use

GS03 124 Application Receiver's Code

Description: Code identifying partyreceiving transmission; codes agreed toby trading partners

M AN 2/15 Must use

GS04 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

GS05 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

M TM 4/8 Must use

GS06 28 Group Control Number

Description: Assigned number originatedand maintained by the sender

M N0 1/9 Must use

GS07 455 Responsible Agency Code

M ID 1/2 Must use


Ref Id Element Name Req Type Min/Max Usage


Description: Code identifying the issuerof the standard; this code is used inconjunction with Data Element 480

CodeList Summary (Total Codes: 2, Included: 1)Code NameX Accredited Standards Committee X12

GS08 480 Version / Release / Industry IdentifierCode

Description: Code indicating the version,release, subrelease, and industryidentifier of the EDI standard being used,including the GS and GE segments; ifcode in DE455 in GS segment is X, thenin DE 480 positions 1-3 are the versionnumber; positions 4-6 are the release andsubrelease, level of the version; andpositions 7-12 are the industry or tradeassociation identifiers (optionally assignedby user); if code in DE455 in GS segmentis T, then other formats are allowed

M AN 1/12 Must use

CodeList Summary (Total Codes: 39, Included: 1)Code Name004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board

through October 1997

Semantics: 1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element in the

associated functional group trailer, GE02.

Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of

similar transaction sets enclosed by a functional group header and a functional group trailer.

D&H Use/Samples:D&H Use/Samples:GS*PO*007911209*999999999*20160229*1715*1999*X*004010GS*PO*007911209*999999999*20160229*1715*1999*X*004010



ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory


User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name850 Purchase Order

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

D&H Use/Samples:D&H Use/Samples:ST*850*0054ST*850*0054



BEG Beginning Segment forPurchase Order

Pos: 020 Max: 1Heading - Mandatory


User Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers anddates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBEG01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 1)Code Name00 Original

BEG02 92 Purchase Order Type Code

Description: Code specifying the type ofPurchase Order

M ID 2/2 Must use

CodeList Summary (Total Codes: 69, Included: 2)Code NameDS DropshipSA Stand-alone Order

BEG03 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaser

M AN 1/22 Must use

BEG05 373 Date


M DT 8/8 Must use

Semantics: 1. BEG05 is the date assigned by the purchaser to purchase order.

D&H Use/Samples:D&H Use/Samples:BEG*00*SA*919844L**20160229BEG*00*SA*919844L**20160229



REF Reference Identification Pos: 050 Max: >1Heading - Optional


User Option (Usage): Must usePurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameIA Internal Vendor Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

D&H Use/Samples:D&H Use/Samples:REF*IA*27778REF*IA*27778



PER AdministrativeCommunications Contact

Pos: 060 Max: 3Heading - Optional


User Option (Usage): Must usePurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 1)Code NameEA EDI Coordinator

PER02 93 Name

Description: Free-form name

O AN 1/60 Must use

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

X ID 2/2 Must use

CodeList Summary (Total Codes: 40, Included: 1)Code NameEM Electronic Mail

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

X AN 1/80 Must use

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

D&H Use/Samples:D&H Use/Samples:PER*EA*EDI Support*EM*[email protected] PER*EA*EDI Support*EM*[email protected]



FOB F.O.B. Related Instructions Pos: 080 Max: >1Heading - Optional


User Option (Usage): Must usePurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 3)Code NameCC CollectPE Prepaid and Summary BillPP Prepaid (by Seller)

FOB02 309 Location Qualifier

Description: Code identifying type oflocation

X ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 2)Code NameDE Destination (Shipping)OR Origin (Shipping Point)

FOB04 334 Transportation Terms Qualifier Code

Description: Code identifying the sourceof the transportation terms

O ID 2/2 Used

CodeList Summary (Total Codes: 3, Included: 1)Code Name01 Incoterms

FOB05 335 Transportation Terms Code

Description: Code identifying the tradeterms which apply to the shipmenttransportation responsibility

X ID 3/3 Used

CodeList Summary (Total Codes: 25, Included: 2)Code NameCIP Carriage and Insurance Paid To

Description: Seller pays cost and freight to named port of destination; buyerassumes all risk of damage or loss and additional costs incurred once goods aredelivered on board the vessel; these risks are assumed by the buyer when thegoods pass over the rail of the ship at the port of shipment; seller must procure (i.e.contract and pay for) marine insurance against the buyer's risk of loss or damageduring carriage; seller must in addition procure (i.e. contract and pay for) cargoinsurance against the buyer's risk of loss or damage to the goods during carriage

DDP Delivered Duty Paid


Code Name


Description: Seller bears costs and risks involved in bringing goods to the namedplace in the country of importation including duties, taxes, and other official chargespayable upon import

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.2. C0405 - If FOB04 is present, then FOB05 is required.3. C0706 - If FOB07 is present, then FOB06 is required.4. C0809 - If FOB08 is present, then FOB09 is required.

Semantics: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying transportation responsibility location.3. FOB06 is the code specifying the title passage location.4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the

location specified in FOB02/FOB03 and FOB06/FOB07.

D&H Use/Samples:D&H Use/Samples:FOB*PP*DEFOB*CC***01*CIPFOB*PP*DEFOB*CC***01*CIP



ITD Terms of Sale/Deferred Termsof Sale

Pos: 130 Max: >1Heading - Optional


User Option (Usage): Must usePurpose: To specify terms of sale

Element Summary: Ref Id Element Name Req Type Min/Max UsageITD01 336 Terms Type Code

Description: Code identifying type ofpayment terms

O ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)Code Name01 Basic02 End of Month (EOM)

ITD02 333 Terms Basis Date Code

Description: Code identifying thebeginning of the terms period

O ID 1/2 Must use

CodeList Summary (Total Codes: 17, Included: 1)Code Name3 Invoice Date

ITD03 338 Terms Discount Percent

Description: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on orbefore the Terms Discount Due Date

O R 1/6 Used

ITD05 351 Terms Discount Days Due

Description: Number of days in the termsdiscount period by which payment is dueif terms discount is earned

X N0 1/3 Used

ITD07 386 Terms Net Days

Description: Number of days until totalinvoice amount is due (discount notapplicable)

O N0 1/3 Used

ITD12 352 Description

Description: A free-form description toclarify the related data elements and theircontent

O AN 1/80 Must use

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.



Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code

in ITD01 is "05", then ITD06 or ITD07 is required.

D&H Use/Samples:D&H Use/Samples:ITD*02*3*0.01**10**20*****.01%10 Net 20ITD*02*3*0.01**10**20*****.01%10 Net 20

D&H Use/Samples 2:D&H Use/Samples 2:License Usage: Optional SegmentLicense Usage: Optional Segment



DTM Date/Time Reference Pos: 150 Max: 10Heading - Optional


User Option (Usage): Must usePurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 1)Code Name037 Ship Not Before

DTM02 373 Date


X DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

D&H Use/Samples:D&H Use/Samples:DTM*037*20160229 Note Changed- 4/10/2016 from qualifer 010 to 037

DTM*037*20160229 Note Changed- 4/10/2016 from qualifer 010 to 037



TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 240 Max: 12Heading - Optional


User Option (Usage): Must usePurpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD501 133 Routing Sequence Code

Description: Code describing therelationship of a carrier to a specificshipment movement

O ID 1/2 Must use

CodeList Summary (Total Codes: 23, Included: 1)Code NameB Origin/Delivery Carrier (Any Mode)

TD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

X ID 1/2 Must use

CodeList Summary (Total Codes: 215, Included: 1)Code Name93 Code assigned by the organization originating the transaction set

TD503 67 Identification Code

Description: Code identifying a party orother code

X AN 2/80 Must use

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.2. C0203 - If TD502 is present, then TD503 is required.3. C0708 - If TD507 is present, then TD508 is required.4. C1011 - If TD510 is present, then TD511 is required.5. C1312 - If TD513 is present, then TD512 is required.6. C1413 - If TD514 is present, then TD513 is required.7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 1. TD515 is the country where the service is to be performed.

Comments: 1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier

within the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.

D&H Use/Samples:D&H Use/Samples:



TD5*B*93*CarrierNameTD5*B*93*CarrierName

D&H Use/Samples 2:D&H Use/Samples 2:License PO Optional SegmentLicense PO Optional Segment



N9 Reference Identification Pos: 295 Max: 1Heading - Optional

Loop: N9 Elements: 2

User Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification Qualifier

Element Summary: Ref Id Element Name Req Type Min/Max UsageN901 128 Reference Identification Qualifier


M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameZZ Mutually Defined

N903 369 Free-form Description

Description: Free-form descriptive text

X AN 1/45 Must use

Syntax Rules: 1. R0203 - At least one of N902 or N903 is required.2. C0605 - If N906 is present, then N905 is required.

Semantics: 1. N906 reflects the time zone which the time reflects.2. N907 contains data relating to the value cited in N902.



MSG Message Text Pos: 300 Max: 1000Heading - Optional


User Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text information

Element Summary: Ref Id Element Name Req Type Min/Max UsageMSG01 933 Free-Form Message Text

Description: Free-form message text

M AN 1/264 Must use

Syntax Rules: 1. C0302 - If MSG03 is present, then MSG02 is required.

Semantics: 1. MSG03 is the number of lines to advance before printing.

Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

D&H Use/Samples:D&H Use/Samples:MSG*Message regarding purchase orderMSG*Message regarding purchase order



N1 Name Pos: 310 Max: 1Heading - Optional


User Option (Usage): Must usePurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 5)Code NameBT Bill-to-PartyDU Resale DealerEN End UserRS Receiving Facility SchedulerST Ship To

N102 93 Name


X AN 1/60 Must use

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)D&H Use/Samples: License Optional elementD&H Use/Samples: License Optional element

X ID 1/2 Must use

CodeList Summary (Total Codes: 215, Included: 1)Code Name92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code

Description: Code identifying a party orother codeD&H Use/Samples: License Order-Optional elementD&H Use/Samples: License Order-Optional element

X AN 2/80 Must use

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.



2. N105 and N106 further define the type of entity in N101.

D&H Use/Samples:D&H Use/Samples:N1*ST*D & H Distributing Co.*92*04N1*ST*D & H Distributing Co.*92*04



N2 Additional Name Information Pos: 320 Max: 2Heading - Optional


User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name


M AN 1/60 Must use

D&H Use/Samples:D&H Use/Samples:N2*D & H Distributing Location 2N2*D & H Distributing Location 2



N3 Address Information Pos: 330 Max: 2Heading - Optional


User Option (Usage): Must usePurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Used

N302 166 Address Information

Description: Address information

O AN 1/55 Used

D&H Use/Samples:D&H Use/Samples:N3*UNION SQUARE IND PK*909 KATIE COURTN3*UNION SQUARE IND PK*909 KATIE COURT



N4 Geographic Location Pos: 340 Max: >1Heading - Optional


User Option (Usage): Must usePurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Must use

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Must use

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Must use

N404 26 Country Code

Description: Code identifying the country

O ID 2/3 Must use

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

D&H Use/Samples:D&H Use/Samples:N4*Harrisburg*PA*17109*USN4*Harrisburg*PA*17109*US



REF Reference Identification Pos: 350 Max: 12Heading - Optional


User Option (Usage): UsedPurpose: To specify identifying information



M ID 2/3 Used

CodeList Summary (Total Codes: 1503, Included: 3)Code NameAH Agreement NumberCO Customer Order NumberCT Contract Number



X AN 1/30 Used



D&H Use/Samples:D&H Use/Samples:REF*CT*123456789012345REF*CO*123456789012345REF*AH*123456789012345

REF*CT*123456789012345REF*CO*123456789012345REF*AH*123456789012345



PER AdministrativeCommunications Contact

Pos: 360 Max: >1Heading - Optional


User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 2)Code NameIC Information ContactNT Notification Contact

PER02 93 Name


O AN 1/60 Must use



X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 1)Code NameTE Telephone



X AN 1/80 Used



X ID 2/2 Used




X AN 1/80 Used



X ID 2/2 Used


Ref Id Element Name Req Type Min/Max Usage





X AN 1/80 Used

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

D&H Use/Samples:D&H Use/Samples:PER*IC*Contact*TE*1234567890*EM*[email protected]*EM*[email protected]*IC*Contact*TE*1234567890*EM*[email protected]*EM*[email protected]



PO1 Baseline Item Data Pos: 010 Max: 1Detail - Mandatory

Loop: PO1 Elements: 10

User Option (Usage): Must usePurpose: To specify basic and most frequently used line item data

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO101 350 Assigned Identification

Description: Alphanumeric charactersassigned for differentiation within atransaction set

O AN 1/20 Must use

PO102 330 Quantity Ordered

Description: Quantity ordered

X R 1/15 Must use

PO103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

O ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 1)Code NameEA Each

PO104 212 Unit Price

Description: Price per unit of product,service, commodity, etc.

X R 1/17 Must use

PO106 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

X ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameVP Vendor's (Seller's) Part Number

PO107 234 Product/Service ID

Description: Identifying number for aproduct or service

X AN 1/48 Must use



X ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameBP Buyer's Part Number





X AN 1/48 Must use



X ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)Code NameUP U.P.C. Consumer Package Code (1-5-5-1)



X AN 1/48 Used

Syntax Rules: 1. C0302 - If PO103 is present, then PO102 is required.2. C0504 - If PO105 is present, then PO104 is required.3. P0607 - If either PO106 or PO107 is present, then the other is required.4. P0809 - If either PO108 or PO109 is present, then the other is required.5. P1011 - If either PO110 or PO111 is present, then the other is required.6. P1213 - If either PO112 or PO113 is present, then the other is required.7. P1415 - If either PO114 or PO115 is present, then the other is required.8. P1617 - If either PO116 or PO117 is present, then the other is required.9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required.11. P2223 - If either PO122 or PO123 is present, then the other is required.12. P2425 - If either PO124 or PO125 is present, then the other is required.

Comments: 1. See the Data Element Dictionary for a complete list of IDs.2. PO101 is the line item identification.3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

D&H Use/Samples:D&H Use/Samples:PO1*001*4*EA*103.00**VP*DES-1026G*BP*DES1026G*UP*790069246548PO1*001*4*EA*103.00**VP*DES-1026G*BP*DES1026G*UP*790069246548

D&H Use/Samples 2:D&H Use/Samples 2:You must return elements exactly used on the Purchase order Line Segment on all your inbound documentsotherwise it will fail translation causing delays processing your documents.

You must return elements exactly used on the Purchase order Line Segment on all your inbound documentsotherwise it will fail translation causing delays processing your documents.



PID Product/Item Description Pos: 050 Max: 1Detail - Optional

Loop: PID Elements: 2

User Option (Usage): Must usePurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

X AN 1/80 Must use

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

D&H Use/Samples:D&H Use/Samples:PID*F****PCI 10/100/1000MBPS AdapterPID*F****PCI 10/100/1000MBPS Adapter



REF Reference Identification Pos: 100 Max: >1Detail - Optional


User Option (Usage): UsedPurpose: To specify identifying information



M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 2)Code Name01 American Bankers Assoc. (ABA) Transit/Routing Number (Including Check Digit, 9

Digits)SE Serial Number



X AN 1/30 Used



D&H Use/Samples:D&H Use/Samples:REF*SE*1458752698532PREF*SE*1458752698532P



DTM Date/Time Reference Pos: 210 Max: 10Detail - Optional


User Option (Usage): Must usePurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 1)Code Name037 Ship Not Before

DTM02 373 Date


X DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

D&H Use/Samples:D&H Use/Samples:DTM*037*20141231 Note Changed 04/10/2016 - qualifer from 002 to 037

DTM*037*20141231 Note Changed 04/10/2016 - qualifer from 002 to 037



CTT Transaction Totals Pos: 010 Max: 1Summary - Optional

Loop: CTT Elements: 2

User Option (Usage): Must usePurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction set

M N0 1/6 Must use

CTT02 347 Hash Total

Description: Sum of values of thespecified data element. All values in thedata element will be summed withoutregard to decimal points (explicit orimplicit) or signs. Truncation will occur onthe left most digits if the sum is greaterthan the maximum size of the hash totalof the data element. Example: -.0018First occurrence of value being hashed. .18 Second occurrence of value beinghashed. 1.8 Third occurrence of valuebeing hashed. 18.01 Fourth occurrence ofvalue being hashed. --------- 1855 Hashtotal prior to truncation. 855 Hash totalafter truncation to three-digit field.

O R 1/10 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

D&H Use/Samples:D&H Use/Samples:CTT*7*47CTT*7*47



AMT Monetary Amount Pos: 020 Max: 1Summary - Optional

Loop: CTT Elements: 2

User Option (Usage): Must usePurpose: To indicate the total monetary amount

Element Summary: Ref Id Element Name Req Type Min/Max UsageAMT01 522 Amount Qualifier Code

Description: Code to qualify amount

M ID 1/3 Must use

CodeList Summary (Total Codes: 1473, Included: 1)Code NameTT Total Transaction Amount

AMT02 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

D&H Use/Samples:D&H Use/Samples:AMT*TT*12345.67AMT*TT*12345.67



SE Transaction Set Trailer Pos: 030 Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

D&H Use/Samples:D&H Use/Samples:SE*25*0001SE*25*0001



GE Functional Group Trailer Pos: Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To indicate the end of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/Max UsageGE01 97 Number of Transaction Sets Included

Description: Total number of transactionsets included in the functional group orinterchange (transmission) groupterminated by the trailer containing thisdata element

M N0 1/6 Must use

GE02 28 Group Control Number

Description: Assigned number originatedand maintained by the sender

M N0 1/9 Must use

Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the

associated functional group header, GS06.

Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is

designed to maximize functional group integrity. The control number is the same as that used in thecorresponding header.

D&H Use/Samples:D&H Use/Samples:GE*4*1999GE*4*1999



IEA Interchange Control Trailer Pos: Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To define the end of an interchange of zero or more functional groups and interchange-related controlsegments

Element Summary: Ref Id Element Name Req Type Min/Max UsageIEA01 I16 Number of Included Functional Groups

Description: A count of the number offunctional groups included in aninterchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number

Description: A control number assignedby the interchange sender

M N0 9/9 Must use

D&H Use/Samples:D&H Use/Samples:IEA*1*000001999IEA*1*000001999

D&H Use/Samples 2:D&H Use/Samples 2:Example.ISA*00* *00* *01*007911209 *01*999999999 *160229*1715*U*00401*000001999*0*P*>~GS*PO*007911209*999999999*20160229*1715*1999*X*004010~ST*850*0001~BEG*00*SA*919844L**20160229~REF*IA*27778~PER*EA*EDI Support*EM*[email protected]~FOB*CC*OR**01*CIP~ITD*02*3*0.01**10**20*****.01%10 Net 20~DTM*010*20160229~TD5*B*93*CarrierName~N9*ZZ**MSG~MSG*Message regarding purchase order~N1*ST*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*RS*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*DU*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*EN*D & H Distributing Co.*92*04~

Example.ISA*00* *00* *01*007911209 *01*999999999 *160229*1715*U*00401*000001999*0*P*>~GS*PO*007911209*999999999*20160229*1715*1999*X*004010~ST*850*0001~BEG*00*SA*919844L**20160229~REF*IA*27778~PER*EA*EDI Support*EM*[email protected]~FOB*CC*OR**01*CIP~ITD*02*3*0.01**10**20*****.01%10 Net 20~DTM*010*20160229~TD5*B*93*CarrierName~N9*ZZ**MSG~MSG*Message regarding purchase order~N1*ST*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*RS*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*DU*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*EN*D & H Distributing Co.*92*04~



N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*BT*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~REF*CT*123456789012345~REF*CO*123456789012345~REF*AH*123456789012345~PER*IC*Contact*TE*1234567890*EM*[email protected]*EM*[email protected]~PO1*001*4*EA*999.00**VP*DES-1026G*BP*DES1026G*UP*790069246548~PID*F****Switch 24-PT 10/100 + 2-PT1000~DTM*002*20141231~PO1*002*20*EA*99.00**VP*DGE-530T*BP*DGE530T*UP*790069251610~PID*F****PCI 10/100/1000MBPS Adapter~DTM*002*20141231~PO1*003*5*EA*999.00**VP*DGS-1024D*BP*DGS1024D*UP*790069268298~PID*F****Switch 24-Port 10/100/1000MBPS~REF*SE*PG15874569852DTM*002*20141231~PO1*004*5*EA*999.00**VP*DAP-2690*BP*DAP2690*UP*790069331244~PID*F****AirPremier N Dual Band PoE AP~DTM*002*20141231~PO1*005*3*EA*999.00**VP*DSR-500*BP*DSR500*UP*790069348242~PID*F****Services Router~DTM*002*20141231~PO1*006*5*EA*999.00**VP*DXE-820T*BP*DXE820T*UP*790069413933~PID*F****PCI Express 10 Gig T Dual Port~DTM*002*20141231~PO1*007*5*EA*999.00**VC*DCS-4701E*BP*DCS4701E*UP*790069417610~PID*F****Out Mini Bullet Cam~DTM*002*20141231~CTT*7*47~AMT*TT*12345.67~SE*25*0001~

N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~N1*BT*D & H Distributing Co.*92*04~N2*D & H Distributing Location 2~N3*3701 S. Minnewawa Ave~N4*Fresno*CA*93725~REF*CT*123456789012345~REF*CO*123456789012345~REF*AH*123456789012345~PER*IC*Contact*TE*1234567890*EM*[email protected]*EM*[email protected]~PO1*001*4*EA*999.00**VP*DES-1026G*BP*DES1026G*UP*790069246548~PID*F****Switch 24-PT 10/100 + 2-PT1000~DTM*002*20141231~PO1*002*20*EA*99.00**VP*DGE-530T*BP*DGE530T*UP*790069251610~PID*F****PCI 10/100/1000MBPS Adapter~DTM*002*20141231~PO1*003*5*EA*999.00**VP*DGS-1024D*BP*DGS1024D*UP*790069268298~PID*F****Switch 24-Port 10/100/1000MBPS~REF*SE*PG15874569852DTM*002*20141231~PO1*004*5*EA*999.00**VP*DAP-2690*BP*DAP2690*UP*790069331244~PID*F****AirPremier N Dual Band PoE AP~DTM*002*20141231~PO1*005*3*EA*999.00**VP*DSR-500*BP*DSR500*UP*790069348242~PID*F****Services Router~DTM*002*20141231~PO1*006*5*EA*999.00**VP*DXE-820T*BP*DXE820T*UP*790069413933~PID*F****PCI Express 10 Gig T Dual Port~DTM*002*20141231~PO1*007*5*EA*999.00**VC*DCS-4701E*BP*DCS4701E*UP*790069417610~PID*F****Out Mini Bullet Cam~DTM*002*20141231~CTT*7*47~AMT*TT*12345.67~SE*25*0001~



D&H Notes/Comments:D&H Notes/Comments:Appendix B

D&H Distribution FacilitiesThe following is a list of the distribution faculties for D&H and the expected EDImessage format for the addresses of the facilities.Katie Court – Branch 1909 Katie CourtHarrisburg, PA 17109N1*ST*D&H - HARRISBURG*92*01N3*UNION SQUARE IND PK*909 KATIE COURTN4*Harrisburg*PA*17109*US

Camp Hill (Returns) – Branch 2500 Terminal RoadCamp Hill, PA 17011N1*ST*D&H – CAMP HILL*92*02N3*500 Terminal RoadN4*Camp Hill*PA*17011*US

Canada – Branch 37975 Heritage Road, Unit 20Brampton, Ontario L6Y5X5ST*D&H - CANADA*92*03 N3*7975 Heritage Road*Unit 20 Building A N4*Brampton*ON*L6Y 5X5*CA

Fresno – Branch 43701 South Minnewawa AvenueFresno, CA 93725N1*ST*D&H - FRESNO*92*04N3*3701 S. Minnewawa AveN4*Fresno*CA*93725*US

Chicago – Branch 51455A Remington BoulevardBolingbrook, IL 90490N1*ST*D&H - CHICAGO*92*05N3*1455A Remington BoulevardN4*Bolingbrook*IL*60490*US

Atlanta/Newnan – Branch 6185 Coweta Industrial ParkwayNewnan, GA 30265N1*ST*D&H - ATLANTA*92*06N3*185 Coweta Industrial ParkwayN4*Newnan*GA*30265*US

Appendix B

D&H Distribution FacilitiesThe following is a list of the distribution faculties for D&H and the expected EDImessage format for the addresses of the facilities.Katie Court – Branch 1909 Katie CourtHarrisburg, PA 17109N1*ST*D&H - HARRISBURG*92*01N3*UNION SQUARE IND PK*909 KATIE COURTN4*Harrisburg*PA*17109*US

Camp Hill (Returns) – Branch 2500 Terminal RoadCamp Hill, PA 17011N1*ST*D&H – CAMP HILL*92*02N3*500 Terminal RoadN4*Camp Hill*PA*17011*US

Canada – Branch 37975 Heritage Road, Unit 20Brampton, Ontario L6Y5X5ST*D&H - CANADA*92*03 N3*7975 Heritage Road*Unit 20 Building A N4*Brampton*ON*L6Y 5X5*CA

Fresno – Branch 43701 South Minnewawa AvenueFresno, CA 93725N1*ST*D&H - FRESNO*92*04N3*3701 S. Minnewawa AveN4*Fresno*CA*93725*US

Chicago – Branch 51455A Remington BoulevardBolingbrook, IL 90490N1*ST*D&H - CHICAGO*92*05N3*1455A Remington BoulevardN4*Bolingbrook*IL*60490*US

Atlanta/Newnan – Branch 6185 Coweta Industrial ParkwayNewnan, GA 30265N1*ST*D&H - ATLANTA*92*06N3*185 Coweta Industrial ParkwayN4*Newnan*GA*30265*US

Documents

850 Purchase Order...Purchase Order - 850 ImplememtationGuide850v0.ecs 1 X12V4010 850Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format