WIXLIB

06/16/2020Purchase Order - 850KEHE DistributorsPurchase OrderEDI 850Version 5010X12/V5010/850 : 850 Purchase OrderCompany:Revised:KeHE Standard 850-PO SpecsKehe Distributos06/16/2020iKehe Distributors

06/16/2020Purchase Order - 850Table of Contents850 Purchase Order .1ISA Interchange Control Header.3GSFunctional Group Header .5STTransaction Set Header.6BEG Beginning Segment for Purchase Order .7REF Reference Identification .8PER Administrative Communications Contact .9SAC Service, Promotion, Allowance, or Charge Information . 10ITD Terms of Sale/Deferred Terms of Sale . 11DTM Date/Time Reference . 12TD5 Carrier Details (Routing Sequence/Transit Time). 13N1Name . . 14N3Address Information . 15N4Geographic Location . 16PER Administrative Communications Contact . 17PO1 Baseline Item Data . 18PID Product/Item Description. 19PO4 Item Physical Details . 20SAC Service, Promotion, Allowance, or Charge Information . 21CTT Transaction Totals . 22AMT Monetary Amount . 23SETransaction Set Trailer . 24GEFunctional Group Trailer . 25IEA Interchange Control Trailer . 26Sample DataKeHE Standard 850-PO SpecsiiKehe Distributos

06/16/2020Purchase Order - 850850Purchase OrderFunctional Group POPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase OrderTransaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can beused to provide for customary and established business and industry practice relative to the placement of purchase orders forgoods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgmentinformation.Notes:2/0100L PO102 is required.2/0100 PO102 is required.3/0100L The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) isthe sum of the value of quantities ordered (PO102) for each PO1 segment.3/0100 The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) isthe sum of the value of quantities ordered (PO102) for each PO1 segment.3/0200 If AMT is used in the summary area, then AMT01 will TT and AMT02 will indicate total transaction amount ascalculated by the sender.Not Defined:PosIdISAGSSegment NameInterchange Control HeaderFunctional Group HeaderReqMMMax Use11RepeatNotesUsageMust useMust usePage35Pos01000200IdSTBEGReqMMMax Use11RepeatNotesUsageMust useMust usePage6705000600REFPEROO1 1UsedMust use891200SACO1Must use101300ITDO1Used1115002400DTMTD5Segment NameTransaction Set HeaderBeginning Segment forPurchase OrderReference IdentificationAdministrativeCommunications ContactService, Promotion,Allowance, or ChargeInformationTerms of Sale/Deferred Termsof SaleDate/Time ReferenceCarrier Details (RoutingSequence/Transit Time)OO1012Must useMust use1213OOOO12 1 1Must useMust useMust useMust use14151617Heading:LOOP ID - N13100N13300N33400N43600PER200NameAddress InformationGeographic LocationAdministrativeCommunications ContactTable of ContentsKeHE Standard 850-PO Specs1Kehe Distributors

06/16/2020Purchase Order - 850Detail:PosIdLOOP ID - PO10100PO1LOOP ID - PID0500PID0900P04LOOP ID - SAC1300SACSegment NameBaseline Item DataReqMax UseM1Repeat100000NotesN2/010LN2/010UsagePageMust use18Must useUsed19201000Product/Item DescriptionItem Physical DetailsOO1 1Service, Promotion, Allowance, Oor Charge Information125Must use21Summary:PosIdLOOP ID - CTT0100CTT0200AMT0300SESegment NameTransaction TotalsMonetary AmountTransaction Set TrailerReqMax UseOOM111ReqMMMax Use11Repeat1NotesN3/010LN3/010N3/020UsagePageMust useMust useMust use222324UsageMust useMust usePage2526Not Defined:PosIdGEIEASegment NameFunctional Group TrailerInterchange Control TrailerRepeatNotesTable of ContentsKeHE Standard 850-PO Specs2Kehe Distributors

