Inbound ANSI X12 850 Version 04010 - Adobe Inc.

06/09/10Purchase Order - 850Inbound ANSI X12 850 Version04010For CLP License OrderingVersion: ANSI X12 850 4010Author:Modified:CLP X12 ANSI8504010 060910.ecsAdobe EDI06/09/20101For internal use only

06/09/10Purchase Order - 850850Purchase OrderFunctional Group POThis Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for usewithin 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 MMax FREFDTMSegment NameTransaction Set HeaderBeginning Segment for PurchaseOrderCurrencyReference IdentificationReference IdentificationReference IdentificationReference IdentificationDate/Time ReferenceMMOOOO1 1 1 1 110N1NameM1LOOP ID - N1310N1NameM1LOOP ID - OP ID - ional200Mandatory200Mandatory200LOOP ID - onal Name InformationAddress InformationGeographic LocationReference IdentificationReference IdentificationAdministrative CommunicationsContactMOMMOOM122 11212 1LOOP ID - N1310320330340350350N1N2N3N4REFREFNameAdditional Name InformationAddress InformationGeographic LocationReference IdentificationReference IdentificationMOMMOM122 11212NameAdditional Name ryMandatoryOptionalMandatoryMandatory200LOOP ID - ionalMandatory200CLP X12 ANSI8504010 060910.ecs2MandatoryOptionalFor internal use only

06/09/10330340350360LOOP ID - N1310320330340350360Purchase Order - 850N3N4REFPERAddress InformationGeographic LocationReference IdentificationAdministrative CommunicationsContactMMOM2 112 1N1N2N3N4REFPERNameAdditional Name InformationAddress InformationGeographic LocationReference IdentificationAdministrative CommunicationsContactMOMMOM122 112 1ReqMax UseBaseline Item DataCurrencyReference IdentificationDate/Time ReferenceDate/Time ReferenceDate/Time ReferenceMOOMOO11 1101010NameAdditional Name InformationAddress InformationGeographic LocationReference IdentificationAdministrative CommunicationsContactMOMMOM122 1123NameAdditional Name InformationAddress InformationGeographic LocationReference IdentificationAdministrative CommunicationsContactMOMMOM122 1123ReqMax UseOOM111ReqMMMax l:PosIdLOOP ID - PO1010PO1020CUR100REF210DTM210DTM210DTMLOOP ID - N1350N1360N2370N3340N4390REF400PERLOOP ID - N1350360370340390400Segment alMandatorySummary:PosIdLOOP ID - CTT010CTT020AMT030SESegment NameTransaction TotalsMonetary AmountTransaction Set ryOptionalMandatoryNot Defined:PosIdGEIEASegment NameFunctional Group TrailerInterchange Control TrailerRepeatNotesUsageMandatoryMandatoryNotes:CLP X12 ANSI8504010 060910.ecs3For internal use only

06/09/102/010L2/0103/010L3/0103/020Purchase Order - 850PO102 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.CLP X12 ANSI8504010 060910.ecs4For internal use only

06/09/10Purchase Order - 850Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16Interchange Control HeaderISAUser Option (Usage): MandatoryTo 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 information inthe Authorization InformationCode00ISA02I02NameNo Authorization Information Present (No Meaningful Information in I02)Authorization tion: Information used for additionalidentification or authorization of the interchange senderor the data in the interchange; the type of information isset by the Authorization Information Qualifier (I01)ISA03I03Security Information QualifierDescription: Code to identify the type of information inthe Security InformationCode00ISA04I04NameNo Security Information Present (No Meaningful Information in I04)Security ion: This is used for identifying the securityinformation about the interchange sender or the data inthe interchange; the type of information is set by theSecurity Information Qualifier (I03)ISA05I05Interchange ID QualifierDescription: Qualifier to designate the system/methodof code structure used to designate the sender orreceiver ID element being qualifiedAll valid X12 codes are used.ISA06I06Interchange Sender IDDescription: Identification code published by the senderfor other parties to use as the receiver ID to route data tothem; the sender always codes this value in the senderID elementISA07I05Interchange ID QualifierDescription: Qualifier to designate the system/methodof code structure used to designate the sender orreceiver ID element being qualifiedCode16ISA08I07NameDuns Number With 4-Character SuffixInterchange Receiver IDDescription: Identification code published by theCLP X12 ANSI8504010 060910.ecs5For internal use only

