855 Purchase Order Acknowledgment

1 855 Purchase OrderAcknowledgmentX12/V4010/855 : 855 Purchase Order AcknowledgmentVersion: Final Author: EDI Department Company: D&H Distributors Publication: 8/26/2016 Modified: 8/25/2016 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) % @ [ ] _ { } # $All messages between trading partners need to meet EDI receiving an EDI message the trading party will validate the message and return a 997 sample segments and messages included in this guide use the asterisk as the data element separator.

2 Theseparators used for actual EDI transmissions will be agreed upon with each trading requires any segment reflected in this guide as mandatory (note under the usage section) to betransmitted in your documents. We will accept all valid X12 segments (By Ansi standards ) but will only process thoserequired for our business unless otherwise negotiated during your implementation8/24/2016 Purchase Order Acknowledgment - 855 Implememtation Guide 855 of Contents855 Purchase Order <PH>ISAI nterchange Control <PH>GSFunctional Group <PH>STTransaction Set <PH>BAKB eginning Segment for Purchase Order <PH>REFR eference <PH>PO1 Baseline Item <PH>ACKLine Item <PH>CTTT ransaction <PH>SETransaction Set <PH>GEFunctional Group <PH>IEAI nterchange Control <PH>.

3 Order Acknowledgment - 855 Implememtation Guide 855 Order AcknowledgmentFunctional Group=PRPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Acknowledgment transaction set (855) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to provide for customary and established business and industrypractice relative to a seller's Acknowledgment of a buyer's Purchase Order . This transaction set can also be used asnotification of a vendor generated Order . This usage advises a buyer that a vendor has or will ship merchandise asprearranged in their partnership.

4 Heading:PosIdSegment NameReqMax UseRepeatNotesUsageISAI nterchange Control HeaderM1 Must useGSFunctional Group HeaderM1 Must use010 STTransaction Set HeaderM1 Must use020 BAKB eginning Segment forPurchase OrderAcknowledgmentM1 Must use050 REFR eference IdentificationO>1 Used Detail:PosIdSegment NameReqMax UseRepeatNotesUsage LOOP ID - PO1 100000N2/010L LOOP ID - PO1 100000N2/010L 010PO1 Baseline Item DataO1 N2/010 Used LOOP ID - ACK 104 LOOP ID - ACK 104 270 ACKLine Item AcknowledgmentO1 Used Summary:PosIdSegment NameReqMax UseRepeatNotesUsage LOOP ID - CTT 1N3/010L LOOP ID - CTT 1N3/010L 010 CTTT ransaction TotalsO1 N3/010 Used030 SETransaction Set TrailerM1 Must useGEFunctional Group TrailerM1 Must useIEAI nterchange Control TrailerM1 Must use Notes: 2/010 LPO102 is is number of line items (CTT01) is the accumulation of the number of PO1 segments.

5 If used, hash total(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 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. 8/24/2016 Purchase Order Acknowledgment - 855 Implememtation Guide 855 Control HeaderPos: Max: 1 Heading - MandatoryLoop: N/AElements: 16 User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegments Element Summary: RefIdElement NameReqTypeMin/MaxUsageISA01I01 Authorization Information Qualifier Description.

6 Code to identify the type ofinformation in the AuthorizationInformation MID2/2 Must useCodeName00No Authorization Information Present (No Meaningful Information in I02) ISA02I02 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) MAN10/10 Must useISA03I03 Security Information Qualifier Description: Code to identify the type ofinformation in the Security Information MID2/2 Must useCodeName00No Security Information Present (No Meaningful Information in I04) ISA04I04 Security Information Description: This is used for identifyingthe security information about theinterchange sender or the data in theinterchange.

7 The type of information is setby the Security Information Qualifier (I03) MAN10/10 Must useISA05I05 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- D & H US08- D & H CanadaD & H Use/Samples: 01- D & H US08- D & H Canada MID2/2 Must useCodeName01 Duns (Dun & Bradstreet)08 UCC EDI Communications ID (Comm ID)12 Phone (Telephone Companies)8/24/2016 Purchase Order Acknowledgment - 855 Implememtation Guide 855 ISA06I06 Interchange Sender ID Description: Identification codepublished by the sender for other partiesto use as the receiver ID to route data tothem.

8 The sender always codes this valuein the sender ID elementD & H Use/Samples: D & H Production and Test ID's 7172557825 - Production7172557825T - Test243337024 - Canada Productioin243337024T - Canada TestingD & H Use/Samples: D & H Production and Test ID's 7172557825 - Production7172557825T - Test243337024 - Canada Productioin243337024T - Canada Testing MAN15/15 Must useISA07I05 Interchange ID Qualifier Description: Qualifier to designate thesystem/method of code structure used todesignate the sender or receiver IDelement being qualifiedD & H Use/Samples: Customer QualifierD & H Use/Samples: Customer Qualifier MID2/2 Must useISA08I07 Interchange Receiver ID Description: Identification codepublished by the receiver of the data.

9 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 themD & H Use/Samples: Receiver(Customer)IDD & H Use/Samples: Receiver(Customer)ID MAN15/15 Must useISA09I08 Interchange Date Description: Date of the interchange MDT6/6 Must useISA10I09 Interchange Time Description: Time of the interchange MTM4/4 Must useISA11I10 Interchange Control StandardsIdentifier Description: Code to identify the agencyresponsible for the control standard usedby the message that is enclosed by theinterchange header and trailer MID1/1 Must EDI Community of ASC X12, TDCC, and UCS ISA12I11 Interchange Control Version Number Description: Code specifying the versionnumber of the interchange controlsegments MID5/5 Must use8/24/2016 Purchase Order Acknowledgment - 855 Implememtation Guide 855 standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1997 ISA13I12 Interchange Control Number Description.

10 A control number assignedby the interchange sender MN09/9 Must useISA14I13 Acknowledgment Requested Description: Code sent by the sender torequest an interchange Acknowledgment (TA1) MID1/1 Must useCodeName0No Acknowledgment Requested ISA15I14 Usage Indicator Description: Code to indicate whetherdata enclosed by this interchangeenvelope is test, production or information MID1/1 Must useCodeNamePProduction DataTTest Data ISA16I15 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.