855 Purchase Order Acknowledgment - Insight

Transcription

855 Purchase OrderAcknowledgmentX12/V4010/855 : 855 Purchase Order AcknowledgmentVersion: 2.0 FinalAuthor:Modified:Insight Direct USA, Inc.4/23/2021

4/23/2021Purchase Order Acknowledgment - 855855Purchase 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.Not Defined:PosIdISAGSSegment NameInterchange Control HeaderFunctional Group HeaderReqMMMax Use11RepeatNotesUsageMust useMust usePos010020IdSTBAKReqMMMax Use11RepeatNotesUsageMust useMust use040CURSegment NameTransaction Set HeaderBeginning Segment forPurchase OrderAcknowledgmentCurrencyO1ReqMax UseO1Heading:UsedDetail:PosIdSegment NameLOOP ID - PO1010PO1Baseline Item DataLOOP ID - ACK270ACKLine Item AcknowledgmentRepeat100000NotesN2/010LUsageMust use104O1ReqMax UseOM11ReqMMMax Use11N2/270Must useNotesN3/010LUsageSummary:PosIdLOOP ID - CTT010CTT030SESegment NameTransaction TotalsTransaction Set TrailerRepeat1UsedMust useNot Defined:PosIdGEIEAInsight 855 ver2.1.ecsSegment NameFunctional Group TrailerInterchange Control Trailer1RepeatNotesUsageMust useMust useFor internal use only

