HIBC-655-2006.pdf

H855V501 (005010)1January 19, 2006 Health Industry Business Communications Council eBusiness Committee 855 Purchase Order Acknowledgment Functional Group ID=PR Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order 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 industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership. Heading: Pos.Seg.Req.LoopNotes and No.IDNameDes.Max.UseRepeatComments 0050ISAInterchange Control HeaderO1 0075GSFunctional Group HeaderO1 M0100STTransaction Set HeaderM1 M0200BAKBeginning Segment for Purchase Order Acknowledgment M1 0500REFReference InformationO1 0600PERAdministrative Communications ContactO3 1500DTMDate/Time ReferenceO10 LOOP ID - N91000 2800N9Extended Reference InformationO1 2900MTXTextO1 LOOP ID - N1200 3000N1Party IdentificationO1 3100N2Additional Name InformationO2 3200N3Party LocationO2 3300N4Geographic LocationO1 3400REFReference InformationO12 3500PERAdministrative Communications ContactO1 H855V501 (005010)2January 19, 2006 Detail: Pos.Seg.Req.LoopNotes and No.IDNameDes.Max.UseRepeatComments LOOP ID - PO1100000 0100PO1Baseline Item DataO1n1 LOOP ID - PID1000 0500PIDProduct/Item DescriptionO1 1000REFReference InformationO1 1900SDQDestination QuantityO500 LOOP ID - ACK104 2700ACKLine Item AcknowledgmentO1 LOOP ID - N91000 3500N9Extended Reference InformationO1 3600MTXTextO1 LOOP ID - N1200 3700N1Party IdentificationO1 Summary: Pos.Seg.Req.LoopNotes and No.IDNameDes.Max.UseRepeatComments LOOP ID - CTT1 0100CTTTransaction TotalsO1n2 M0300SETransaction Set TrailerM1 Transaction Set Notes 1.PO102 is required. 2.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. H855V501 (005010)3January 19, 2006 Segment:ISA Interchange Control Header Position:0050 Loop: Level:Heading Usage:Optional Max Use:1 Purpose:To start and identify an interchange of zero or more functional groups and interchange- related control segments Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref.Data Des.ElementName Attributes MISA01I01Authorization Information QualifierM1 ID 2/2 Code identifying the type of information in the Authorization Information Refer to 005010 Data Element Dictionary for acceptable code values. MISA02I02Authorization InformationM1 AN 10/10 Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01) MISA03I03Security Information QualifierM1 ID 2/2 Code identifying the type of information in the Security Information Refer to 005010 Data Element Dictionary for acceptable code values. MISA04I04Security InformationM1 AN 10/10 This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) MISA05I05Interchange ID QualifierM1 ID 2/2 Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified Refer to 005010 Data Element Dictionary for acceptable code values. MISA06I06Interchange Sender IDM1 AN 15/15 Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element MISA07I05Interchange ID QualifierM1 ID 2/2 Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified Refer to 005010 Data Element Dictionary for acceptable code values. MISA08I07Interchange Receiver IDM1 AN 15/15 Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them MISA09I08Interchange DateM1 DT 6/6 Date of the interchange MISA10I09Interchange TimeM1 TM 4/4 Time of the interchange MISA11I65Repetition SeparatorM1 AN 1/1 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator MISA12I11Interchange Control Version NumberM1 ID 5/5 Code specifying the version number of the interchange control segments H855V501 (005010)4January 19, 2006 Refer to 005010 Data Element Dictionary for acceptable code values. MISA13I12Interchange Control NumberM1 N0 9/9 A control number assigned by the interchange sender MISA14I13Acknowledgment RequestedM1 ID 1/1 Code indicating sender's request for an interchange acknowledgment Refer to 005010 Data Element Dictionary for acceptable code values. MISA15I14Interchange Usage IndicatorM1 ID 1/1 Code indicating whether data enclosed by this interchange envelope is test, production or information Refer to 005010 Data Element Dictionary for acceptable code values. MISA16I15Component Element SeparatorM1 AN 1/1 Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator H855V501 (005010)5January 19, 2006 Segment:GS Functional Group Header Position:0075 Loop: Level:Heading Usage:Optional Max Use:1 Purpose:To indicate the beginning of a functional group and to provide control information Syntax Notes: Semantic Notes:1GS04 is the group date. 2GS05 is the group time. 3The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments:1A 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. Data Element Summary Ref.Data Des.ElementName Attributes MGS01479Functional Identifier CodeM1 ID 2/2 Code identifying a group of application related transaction sets Refer to 005010 Data Element Dictionary for acceptable code values. MGS02142Application Sender's CodeM1 AN 2/15 Code identifying party sending transmission; codes agreed to by trading partners MGS03124Application Receiver's CodeM1 AN 2/15 Code identifying party receiving transmission; codes agreed to by trading partners MGS04373DateM1 DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year MGS05337TimeM1 TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00- 59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) MGS0628Group Control NumberM1 N0 1/9 Assigned number originated and maintained by the sender MGS07455Responsible Agency CodeM1 ID 1/2 Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480 Refer to 005010 Data Element Dictionary for acceptable code values. MGS08480Version / Release / Industry Identifier CodeM1 AN 1/12 Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed Refer to 005010 Data Element Dictionary for acceptable code values. H855V501 (005010)6January 19, 2006 Segment:ST Transaction Set Header Position:0100 Loop: Level:Heading Usage:Mandatory Max Use:1 Purpose:To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes:1The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). 2The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08. Comments: Data Element Summary Ref.Data Des.ElementName Attributes MST01143Transaction Set Identifier CodeM1 ID 3/3 Code uniquely identifying a Transaction Set 855Purchase Order Acknowledgment MST02329Transaction Set Control NumberM1 AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set H855V501 (005010)7January 19, 2006 Segment:BAK Beginning Segment for Purchase Order Acknowledgment Position:0200 Loop: Level:Heading Usage:Mandatory Max Use:1 Purpose:To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates Syntax Notes: Semantic Notes:1BAK04 is the date assigned by the purchaser to purchase order. 2BAK08 is the seller's order number. 3BAK09 is the date assigned by the sender to the acknowledgment. Comments: Data Element Summary Ref.Data Des.ElementName Attributes MBAK01353Transaction Set Purpose CodeM1 ID 2/2 Code identifying purpose of transaction set 00Original 01Cancellation 04Change 05Replace 06Confirmation 08Status 12Not Processed 14Advance Notification 16Proposed 18Reissue 22Information Copy MBAK02587Acknowledgment TypeM1 ID 2/2 Code specifying the type of acknowledgment ACAcknowledge - With Detail and Change ADAcknowledge - With Detail, No Change AEAcknowledge - With Exception Detail Only AKAcknowledge - No Detail or Change APAcknowledge - Product Replenishment RDReject with Detail RJRejected - No Detail MBAK03324Purchase Order NumberM1 AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser MBAK04373DateM1 DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year BAK05328Release NumberO1 AN 1/30 Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction BAK06326Request Reference NumberO1 AN 1/45 Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number) BAK07367Contract NumberO1 AN 1/30 Contract number BAK08127Reference IdentificationO1 AN 1/50 H855V501 (005010)8January 19, 2006 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier BAK09373DateO1 DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year H855V501 (005010)9January 19, 2006 Segment:REF Reference Information Position:0500 Loop: Level:Heading Usage:Optional Max Use:1 Purpose:To specify identifying information Syntax Notes:1At least one of REF02 or REF03 is required. 2If either C04003 or C04004 is present, then the other is required. 3If either C04005 or C04006 is present, then the other is required. Semantic Notes:1REF04 contains data relating to the value cited in REF02. Comments: Data Element Summary Ref.Data Des.ElementName Attributes MREF01128Reference Identification QualifierM1 ID 2/3 Code qualifying the Reference Identification BKBroker's Order Number CACost Allocation Reference COCustomer Order Number CRCustomer Reference Number CTContract Number DHDrug Enforcement Administration Number DPDepartment Number MHManufacturing Order Number PDPromotion/Deal Number PRPrice Quote Number RERelease Number RQPurchase Requisition Number STStore Number VCVendor Contract Number VNVendor Order Number REF02127Reference IdentificationX1 AN 1/50 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier H855V501 (005010)10January 19, 2006 Segment:PER Administrative Communications Contact Position:0600 Loop: Level:Heading Usage:Optional Max Use:3 Purpose:To identify a person or office to whom administrative communications should be directed Syntax Notes:1If either PER03 or PER04 is present, then the other is required. 2If either PER05 or PER06 is present, then the other is required. 3If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref.Data Des.ElementName Attributes MPER01366Contact Function CodeM1 ID 2/2 Code identifying the major duty or responsibility of the person or group named PER0293NameO1 AN 1/60 Free-form name PER03365Communication Number QualifierX1 ID 2/2 Code identifying the type of communication number EAInternet Email Address Internet based electronic mail address with a structure of “ADDRESSEE DOMAIN NAME . DOMAIN NAME EXTENSION“ EMElectronic Mail FXFacsimile TETelephone URUniform Resource Locator (URL) PER04364Communication NumberX1 AN 1/256 Complete communications number including country or area code when applicable PER05365Communication Number QualifierX1 ID 2/2 Code identifying the type of communication number See PER03 for values PER06364Communication NumberX1 AN 1/256 Complete communications number including country or area code when applicable PER07365Communication Number QualifierX1 ID 2/2 Code identifying the type of communication number See PER03 for values PER08364Communication NumberX1 AN 1/256 Complete communications number including country or area code when applicable PER09443Contact Inquiry ReferenceO1 AN 1/20 Additional reference number or description to clarify a contact number H855V501 (005010)11January 19, 2006 Segment:DTM Date/Time Reference Position:1500 Loop: Level:Heading Usage:Optional Max Use:10 Purpose:To specify pertinent dates and times Syntax Notes:1At least one of DTM02 DTM03 or DTM05 is required. 2If DTM04 is present, then DTM03 is required. 3If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref.Data Des.ElementName Attributes MDTM01374Date/Time QualifierM1 ID 3/3 Code specifying type of date or time, or both date and time 002Delivery Requested 010Requested Ship 017Estimated Deliv