06/09/10Purchase Order - 850receiver of the data; When sending, it is used by thesender as their sending ID, thus other parties sending tothem will use this as a receiving ID to route data to themISA09I08Interchange ID5/5MandatoryDescription: Date of the interchangeAdobe: Production ID : 102096559PRODTest ID: 102096559TESTISA10I09Interchange TimeDescription: Time of the interchangeISA11I10Interchange Control Standards IdentifierDescription: Code to identify the agency responsible forthe control standard used by the message that isenclosed by the interchange header and trailerAll valid X12 codes are used.ISA12I11Interchange Control Version NumberDescription: This version number covers theinterchange control segmentsCode00401ISA13I12NameDraft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997Interchange 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.ISA15I14Usage IndicatorDescription: Code to indicate whether data enclosed bythis interchange envelope is test, production orinformationCodePTISA16I15NameProduction DataTest DataComponent Element SeparatorMDescription: Type is not applicable; the componentelement separator is a delimiter and not a data element;this field provides the delimiter used to separatecomponent data elements within a composite datastructure; this value must be different than the dataelement separator and the segment terminatorCLP X12 ANSI8504010 060910.ecs6For internal use only

06/09/10Purchase Order - 850Pos:Max: 1Not Defined - MandatoryLoop: N/AElements: 8Functional Group HeaderGSUser Option (Usage): MandatoryTo indicate the beginning of a functional group and to provide control informationElement Summary:RefGS01Id479Element NameFunctional Identifier ription: Code identifying a group of applicationrelated transaction setsCodePOGS02142NamePurchase Order (850)Application 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 time asfollows: HHMM, or HHMMSS, or HHMMSSD, orHHMMSSDD, where H hours (00-23), M minutes(00-59), S integer seconds (00-59) and DD decimalseconds; decimal seconds are expressed as follows: 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 standardCodeXGS08480NameAccredited Standards Committee X12Version / Release / Industry Identifier CodeDescription: Code indicating the version, release,subrelease, and industry identifier of the EDI standardbeing used, including the GS and GE segments; if codein DE455 in GS segment is X, then in DE 480 positions1-3 are the version number; positions 4-6 are the releaseand subrelease, level of the version; and positions 7-12are the industry or trade association identifiers(optionally assigned by user); if code in DE455 in GSCLP X12 ANSI8504010 060910.ecs7For internal use only

06/09/10Purchase Order - 850segment is T, then other formats are allowedCode004010NameDraft Standards Approved for Publication by ASC X12 Procedures Review Board through October1997Semantics: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.CLP X12 ANSI8504010 060910.ecs8For internal use only

06/09/10Purchase Order - 850Pos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderSTUser Option (Usage): MandatoryTo 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 TransactionSetCode850ST02329NamePurchase OrderTransaction Set Control NumberDescription: Identifying control number that must beunique within the transaction set functional groupassigned by the originator for a transaction setCLP X12 ANSI8504010 060910.ecs9For internal use only

06/09/10Purchase Order - 850Beginning Segment for PurchaseOrderBEGPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 4User Option (Usage): MandatoryTo indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and datesEXAMPLE:Example: BEG 00 NE MH80312 20090101Element Summary:RefBEG01Id353Element NameTransaction Set Purpose oryDescription: Code identifying purpose of transaction setCode00BEG0292NameOriginalPurchase Order Type CodeDescription: Code specifying the type of PurchaseOrderCodeNESABEG03324NameNew OrderAdobe:CLP - The Purchase order referenced here is a CLP order.Stand-alone OrderAdobe:CLP - The Purchase order referenced here is a CLP order.Purchase Order NumberMAN1/22MandatoryMDT8/8MandatoryDescription: Identifying number for Purchase Orderassigned by the orderer/purchaserAdobe: The maximum PO length for Adobe's back officeis 20 characters. PO numbers exceeding 20 characterswill be truncated by Adobe's back office system to thefirst 20 characters read.BEG05373DateDescription: Date expressed as CCYYMMDDCLP X12 ANSI8504010 060910.ecs10For internal use only

06/09/10Purchase Order - 850Pos: 040Max: 1Heading - MandatoryLoop: N/AElements: 2CurrencyCURUser Option (Usage): MandatoryTo 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 organizational entity, aphysical location, property or an individualCodeSECUR02100NameSelling PartyCurrency CodeDescription: Code (Standard ISO) for country in whosecurrency the charges are specifiedCLP X12 ANSI8504010 060910.ecs11For internal use only