Transcription
IBX X12 4010 855 Purchase OrderAcknowledgmentSpecificationDocument Owner: Christian DruschkeProduct ManagementMarch 2015Company Public Information
Table of Contents1.Introduction 32.Purpose 33.Schema Validation 34.IBX ANSI X12 855 Purchase Order Acknowledgement 44.1General information 41.1.1ANSI X.12 Version 44.2ISA - Interchange Control Header 44.3GS - Functional Group Header 64.4ST - Transaction Set Header 74.5BAK - Beginning Segment for Purchase Order Acknowledgment 74.6CUR - Currency 94.7REF - Reference Identification 94.8FOB - F.O.B. Related Instructions 94.9ITD - Terms of Sale/Deferred Terms of Sale 114.10 CTB - Restrictions/Conditions 124.11 N9 - Extended Reference Information 124.12 N1 - Name Information 134.13 N2 - Additional Name Information 134.14 N3 - Address Information 144.15 N4 - Geographic Location 144.16 NX2 - Location ID Component 144.17 PER - Administration Communication Contact 154.18 PO1 - Baseline Item Data (Purchase Order Item Data) 154.19 CUR - Currency 164.20 CTP - Pricing Information 174.21 PID - Product/Item Description 174.22 REF - Reference Information 184.23 FOB - F.O.B. Related Instructions 18The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 1
4.24 ACK - Line Item Acknowledgment 204.25 N9 - Extended Reference Information 214.26 N1 - Name Information 224.27 N4 - Geographic Location 224.28 CTT - Transaction Totals 234.29 AMT - Monetary Amount 234.30 SE - Transaction Set Trailer 234.31 GE - Functional Group Trailer 244.32 IEA - Interchange Control Trailer 245.Example 24The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 2
1.IntroductionThe EDI (Electronic Data Interchange) Standard (X12), version (4010) and Transaction Set (855) is a globallystandardized order acknowledgement format developed by ANSI (American National Standards Institute), aprivate not-for-profit organization that oversees the creation, promulgation and use of thousands ofnorms and guidelines that directly impact businesses.This format is most commonly used in the United States. The IBX Connect platform has implementedsupport in receiving X12 4010:855 Order Acknowledgements from North American suppliers viaHttps/Post and FTP. This format support will allow suppliers to send purchase order acknowledgmentsto their customers via the IBX Connect platform without implementing mappings from their internalEDI format to XML.Like any other electronic order acknowledgment document, the ANSI X12 855 document containsinformation regarding the products/services and the quantities accepted or rejected, shipping details,payment terms, etc.Below is an example typical structure supported by the IBX Connect Platform when receiving ANSI X12855 transactions.2.PurposeThe purpose of this document is to detail the meaning and the information contained in the segmentsof the ANSI X12 format as received by the IBX Connect platform. More information regarding ANSI X124010 transaction sets can be found at http://www.disa.org. Please note publications are available at a cost.3.Schema ValidationAny ANSI X12 order response received by IBX Connect from suppliers must be valid according to the global X12schema version 4010 for order acknowledgements. Documents which do not comply with the standard ANSI X12specifications might not be processed.The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 3
4.4.11.1.1IBX ANSI X12 855 Purchase Order AcknowledgementGeneral informationANSI X.12 VersionThe IBX Connect Platform supports ANSI X.12, Version 004010.Below is a structure of the segments used by IBX Connect Platform when processing X12 855 Orderacknowledgements. The structure is complete with explanations for each segments’ elements.4.2ISA - Interchange Control HeaderThis segment starts and identifies an interchange of one or more groups or loops and their relatedsegments. This segment is ended by the IEA segment. Only one ISA -IEA control loop may be used Authorization Information Qualifier2/2Required?YesDefault: "00" “No Authorization InformationPresent”ISA02Authorization Information10/10Yes2/2Yes10/10Yes2/2YesDefault: emptyISA03Security Information QualifierDefault: "00" “No Security InformationPresent”ISA04Security InformationDefault: emptyISA05Interchange ID QualifierDefault: "ZZ" "Mutually Defined"ISA06Interchange Sender ID15/15YesISA07Interchange ID Qualifier2/2YesDefault: "ZZ" "Mutually Defined"The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 4
Other values e.g.: "01" “DUNS number"ISA08Interchange Receiver ID15/15YesISA09Interchange Date - YYMMDD6/6YesISA10Interchange Time - HHMM4/4YesISA11Repetition Separator - 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 terminator.1/1YesExample: “*”ISA12Interchange Control Version Number - Indicatesthe version of the ISA/IEA envelope5/5YesISA13ISA13 - Interchange Control Number - A controlnumber assigned by the interchange sender.May take any numeric value, but is usuallyincremented by one for each interchange sent tothe same trading partner.9/9YesISA14Acknowledgment Requested1/1Yes1/1Yes1/1YesDefault: “0”ISA15Test Indicator“T” Test“P” ProductionISA16The component element separator is a delimiterand not a data element; this field provides thedelimiter used to separate component dataelements within a composite data structure; thisvalue must be different than the data elementseparator and the segment terminatorExample: “ 45*0*T* *ZZ*SenderIDThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.*ZZ*ReceiverIDPage 5
4.3GS - Functional Group HeaderThe GS segment indicates the beginning of a functional group and provides control information. The GS segmentis ended by the GE segment. One or more GS-GE control loops may be used per transmission by the sender, butat least one is 2YesFunctional Group Header Code - Same as theGroup Type of the included Transaction SetsGS01Example: “PR” Functional code for “PurchaseOrder Acknowledgment (855)”GS02Application Sender's Code24/24YesGS03Application Receiver's Code24/24YesGS04Date - YYMMDD, or CCYYMMDD as of 40108/8YesGS05Time - HHMM4/4Yes9/9YesGS06Group Control Number - Like the ISA controlnumber, is used for audit and to detectduplicates, missing, or out of sequence groups.Most importantly, the 997 FunctionalAcknowledgement, which acts as a return receiptfor the group, references the group controlnumber. May take any numeric value so long asthere are no duplicates in the interchange, but isusually incremented by one for each group of thistype sent to the same trading partner1/1Yes5/5YesResponsible Agency Code – “X” for X12 or “T” forTDCCGS07Default: “X”Version/Release/Industry Identifier Code - Thefirst six characters specify the X12 version andrelease, while any of the last six may be used toindicate an Industry standard or ImplementationConvention reference.GS08Default: 0410*1232*163100545*X*004010 The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 6
4.4ST - Transaction Set HeaderThis segment indicates the start of a transaction set and assigns a control number. It is ended by the SE segment.Invoices may be transmitted within one ST-SE control loop, but only Invoices may be present within thismandatory Transaction Set Identifier Code - A three digitnumeric code identifying the Transaction Settype, from the Transaction Set table. Must alwaysbe “855” for order acknowledgements.3/3YesST02Transaction Set Control Number - May take anyalphanumeric value so long as there are noduplicates in the functional group. Usually startswith 0001 in each group, but there are severalother numbering schemes in common usage.4/9YesExample:4.5ST*855*0001 BAK - Beginning Segment for Purchase Order AcknowledgmentThis segment is used to indicate the beginning of the Purchase Order Acknowledgment Transaction Set and totransmit identifying numbers and Transaction Set Purpose Code - Code identifyingpurpose of transaction setSupported codes:“00” “Original”“01” “Cancellation”“04” “Change”BAK01“05” “Replace”“06” “Confirmation”“07” “Duplicate”“ZZ” “Mutually Defined”(Any other code used will be interpreted as“Original”!)The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 7
Code specifying the type of acknowledgment.Supported codesBAK02ACAcknowledge - With Detail and ChangeADAcknowledge - With Detail, No ChangeATAcceptedNANo Acknowledgment NeededRDReject with DetailRFReject with Exception Detail OnlyRJRejected - No DetailRNRejected - Not as AgreedRORejected With Counter OfferRVRejected - Violates Industry PracticesZZMutually Defined2/2Yes(Any other code used will be interpreted like“Mutually Defined”!)BAK03Purchase order number - Identifying number forPurchase Order assigned by theorderer/purchaser1/22YesBAK04Purchase order date, expressed as CCYYMMDDwhere CC represents the first two digits of thecalendar year.8/8YesBAK08Reference information as defined for a particularTransaction Set - used for reference purposes. IBXcurrently interprets this information as thedocument’s order response number. (If notprovided then the purchase order number inBAK03 will be taken also as order responsenumber!)1/80No8/8NoOrder acknowledgment issue dateBAK09Example:(If not provided then the purchase order date inBAK04 will be taken also as orderacknowledgment issue date!)BAK*07*AT*987987*20130101****1234*20130102 The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 8
4.6CUR - CurrencyThis segment is used to specify the currency (dollars, pounds, euros, etc.) used in a 2/3Yes3/3YesEntity Identifier Code - Code identifying anorganizational entity, a physical location,property or an individualCUR01Example: “SE” Selling Party"(Must be a valid code but has no impact onprocessing wihin IBX Connect!)CUR02Example:4.7Code specifying the standard ISO code forcountry in whose currency the charges arespecifiedCUR*SE*USD REF - Reference IdentificationThe REF segment is used to specify identifying information/numbers. References such as Purchase Orderreference, Contract Reference, Account numbers 30YesReference Identification Qualifier. Code qualifyingthe Reference Number.Supported codes:REF01“Q1” “Quote Number”“11” “Account Number”REF02Example:Reference Identification. Reference number oridentification number as specified by theReference Identification Qualifier.REF*11*14779413 REF*Q1*24779413 4.8FOB - F.O.B. Related InstructionsThis segment is used to specify transportation instructions relating to shipment.The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 9
nt Method of Payment Code - Codeidentifying payment terms for transportationchargesSupported codes:11Rule 11 ShipmentBPPaid by BuyerCAAdvance CollectCCCollectCDCollect on DeliveryCFCollect, Freight Credited Back toCustomerFOB01CNCost and FreightDEPer ContractDFDefined by Buyer and SellerFOFOB Port of CallHPHalf PrepaidMXMixedNCService Freight, No ChargeNRNon RevenuePAAdvance PrepaidPBCustomer Pickup/BackhaulPCPrepaid but Charged to CustomerPDPrepaid by ProcessorPEPrepaid and Summary BillPLPrepaid Local, Collect OutstatePOPrepaid OnlyPPPrepaid (by Seller)PSPaid by SellerPUPickupRCReturn Container Freight Paid byCustomerRFReturn Container Freight FreeThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 10
RSReturn Container Freight Paid by SupplierTPThird Party PayWCWeight ConditionLocation Qualifier - Code identifying type oflocationExample: “ZZ” Mutually Defined”FOB06(Must be a valid code, but has no impact onprocessing within IBX Connect!)FOB07Description – Can be used for TransportdescriptionYes, if FOB07 ermsOfDeliveryDescription free textnote**TransportDescription free text note 4.9ITD - Terms of Sale/Deferred Terms of SaleTo specify terms of 2/2No1/2No1/6No8/8No1/3NoTerms Type Code - Code identifying type ofpayment termsITD01Example:“02” “End of Month”Terms Basis Date CodeITD02Code identifying the beginning of the termsperiodTerms Discount PercentITD03Terms discount percentage, expressed as apercent, available to the purchaser if an invoice ispaid on or before the Terms Discount Due DateTerms Discount Due DateITD04ITD05Date payment is due if discount is to be earnedexpressed in format CCYYMMDD where CCrepresents the first two digits of the calendaryearTerms Discount Days DueNumber of days in the terms discount period byThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 11
which payment is due if terms discount is earnedTerms Net Due DateITD06Date when total invoice amount becomes dueexpressed in format CCYYMMDD where CCrepresents the first two digits of the calendaryear8/8No1/3No1/80No1/2NoTerms Net DaysITD07ITD12Number of days until total invoice amount is due(discount not applicable)Description - A free-form description to clarify therelated data elements and their content(Payment terms note)Payment Method Type CodeITD14Example:“AA” “Bank Draft”Example:4.10ITD*02***********Payment terms note**AA CTB - Restrictions/ConditionsThe CTB segment specifies restrictions or conditions regarding the ordering as free text with max 60 /3Yes1/60YesRestrictions/Conditions QualifierCTB01Only supported value:“OR” “Ordering”CTB02Example:DescriptionCTB*OR*This is the Order Response Header Note The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 12
4.11N1 - Name InformationThis segment is used to specify information about the buyer party, seller party, ship to party, bill to party, remitto party or ship from party. Used alone, it provides the most efficient method of providing organizationalidentification. The segment identifies a party by type of organization, name, and code.LengthElementMeaning(min/max)Entity Identifier Code.Required?YesSupported codes:“BY” ”Buying Party”“SE” “Seller”“ST” “Ship to”N101“BT” “Bill to”2/3N102Name of Entity1/60Identification Code Qualifier. Code designatingthe system/method of code structure used forIdentification CodeN103Example: “92” “Assigned by Buyer or Buyer’sAgent”N104Identification Code. Code identifying a party orother code. Usually an internal ID of the party inthe buyer’s 92*VendorID N2 - Additional Name InformationThis segment is be used only to specify additional name information. It is used if the informationcontained in N1 regarding the name of the entity is not ree-form name1/60YesExample:N2*SellerName2 N2*SellerName3 The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 13
4.13N3 - Address InformationThis segment is used to specify the location of the named party in ss Information1/55YesExample:4.14N3*SellerStreet 12 N4 - Geographic LocationThis segment is used to specify the location of the named party from N1.LengthElementMeaning(min/max)Required?N401City Name2/30NoN402State or Province Code2/2NoN403Postal Code3/15NoN404Country Code2/3NoExample:4.15N4*SellerCity*CA*12345*US NX2 - Location ID ComponentThis segment is used to define types and values of a geographic location.LengthElementMeaning(min/max)Address Component QualifierRequired?YesSupported Codes:“05” “P.O. Box Number““12” “Building Name”“20” “County”“32” “Floor”“35” “Room”NX201“53” “Postal District”2/2The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 14
NX202Address Information1/55YesExample: NX2*12*First Building 11 NX2*32*1th Floor NX2*35*1st Room 4.16PER - Administration Communication ContactThis segment is used to identify a person or office to which administrative communications should be directed.LengthElementMeaning(min/max)Contact Function CodePER01Only supported code currently:Required?Yes2/2“OC” “Order Contact”PER02Name1/60NoPER03Communication Number Qualifier – Can bespecified as ‘EM’ for email, ‘TE’ for telephone or‘FX’ for Fax2/2NoPER04Communication Number – Value according to thequalifier above1/256NoPER05Communication Number Qualifier – Can bespecified as ‘EM’ for email, ‘TE’ for telephone or‘FX’ for Fax2/2NoPER06Communication Number – Value according to thequalifier above1/256NoPER07Communication Number Qualifier – Can bespecified as ‘EM’ for email, ‘TE’ for telephone or‘FX’ for Fax2/2NoPER08Communication Number – Value according to thequalifier TE* 4681234567*EM*SellerOrderContact@seller.com*FX* 46812345674.17PO1 - Baseline Item Data (Purchase Order Item Data)This segment is mandatory and is used to specify basic and most frequently used line item data.The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 15
LengthElementMeaning(min/max)Required?Alphanumeric characters assigned fordifferentiation within a transactionsetPO101Example: “0000000001” or “1” identifying firstline item1/20NoPO102Quantity ordered1/15NoUnit of measurementNoPO103Example: “EA” “Each”2/2PO104Unit Price per 1 item1/17Product/Service ID QualifierNoNoExample:“VN” “Vendor’s / Seller’s Item Number”PO106“VP” “Vendor’s / Seller’s Part Number2/2PO107Product/Service ID (Seller’s Part Number)1/48Product / Service ID QualifierNoNoExample:PO108“BP” “Buyer’s Part Number”2/2PO109Product / Service ID (Buyer’s Part Number)1/48Product/Service ID QualifierNoNoExample:PO110“MG” “Manufacturer’s Part Number”2/2PO111Product / Service ID (Manufacturer’s 9.250000**VP*ALI0767000100*BP*G0248768*MG*0767000 100 4.18CUR - CurrencyThis segment is used to specify the currency that applies to the whole order.The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 16
LengthElementMeaning(min/max)Required?CUR01Code identifying an organizational entity, aphysical location, property or anindividual.2/3Yes3/3YesDefault: "BY" ”Buyer”CUR02Standard ISO currency codeExamples: “USD”, “EUR”Example:4.19CUR*BY*USDCTP - Pricing InformationThis segment is used to specify information about the price and quantity of the products or services in the orderif the PO1 segment is not sufficient due to the complexity of price and quantity information.LengthElementMeaning(min/max)CTP03Unit Price. Price per unit of product, service,commodity, etc.1/17CTP04Quantity: Numeric value of quantity which theUnit Price applies to.1/15NoNoComposite Unit of Measure. UoM Code which theQuantity in CTP04 refers to.NoCTP05Example: “EA” “Each”2/2CTP08Monetary Amount. The total price amount of theline item.1/18CTP11Multiple Price Quantity. Quantity of units for agiven price, e.g., 3 for 1.000*EA***59.250000 PID - Product/Item DescriptionThe PID segment is used to describe a product or process in coded or free -form format.The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 17
LengthElementMeaning(min/max)Item Description TypeYesPID01(Must be a valid code but has no impact onprocessing within IBX Connect!)1/1PID05Item Description1/80NoPID*F****ITEM DESCRIPTION 1 PID*F****ITEM DESCRIPTION 2 Example:4.21Required?REF - Reference InformationTo specify identifying information.LengthElementMeaning(min/max)Reference Identification QualifierRequired?YesExamples:“PO” “Purchase Order Number”REF01“LI” “Line Item Identifier (Seller's)”2/3REF02Reference Identification1/80REF*PO*987987 Example:4.22YesFOB - F.O.B. Related InstructionsThis segment is used to specify transportation instructions relating to shipment per line hipment Method of Payment Code - Codeidentifying payment terms for transportationchargesFOB01Supported codes:11Rule 11 ShipmentBPPaid by BuyerCAAdvance CollectThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 18
CCCollectCDCollect on DeliveryCFCollect, Freight Credited Back toCustomerCNCost and FreightDEPer ContractDFDefined by Buyer and SellerFOFOB Port of CallHPHalf PrepaidMXMixedNCService Freight, No ChargeNRNon RevenuePAAdvance PrepaidPBCustomer Pickup/BackhaulPCPrepaid but Charged to CustomerPDPrepaid by ProcessorPEPrepaid and Summary BillPLPrepaid Local, Collect OutstatePOPrepaid OnlyPPPrepaid (by Seller)PSPaid by SellerPUPickupRCReturn Container Freight Paid byCustomerRFReturn Container Freight FreeRSReturn Container Freight Paid by SupplierTPThird Party PayWCWeight ConditionLocation Qualifier - Code identifying type oflocationExample: “ZZ” Mutually Defined”FOB06FOB07Yes, if FOB07 isprovided.1/2(Must be a valid code, but has no impact onprocessing within IBX Connect!)Description – Can be used for Transport1/80NoThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 19
iveryDescription free textnote**TransportDescription free text note 4.23ACK - Line Item AcknowledgmentTo acknowledge the ordered quantities and specify the ready date for a specific line ode specifying the action taken by the seller ona line item requested by the buyerSupported codes:ACK01AAItem AcceptedACItem AcceptedARItem AcceptedBPItem AcceptedDRItem AcceptedIAItem AcceptedIBAccepted With AmmendmentICAccepted With AmmendmentIDItem Not Accepted By The SellerIEAccepted With AmmendmentIFItem on HoldIHItem on HoldIPAccepted With AmmendmentIQAccepted With AmmendmentIRItem Not Accepted By The SellerISAccepted With AmmendmentIWItem on HoldR1Item Not Accepted By The SellerR2Item Not Accepted By The SellerR3Item Not Accepted By The SellerR4Item Not Accepted By The SellerThe information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 20
R5Item Not Accepted By The SellerR6Item Not Accepted By The SellerR7Item Not Accepted By The SellerR8Item Not Accepted By The SellerSPAccepted With AmmendmentNote! If there are multiple ACK segments for oneline item then the ACK01 element in the first ACKsegment is used to indicate whether the lineitem as such is accepted, not accepted etc.Multiple ACK segments per line item can beprovided to express partial deliveries.ACK02Quantity of the items that the date in ACK05applies for.1/15No3/3No8/8NoDate/Time Qualifier - Code specifying type of dateor time, or both date and time.Supported codes:ACK04“002” “Delivery requested”“070” “Scheduled for Delivery”“072” “Scheduled for 130201 N9 - Extended Reference InformationThis segment is used to transmit additional information as specified by the Reference Identification 01Code identifying the Reference Identification.2/3YesN902Reference Identification. Used to specify the typeof reference that is provided in N903.1/30YesExample:N9*CT*ContractNumber The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 21
4.25N1 - Name InformationThis segment is used to specify information about the buyer party, seller party, ship to party, bill to party, remitto party or ship from party. Used alone, it provides the most efficient method of providing organizationalidentification. The segment identifies a party by type of organization, name, and code.LengthElementMeaning(min/max)Entity Identifier Code.Required?YesSupported codes:N101“DA” “Delivery Address”2/3N102Name of Entity1/60Identification Code Qualifier. Code designatingthe system/method of code structure used forIdentification CodeN103Example: “92” “Assigned by Buyer or Buyer’sAgent”N104Identification Code. Code identifying a party orother code. Usually an internal ID of the party inthe buyer’s ess Name1*92*AddressID N4 - Geographic LocationThis segment is used to specify the location of the named party from N1.LengthElementMeaning(min/max)Required?N401City Name2/30NoN402State or Province Code2/2NoN403Postal Code3/15NoN404Country Code2/3NoExample:N4****US The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 22
4.27CTT - Transaction TotalsTo transmit a total for the number of line items for elements in the transaction set, we use this 1Number of Line Items -Total number of LineItems in the transaction set1/6YesDescription - A free-form description to clarifythe related data elements and their content(OrderResponse Summary se Summary Freetxt Note AMT - Monetary AmountThis segment contains information regarding the total monetary amount for the es1/18YesAmount Qualifier CodeAMT01Supported codes:“TT” “Total Transaction Amount”AMT02Example:4.29Monetary Amount according to the qualifier codesupplied above.AMT*TT*59.250000 SE - Transaction Set TrailerThis segment is used to indicate the end of the transaction set and provide the count of the transmittedsegments (including the beginning (ST) and ending (SE) segments).LengthElementMeaning(min/max)SE01Number of Included Segments3/3YesSE02Transaction Set Control Number4/9YesExample:Required?SE*54*0001 The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 23
4.30GE - Functional Group TrailerThis segment indicates the end of a functional group and provides control information. It ends the quired?GE01Number of included Transaction Sets - This is usedfor message integrity1/6YesGE02Group Control Number - Must match the groupcontrol number of the GS segment1/9YesGE*1*1403 Example:4.31IEA - Interchange Control TrailerThis segment defines the end of an interchange of one or more functional groups and interchange-relatedcontrol 01Number of Included Functional Groups - This isused for message integrity1/5YesIEA02Interchange Control Number - Must match thecontrol number in the IEA9/9YesExample:5.IEA*1*000001403 001403*0*P* 04010 ST*855*0001 BAK*07*AT*987987*20130101****1234*20130102 CUR*SE*USD The information contained in this document is proprietary. Copyright 2012 Capgemini. All rights reserved.Page 24
REF*11*14779413 REF*Q1*24779413 FOB*DF*ZZ**01*FCA*ZZ*TermsOfDeliveryDescription free text note**TransportDescription free text note ITD*02***********Payment terms note**AA CTB*OR*This is the Order Response Header Note N1*SE*SellerName1*92*VendorID N2*SellerName2 N2*SellerName3 N3*SellerStreet 12 N
EDI format to XML. Like any other electronic order acknowledgment document, the ANSI X12 855 document contains information regarding the products/services and the quantities accepted or rejected, shipping details, payment terms, etc. Below is an example typical structure supported by the IBX Connect Platform when receiving ANSI X12 855 .