06/16/2020Purchase Order - 850Interchange 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 control segmentsElement Summary:RefISA01IdI01Element NameAuthorization Information QualifierReqMTypeIDMin/Max2/2UsageMust useDescription: Code to identify the type of information in the Authorization InformationCodeList 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 interchange senderor the data in the interchange; the type of information is set by the Authorization Information Qualifier(I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationCodeList 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 interchange sender or thedata in the interchange; the type of information is set by the Security Information Qualifier (I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designate the senderor receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)CodeName16Duns Number With 4-Character SuffixISA06I06Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as the receiver ID toroute data to them; the sender always codes this value in the sender ID elementKEHE Id:ISA07I050569813430000OR0054370330000Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designate the senderor receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)CodeNameDefined by Trading PartnerTable of ContentsKeHE Standard 850-PO Specs3Kehe Distributors

06/16/2020ISA08Purchase Order - 850I07Interchange Receiver IDMAN15/15Must useDescription: Identification code published by the receiver of the data; When sending, it is used by thesender as their sending ID, thus other parties sending to them will use this as a receiving ID to routedata to themISA09I08Interchange 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 the messagethat is enclosed by the interchange header and trailerAll valid standard codes are optional.Code Name Repetition SeparatorISA12I11Interchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsCodeList Summary (Total Codes: 14, Included: 1)CodeName00501Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1997ISA13I12Interchange Control NumberMN09/9Must use1/1Must useDescription: A control number assigned by the interchange senderISA14I13Acknowledgment RequestedMIDDescription: Code sent by the sender to request an interchange acknowledgment (TA1)CodeList Summary (Total Codes: 2, Included: 1)CodeName0No Acknowledgment RequestedISA15I14Usage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test, productionor informationCodeList 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 not a dataelement; this field provides the delimiter used to separate component data elements within a compositedata structure; this value must be different than the data element separator and the segment terminatorTable of ContentsKeHE Standard 850-PO Specs4Kehe Distributors

06/16/2020Purchase Order - 850Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 8Functional Group HeaderGSUser Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control informationComments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similartransaction sets enclosed by a functional group header and a functional group trailer.Element Summary:RefGS01Id479Element NameFunctional Identifier CodeReqMTypeIDMin/Max2/2UsageMust useDescription: Code identifying a group of application related transaction setsCodeList Summary (Total Codes: 240, Included: 1)CodeNamePOPurchase Order (850)GS02142Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by trading partnersKEHE Production Id:GS031240569813430000ORApplication Receiver's Code0054370330000MAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by trading partnersGS04373DateMDT8/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 integer seconds(00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) andDD hundredths (00-99)GS0628Group Control NumberMN01/9Must use1/2Must useDescription: Assigned number originated and maintained by the senderGS07455Responsible Agency CodeMIDDescription: Code identifying the issuer of the standard; this code is used in conjunction with DataElement 480CodeList Summary (Total Codes: 2, Included: 1)CodeName Accredited Standards Committee X12GS08480Version / Release / Industry Identifier CodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of the EDIstandard being used, including the GS and GE segments; if code in DE455 in GS segment is X, thenin DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level ofthe version; and positions 7-12 are the industry or trade association identifiers (optionally assigned byuser); if code in DE455 in GS segment is T, then other formats are allowedCodeList Summary (Total Codes: 39, Included: 1)CodeName005010Draft Standards Approved for Publication through October 2004Table of ContentsKeHE Standard 850-PO Specs5Kehe Distributors

06/16/2020Purchase Order - 850Pos: 0100Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderSTUser 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 useAN4/9Must useDescription: Code uniquely identifying a Transaction SetCodeList Summary (Total Codes: 298, Included: 1)CodeName850Purchase OrderST02329Transaction Set Control NumberMDescription: Identifying control number that must be unique within the transaction set functionalgroup assigned by the originator for a transaction setTable of ContentsKeHE Standard 850-PO Specs6Kehe Distributors