4/23/2021Purchase Order Acknowledgment - 855Interchange Control HeaderISAPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegmentsElement Summary:RefISA01IdI01Element NameAuthorization Information QualifierReqMTypeIDMin/Max2/2UsageMust useDescription: Code to identify the type of information in the Authorization InformationCode List Summary (Total Codes: 7, Included: 1)CodeName00No Authorization Information Present (No Meaningful Information in I02)ISA02I02Authorization InformationMAN10/10Must useDescription: Information used for additional identification or authorization of the interchangesender or the data in the interchange; the type of information is set by the AuthorizationInformation Qualifier (I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationCode List Summary (Total Codes: 2, Included: 1)CodeName00No Security Information Present (No Meaningful Information in I04)ISA04I04Security InformationMAN10/10Must useDescription: This is used for identifying the security information about the interchangesender or the data in the interchange; the type of information is set by the SecurityInformation Qualifier (I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedAll valid standard codes are used. (Total Codes: 38)ISA06I06Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as thereceiver ID to route data to them; the sender always codes this value in the sender IDelementISA07I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedCode List Summary (Total Codes: 38, Included: 2)CodeName01Duns (Dun & Bradstreet)Insight Note:Insight Test ID Qualifier12Phone (Telephone Companies)Insight Note:Insight Production ID QualifierISA08I07Insight 855 ver2.1.ecsInterchange Receiver IDM2AN15/15Must useFor internal use only

4/23/2021Purchase Order Acknowledgment - 855Description: Identification code published by the receiver of the data; When sending, it isused by the sender as their sending ID, thus other parties sending to them will use this as areceiving ID to route data to themInsight Note: Test ID: 6309246701TProduction ID: 6309246701ISA09I08Interchange DateMDT6/6Must useMTM4/4Must useMID1/1Must useDescription: Date of the interchangeISA10I09Interchange TimeDescription: Time of the interchangeISA11I10Interchange Control Standards IdentifierDescription: Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerAll valid standard codes are used. (Total Codes: 1)ISA12I11Interchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsCode List Summary (Total Codes: 14, Included: 1)CodeName00401Draft Standards for Trial Use Approved for Publication by ASC X12Procedures Review Board through October 1997ISA13I12Interchange Control NumberMN09/9Must useDescription: A control number assigned by the interchange senderISA14I13Acknowledgment RequestedMID1/1Must useDescription: Code sent by the sender to request an interchange acknowledgment (TA1)All valid standard codes are used. (Total Codes: 2)ISA15I14Usage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test,production or informationCode List Summary (Total Codes: 3, Included: 2)CodeNamePProduction DataTTest DataISA16I15Component Element SeparatorM1/1Must useDescription: Type is not applicable; the component element separator is a delimiter and nota data element; this field provides the delimiter used to separate component data elementswithin a composite data structure; this value must be different than the data elementseparator and the segment terminatorInsight 855 ver2.1.ecs3For internal use only

4/23/2021Purchase Order Acknowledgment - 855Functional Group HeaderGSPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 8User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control informationElement Summary:RefGS01Id479Element NameFunctional Identifier CodeReqMTypeIDMin/Max2/2UsageMust useDescription: Code identifying a group of application related transaction setsCode List Summary (Total Codes: 240, Included: 1)CodeNamePRPurchase Order Acknowledgement (855)GS02142Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by tradingpartnersGS03124Application Receiver's CodeMAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by tradingpartnersInsight Note: Test ID: 6309246701TProduction ID: 6309246701GS04373DateMDT8/8Must useMTM4/8Must useDescription: Date expressed as CCYYMMDDGS05337TimeDescription: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integerseconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99)GS0628Group Control NumberMN01/9Must useDescription: Assigned number originated and maintained by the senderGS07455Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer of the standard; this code is used in conjunctionwith Data Element 480Code List Summary (Total Codes: 2, Included: 1)CodeNameXAccredited Standards Committee X12GS08480Version / Release / Industry IdentifierCodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of theEDI standard being used, including the GS and GE segments; if code in DE455 in GSsegment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are therelease and subrelease, level of the version; and positions 7-12 are the industry or tradeassociation identifiers (optionally assigned by user); if code in DE455 in GS segment is T,then other formats are allowedCode List Summary (Total Codes: 39, Included: 1)CodeName004010Draft Standards Approved for Publication by ASC X12 Procedures ReviewBoard through October 1997Insight 855 ver2.1.ecs4For internal use only

4/23/2021STPurchase Order Acknowledgment - 855Pos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderUser Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control numberElement Summary:RefST01Id143Element NameTransaction Set Identifier CodeReqMTypeIDMin/Max3/3UsageMust use4/9Must useDescription: Code uniquely identifying a Transaction SetCode List Summary (Total Codes: 298, Included: 1)CodeName855Purchase Order AcknowledgmentST02329Transaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setInsight 855 ver2.1.ecs5For internal use only

4/23/2021Purchase Order Acknowledgment - 855BAK Beginning Segment forPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 6Purchase OrderAcknowledgmentUser Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifyingnumbers and datesElement Summary:RefBAK01Id353Element NameTransaction Set Purpose CodeReqMTypeIDMin/Max2/2UsageMust use2/2Must use1/22Must useDescription: Code identifying purpose of transaction setCode List Summary (Total Codes: 65, Included: 1)CodeName00OriginalBAK02587Acknowledgment TypeMIDDescription: Code specifying the type of acknowledgmentCode List Summary (Total Codes: 15, Included: 3)CodeNameACAcknowledge - With Detail and ChangeADAcknowledge - With Detail, No ChangeRDReject with DetailBAK03324Purchase Order NumberMANDescription: Identifying number for Purchase Order assigned by the orderer/purchaserInsight Note: Insight Purchase Order NumberBAK04373DateMDT8/8Must useOAN1/30UsedDescription: Date expressed as CCYYMMDDInsight Note: Insight Purchase Order DateBAK08127Reference IdentificationDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierInsight Note: Vendor Sales Order NumberBAK09373DateODT8/8UsedDescription: Date expressed as 23456*20040425Insight 855 ver2.1.ecs6For internal use only

4/23/2021Purchase Order Acknowledgment - 855Pos: 040Max: 1Heading - OptionalLoop: N/AElements: 2CUR CurrencyUser Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transactionElement Summary:RefCUR01Id98Element NameEntity Identifier CodeReqMTypeIDMin/Max2/3UsageMust useDescription: Code identifying an organizational entity, a physical location, property or anindividualCode List Summary (Total Codes: 1312, Included: 1)CodeNameBYBuying Party (Purchaser)CUR02100Currency CodeMID3/3Must useDescription: Code (Standard ISO) for country in whose currency the charges are specifiedExample:CUR*BY*USDInsight 855 ver2.1.ecs7For internal use only

4/23/2021PO1Purchase Order Acknowledgment - 855Pos: 010Max: 1Detail - OptionalLoop: PO1Elements: 9Baseline Item DataUser Option (Usage): Must usePurpose: To specify basic and most frequently used line item dataElement Summary:RefPO101Id350Element NameAssigned IdentificationReqOTypeANMin/Max1/20UsageMust useDescription: Alphanumeric characters assigned for differentiation within a transaction setInsight Note: This is the line item number from the original Purchase Order. This numbermust match the line item number on the original purchase order. If the orderwas not sent via EDI and you are returning the 855 EDI you must number theline item 00010, 00020 00030 etc.PO102330Quantity OrderedXR1/15UsedDescription: Quantity orderedInsight Note: This must equal the quantity from the original purchase order line.PO103355Unit or Basis for Measurement CodeOID2/2UsedDescription: Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenAll valid standard codes are used. (Total Codes: 794)PO104212Unit PriceXR1/17Used2/2Used2/2UsedDescription: Price per unit of product, service, commodity, etc.Insight Note: This is the price the vendor is charging Insight.PO105639Basis of Unit Price CodeOIDDescription: Code identifying the type of unit price for an itemAll valid standard codes are used. (Total Codes: 91)PO106235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Code List Summary (Total Codes: 477, Included: 1)CodeNameBPBuyer's Part NumberPO107234Product/Service IDXAN1/48Used2/2UsedDescription: Identifying number for a product or servicePO108235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Code List Summary (Total Codes: 477, Included: 1)CodeNameVPVendor's (Seller's) Part NumberPO109234Product/Service IDXAN1/48UsedDescription: Identifying number for a product or 3*VP*777777723Insight 855 ver2.1.ecs8For internal use only

4/23/2021Purchase Order Acknowledgment - 855ACK Line Item AcknowledgmentPos: 270Max: 1Detail - OptionalLoop: ACKElements: 5User Option (Usage): Must usePurpose: To acknowledge the ordered quantities and specify the ready date for a specific line itemElement Summary:RefACK01Id668Element NameLine Item Status CodeReqMTypeIDMin/Max2/2UsageMust useDescription: Code specifying the action taken by the seller on a line item requested by thebuyerInsight Note: See examples below to determine how to use the various code combinationsinthis segment.Code List Summary (Total Codes: 26, Included: 3)CodeNameIAItem AcceptedIBItem BackorderedIRItem RejectedACK02380QuantityXR1/15UsedDescription: Numeric value of quantityInsight Note: The sum of ACK02 elements must equal the corresponding quantity in thePO102.ACK03355Unit or Basis for Measurement CodeXID2/2UsedDescription: Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenCode List Summary (Total Codes: 794, Included: 1)CodeNameEAEachACK04374Date/Time QualifierOID3/3UsedDescription: Code specifying type of date or time, or both date and timeCode List Summary (Total Codes: 1112, Included: 2)CodeName055ConfirmedInsight Note:Used with ACK01 value IA. This is the confirmed ship date.068Current Schedule ShipInsight Note:Used with ACK01 value IB. This is the date the shipment is expected toship.ACK05373DateXDT8/8UsedDescription: Date expressed as CCYYMMDDInsight Note:Line item changes (IC) are not accepted via EDI. Please contact the buyer before making any changes to theInsight PO.Example:Example: Original PO line was for a quantity of 7.Line Item Accepted as is - no changes:ACK*IA*7*EA*055*20060425Insight 855 ver2.1.ecs9For internal use only

4/23/2021Purchase Order Acknowledgment - 855Line Item Rejected:The quantity in ACK02 must equal the quantity from the original purchase order line.ACK*IR*7*EALine Item Fully Backordered:The quantity in ACK02 must equal the quantity from the original purchase order line.ACK*IB*7*EA*068*20060505Line Item Partially Backordered:If an item has been partially accepted and the remainder has been backordered, we would expect an ACKsegment for the quantity accepted (ACK*IA) and another ACK segment for the quantity Backordered (ACK*IB).For Example: The original PO contained a line item which asked for a quantity of 7. Of that 7, only 3 could beshipped and 4 went on backorder. The following should be 519Insight 855 ver2.1.ecs10For internal use only

4/23/2021CTTPurchase Order Acknowledgment - 855Pos: 010Max: 1Summary - OptionalLoop: CTTElements: 1Transaction TotalsUser Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction setElement Summary:RefCTT01Id354Element NameNumber of Line ItemsReqMTypeN0Min/Max1/6UsageMust useDescription: Total number of line items in the transaction setExample: CTT*1Insight 855 ver2.1.ecs11For internal use only

4/23/2021Purchase Order Acknowledgment - 855Pos: 030Max: 1Summary - MandatoryLoop: N/AElements: 2Transaction Set TrailerSEUser 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:RefSE01Id96Element NameNumber of Included SegmentsReqMTypeN0Min/Max1/10UsageMust useDescription: Total number of segments included in a transaction set including ST and SEsegmentsSE02329Transaction Set Control NumberMAN4/9Must useDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setInsight 855 ver2.1.ecs12For internal use only

4/23/2021Purchase Order Acknowledgment - 855Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 2Functional Group TrailerGEUser Option (Usage): Must usePurpose: To indicate the end of a functional group and to provide control informationElement Summary:RefGE01Id97Element NameNumber of Transaction Sets IncludedReqMTypeN0Min/Max1/6UsageMust useDescription: Total number of transaction sets included in the functional group orinterchange (transmission) group terminated by the trailer containing this data elementGE0228Group Control NumberMN01/9Must useDescription: Assigned number originated and maintained by the senderInsight 855 ver2.1.ecs13For internal use only

4/23/2021Purchase Order Acknowledgment - 855Interchange Control TrailerIEAPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 2User Option (Usage): Must usePurpose: To define the end of an interchange of zero or more functional groups and interchange-related controlsegmentsElement Summary:RefIEA01IdI16Element NameNumber of Included Functional GroupsReqMTypeN0Min/Max1/5UsageMust useDescription: A count of the number of functional groups included in an interchangeIEA02I12Interchange Control NumberMN09/9Must useDescription: A control number assigned by the interchange senderInsight 855 ver2.1.ecs14For internal use only

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