Transcription
Verizon Logistics 855 Implementation GuideANSI Version 4010855 Purchase Order AcknowledgementEDI Implementation GuideTrading Partner EditionANSI Version 4010January 21, 2002
Verizon Logistics 855 Implementation GuideANSI Version 4010855 Purchase Order AcknowledgmentPRFunctional Group ID Introduction:This Standard contains the format and establishes the data contents of the Purchase Order AcknowledgmentTransaction Set (855) for use within the context of VERIZON Logistics's Electronic Data Interchange (EDI)environment. The seller uses this transaction set to provide VERIZON Logistics with an acknowledgment to theiroriginal purchase order. VERIZON Logistics uses a three-way check to match the purchase order acknowledgmentwith the original purchase order; the purchase order number, the line item number, and the buyer's part number. Thepurchase order acknowledgment is also used to advise VERIZON Logistics that the merchandise has or will beshipped as requested, or to notify them of any quantity, price or shipping changes so that potential problems can beprevented prior to shipping or K050060300N1320330Pos.No.Seg.ID010PO1Baseline Item DataM1030PO3Additional Item DetailO25270ACKO1NameTransaction Set HeaderMax.Use1M1REFBeginning Segment for Purchase OrderAcknowledgmentReference IdentificationO 1PERAdministrative Communications ContactO3NameO1N3Address InformationO2N4Geographic LocationO1LOOP ID - N1LoopRepeatNotes andComments200Detail:MReq.Des.NameLOOP ID - PO1Max.UseLOOP ID - ACKMust UseLoopRepeat100000Notes andCommentsn1104Line Item Transaction TotalsO1030SETransaction Set TrailerM1NameLOOP ID - CTTMax.UseLoopRepeatNotes andComments12n202/07/02
376543210LEVELMST1MBAK1OREF 11MSE1Verizon Logistics 855 Implementation GuideANSI Version 401002/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.ST01MST02ST Transaction Set Header010HeadingMandatory1To indicate the start of a transaction set and to assign a control number1The transaction set identifier (ST01) is used by the translation routines of theinterchange partners to select the appropriate transaction set definition (e.g., 850selects the Purchase Order Transaction Set and the 810 selects the InvoiceTransaction Set).Example: ST*855*0012 Data Element SummaryDataElement NameAttributes143Transaction Set Identifier CodeM ID 3/3Code uniquely identifying a Transaction Set855Purchase Order Acknowledgment329Transaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setThe data interchange control number must be identical to the same dataelement in the associated transaction set trailer, SE02.402/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic K04BAK07Must UseBAK09BAK Beginning Segment for Purchase Order Acknowledgment020HeadingMandatory1To indicate the beginning of the Purchase Order Acknowledgment Transaction Set andtransmit identifying numbers and 0943**19990428 3!Data Element SummaryDataElement NameAttributes353Transaction Set Purpose CodeM ID 2/2Code identifying purpose of transaction set00Original587Acknowledgment TypeM ID 2/2Code specifying the type of acknowledgmentACAcknowledge - With Detail and ChangeADAcknowledge - With Detail, No ChangeAEAcknowledge - With Exception Detail Only324Purchase Order NumberM AN 1/22Identifying number for Purchase Order assigned by the orderer/purchaser373Purchase Order DateM DT 8/8Date expressed as CCYYMMDDThe date assigned by the purchaser to the purchase order.367Contract NumberO AN 1/30Contract numberVendor's Reference Number373Acknowledgment DateO DT 8/8Date expressed as CCYYMMDDThe date assigned by the sender to the acknowledgment.502/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.REF01MREF02REF03REF Reference Identification050HeadingOptional 1To specify identifying information1REF04 contains data relating to the value cited in REF02.Example: REF*L1*3920394930203*GENERAL PURPOSE!Data Element SummaryDataElement NameAttributes128Reference Identification QualifierM ID 2/3Code qualifying the Reference IdentificationL1Letters or Notes127Reference IdentificationM AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification Qualifier"PUR" Purchasing Information352DescriptionO AN 1/60A free-form description to clarify the related data elements and their content602/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.PER01PER02PER Administrative Communications Contact060HeadingOptional3To identify the buyer to whom this communication should be directedExample: PER*OC*ARTHUR JONES Data Element SummaryDataElement NameAttributes366Contact Function CodeM ID 2/2Code identifying the major duty or responsibility of the person or group namedOCOrder Contact93NameO AN 1/30Free-form nameVERIZON Logistics buyer's name sent on the corresponding purchase order.702/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.N101N102N103N104N1 Name300N1OptionalHeadingOptional1To identify the ship to location's name and code1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is required.1 The Identification Code in element N104 is maintained by VERIZON Logistics.Example: N1*ST*VERIZON WAREHOUSE*92*5464613 Data Element SummaryDataElement NameAttributes98Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualSTShip To93NameX AN 1/30Free-form nameShip to name identified on the corresponding purchase order.66Identification Code QualifierX ID 1/2Code designating the system/method of code structure used for IdentificationCode (67)92Assigned by Buyer or Buyer's Agent67Identification CodeX AN 2/10Code identifying a party or other codeShip to location code identified on the corresponding purchase order.802/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.N301N302N3 Address Information320N1OptionalHeadingOptional2To specify the address of the ship to location.Example: N3*PO BOX 123*157 WEST 57TH STREET Data Element SummaryDataElement Name166Address InformationAddress informationFirst address line of the ship to location.166Address InformationAddress informationSecond address line of the ship to location.9AttributesM AN 1/30OAN 1/3002/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:Ref.Des.N401N402N403N4 Geographic Location330N1OptionalHeadingOptional1To specify the city, state and zip of the ship to location.Example: N4*CINCINNATI*OH*43017 Data Element SummaryDataElement NameAttributes19City NameO AN 2/19Free-form text for city nameCity in which the ship to location is located.156State or Province CodeO ID 2/2Code (Standard State/Province) as defined by appropriate government agencyState in which the ship to location is located.116Postal CodeO ID 3/9Code defining international postal zone code excluding punctuation and blanks(zip code for United States)Zip Code in which the ship to location is located.1002/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Notes:MRef.Des.N101N102N1 Name300N1OptionalHeadingOptional1To identify the ship from location's name and code1 At least one of N102 or N103 is required.Example: N1*SF*VENDOR WAREHOUSEData Element SummaryDataElement NameAttributes98Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualSFShip From93NameX AN 1/30Free-form nameShip from name.VENDOR WAREHOUSE1102/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.N301N302N3 Address Information320N1OptionalHeadingOptional2To specify the address of the ship from location.Example: N3*PO BOX 123*157 WEST 57 STREET Data Element SummaryDataElement Name166Address InformationAddress informationFirst address line of the ship from location.PO BOX 123166Address InformationAddress informationSecond address line of the ship from location.157 WEST 57 STREET12AttributesM AN 1/30OAN 1/3002/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:Ref.Des.N401N402N403N4 Geographic Location330N1OptionalHeadingOptional1To specify the city, state and zip of the ship from location.Example: N4*CINCINNATI*OH*43017 Data Element SummaryDataElement NameAttributes19City NameO AN 2/19Free-form text for city nameCity in which the ship from location is located.CINCINNATI156State or Province CodeO ID 2/2Code (Standard State/Province) as defined by appropriate government agencyState in which the ship from location is located.OH116Postal CodeO ID 3/9Code defining international postal zone code excluding punctuation and blanks(zip code for United States)Zip Code in which the ship from location is located.430171302/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:PO1 Baseline Item Data010PO1MandatoryDetailMandatory1To specify the line item data from the original purchase order1 If PO103 is present, then PO102 is required.2 If PO105 is present, then PO104 is required.3 If either PO106 or PO107 is present, then the other is required.4 If either PO108 or PO109 is present, then the other is required.5 If either PO110 or PO111 is present, then the other is required.1The purchase order line item detail segment is required for VERIZON Logistics'sprocessing. This segment should contain the original information on the purchaseorder that is being acknowledged.2 See the Data Element Dictionary for a complete list of IDs available for the Unit orBasis for Measurement Code.3 VERIZON Logistics recommends the Buyer's Item Number 'IN' be sent in positionsPO106 - PO107.4 VERIZON Logistics recommends the Vender's Item Number 'VN' be sent inpositions PO108 - PO109.5 VERIZON Logistics recommends the UPC Code 'UP' be sent in positions PO110 PO111.VERIZON Logistics requires the Buyer's Part Number (ID Code 'BP') be transmitted ineach PO1 segment. Without this product ID, VERIZON Logistics cannot match thePurchase Order Acknowledgment with the original Purchase 297990 PO1*AAA849*100*DP*100.00*PD*BP*ASSEMBLY*VN*BRAND ORLABEL*UP*CUST12345!MRef.Des.PO101Must UsePO102PO103PO104Data Element SummaryDataElement NameAttributes350Purchase Order Line NumberM AN 1/11Alphanumeric characters assigned for differentiation within a transaction setThe line item identification from the original purchase order. VERIZONLogistics must have the original line item number from the PO to match thePOA with the PO.330Quantity OrderedX R 1/10Quantity orderedThe quantity ordered on the original purchase order.355Unit or Basis for Measurement CodeO ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenThe unit of measure code from the original purchase order.Refer to 004010 Data Element Dictionary for acceptable code values.212Unit PriceX R 1/13Price per unit of product, service, commodity, etc.The unit price of material from the original purchase order.The price is sent with a decimal point only when needed, e.g. 15.95 would be1402/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010PO105639Must UsePO106235Must UsePO107234PO108235PO109234PO110235PO111234sent as "15.95", and 29.00 would be sent as "29".Maximum of seven whole digits and five decimal places.Basis of Unit Price CodeO ID 2/2Code identifying the type of unit price for an itemThe unit price basis from the original purchase order.Note: this value should be equivalent to the unit of measure basis.Refer to 004010 Data Element Dictionary for acceptable code values.Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)VERIZON Logistics recommends sending the Buyer's Part Number (BP) inPO106.BPBuyer's Part NumberProduct/Service IDX AN 1/30Identifying number for a product or serviceVERIZON Logistics's Part Number (associated to code 'BP' in PO106) orderedon the original purchase order.Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)VERIZON Logistics recommends sending the Vendor's (Seller's) Item Number(VN) in PO108.VNVendor's (Seller's) Item NumberProduct/Service IDX AN 1/30Identifying number for a product or serviceVendor's item number (associated to code 'VN' in PO108) ordered on theoriginal purchase order.Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)VERIZON Logistics recommends sending the UPC Code (UP) in PO110.UPU.P.C. Consumer Package Code (1-5-5-1)Product/Service IDX AN 1/30Identifying number for a product or serviceUPC Code (associated to code 'UP' in PO110) identifying this product.1502/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic 6MPO307PO3 Additional Item Detail030PO1MandatoryDetailOptional25To specify changes to the original purchase order line item price, unit of measure and/orquantity.1 If PO304 is present, then PO305 is required.2 If PO306 is present, then PO307 is required.1This segment should contain price and/or quantity changes to the baseline data (PO1segment). Some examples of price/quantity variations are: price in different unitsfrom the PO1 segment, price changes by date, or price changes by quantity (breakand ta Element SummaryDataElement NameAttributes371Change Reason CodeM ID 2/2Code specifying the reason for price or quantity changeQOQuantity OrderedQTQuantity Price BreakUMUnit of Measure DifferenceUPUnit Price212Unit PriceO R 1/14Price per unit of product, service, commodity, etc.New unit price of material.Used when PO301 'QT' or 'UP'.The price is sent with a decimal point only when needed, e.g. 15.95 would besent as "15.95", and 29.00 would be sent as "29".Maximum of eight whole digits and five decimal places.639Basis of Unit Price CodeX ID 2/2Code identifying the type of unit price for an itemNew Unit Price Basis associated to the New Unit Price identified in PO304.Used when PO301 'QT' or 'UP'.Note: The new unit price basis should be equivalent to the new unit of measurebasis.Refer to 004010 Data Element Dictionary for acceptable code values.380QuantityM R 1/10Numeric value of quantity355Unit or Basis for Measurement CodeM ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenThe new measurement code associated to the new quantity in PO306.Refer to 004010 Data Element Dictionary for acceptable code values.1602/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic ACK Line Item Acknowledgment270ACKOptional (Must Use)DetailOptional (Must Use)1To acknowledge the line item status, it's promise ship date, a part number change, asubstituted item or an item's backorder status.1 If ACK04 is present, then ACK05 is required.2 If either ACK02 or ACK03 is present, then the other is required.3 If either ACK07 or ACK08 is present, then the other is required.1 VERIZON Logistics recommends sending the Promise Ship Date in 79*19990712!ACK*IC***079*19990712**VN*BRAND OR 990712**VN*BRAND OR LABEL!Data Element SummaryDataElement NameAttributes668Line Item Status CodeM ID 2/2Code specifying the action taken by the seller on a line item requested by thebuyerBPItem Accepted - Partial Shipment, Partial BackorderedDRItem Accepted - Date RescheduledIAItem AcceptedIBItem BackorderedICItem Accepted - Changes Made(Part Number Change only)IDItem DeletedIHItem on HoldISItem Accepted - Substitution Made380QuantityX R 1/10Numeric value of quantityBackordered QuantityUsed when ACK01 'BP' or 'IB'355Unit or Basis for Measurement CodeX ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenUnit of measure associated to the backorder quantity in ACK02.Used when ACK01 'BP' or 'IB'Refer to 004010 Data Element Dictionary for acceptable code values.374Date/Time QualifierO ID 3/3Code specifying type of date or time, or both date and timeTo indicate the type of date.Used when ACK01 'BP', 'DR', 'IA', 'IB', 'IC', 'IH', or 'IS'1702/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010ACK05373ACK07235ACK08234079Promised for ShipmentDateX DT 8/8Date expressed as CCYYMMDDThe promised ship date of the item being acknowledged.Used when ACK01 'BP', 'DR', 'IA', 'IB', 'IC', 'IH', or 'IS'Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Used when ACK01 'IC' or 'IS'VNVendor's (Seller's) Item NumberProduct/Service IDX AN 1/30Identifying number for a product or serviceThe changed or substituted vendor part number.Used when ACK01 'IC' or 'IS'1802/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.CTT01CTT Transaction Totals010CTTOptionalSummaryOptional1To transmit a hash total for a specific element in the transaction set1This segment is intended to provide hash totals used to validate the transaction forcompleteness and correctness.Example: CTT*2 Data Element SummaryDataElement NameAttributes354Number of Line ItemsM N0 1/6Total number of line items in the transaction setCount of Purchase Order Line Items (PO1 segments) included in thistransaction.1902/07/02
Verizon Logistics 855 Implementation GuideANSI Version 4010Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:MRef.Des.SE01MSE02SE Transaction Set Trailer030SummaryMandatory1To indicate the end of the transaction set and provide the count of the transmittedsegments (including the beginning (ST) and ending (SE) segments)1 SE is the last segment of each transaction set.Example: SE*20*0012 Data Element SummaryDataElement NameAttributes96Number of Included SegmentsM N0 1/10Total number of segments included in a transaction set including ST and SEsegments329Transaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setThe data interchange control number must be identical to the same dataelement in the associated transaction set header, ST02.2002/07/02
855 Purchase Order Acknowledgement EDI Implementation Guide Trading Partner Edition ANSI Version 4010 January 21, 2002 . Verizon Logistics 855 Implementation Guide . Transaction Set (855) for use within the context of VERIZON Logistics's Electronic Data Interchange (EDI) environment. The seller uses this transaction set to provide VERIZON .
