Transcription
Purchase Order - 850850 Purchase Order v4030X12/V4030/850Version: 1.1 FinalAuthor:Publication:Modified:PepBoys850 4030 v1 1FINAL.ecsInovisApril 1, 200806/30/20081Ver 1.1
Purchase Order - 850Revision HistoryDateApril 1, 2008Version1.0June 30, 20081.1PepBoys850 4030 v1 1FINAL.ecsRevisionInitial PublicationAdded BEG06Added explanatory notesfor special orders.2Approved ByDiane PizzarelliDiane PizzarelliVer 1.1
Purchase Order - 850850Purchase OrderFunctional Group POThis 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 transactionset can be used to provide for customary and established business and industry practice relative to the placement ofpurchase orders for goods and services. This transaction set should not be used to convey purchase order changesor purchase order acknowledgment information.User Note:PLEASE NOTE THAT IN 4030 THE ISA11 NO LONGER CONTAINS THE INTERCHANGE CONTROLSTANDARDS IDENTIFIER. IT IS NOW USED TO IDENTIFY THE REPETITION EFPER1300ITD1500DTMLOOP ID - N13100N13200N23300N33400N43600PERSegment NameInterchange Control HeaderFunctional Group HeaderTransaction Set HeaderBeginning Segment forPurchase OrderReference IdentificationAdministrativeCommunications ContactTerms of Sale/DeferredTerms of SaleDate/Time ReferenceReqMMMMMax Use1111RepeatNotesUsageMust useMust useMust useMust useOO 13UsedUsedO 1UsedO10Used200NameAdditional Name InformationAddress InformationGeographic LocationAdministrativeCommunications ContactOOOOO122 1 1ReqMax UseM1UsedUsedUsedUsedUsedDetail:PosIdLOOP ID - PO10100PO1LOOP ID - PID0500PIDSegment NameBaseline Item DataRepeat100000NotesN2/0100LN2/0100UsageMust use1000Product/Item DescriptionO1ReqMax UseOMMM1111UsedSummary:PosIdLOOP ID - CTT0100CTT0300SEGEIEASegment NameTransaction TotalsTransaction Set TrailerFunctional Group TrailerInterchange Control TrailerPepBoys850 4030 v1 t useMust useMust useVer 1.1
Purchase Order - 850Interchange Control HeaderISAPos:Max: 1Heading - MandatoryElements: 16Loop: N/AUser Option (Usage): Must useTo start and identify an interchange of zero or more functional groups and interchange-related control segmentsElement I05ISA06I06ISA07I05Element NameReqTypeMin/MaxUsageAuthorization Information QualifierMID2/2Must useDescription: Code identifying the type ofinformation in the Authorization InformationNameCode00No Authorization Information Present (No Meaningful Information in I02)Authorization InformationMAN10/10Must useDescription: Information used for additionalidentification or authorization of theinterchange sender or the data in theinterchange; the type of information is set bythe Authorization Information Qualifier (I01)Security Information QualifierMID2/2Must useDescription: Code identifying the type ofinformation in the Security InformationNameCode00No Security Information Present (No Meaningful Information in I04)Security InformationMAN10/10Must useDescription: This is used for identifying thesecurity information about the interchangesender or the data in the interchange; thetype of information is set by the SecurityInformation Qualifier (I03)Interchange ID QualifierMID2/2Must useDescription: Code indicating thesystem/method of code structure used todesignate the sender or receiver ID elementbeing qualifiedCodeName01Duns (Dun & Bradstreet)ZZMutually DefinedInterchange Sender IDMAN15/15Must useDescription: Identification code published bythe sender for other parties to use as thereceiver ID to route data to them; the senderalways codes this value in the sender IDelementUser Note: Inovis Test: CLPEPBOYSPep Boys Test: 007914401TProduction: 007914401Interchange ID QualifierDescription: Code indicating thesystem/method of code structure used toPepBoys850 4030 v1 1FINAL.ecs4MID2/2Must useVer 1.1
Purchase Order - 2ISA14I13ISA15I14ISA16I15designate the sender or receiver ID elementbeing qualifiedAll valid standard codes are used.Interchange Receiver IDMAN15/15Must useDescription: Identification code published bythe receiver of the data; When sending, it isused by the sender as their sending ID, thusother parties sending to them will use this asa receiving ID to route data to themInterchange DateMDT6/6Must useDescription: Date of the interchangeInterchange TimeMTM4/4Must useDescription: Time of the interchangeRepetition SeparatorM1/1Must useDescription: Type is not applicable; therepetition separator is a delimiter and not adata element; this field provides the delimiterused to separate repeated occurrences of asimple data element or a composite datastructure; this value must be different than thedata element separator, component elementseparator, and the segment terminatorInterchange Control Version NumberMID5/5Must useDescription: Code specifying the versionnumber of the interchange control segmentsNameCode00403Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1999Interchange Control NumberMN09/9Must useDescription: A control number assigned bythe interchange senderAcknowledgment RequestedMID1/1Must useDescription: Code indicating sender'srequest for an interchange acknowledgmentCodeName1Interchange Acknowledgment RequestedUsage IndicatorMID1/1Must useDescription: Code indicating whether dataenclosed by this interchange envelope is test,production or informationNameCodePProduction DataTTest DataComponent Element SeparatorM1/1Must useDescription: Type is not applicable; thecomponent element separator is a delimiterand not a data element; this field provides thedelimiter used to separate component dataelements within a composite data structure;this value must be different than the dataelement separator and the segmentterminatorPepBoys850 4030 v1 1FINAL.ecs5Ver 1.1
Purchase Order - 850Functional Group HeaderGSPos:Max: 1Heading - MandatoryElements: 8Loop: N/AUser Option (Usage): Must useTo indicate the beginning of a functional group and to provide control informationSemantics:1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element in theassociated functional group trailer, GE02.Comments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection ofsimilar transaction sets enclosed by a functional group header and a functional group trailer.Element 0628Element NameFunctional Identifier CodeDescription: Code identifying a group ofapplication related transaction setsNameCodePOPurchase Order (850)Application Sender's CodeDescription: Code identifying party sendingtransmission; codes agreed to by tradingpartnersUser Note: Inovis Test: CLPEPBOYSPep Boys Test: 007914401TProduction: 007914401Application Receiver's CodeDescription: Code identifying party receivingtransmission; codes agreed to by tradingpartnersDateDescription: Date expressed asCCYYMMDD where CC represents the firsttwo digits of the calendar yearTimeDescription: Time expressed in 24-hourclock 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 decimalseconds; decimal seconds are expressed asfollows: D tenths (0-9) and DD hundredths (00-99)Group Control NumberDescription: Assigned number originatedPepBoys850 4030 v1 1FINAL.ecs6ReqMTypeIDMin/Max2/2UsageMust useMAN2/15Must useMAN2/15Must useMDT8/8Must useMTM4/8Must useMN01/9Must useVer 1.1
Purchase Order - 850GS07455GS08480and maintained by the senderResponsible Agency CodeMID1/2Must useDescription: Code identifying the issuer ofthe standard; this code is used in conjunctionwith Data Element 480CodeNameXAccredited Standards Committee X12Version / Release / Industry Identifier CodeMAN1/12Must useDescription: Code indicating the version,release, subrelease, and industry identifier ofthe EDI standard being used, including theGS and GE segments; if code in DE455 inGS segment is X, then in DE 480 positions 13 are the version number; positions 4-6 arethe release and subrelease, level of theversion; and positions 7-12 are the industry ortrade association identifiers (optionallyassigned by user); if code in DE455 in GSsegment is T, then other formats are allowedNameCode004030Draft Standards Approved for Publication by ASC X12 Procedures ReviewBoard through October 1999PepBoys850 4030 v1 1FINAL.ecs7Ver 1.1
Purchase Order - 850Pos: 0100Max: 1Heading - MandatoryElements: 2Loop: N/ATransaction Set HeaderSTUser Option (Usage): Must useTo indicate the start of a transaction set and to assign a control numberSemantics:1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select theappropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).2. The implementation convention reference (ST03) is used by the translation routines of the interchange partnersto select the appropriate implementation convention to match the transaction set definition.Example:ST*850*001Element Summary:RefST01Id143ST02329Element NameTransaction Set Identifier CodeDescription: Code uniquely identifying aTransaction SetNameCode850Purchase OrderTransaction Set Control NumberDescription: Identifying control number thatmust be unique within the transaction setfunctional group assigned by the originator fora transaction setPepBoys850 4030 v1 1FINAL.ecs8ReqMTypeIDMin/Max3/3UsageMust useMAN4/9Must useVer 1.1
Purchase Order - 850BEG Beginning Segment forPos: 0200Max: 1Heading - MandatoryElements: 5Loop: N/APurchase OrderUser Option (Usage): Must useTo indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and datesSemantics:1. BEG05 is the date assigned by the purchaser to purchase order.Example:BEG*00*NE*N8095301**20080115 Element 67Element NameTransaction Set Purpose CodeDescription: Code identifying purpose oftransaction setCodeName00OriginalPurchase Order Type CodeDescription: Code specifying the type ofPurchase OrderNameCodeNENew OrderOSSpecial OrderPurchase Order NumberDescription: Identifying number for PurchaseOrder assigned by the orderer/purchaserDateDescription: Date expressed asCCYYMMDD where CC represents the firsttwo digits of the calendar yearContract NumberDescription: Contract numberUser Note: Pep Boys-assigned VendorNumber. Used for Special Orders only.PepBoys850 4030 v1 1FINAL.ecs9ReqMTypeIDMin/Max2/2UsageMust useMID2/2Must useMAN8/8Must useMDT8/8Must useOAN10/10UsedVer 1.1
Purchase Order - 850Pos: 0500Max: 1Heading - OptionalElements: 3Loop: N/AReference IdentificationREFUser Option (Usage): UsedTo specify identifying informationSyntax Rules:1. R0203 - At least one of REF02 or REF03 is required.Semantics:1. REF04 contains data relating to the value cited in REF02.Example:REF*IA*1234567890 REF*L1**FREE-FORM MESSAGE User Note:No REF segments will be sent for Special Orders.Element Summary:RefREF01Id128REF02127REF03352Element NameReference Identification QualifierDescription: Code qualifying the ReferenceIdentificationNameCodeIAInternal Vendor NumberL1Letters or NotesReference IdentificationDescription: Reference information asdefined for a particular Transaction Set or asspecified by the Reference IdentificationQualifierUser Note: Used for vendor numberassigned by Pep Boys (DC and Drop Shiponly) only when REF01 IADescriptionDescription: A free-form description to clarifythe related data elements and their contentUser Note: Used for free-form message onlywhen REF01 L1PepBoys850 4030 v1 1FINAL.ecs10ReqMTypeIDMin/Max2/3UsageMust useXAN1/10UsedXAN1/60UsedVer 1.1
Purchase Order - 850AdministrativeCommunications ContactPERPos: 0600Max: 3Heading - OptionalElements: 4Loop: N/AUser Option (Usage): UsedTo identify a person or office to whom administrative communications should be directedSyntax Rules:1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.Example:PER*CW*ABC SUPPLY*FX*8005551234 Element t NameContact Function CodeDescription: Code identifying the major dutyor responsibility of the person or groupnamedNameCodeCWConfirmed WithNameDescription: Free-form nameCommunication Number QualifierDescription: Code identifying the type ofcommunication numberNameCodeFXFacsimileCommunication NumberDescription: Complete communicationsnumber including country or area code whenapplicablePepBoys850 4030 v1 1FINAL.ecs11ReqMTypeIDMin/Max2/2UsageMust useOAN1/30UsedXID2/2UsedXAN1/10UsedVer 1.1
Purchase Order - 850Terms of Sale/DeferredTerms of SaleITDPos: 1300Max: 1Heading - OptionalElements: 5Loop: N/AUser Option (Usage): UsedTo specify terms of saleSyntax Rules:1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.Semantics:1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.Comments:1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the codein ITD01 is "05", then ITD06 or ITD07 is required.Example:ITD*01*3*2**60**90User Note:No ITD Segment will be sent for Special Orders.Element 386Element NameTerms Type CodeDescription: Code identifying type ofpayment termsNameCode01BasicTerms Basis Date CodeDescription: Code identifying the beginningof the terms periodCodeName3Invoice DateTerms Discount PercentDescription: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on or beforethe Terms Discount Due DateTerms Discount Days DueDescription: Number of days in the termsdiscount period by which payment is due ifterms discount is earnedTerms Net DaysDescription: Number of days until totalinvoice amount is due (discount notapplicable)PepBoys850 4030 v1 dOR1/6UsedXN01/3UsedON01/3UsedVer 1.1
Purchase Order - 850DTMPos: 1500Max: 10Heading - OptionalElements: 2Loop: N/ADate/Time ReferenceUser Option (Usage): UsedTo specify pertinent dates and timesSyntax Rules:1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.Example:DTM*002*20080120 DTM*010*20080115 DTM*938*20080229 User Note:002 - Delivery Requested Date - is used for standard orders only.010 - Requested Ship Date - is used for standard orders only.938 - Order Date - is used for special orders only.Element Summary:RefDTM01Id374DTM02373Element NameDate/Time QualifierDescription: Code specifying type of date ortime, or both date and timeNameCode002Delivery Requested010Requested Ship938OrderDateDescription: Date expressed asCCYYMMDD where CC represents the firsttwo digits of the calendar yearPepBoys850 4030 v1 1FINAL.ecs13ReqMTypeIDMin/Max3/3UsageMust useXDT8/8UsedVer 1.1
Purchase Order - 850Pos: 3100Max: 1Heading - OptionalLoop: N1Elements: 4NameN1User Option (Usage): UsedTo identify a party by type of organization, name, and codeSyntax Rules:1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.Comments:1. This segment, used alone, provides the most efficient method of providing organizational identification. Toobtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.2. N105 and N106 further define the type of entity in N101.Example:N1*ST*PEP BOYS*92*14011 Element Summary:RefN101Id98N10293N10366N10467Element NameReqEntity Identifier CodeMDescription: Code identifying anorganizational entity, a physical location,property or an individualNameCodeSTShip ToNameXDescription: Free-form nameIdentification Code QualifierXDescription: Code designating thesystem/method of code structure used forIdentification Code (67)User Note: 92 - Assigned by Buyer - used forstandard orders only.ZZ - Mutually Defined - used for specialorders only.NameCode92Assigned by Buyer or Buyer's AgentZZMutually DefinedIdentification CodeXDescription: Code identifying a party or othercodeUser Note: Pep Boys Store NumberPepBoys850 4030 v1 1FINAL.ecs14TypeIDMin/Max2/3UsageMust useAN1/60UsedID1/2UsedAN2/5UsedVer 1.1
Purchase Order - 850Additional NameInformationN2Pos: 3200Max: 2Heading - OptionalLoop: N1Elements: 1User Option (Usage): UsedTo specify additional namesExample:N2*ATLANTA DIST CNTR User Note:N2 segment not sent for special orders.Element Summary:RefN201Id93Element NameNameDescription: Free-form namePepBoys850 4030 v1 1FINAL.ecsReqM15TypeANMin/Max1/60UsageMust useVer 1.1
Purchase Order - 850Pos: 3300Max: 2Heading - OptionalLoop: N1Elements: 2Address InformationN3User Option (Usage): UsedTo specify the location of the named partyExample:N3*2640 EAST 45TH STREET Element Summary:RefN301Id166N302166Element NameAddress InformationDescription: Address informationAddress InformationDescription: Address informationPepBoys850 4030 v1 1FINAL.ecs16ReqMTypeANMin/Max1/55UsageMust useOAN1/55UsedVer 1.1
Purchase Order - 850Pos: 3400Max: 1Heading - OptionalLoop: N1Elements: 3Geographic LocationN4User Option (Usage): UsedTo specify the geographic place of the named partySyntax Rules:1. E0207 - Only one of N402 or N407 may be present.2. C0605 - If N406 is present, then N405 is required.3. C0704 - If N407 is present, then N404 is required.Comments:1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.Example:N4*LOS ANGELES*CA*90058 Element Summary:RefN401Id19N402156N403116Element NameCity NameDescription: Free-form text for city nameState or Province CodeDescription: Code (Standard State/Province)as defined by appropriate government agencyPostal CodeDescription: Code defining internationalpostal zone code excluding punctuation andblanks (zip code for United States)PepBoys850 4030 v1 edOID3/15UsedVer 1.1
Purchase Order - 850AdministrativeCommunications ContactPERPos: 3600Max: 1Heading - OptionalLoop: N1Elements: 3User Option (Usage): UsedTo identify a person or office to whom administrative communications should be directedSyntax Rules:1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.Example:PER*ZZ**TE*2155551212 PER*OC**AD*3055551234 User Note:PER01 qualifier OC and PER03 qualifier AD will be used for special orders only.Element Summary:RefPER01Id366PER03365PER04364Element NameContact Function CodeDescription: Code identifying the major dutyor responsibility of the person or groupnamedNameCodeOCOrder ContactZZMutually DefinedCommunication Number QualifierDescription: Code identifying the type ofcommunication numberNameCodeADDelivery Location PhoneTETelephoneCommunication NumberDescription: Complete communicationsnumber including country or area code whenapplicablePepBoys850 4030 v1 1FINAL.ecs18ReqMTypeIDMin/Max2/2UsageMust useXID2/2UsedXAN1/10UsedVer 1.1
Purchase Order - 850Pos: 0100Max: 1Detail - MandatoryElements: 13Loop: PO1Baseline Item DataPO1User Option (Usage): Must useTo specify basic and most frequently used line item dataSyntax Rules:1.2.3.4.5.6.7.8.9.10.11.12.C0302 - If PO103 is present, then PO102 is required.C0504 - If PO105 is present, then PO104 is required.P0607 - If either PO106 or PO107 is present, then the other is required.P0809 - If either PO108 or PO109 is present, then the other is required.P1011 - If either PO110 or PO111 is present, then the other is required.P1213 - If either PO112 or PO113 is present, then the other is required.P1415 - If either PO114 or PO115 is present, then the other is required.P1617 - If either PO116 or PO117 is present, then the other is required.P1819 - If either PO118 or PO119 is present, then the other is required.P2021 - If either PO120 or PO121 is present, then the other is required.P2223 - If either PO122 or PO123 is present, then the other is required.P2425 - If either PO124 or PO125 is present, then the other is required.Comments:1. See the Data Element Dictionary for a complete list of IDs.2. PO101 is the line item identification.3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color,Drawing No., U.P.C. No., ISBN No., Model No., or SKU.Example:Standard Order - 453 Special Order - PO1*001*1*EA*****VP*PF52***TP*UMF*MD*01 User Note:PO106/PO107 and PO110/PO111 not sent for special orders.PO112 thru PO115 not sent for standard orders.Element nt NameAssigned IdentificationDescription: Alphanumeric charactersassigned for differentiation within atransaction setQuantity OrderedDescription: Quantity orderedUnit or Basis for Measurement CodeDescription: Code specifying the units inwhich a value is being expressed, or mannerin which a measurement has been takenNameCodeEAEachProduct/Service ID QualifierDescription: Code identifying thePepBoys850 4030 v1 edOID2/2UsedXID2/2UsedVer 1.1
Purchase Order - 5PO113234PO114235PO115234type/source of the descriptive number used inProduct/Service ID (234)CodeNameBPBuyer's Part NumberProduct/Service IDXAN1/10UsedDescription: Identifying number for a productor serviceProduct/Service ID QualifierXID2/2UsedDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)NameCodeVPVendor's (Seller's) Part NumberProduct/Service IDXAN1/20UsedDescription: Identifying number for a productor serviceProduct/Service ID QualifierXID2/2UsedDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)CodeNameUKEAN/UCC - 14Description: Data structure for the 14 digit EAN.UCC (EANInternational.Uniform Code Council) Global Trade Identification Number (GTIN)Product/Service IDXAN14/14UsedDescription: Identifying number for a productor serviceProduct/Service ID QualifierXID2/2UsedDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)CodeNameTPProduct Type CodeProduct/Service IDXAN1/48UsedDescription: Identifying number for a productor serviceProduct/Service ID QualifierXID2/2UsedDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)NameCodeMDMethod of Delivery CodeProduct/Service IDXAN1/48UsedDescription: Identifying number for a productor serviceNameCode01Ships in 3 - 5 Business Days02Ships Next Business Day03Expedite - 24/48 Hour Guarantee04Two Day Air05International Ship06Your Truck07PickupPepBoys850 4030 v1 1FINAL.ecs20Ver 1.1
Purchase Order - 850Product/Item DescriptionPIDPos: 0500Max: 1Detail - OptionalLoop: PIDElements: 2User Option (Usage): UsedTo describe a product or process in coded or free-form formatSyntax Rules:1.2.3.4.5.C0403 - If PID04 is present, then PID03 is required.R0405 - At least one of PID04 or PID05 is required.C0703 - If PID07 is present, then PID03 is required.C0804 - If PID08 is present, then PID04 is required.C0905 - If PID09 is present, then PID05 is required.Semantics:1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specifiedattribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.Comments:1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then bothPID04 and PID05 are used.2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.Example:PID*F****PART DESCRIPTION Element Summary:RefPID01Id349PID05352Element NameItem Description TypeDescription: Code indicating the format of on: A free-form description to clarifythe related data elements and their contentPepBoys850 4030 v1 1FINAL.ecs21ReqMTypeIDMin/Max1/1UsageMust useXAN1/25UsedVer 1.1
Purchase Order - 850Pos: 0100Max: 1Summary - OptionalElements: 2Loop: CTTTransaction TotalsCTTUser Option (Usage): UsedTo transmit a hash total for a specific element in the transaction setSyntax Rules:1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.Comments:1. This segment is intended to provide hash totals to validate transaction completeness and correctness.Example:CTT*5*90 Element Summary:RefCTT01Id354CTT02347Element NameNumber of Line ItemsDescription: Total number of line items in thetransaction setHash TotalDescription: Sum of values of the specifieddata element. All values in the data elementwill be summed without regard to decimalpoints (explicit or implicit) or signs. Truncationwill occur on the left most digits if the sum isgreater than the maximum size of the hashtotal of the data element. Example: -.0018First occurrence of value being hashed. .18Second occurrence of value being hashed.1.8 Third occurrence of value being hashed.18.01 Fourth occurrence of value beinghashed. --------- 1855 Hash TotalUser Note: Total Quantity in Line ItemsPepBoys850 4030 v1 1FINAL.ecs22ReqMTypeN0Min/Max1/6UsageMust useOR1/10UsedVer 1.1
Purchase Order - 850Pos: 0300Max: 1Summary - MandatoryElements: 2Loop: N/ATransaction Set TrailerSEUser Option (Usage): Must useTo indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning(ST) and ending (SE) segments)Comments:1. SE is the last segment of each transaction set.Example:SE*15*001 Element Summary:RefSE01Id96SE02329Element NameNumber of Included SegmentsDescription: Total number of segmentsincluded in a transaction set including ST andSE segmentsTransaction Set Control NumberDescription: Identifying control number thatmust be unique within the transaction setfunctional group assigned by the originator fora transaction setPepBoys850 4030 v1 1FINAL.ecs23ReqMTypeN0Min/Max1/10UsageMust useMAN4/9Must useVer 1.1
Purchase Order - 850Pos:Max: 1Summary - MandatoryElements: 2Loop: N/AFunctional Group TrailerGEUser Option (Usage): Must useTo indicate the end of a functional group and to provide control informationSemantics:1. The data interchange control number GE02 in this trailer must be identical to the same data element in theassociated functional group header, GS06.Comments:1. The use of identical data interchange control numbers in the associated functional group header and trailer isdesigned to maximize functional group integrity. The control number is the same as that used in thecorresponding header.Element Summary:RefGE01Id97GE0228Element NameNumber of Transaction Sets IncludedDescription: Total number of transactionsets included in the functional group orinterchange (transmission) group terminatedby the trailer containing this data elementGroup Control NumberDescription: Assigned number originatedand maintained by the senderPepBoys850 4030 v1 1FINAL.ecs24ReqMTypeN0Min/Max1/6UsageMust useMN01/9Must useVer 1.1
Purchase Order - 850Interchange Control TrailerIEAPos:Max: 1Summary - MandatoryElements: 2Loop: N/AUser Option (Usage): Must useTo define the end of an interchange of zero or more functional groups and interchange-related control segmentsElement Summary:RefIEA01IdI16IEA02I12Element NameNumber of Included Functional GroupsDescription: A count of the number offunctional groups included in an interchangeInterchange Control NumberDescription: A control number assigned bythe interchange senderPepBoys850 4030 v1 1FINAL.ecs25ReqMTypeN0Min/Max1/5UsageMust useMN09/9Must useVer 1.1
X12/V4030/850 Version: 1.1 Final Author: Inovis Publication: April 1, 2008 Modified: 06/30/2008. Purchase Order - 850 PepBoys850_4030_v1_1FINAL.ecs 2 Ver 1.1 . 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-
