Inbound X12 850 Version 004010 - Adobe Inc.

Inbound X12 850 Version 004010For Ordering Shrink Wrap ProductVersion: ANSI ASC X12 850 4010Author:Company:Modified:Adobe EDI9/29/2015

9/29/2015Purchase Order - 850850Purchase OrderFunctional Group POPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850)for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary andestablished business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should notbe used to convey purchase order changes or purchase order acknowledgment information.Not Defined:PosIdISAGSSegment NameInterchange Control HeaderFunctional Group HeaderReqMMMax t NameTransaction Set HeaderBeginning Segment for PurchaseOrderCurrencyReference IdentificationDate/Time ReferenceDate/Time ReferenceReqMMMax Use11RepeatNotesUsageMandatoryMandatoryMMOO1 11010NameM1LOOP ID - N1310N1NameM1LOOP ID - N1310N1NameM1NameAdditional Name InformationAddress InformationGeographic LocationAdministrative CommunicationsContactMOMMO122 1 1ReqMax UseMO110ReqMax UseOOM111ReqMMMax Use11Heading:Pos010020040CUR050REF150DTM150DTMLOOP ID - N1310N1LOOP ID - PosIdLOOP ID - PO1010PO1210DTMSegment NameBaseline Item DataDate/Time oryOptionalSummary:PosIdLOOP ID - CTT010CTT020AMT030SESegment NameTransaction TotalsMonetary AmountTransaction Set ryOptionalMandatoryNot Defined:PosIdGEIEASegment NameFunctional Group TrailerInterchange Control TrailerSW X12 850 4010 092915.ecs1RepeatNotesUsageOptionalOptionalFor internal use only

9/29/2015Purchase Order - 850Notes:2/010L2/0103/010L3/0103/020PO102 is required.PO102 is required.The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of thevalue of quantities ordered (PO102) for each PO1 segment.The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of thevalue of quantities ordered (PO102) for each PO1 segment.If AMT is used in the summary area, then AMT01 will TT and AMT02 will indicate total transaction amount as calculated by thesender.SW X12 850 4010 092915.ecs2For internal use only

9/29/2015Purchase Order - 850Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16Interchange Control HeaderISAUser Option (Usage): OptionalPurpose: To start and identify an interchange of zero or more functional groups and interchange-related control segmentsElement Summary:RefISA01IdI01Element NameAuthorization Information tion: Code to identify the type of informationin the Authorization InformationCodeList Summary (Total Codes: 7, Included: 1)CodeName00No Authorization Information Present (No Meaningful Information in I02)ISA02I02Authorization tion: Information used for additionalidentification or authorization of the interchangesender or the data in the interchange; the type ofinformation is set by the Authorization InformationQualifier (I01)ISA03I03Security Information QualifierDescription: Code to identify the type of informationin the Security InformationCodeList Summary (Total Codes: 2, Included: 1)CodeName00No Security Information Present (No Meaningful Information in I04)ISA04I04Security ion: This is used for identifying the securityinformation about the interchange sender or the datain the interchange; the type of information is set bythe Security Information Qualifier (I03)ISA05I05Interchange ID QualifierDescription: Qualifier to designate thesystem/method of code structure used to designatethe sender or receiver ID element being qualifiedAll valid X12 codes are used. (Total Codes: 38)ISA06I06Interchange Sender IDDescription: Identification code published by thesender for other parties to use as the receiver ID toroute data to them; the sender always codes thisvalue in the sender ID elementISA07I05Interchange ID QualifierDescription: Qualifier to designate thesystem/method of code structure used to designatethe sender or receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)CodeName16Duns Number With 4-Character SuffixISA08I07Interchange Receiver IDDescription: Identification code published by thereceiver of the data; When sending, it is used by thesender as their sending ID, thus other partiesSW X12 850 4010 092915.ecs3For internal use only

9/29/2015Purchase Order - 850sending to them will use this as a receiving ID toroute data to themAdobe: Production ID : 102096559PRODTest ID: 102096559TESTISA09I08Interchange ID5/5MandatoryDescription: Date of the interchangeISA10I09Interchange TimeDescription: Time of the interchangeISA11I10Interchange Control Standards IdentifierDescription: Code to identify the agency responsiblefor the control standard used by the message that isenclosed by the interchange header and trailerAll valid X12 codes are used. (Total Codes: 1)ISA12I11Interchange Control Version NumberDescription: This version number covers theinterchange control segmentsCodeList Summary (Total Codes: 14, Included: 1)CodeName00401Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997ISA13I12Interchange Control y1/1MandatoryDescription: A control number assigned by theinterchange senderISA14I13Acknowledgment RequestedDescription: Code sent by the sender to request aninterchange acknowledgment (TA1)All valid X12 codes are used. (Total Codes: 2)ISA15I14Usage IndicatorDescription: Code to indicate whether data enclosedby this interchange envelope is test, production orinformationCodeList Summary (Total Codes: 3, Included: 2)CodeNamePProduction DataTTest DataISA16I15Component Element SeparatorMDescription: Type is not applicable; the componentelement separator is a delimiter and not a dataelement; this field provides the delimiter used toseparate component data elements within acomposite data structure; this value must be differentthan the data element separator and the segmentterminatorSW X12 850 4010 092915.ecs4For internal use only

9/29/2015Purchase Order - 850Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 8Functional Group HeaderGSUser Option (Usage): OptionalPurpose: To indicate the beginning of a functional group and to provide control informationElement Summary:RefGS01Id479Element NameFunctional Identifier ription: Code identifying a group of applicationrelated transaction setsCodeList Summary (Total Codes: 234, Included: 1)CodeNamePOPurchase Order (850)GS02142Application Sender's CodeDescription: Code identifying party sendingtransmission; codes agreed to by trading partnersGS03124Application Receiver's CodeDescription: Code identifying party receivingtransmission. Codes agreed to by trading partnersAdobe: PRODUCTION ID : 102096559PRODTEST ID : 102096559TESTGS04373DateDescription: Date expressed as CCYYMMDDGS05337TimeDescription: Time expressed in 24-hour clock timeas follows: HHMM, or HHMMSS, or HHMMSSD, orHHMMSSDD, where H hours (00-23), M minutes(00-59), S integer seconds (00-59) and DD decimal seconds; decimal seconds are expressed asfollows: D tenths (0-9) and DD hundredths(00-99)GS0628Group Control NumberDescription: Assigned number originated andmaintained by the senderGS07455Responsible Agency CodeDescription: Code used in conjunction with DataElement 480 to identify the issuer of the standardCodeList Summary (Total Codes: 2, Included: 1)CodeNameXAccredited Standards Committee X12GS08480Version / Release / Industry Identifier CodeDescription: Code indicating the version, release,subrelease, and industry identifier of the EDIstandard being used, including the GS and GEsegments; 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 ortrade association identifiers (optionally assigned byuser); if code in DE455 in GS segment is T, thenother formats are allowedSW X12 850 4010 092915.ecs5For internal use only

9/29/2015Purchase Order - 850CodeList Summary (Total Codes: 36, Included: 1)CodeName004010Draft Standards Approved for Publication by ASC X12 Procedures Review Board throughOctober 1997Semantics: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 the associated functional grouptrailer, GE02.Comments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction setsenclosed by a functional group header and a functional group trailer.SW X12 850 4010 092915.ecs6For internal use only

9/29/2015Purchase Order - 850Pos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderSTUser Option (Usage): MandatoryPurpose: To indicate the start of a transaction set and to assign a control numberEXAMPLE:Example: ST*850*130581Element Summary:RefST01Id143Element NameTransaction Set Identifier oryDescription: Code uniquely identifying a TransactionSetCodeList Summary (Total Codes: 298, Included: 1)CodeName850Purchase OrderST02329Transaction Set Control NumberDescription: Identifying control number that must beunique within the transaction set functional groupassigned by the originator for a transaction setSemantics:1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction setdefinition (e.g., 810 selects the Invoice Transaction Set).SW X12 850 4010 092915.ecs7For internal use only

9/29/2015Purchase Order - 850Beginning Segment for PurchaseOrderBEGPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 4User Option (Usage): MandatoryPurpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and datesEXAMPLE:Example: BEG*00*NE*MH80312**20150831Element Summary:RefBEG01Id353Element NameTransaction Set Purpose oryMAN1/22MandatoryMDT8/8MandatoryDescription: Code identifying purpose of transactionsetCodeList Summary (Total Codes: 65, Included: 1)CodeName00OriginalBEG0292Purchase Order Type CodeDescription: Code specifying the type of PurchaseOrderCodeList Summary (Total Codes: 70, Included: 2)CodeNameNENew OrderAdobe:Shrink WrapSAStand-alone OrderAdobe:Shrink WrapBEG03324Purchase Order NumberDescription: Identifying number for Purchase Orderassigned by the orderer/purchaserAdobe: The maximum PO length for Adobe's backoffice is 20 characters.PO numbers exceding 20 characters will betruncated by Adobe's back office system to the first20 characters read.BEG05373DateDescription: Date expressed as CCYYMMDDSemantics:1. BEG05 is the date assigned by the purchaser to purchase order.SW X12 850 4010 092915.ecs8For internal use only

9/29/2015Purchase Order - 850Pos: 040Max: 1Heading - MandatoryLoop: N/AElements: 2CurrencyCURUser Option (Usage): MandatoryPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transactionEXAMPLE:Example: CUR*SE*USDAdobe:Currency is MANDATORY and must be sent.Element Summary:RefCUR01Id98Element NameEntity Identifier oryDescription: Code identifying an organizationalentity, a physical location, property or an individualCodeList Summary (Total Codes: 1312, Included: 1)CodeNameSESelling PartyCUR02100Currency CodeDescription: Code (Standard ISO) for country inwhose currency the charges are specifiedComments:1. See Figures Appendix for examples detailing the use of the CUR segment.SW X12 850 4010 092915.ecs9For internal use only