IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS. PentaSAP PURCHASE ORDER (850) TRANSACTION SET

Size: px
Start display at page:

Download "IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS. PentaSAP PURCHASE ORDER (850) TRANSACTION SET"

Transcription

1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS PentaSAP PURCHASE ORDER (850) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

2 850 Purchase Order Functional Group ID=PO Introduction: This X12 Transaction Set 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 and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information. Notes: History of Change: 02/02/2012: Initial Guide Creation 03/02/2012: Header - Enabled SAC Segment Detail - IN Qualifier Disabled for PO106 Element 08/20/2012: Header - RL Qualifier Added to Element BEG02 Header - Enabled BEG04 Element Header - Removed Must Use from FOB Segment Header - FOB04 & FOB05 Changed from Must Use to Optional Header - Disabled CTP Segment Header - TOC Qualifier Enabled for Element N901 Header - Enabled SAC02, SAC03 & SAC04 Elements Header - Disabled SAC14 Element Header - CHG Qualifier Enabled for Element MTX01 Header - N103 and N104 Changed from Must Use to Optional Header - N2 Changed from Must Use to Optional Header - N4 Changed from Must Use to Optional Header - PER Changed from Must Use to Optional Header - PER03 & PER04 Changed from Must Use to Optional Detail - PO106 & PO107 Changed from Must Use to Optional Detail - Enabled PO3 Segment Detail - BT & BY Qualifier Disabled for Element N101 Detail - N103 and N104 Changed from Must Use to Optional Detail - N2 Changed from Must Use to Optional Detail - N4 Changed from Must Use to Optional Detail - PER Changed from Must Use to Optional 09/16/2016 V/R FCA US

3 Detail - IC Qualifier Disabled for Element PER01 Detail - PER03 & PER04 Changed from Must Use to Optional Detail - Enabled SCH12 Element Sub-Detail - Enabled SLN Segment Sub-Detail - Enabled PID Segment 10/10/2012: Header - SAC04 Added support for Unitized Packaging. 10/12/2012: Header - N1 Added Example and Notes for Mopar 03/07/2013: Header - KC & SA Qualifier Enabled for Element BEG02 07/18/2013: Detail - MTX02 Changed Size From 70 To 80 08/01/2013: Added Indirect Purchasing Examples 09/11/2013: Header - Updated the element usage description for BEG03 and BEG04. 11/08/2013: Detail - Enabled SCH Loop Detail - N1 Changed from Must Use to Optional 12/06/2013: Examples - Upated Example 7. Removed the second Ship to. 06/20/2014: Header - Disabled BEG04 Element Header - Enabled BEG06 Element Header - Updated element usage description for BEG03 Header - Updated BEG examples 02/27/2015: Name Change To FCA US 09/09/2015: Appendix A - Updated 09/16/2016: Header - Updated Example in Segment N1 and added notes in Element N101 Heading: 09/16/2016 V/R FCA US

4 Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments ST Transaction Set Header M M BEG Beginning Segment for Purchase Order M M CUR Currency O Must Use REF Reference Information O Not > PER Administrative Communications O Not 3 Contact 0700 TAX Tax Reference O Not > FOB F.O.B. Related Instructions O > CTP Pricing Information O Not > PAM Period Amount O Not CSH Sales Requirements O Not TC2 Commodity O Not >1 LOOP ID - SAC SAC Service, Promotion, Allowance, or O 1 Charge Information 1250 CUR Currency O Not ITD Terms of Sale/Deferred Terms of Sale O > DIS Discount Detail O Not INC Installment Information O Not DTM Date/Time Reference O LIN Item Identification O Not 5 n SI Service Characteristic Identification O Not > PID Product/Item Description O Not MEA Measurements O Not PWK Paperwork O Not PKG Marking, Packaging, Loading O TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing O Not >1 Sequence/Transit Time) 2500 TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or O Not 5 Hazardous Materials, or Both) 2700 MAN Marks and Numbers Information O Not PCT Percent Amounts O Not > CTB Restrictions/Conditions O Not TXI Tax Information O Not >1 LOOP ID - LDT > LDT Lead Time O Not QTY Quantity Information O Not > MTX Text O Not > REF Reference Information O Not >1 LOOP ID - AMT > AMT Monetary Amount Information O Not REF Reference Information O Not > DTM Date/Time Reference O Not PCT Percent Amounts O Not >1 09/16/2016 V/R FCA US

5 LOOP ID - FA1 > FA1 Type of Financial Accounting Data O Not FA2 Accounting Data M Not >1 LOOP ID - N N9 Extended Reference Information O DTM Date/Time Reference O Not > MTX Text O > PWK Paperwork O Not > EFI Electronic Format Identification O Not >1 LOOP ID - N N1 Party Identification O Must Use N2 Additional Name Information O IN2 Individual Name Structure Components O Not > N3 Party Location O N4 Geographic Location O > NX2 Location ID Component O Not > REF Reference Information O Not PER Administrative Communications Contact O > SI Service Characteristic Identification O Not > FOB F.O.B. Related Instructions O Not TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not PKG Marking, Packaging, Loading O Not 200 LOOP ID - LM > LM Code Source Information O Not LQ Industry Code Identification M Not >1 LOOP ID - SPI > SPI Specification Identifier O Not REF Reference Information O Not DTM Date/Time Reference O Not MTX Text O Not >1 LOOP ID - N N1 Party Identification O Not N2 Additional Name Information O Not N3 Party Location O Not N4 Geographic Location O Not REF Reference Information O Not G61 Contact O Not MTX Text O Not >1 LOOP ID - CB1 > CB1 Contract and Cost Accounting O Not 1 09/16/2016 V/R FCA US

6 Standards Data 5700 REF Reference Information O Not DTM Date/Time Reference O Not LDT Lead Time O Not MTX Text O Not >1 LOOP ID - ADV > ADV Advertising Demographic Information O Not DTM Date/Time Reference O Not > MTX Text O Not >1 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - PO PO1 Baseline Item Data M M 1 n LIN Item Identification O Not > SI Service Characteristic Identification O Not > CUR Currency O Not CN1 Contract Information O Not PO3 Additional Item Detail O 25 LOOP ID - CTP > CTP Pricing Information O Not CUR Currency O Not PAM Period Amount O Not MEA Measurements O Not 40 LOOP ID - PID PID Product/Item Description O Must Use MEA Measurements O Not PWK Paperwork O Not PO4 Item Physical Details O Not > REF Reference Information O > PER Administrative Communications Contact O Not 3 LOOP ID - SAC SAC Service, Promotion, Allowance, or Charge Information O Not CUR Currency O Not CTP Pricing Information O Not IT8 Conditions of Sale O Not CSH Sales Requirements O Not > ITD Terms of Sale/Deferred Terms of Sale O Not > DIS Discount Detail O Not INC Installment Information O Not TAX Tax Reference O Not > FOB F.O.B. Related Instructions O Not > SDQ Destination Quantity O Not /16/2016 V/R FCA US

7 2000 IT3 Additional Item Data O Not DTM Date/Time Reference O TC2 Commodity O Not > TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not PCT Percent Amounts O Not > MAN Marks and Numbers Information O Not MTX Text O > SPI Specification Identifier O Not > TXI Tax Information O Not > CTB Restrictions/Conditions O Not >1 LOOP ID - QTY > QTY Quantity Information O Not SI Service Characteristic Identification O Not >1 LOOP ID - SCH SCH Line Item Schedule O 1 n TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not REF Reference Information O Not >1 LOOP ID - PKG PKG Marking, Packaging, Loading O Not MEA Measurements O Not > LS Loop Header O Not 1 LOOP ID - LDT > LDT Lead Time O Not QTY Quantity Information O Not > MTX Text O Not > REF Reference Information O Not 3 LOOP ID - LM > LM Code Source Information O Not LQ Industry Code Identification M Not > LE Loop Trailer O Not 1 LOOP ID - N N9 Extended Reference Information O Not DTM Date/Time Reference O Not > MEA Measurements O Not MTX Text O Not > PWK Paperwork O Not > EFI Electronic Format Identification O Not >1 09/16/2016 V/R FCA US

8 LOOP ID - N N1 Party Identification O N2 Additional Name Information O IN2 Individual Name Structure Components O Not > N3 Party Location O N4 Geographic Location O QTY Quantity Information O Not > NX2 Location ID Component O Not > REF Reference Information O Not PER Administrative Communications Contact O SI Service Characteristic Identification O Not > DTM Date/Time Reference O Not FOB F.O.B. Related Instructions O Not SCH Line Item Schedule O TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not PKG Marking, Packaging, Loading O Not 200 LOOP ID - LDT > LDT Lead Time O Not MAN Marks and Numbers Information O Not QTY Quantity Information O Not MTX Text O Not > REF Reference Information O Not 3 LOOP ID - SLN SLN Subline Item Detail O MTX Text O Not > SI Service Characteristic Identification O Not > PID Product/Item Description O PO3 Additional Item Detail O Not MEA Measurements O Not > TC2 Commodity O Not > ADV Advertising Demographic Information O Not > DTM Date/Time Reference O Not CTP Pricing Information O Not PAM Period Amount O Not PO4 Item Physical Details O Not TAX Tax Reference O Not 3 LOOP ID - N9 > N9 Extended Reference Information O Not DTM Date/Time Reference O Not > MTX Text O Not >1 LOOP ID - SAC 25 09/16/2016 V/R FCA US

9 5260 SAC Service, Promotion, Allowance, or Charge Information O Not CUR Currency O Not CTP Pricing Information O Not 1 LOOP ID - QTY > QTY Quantity Information O Not SI Service Characteristic Identification O Not >1 LOOP ID - N N1 Party Identification O Not N2 Additional Name Information O Not IN2 Individual Name Structure Components O Not > N3 Party Location O Not N4 Geographic Location O Not NX2 Location ID Component O Not > REF Reference Information O Not PER Administrative Communications Contact O Not SI Service Characteristic Identification O Not >1 LOOP ID - AMT > AMT Monetary Amount Information O Not REF Reference Information O Not > PCT Percent Amounts O Not >1 LOOP ID - LM > LM Code Source Information O Not LQ Industry Code Identification M Not >1 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - CTT CTT Transaction Totals O 1 n AMT Monetary Amount Information O Not 1 n SE Transaction Set Trailer M M 1 Transaction Set Notes 1. If segment LIN is used, do not use LIN PO102 is required. 3. The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment. 4. The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment. 5. If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender. 09/16/2016 V/R FCA US

10 Segment: ST Transaction Set Header Position: 0100 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate 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 partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ST Transaction Set Identifier Code M 1 ID 3/3 M Code uniquely identifying a Transaction Set ST Transaction Set Control Number M 1 AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set ST Implementation Convention Reference O 1 AN 1/35 Reference assigned to identify Implementation Convention 09/16/2016 V/R FCA US

11 Segment: BEG Beginning Segment for Purchase Order Position: 0200 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates Syntax Notes: Semantic Notes: 1 BEG05 is the date assigned by the purchaser to purchase order. Comments: Notes: Examples: BEG~00~NE~ ~~ BEG~00~SA~ ~~ BEG~00~KC~ ~~ ~ BEG~00~RL~ ~~ ~ (PO at header level - applies to all items) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BEG Transaction Set Purpose Code M 1 ID 2/2 M Code identifying purpose of transaction set 00 Original BEG02 92 Purchase Order Type Code M 1 ID 2/2 M Code specifying the type of Purchase Order KC Contract Indirect Supplier - Contract NE New Order RL Purchase Order Against The Contract Indirect Suppliers Only SA Stand-alone Order Indirect Supplier - Spot Buy BEG Purchase Order Number M 1 AN 1/22 M Identifying number for Purchase Order assigned by the orderer/purchaser See Appendix A for PO Number Range Worksheet. When BEG02 = KC (Indirect Supplier Contract), Contract Number. When BEG02 = NE (Direct Supplier), Purchase Order Number context is defined in Appendix A. When BEG02 = RL (Indirect Supplier PO), Purchase Order Number against the Contract. When BEG02 = SA (Indirect Supplier Spot-Buy), Purchase Order Number. BEG Release Number O 1 AN 1/30 Not 09/16/2016 V/R FCA US

12 BEG Date M 1 DT 8/8 M Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year BEG Contract Number O 1 AN 1/30 Contract number See Appendix A for PO Number Range Worksheet. When BEG02 = KC (Indirect Supplier Contract), Contract Number. When BEG02 = RL (Indirect Supplier PO), Contract Number. BEG Acknowledgment Type O 1 ID 2/2 Not BEG Invoice Type Code O 1 ID 3/3 Not BEG Contract Type Code O 1 ID 2/2 Not BEG Purchase Category O 1 ID 2/2 Not BEG Security Level Code O 1 ID 2/2 Not BEG Transaction Type Code O 1 ID 2/2 Not 09/16/2016 V/R FCA US

13 Segment: CUR Currency Position: 0400 Loop: Level: Heading Usage: Optional (Must Use) Max Use: 1 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required. 3 If CUR10 is present, then at least one of CUR11 or CUR12 is required. 4 If CUR11 is present, then CUR10 is required. 5 If CUR12 is present, then CUR10 is required. 6 If CUR13 is present, then at least one of CUR14 or CUR15 is required. 7 If CUR14 is present, then CUR13 is required. 8 If CUR15 is present, then CUR13 is required. 9 If CUR16 is present, then at least one of CUR17 or CUR18 is required. 10 If CUR17 is present, then CUR16 is required. 11 If CUR18 is present, then CUR16 is required. 12 If CUR19 is present, then at least one of CUR20 or CUR21 is required. 13 If CUR20 is present, then CUR19 is required. 14 If CUR21 is present, then CUR19 is required. Semantic Notes: Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment. Notes: Example: CUR~BY~USD Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CUR01 98 Entity Identifier Code M 1 ID 2/3 M Code identifying an organizational entity, a physical location, property or an individual BY Buying Party (Purchaser) CUR Currency Code M 1 ID 3/3 M Code (Standard ISO) for country in whose currency the charges are specified An appropriate currency code will be provided from the ISO 4217 currency and funds name and code elements. Note: The code list for this element is maintained by the International Organization for Standardization. Follow the link: Additional Note: As with any website, changes to the website are possible. The path that should be followed to obtain the ISO Recommendation is subject to change without notice and may not be represented in this documentation. This path is provided to assist the trading partner. CUR Exchange Rate O 1 R 4/10 Not 09/16/2016 V/R FCA US

14 CUR04 98 Entity Identifier Code O 1 ID 2/3 Not CUR Currency Code O 1 ID 3/3 Not CUR Currency Market/Exchange Code O 1 ID 3/3 Not CUR Date/Time Qualifier X 1 ID 3/3 Not CUR Date O 1 DT 8/8 Not CUR Time O 1 TM 4/8 Not CUR Date/Time Qualifier X 1 ID 3/3 Not CUR Date X 1 DT 8/8 Not CUR Time X 1 TM 4/8 Not CUR Date/Time Qualifier X 1 ID 3/3 Not CUR Date X 1 DT 8/8 Not CUR Time X 1 TM 4/8 Not CUR Date/Time Qualifier X 1 ID 3/3 Not CUR Date X 1 DT 8/8 Not CUR Time X 1 TM 4/8 Not CUR Date/Time Qualifier X 1 ID 3/3 Not CUR Date X 1 DT 8/8 Not CUR Time X 1 TM 4/8 Not 09/16/2016 V/R FCA US

15 Segment: FOB F.O.B. Related Instructions Position: 0800 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify transportation instructions relating to shipment Syntax Notes: 1 If FOB03 is present, then FOB02 is required. 2 If FOB04 is present, then FOB05 is required. 3 If FOB07 is present, then FOB06 is required. 4 If FOB08 is present, then FOB09 is required. Semantic Notes: 1 FOB01 indicates which party will pay the carrier. 2 FOB02 is the code specifying transportation responsibility location. 3 FOB06 is the code specifying the title passage location. 4 FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07. Comments: Notes: Examples: FOB~DF~~~01~FCA~ZZ~Free Carriage and Freight STRATFORD ON N5A 6T2 CA FOB~DF~~~~~ZZ~ CHESTERFIELD MI US Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes FOB Shipment Method of Payment M 1 ID 2/2 M Code identifying payment terms for transportation charges DF Defined by Buyer and Seller FOB Location Qualifier X 1 ID 1/2 Not FOB Description O 1 AN 1/80 Not FOB Transportation Terms Qualifier Code O 1 ID 2/2 Code identifying the source of the transportation terms 01 Incoterms FOB Transportation Terms Code X 1 ID 3/3 Code identifying the trade terms which apply to the shipment transportation responsibility CFR Cost and Freight CIF Cost, Insurance, and Freight CIP Carriage and Insurance Paid To CPT Carriage Paid To DAP Delivered at Place 09/16/2016 V/R FCA US

16 DAT DDP EXW FAS FCA FOB Delivered at Terminal Delivered Duty Paid Ex Works Free Alongside Ship Free Carrier Free on Board FOB Location Qualifier X 1 ID 1/2 Must Use Code identifying type of location ZZ Mutually Defined FOB Description O 1 AN 1/80 Must Use A free-form description to clarify the related data elements and their content City/Country/State/ZIP/Description Supplier Address FOB08 54 Risk of Loss Code O 1 ID 2/2 Not FOB Description X 1 AN 1/80 Not 09/16/2016 V/R FCA US

17 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 1200 Loop: SAC Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge Syntax Notes: 1 At least one of SAC02 or SAC03 is required. 2 If either SAC03 or SAC04 is present, then the other is required. 3 If either SAC06 or SAC07 is present, then the other is required. 4 If either SAC09 or SAC10 is present, then the other is required. 5 If SAC11 is present, then SAC10 is required. 6 If SAC14 is present, then SAC13 is required. 7 If SAC16 is present, then SAC15 is required. Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required. 2 SAC05 is the total amount for the service, promotion, allowance, or charge. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence. 3 SAC08 is the allowance or charge rate per unit. 4 SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge. 5 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used. 6 SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 7 SAC16 is used to identify the language being used in SAC15. Comments: 1 SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02. 2 In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09. Notes: Example: SAC~C~F155~AB~092~10000~~~~~~~06~~~Production Packaging Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SAC Allowance or Charge Indicator M 1 ID 1/1 M Code which indicates an allowance or charge for the service specified A Allowance C Charge 09/16/2016 V/R FCA US

18 N No Allowance or Charge SAC Service, Promotion, Allowance, or Charge Code X 1 ID 4/4 Code identifying the service, promotion, allowance, or charge F155 Packaging SAC Agency Qualifier Code X 1 ID 2/2 Code identifying the agency assigning the code values AB Assigned by Buyer SAC Agency Service, Promotion, Allowance, or Charge Code X 1 AN 1/10 Agency maintained code identifying the service, promotion, allowance, or charge Production Packaging 092A - Mopar Packaging Intl - International Packaging Unit - Unitized packaging SAC Amount O 1 N2 1/15 Monetary amount SAC Allowance/Charge Percent Qualifier X 1 ID 1/1 Not SAC Percent, Decimal Format X 1 R 1/6 Not SAC Rate O 1 R 1/9 Not SAC Unit or Basis for Measurement Code X 1 ID 2/2 Not SAC Quantity X 1 R 1/15 Not SAC Quantity O 1 R 1/15 Not SAC Allowance or Charge Method of Handling Code O 1 ID 2/2 Code indicating method of handling for an allowance or charge 06 Charge to be Paid by Customer SAC Reference Identification X 1 AN 1/80 Not SAC Option Number O 1 AN 1/20 Not SAC Description X 1 AN 1/80 A free-form description to clarify the related data elements and their content SAC Language Code O 1 ID 2/3 Not 09/16/2016 V/R FCA US

19 Segment: ITD Terms of Sale/Deferred Terms of Sale Position: 1300 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify terms of sale Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required. 2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required. 3 If ITD09 is present, then at least one of ITD10 or ITD11 is required. Semantic Notes: 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 code in ITD01 is "05", then ITD06 or ITD07 is required. Notes: Examples: ITD~~3~~~4~~45~~~~~NET 45 DAYS ITD~~3~~~15~~~~~~~NET 15TH AND 30TH PROX Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ITD Terms Type Code O 1 ID 2/2 Not ITD Terms Basis Date Code O 1 ID 1/2 Must Use Code identifying the beginning of the terms period 3 Invoice Date ITD Terms Discount Percent O 1 R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date ITD Terms Discount Due Date X 1 DT 8/8 Not ITD Terms Discount Days Due X 1 N0 1/3 Number of days in the terms discount period by which payment is due if terms discount is earned ITD Terms Net Due Date O 1 DT 8/8 Not ITD Terms Net Days O 1 N0 1/3 Number of days until total invoice amount is due (discount not applicable) ITD Terms Discount Amount O 1 N2 1/10 Not ITD Terms Deferred Due Date O 1 DT 8/8 Not 09/16/2016 V/R FCA US

20 ITD Deferred Amount Due X 1 N2 1/10 Not ITD Percent of Invoice Payable X 1 R 1/5 Not ITD Description O 1 AN 1/80 A free-form description to clarify the related data elements and their content ITD Day of Month X 1 N0 1/2 Not ITD Payment Method Type Code O 1 ID 1/2 Not ITD Percentage as Decimal O 1 R 1/10 Not 09/16/2016 V/R FCA US

21 Segment: DTM Date/Time Reference Position: 1500 Loop: Level: Heading Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Notes: Example: DTM~092~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M 1 ID 3/3 M Code specifying type of date or time, or both date and time 092 Contract Effective 093 Contract Expiration 113 Sample Required 114 Tooling Required DTM Date X 1 DT 8/8 Must Use Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year DTM Time X 1 TM 4/8 Not DTM Time Code O 1 ID 2/2 Not DTM Date Time Period Format Qualifier X 1 ID 2/3 Not DTM Date Time Period X 1 AN 1/35 Not 09/16/2016 V/R FCA US

22 Segment: PKG Marking, Packaging, Loading Position: 2200 Loop: Level: Heading Usage: Optional Max Use: 200 Purpose: To describe marking, packaging, loading, and unloading requirements Syntax Notes: 1 At least one of PKG04 PKG05 or PKG06 is required. 2 If PKG04 is present, then PKG03 is required. 3 If PKG05 is present, then PKG01 is required. Semantic Notes: 1 PKG04 should be used for industry-specific packaging description codes. Comments: 1 Use the MEA (Measurements) Segment to define dimensions, tolerances, weights, counts, physical restrictions, etc. 2 If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used. 3 Use PKG03 to indicate the organization that publishes the code list being referred to. 4 Special marking or tagging data can be given in PKG05 (description). Notes: Example: PKG~F~35~~~RETURNABLE Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PKG Item Description Type X 1 ID 1/1 Must Use Code indicating the format of a description F Free-form PKG Packaging Characteristic Code O 1 ID 1/5 Must Use Code specifying the marking, packaging, loading and related characteristics being described 35 Type of Package PKG Agency Qualifier Code X 1 ID 2/2 Not PKG Packaging Description Code X 1 AN 1/7 Not PKG Description X 1 AN 1/80 Must Use A free-form description to clarify the related data elements and their content PKG Unit Load Option Code X 1 ID 2/2 Not 09/16/2016 V/R FCA US

23 Segment: N9 Extended Reference Information Position: 2950 Loop: N9 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Syntax Notes: 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. Comments: Notes: Examples: N9~CJ~A01 N9~OP~POO N9~TOC~~USD,4012 (Currency and ship to Plant of the component Supplier) N9~ZZ~~See Below Text Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Reference Identification Qualifier M 1 ID 2/3 M Code qualifying the Reference Identification CJ Clause Number OP Original Purchase Order TOC Type of Comment For Modular Supplier Only ZZ Mutually Defined N Reference Identification X 1 AN 1/80 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X 1 AN 1/45 Free-form descriptive text N Date O 1 DT 8/8 Not N Time X 1 TM 4/8 Not N Time Code O 1 ID 2/2 Not N907 C040 Reference Identifier O 1 Not 09/16/2016 V/R FCA US

24 Use d To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier C Reference Identification Qualifier M ID 2/3 Not Code qualifying the Reference Identification C Reference Identification M AN 1/80 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/80 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/80 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 09/16/2016 V/R FCA US

25 Segment: MTX Text Position: 3000 Loop: N9 Optional Level: Heading Usage: Optional Max Use: >1 Purpose: To specify textual data Syntax Notes: 1 If MTX01 is present, then MTX02 is required. 2 If MTX03 is present, then MTX02 is required. 3 If MTX05 is present, then MTX04 is required. Semantic Notes: 1 MTX05 is the number of lines to advance before printing. Comments: 1 If MTX04 is "AA - Advance the specific number of lines before print", then MTX05 is required. Notes: Examples: MTX~BBH~THIS PO REPLACES POO All terms and conditions MTX~BBH~remain unchanged MTX~CCE~Seller agrees to sell and deliver the goods and services specified in MTX~CCE~The FCA US order in accordance to the Terms and Conditions MTX~CCE~contained in the order. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes MTX Note Reference Code O 1 ID 3/3 Must Use Code identifying the functional area or purpose for which the note applies BBH Business History CCE Contract Details CHG Change DEL Delivery GEN Entire Transaction Set TRA Transportation MTX Textual Data X 1 AN 1/4096 To transmit large volumes of message text MTX Textual Data O 1 AN 1/4096 Must Use Not MTX Printer Carriage Control Code X 1 ID 2/2 Not MTX Number O 1 N0 1/9 Not MTX Language Code O 1 ID 2/3 Not AN 1/70 09/16/2016 V/R FCA US

26 Segment: N1 Party Identification Position: 3100 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional (Must Use) Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. Notes: Examples: N1~BT~AP Center~92~0G589 N1~DV~MOPAR N1~BY~FIAT CHRYSLER AUTOMOBILES N1~BY~ATTN: John Doe Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M 1 ID 2/3 M Code identifying an organizational entity, a physical location, property or an individual These qualifiers can be duplicated 28 Subcontractor BT Bill-to-Party BY Buying Party (Purchaser) DV Division MI Planning Schedule/Material Release Issuer MP Manufacturing Plant PD Purchaser's Department Buyer PN Party to Receive Shipping Notice RC Receiving Location SE Selling Party ST Ship To N Name X 1 AN 1/60 Must Use Free-form name If N101 = DV and N102 = 'MOPAR' This contract is available for Mopar use N Identification Code Qualifier X 1 ID 1/2 09/16/2016 V/R FCA US

27 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code X 1 AN 2/80 Code identifying a party or other code N Entity Relationship Code O 1 ID 2/2 Not N Entity Identifier Code O 1 ID 2/3 Not 09/16/2016 V/R FCA US

28 Segment: N2 Additional Name Information Position: 3200 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Max Use: 2 Purpose: To specify additional names Syntax Notes: Semantic Notes: Comments: Notes: Example: N2~AP Center Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Name M 1 AN 1/60 M Free-form name N Name O 1 AN 1/60 Free-form name 09/16/2016 V/R FCA US

29 Segment: N3 Party Location Position: 3300 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Notes: Example: N3~345 Mound Rd Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Address Information M 1 AN 1/55 M Address information N Address Information O 1 AN 1/55 Address information 09/16/2016 V/R FCA US

30 Segment: N4 Geographic Location Position: 3400 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Max Use: >1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 Only one of N402 or N407 may be present. 2 If N406 is present, then N405 is required. 3 If N407 is present, then N404 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. Notes: Example: N4~Sterling Heights~MI~48312~US Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N City Name O 1 AN 2/30 Must Use Free-form text for city name N State or Province Code X 1 ID 2/2 Must Use Code (Standard State/Province) as defined by appropriate government agency N Postal Code O 1 ID 3/15 Must Use Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code X 1 ID 2/3 Must Use Code identifying the country N Location Qualifier X 1 ID 1/2 Not N Location Identifier O 1 AN 1/30 Not N Country Subdivision Code X 1 ID 1/3 Not 09/16/2016 V/R FCA US

31 Segment: PER Administrative Communications Contact Position: 3600 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Max Use: >1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: Notes: Example: PER~BD~George Jones~TE~ ~EM~gj77@fcagroup.com Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PER Contact Function Code M 1 ID 2/2 M Code identifying the major duty or responsibility of the person or group named BD Buyer Name or Department PER02 93 Name O 1 AN 1/60 Must Use Free-form name PER Communication Number Qualifier X 1 ID 2/2 Code identifying the type of communication number TE Telephone PER Communication Number X 1 AN 1/256 AN 1/30 Complete communications number including country or area code when applicable PER Communication Number Qualifier X 1 ID 2/2 Must Use Code identifying the type of communication number EM Electronic Mail PER Communication Number X 1 AN 1/256 Must Use AN 1/60 Complete communications number including country or area code when applicable PER Communication Number Qualifier X 1 ID 2/2 Not PER Communication Number X 1 AN 1/256 Not PER Contact Inquiry Reference O 1 AN 1/20 Not 09/16/2016 V/R FCA US

32 Segment: PO1 Baseline Item Data Position: 0100 Loop: PO1 Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify basic and most frequently used line item data Syntax Notes: 1 If PO103 is present, then PO102 is required. 2 If PO105 is present, then PO104 is required. 3 If either PO106 or PO107 is present, then the other is required. 4 If either PO108 or PO109 is present, then the other is required. 5 If either PO110 or PO111 is present, then the other is required. 6 If either PO112 or PO113 is present, then the other is required. 7 If either PO114 or PO115 is present, then the other is required. 8 If either PO116 or PO117 is present, then the other is required. 9 If either PO118 or PO119 is present, then the other is required. 10 If either PO120 or PO121 is present, then the other is required. 11 If either PO122 or PO123 is present, then the other is required. 12 If either PO124 or PO125 is present, then the other is required. Semantic Notes: 1 PO102 is quantity ordered. 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., ISBN No., Model No., or SKU. Notes: Examples: PO1~00010~9999~EA~66~PE~BP~ AB~PT~ AB~DR~A PO1~00001~0~EA~ ~HP~BP~MC8888PB PO1~00002~2~EA~152600~PE (Tooling) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PO Assigned Identification O 1 AN 1/20 Must Use Alphanumeric characters assigned for differentiation within a transaction set PO Quantity X 1 R 1/15 Must Use Numeric value of quantity PO Unit or Basis for Measurement Code O 1 ID 2/2 Must Use Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken PO Unit Price X 1 R 1/17 Must Use Price per unit of product, service, commodity, etc. 09/16/2016 V/R FCA US

33 PO Basis of Unit Price Code O 1 ID 2/2 Must Use Code identifying the type of unit price for an item HP Price per Hundred HT Price Per 100,000 PE PN TP Price per Each Price per Ten Price per Thousand TT Price Per 10,000 PO Product/Service ID Qualifier X 1 ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number PO Product/Service ID X 1 AN 1/80 Identifying number for a product or service Indirect Suppliers: NPM Code or NPM Material Number Direct Suppliers: Part Number PO Product/Service ID Qualifier X 1 ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) PT Print or Drawing PO Product/Service ID X 1 AN 1/80 Identifying number for a product or service PO Product/Service ID Qualifier X 1 ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) DR Drawing Revision Number PO Product/Service ID X 1 AN 1/80 Identifying number for a product or service PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not 09/16/2016 V/R FCA US

34 PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not PO Product/Service ID Qualifier X 1 ID 2/2 Not PO Product/Service ID X 1 AN 1/80 Not 09/16/2016 V/R FCA US

35 Segment: PO3 Additional Item Detail Position: 0300 Loop: PO1 Mandatory Level: Detail Usage: Optional Max Use: 25 Purpose: To specify additional item-related data involving variations in normal price/quantity structure Syntax Notes: 1 If PO304 is present, then at least one of PO303 or PO305 is required. Semantic Notes: Comments: 1 Some examples of price/quantity variations are: price in different units from the PO1 segment, price changes by date, or price changes by quantity (break and level). 2 PO307 defines the unit of measure for PO306. Notes: Example: PO3~QT~~PBQ~10.00~~10~EA Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PO Change Reason Code M 1 ID 2/2 M Code specifying the reason for price or quantity change QT Quantity Price Break PO Date O 1 DT 8/8 Not PO Price Identifier Code X 1 ID 3/3 Code identifying pricing specification PBQ Unit Price Beginning Quantity PO Unit Price O 1 R 1/17 Price per unit of product, service, commodity, etc. PO Basis of Unit Price Code X 1 ID 2/2 Not PO Quantity M 1 R 1/15 M Numeric value of quantity PO Unit or Basis for Measurement Code M 1 ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken PO Description O 1 AN 1/80 Not 09/16/2016 V/R FCA US

36 Segment: PID Product/Item Description Position: 0500 Loop: PID Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 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 specified attribute 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 both PID04 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. Notes: Examples: PID~F~08~~~METRO MOULDED TRUNK SEAL PID~F~08~~~Tooling for T ,MY 13 (Tooling) For Steel Order a series of PID will be created which describe the Steel attributes, See Offload Steel Example Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PID Item Description Type M 1 ID 1/1 M Code indicating the format of a description F Free-form PID Product/Process Characteristic Code O 1 ID 2/3 Must Use Code identifying the general class of a product or process characteristic 08 Product PID Agency Qualifier Code X 1 ID 2/2 Not PID Product Description Code X 1 AN 1/12 Not PID Description X 1 AN 1/80 Must 09/16/2016 V/R FCA US

37 A free-form description to clarify the related data elements and their content PID Surface/Layer/Position Code O 1 ID 2/2 Not PID Source Subqualifier O 1 AN 1/15 Not PID Yes/No Condition or Response Code O 1 ID 1/1 Not PID Language Code O 1 ID 2/3 Not Use 09/16/2016 V/R FCA US

38 Segment: REF Reference Information Position: 1000 Loop: PO1 Mandatory Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: Example: REF~RQ~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Identification Qualifier M 1 ID 2/3 M Code qualifying the Reference Identification AAJ Prior Contract Number CA Cost Allocation Reference IT Internal Customer Number MF Manufacturers Part Number MY Model year number PZ Product Change Notice Number RQ Purchase Requisition Number REF Reference Identification X 1 AN 1/80 Must Use Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier REF Description X 1 AN 1/80 Not REF04 C040 Reference Identifier O 1 Not Use d To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier C Reference Identification Qualifier M ID 2/3 Not Code qualifying the Reference Identification C Reference Identification M AN 1/80 Not 09/16/2016 V/R FCA US

39 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/80 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/80 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 09/16/2016 V/R FCA US

40 Segment: DTM Date/Time Reference Position: 2100 Loop: PO1 Mandatory Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Notes: Example: DTM~113~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M 1 ID 3/3 M Code specifying type of date or time, or both date and time 007 Effective 113 Sample Required 114 Tooling Required DTM Date X 1 DT 8/8 Must Use Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year DTM Time X 1 TM 4/8 Not DTM Time Code O 1 ID 2/2 Not DTM Date Time Period Format Qualifier X 1 ID 2/3 Not DTM Date Time Period X 1 AN 1/35 Not 09/16/2016 V/R FCA US

41 Segment: MTX Text Position: 2890 Loop: PO1 Mandatory Level: Detail Usage: Optional Max Use: >1 Purpose: To specify textual data Syntax Notes: 1 If MTX01 is present, then MTX02 is required. 2 If MTX03 is present, then MTX02 is required. 3 If MTX05 is present, then MTX04 is required. Semantic Notes: 1 MTX05 is the number of lines to advance before printing. Comments: 1 If MTX04 is "AA - Advance the specific number of lines before print", then MTX05 is required. Notes: Example: MTX~CCE~Material Type: AA01US - ALUM-PRIMARY/MW US TRANSACTION Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes MTX Note Reference Code O 1 ID 3/3 Must Use Code identifying the functional area or purpose for which the note applies CCE Contract Details DEL Delivery MTX Textual Data X 1 AN 1/4096 To transmit large volumes of message text MTX Textual Data O 1 AN 1/4096 Must Use Not MTX Printer Carriage Control Code X 1 ID 2/2 Not MTX Number O 1 N0 1/9 Not MTX Language Code O 1 ID 2/3 Not AN 1/80 09/16/2016 V/R FCA US

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

More information

810 IBM Subset - Invoice To Customer - (004010)

810 IBM Subset - Invoice To Customer - (004010) 810 IBM Subset - Invoice To Customer - (004010) Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set

More information

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

Orchard Supply Hardware Direct to Consumer 850 Purchase Order Orchard Supply Hardware Direct to Consumer 850 Purchase Order X12/V4010/850: 850 Purchase Order Author: Orchard Supply Hardware Trading Partner: Created: May 25, 2011 Modified: June 9, 2011 Notes: ISA/GS

More information

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0.

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0. EDI Implementation Guide ESIS Purchase Order Change X12 860 Version 4010 Release 8.0 Page 1 of 37 EDI Implementation Support Information EDI Contact Name: ESIS, E-Commerce Provider of Raytheon EDI Contact

More information

850 Purchase Order

850 Purchase Order 850 Purchase Order - 4010 Version: 1.0 Author: Land O' Lakes Inc. V4010 1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents

More information

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 400 IMPLEMENTATION GUIDE Purchase Order 850 Functional Group PO 400 This Draft Standard for Trial Use contains the format and establishes the data contents

More information

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010 ANSI X12 850 (Purchase Order) Inbound (to Eclipse) Version 4010 Eclipse 850 4010 (Customer) 1 10/11/2012 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format

More information

846 RAPID Inventory Inquiry/Advice Standard

846 RAPID Inventory Inquiry/Advice Standard 846 RAPID Inventory Inquiry/Advice Standard Functional Group ID=IB Introduction: This Standard contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846)

More information

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction 860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction Functional Group ID=PC Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents

More information

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline.

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline. Introduction This guideline provides a description and technical layout of the data segments used when creating 3M s EDI Planning Schedules with Release Capability (Forecast) (ASC X12 transaction set 830)

More information

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

More information

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: Table of Contents 850 Purchase Order...1 ISA Interchange Control Header...3 GS Functional Group Header...5

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003040

More information

830 Planning Schedule with Release Capability

830 Planning Schedule with Release Capability 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V5010/846: 846 Inventory Inquiry/Advice Company: Contact: GovX.com integrations@govx.com 846 Inventory Inquiry/Advice Functional Group=IB Purpose: This X12 Transaction

More information

RCI 855 Purchase Order Acknowledgment

RCI 855 Purchase Order Acknowledgment RCI 855 Purchase Order Acknowledgment X12/V4030/855 : 855 Purchase Order Acknowledgment Version: 1.0 Draft Company: DiCentral Publication: 8/18/2017 Notes Table of Contents 855 Purchase Order Acknowledgment.....................................................................................................

More information

JR Simplot Corporate 810 Invoice

JR Simplot Corporate 810 Invoice JR Simplot Corporate 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Company: JR Simplot Company Modified: 3/2/2018 Notes: edi@simplot.com Table of Contents 810 Invoice.......................................................................................................................................

More information

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: edi@simplot.com Table of Contents 850 Purchase Order............................................................................................................................

More information

evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes:

evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes: evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes: 855 Purchase Order Acknowledgment Functional Group= PR Purpose:

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for

More information

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format and establishes the data

More information

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

Oshkosh 860 Purchase Order Change Request - Buyer Initiated Oshkosh 860 Purchase Order Change Request - Buyer Initiated AIAG X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Final Company: Oshkosh Corporation Publication: 11/13/2015

More information

Purchase Order Change Request - Buyer Initiated

Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated Functional Group= PC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request

More information

850 Purchase Order. Version: X12

850 Purchase Order. Version: X12 850 Purchase Order Version: 004010 X12 Company: DOT FOODS, INC. Publication: 5/18/2012 850 Purchase Order Functional Group= PO Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

850 Purchase Order - v4030

850 Purchase Order - v4030 850 Purchase Order - v4030 X12/V4030/850 Version: 1.0 Final Author: Inovis Publication: April 1, 2008 PepBoys850_4030_FINAL.ecs 1 Ver 1.0 Revision History Date Version Revision Approved By April 1, 2008

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 9/19/2018 Added new value UP in PO106 Added TD512 segment Table

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 Added new value UP in PO106 2 Table of Contents 850 Purchase

More information

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes:

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes: 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Final Author: Baker & Taylor Company: Baker & Taylor Modified: 10/26/2010 Notes: Table of Contents 810 Invoice... 1 ISA Interchange Control Header...

More information

Inbound ANSI X Version 04010

Inbound ANSI X Version 04010 Inbound ANSI X12 850 Version 04010 For CLP License Ordering Version: ANSI X12 850 4010 Author: Adobe EDI Modified: 06/09/2010 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only 850 Purchase Order Functional

More information

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X CVS/Caremark Implementation Guide 810 DSD Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ISA Interchange Control Header... 2 GS Functional Group Header...

More information

810 Invoice Service Parts Version:

810 Invoice Service Parts Version: 810 Invoice Service Parts Version: 004010 CNH_810v4010_ServiceParts.ecs 1 Table of Contents 810 Invoice... 4 ISA Interchange Control Header... 7 GS Functional Group Header... 9 ST Transaction Set Header...

More information

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications EDI 850 Version 4010 ANSI X12 Purchase Order Specifications Coupa Software, Inc. 1855 S. Grant St. 5 th Floor San Mateo, CA 94402 www.coupa.com Contents Purchase Order Details 3 Introduction 3 File Format

More information

EDI Guidelines for Purchase Order (850) v. 4010

EDI Guidelines for Purchase Order (850) v. 4010 November 14, 2003 EDI Guidelines for Purchase Order (850) v. 4010 thyssenkrupp Materials NA 22355 West Eleven Mile Road Southfield, MI 48033 WEB850.ecs 1 For internal use only 850 Purchase Order Functional

More information

Purchase Order - v4010 Functional Group ID = PO

Purchase Order - v4010 Functional Group ID = PO 850 Functional Group ID = PO TESTING PROCEDURES & TIPS ON AUTOLIV's 850 DOCUMENT is now using this 850 document for MRO ordering. If you have any questions, please contact Autoliv IT Service Center at

More information

ANSI X (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010

ANSI X (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010 ANSI X12 855 (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010 Eclipse 855 4010 (Vendor) 1 10/12/2012 855 Purchase Order Acknowledgment Functional Group=PR Purpose: This Draft Standard

More information

EDI Implementation Guide. Catalog Supplier Program

EDI Implementation Guide. Catalog Supplier Program EDI Implementation Guide Catalog Supplier Program Original Publication Date: June 23, 2005 Revision Date: July 10, 2008 This page is intentionally left blank. Table of Contents REVISION SECTION...4 CONTACT

More information

855 Purchase Order Acknowledgment. United Natural Foods

855 Purchase Order Acknowledgment. United Natural Foods 855 Purchase Order Acknowledgment Company: United Natural Foods Table of Contents 855 Purchase Order Acknowledgment... 1 ST Transaction Set Header... 2 BAK Beginning Segment for Purchase Order Acknowledgment...

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/7/2016 Notes: Table of Contents 860 Purchase Order

More information

850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes:

850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes: 850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes: edi@simplot.com Table of Contents 850 Purchase Order...........................................................................................................................

More information

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0 Zappos EDI Guideline X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Author: Zappos Created: 07/06/2011 Last updated: 01/15/2014 Electronic Data Interchange 860 Purchase

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/11/2018 Notes: Table of Contents 860 Purchase Order

More information

COMMUNICATION ID S. Strouds Voice (626) South Nogales St. City of Industry, Ca Fax (626)

COMMUNICATION ID S. Strouds Voice (626) South Nogales St. City of Industry, Ca Fax (626) COMMUNICATION ID S Communication Information Strouds Voice (626) 912 2866 780 South Nogales St. City of Industry, Ca 91748 Fax (626) 913 4841 ISA Header Interchange ID Qualifier (ISA 05/07) 01 Interchange

More information

Golfsmith 846 EDI Guidelines

Golfsmith 846 EDI Guidelines Golfsmith 846 EDI Guidelines X12/V4050/846: 846 Inventory Inquiry/Advice Author: SPS Commerce Trading Partner: Created: 10/19/2010 Modified: 04/19/2011 Notes: 846 Inventory Inquiry/Advice Functional Group=IB

More information

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 2.0 Final Author: D&H Distributors Company: D&H Distributors Publication: 8/15/2016 Trading Partner: Modified: 8/12/2016 Notes EDI notes The

More information

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009 Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 830 TRANSACTION SET MATERIAL RELEASE Version 004010 Revised November 18, 2009 2 P a g e 830 Material Release Functional Group ID=PS Introduction:

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Company: General Mills Modified: 1/11/2018 Notes: Production Orders for copack and warehousing partners. Table of Contents 850 Purchase Order............................................................................................................................

More information

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE 1 Purchase Order Acknowledgement 855 4010 Functional Group PR This Draft Standard for Trial Use contains the

More information

830 Planning Schedule with Release Capability

830 Planning Schedule with Release Capability AN AIAG IMPLEMENTATION GUIDELINE VERSION 004 RELEASE 010 830 830 Planning Schedule with Release Capability PREFACE This is the AIAG s recommended usage for the 830 - Planning Schedule with Release Capability

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report Functional Group=RS This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context

More information

7/4/2011 Page 1 Retek850.xls

7/4/2011 Page 1 Retek850.xls The following control characters will be sent in the document. Changes can be made if requested. ASCII HEX Segment Terminator CR x0d Element Separator * x2a Segment: ISA - INTERCHANGE CONTROL HEADER Level:

More information

850 Purchase Order X12 Version Version: 2.0

850 Purchase Order X12 Version Version: 2.0 850 Purchase Order X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 12/03/2016 Revision History Date Version Description Author 1/15/2013 NA Original publication

More information

Inbound X Version 04010

Inbound X Version 04010 Inbound X12 850 Version 04010 For Value Incentive Plan (VIP) License Ordering Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Adobe Systems Inc Modified: 8/31/2015 850 Purchase Order Functional

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 02/14/2012 Current: 02/14/2012 Table of Contents 850 Purchase Order. BEG

More information

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 ANSI X12 856 (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 Eclipse 856 4010 (Vendor) 1 10/12/2012 856 Ship Notice/Manifest Functional Group=SH Purpose: This Draft Standard for Trial

More information

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct X12/V4010/832: 832 Price/Sales Catalog Version: 1.0 Final Author: Publication: Trading Partner: All Notes: Brand Technology Services Table of Contents

More information

867 Bill Back itradenetwork OMS

867 Bill Back itradenetwork OMS 867 Bill Back itradenetwork OMS X12/V4010/867: 867 Product Transfer and Resale Report Version: 1.3 Final Company: itradenetwork Publication: 12/23/2013 Trading Partner: Current: 4/3/2015 Table of Contents

More information

867 Product Transfer and Resale Report Functional Group=PT

867 Product Transfer and Resale Report Functional Group=PT 867 Product Transfer and Resale Report Functional Group=PT This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction

More information

812 Credit/Debit Adjustment

812 Credit/Debit Adjustment 812 Credit/Debit Adjustment Functional Group ID=CD Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Credit/Debit Adjustment Transaction Set (812)

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment Changes 9/2009: PO1 Segment is mandatory PO1 segment 02 position is mandatory Changes 5/2011: SCH11 Schedule line identifier 855 Purchase Order Acknowledgment Functional Group ID=PR Introduction: This

More information

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010 ANSI X12 867 (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010 Eclipse 867 4010 (Vendor) 1 10/12/2012 867 Product Transfer and Resale Report Functional Group=PT Purpose: This Draft

More information

Product Transfer and Resale Report - 867

Product Transfer and Resale Report - 867 867 Product Transfer and Resale Report - 4010 Version: 1.0 Author: Land O' Lakes, Inc. V4010 1 867 Product Transfer and Resale Report Functional Group=PT This Draft Standard for Trial Use contains the

More information

Invoice Specification EDI 810

Invoice Specification EDI 810 Invoice Specification EDI 80 This document is solely for the use of Logicbroker, Inc. personnel and its intended client. No part of it may be circulated, Quoted, or reproduced for distribution outside

More information

Purchase Order Specification EDI 850

Purchase Order Specification EDI 850 Purchase Order Specification EDI 850 This document is solely for the use of Logicbroker, Inc. personnel and its intended client. No part of it may be circulated, Quoted, or reproduced for distribution

More information

940 Warehouse Shipping Order

940 Warehouse Shipping Order 940 Warehouse Shipping Order X12/V4030/940: 940 Warehouse Shipping Order Version: 1.0 Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 03/21/2012 Current: 03/21/2012 Table of Contents

More information

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction HUBBELL855_Inbound_V4 (004010) Septemember 15, 2016 855 Purchase Order Acknowledgement v. 4010 Supplier to Hubbell Inbound Transaction Introduction: Functional Group ID=PR This Draft Standard for Trial

More information

846 Inventory Inquiry / Advice _Outbound

846 Inventory Inquiry / Advice _Outbound 846 Inventory Inquiry / Advice _Outbound 846 ANSI X12 004010 Version: 1.1 Publication: 02.09.2014 Version Version Date Description of Change Reason of Change Author Change Reference Number 1.0 09.02.2014

More information

Transaction Set 860, Version ANSI Standard Version Segments used by Home Shopping Network for Traditional Purchase Orders Change.

Transaction Set 860, Version ANSI Standard Version Segments used by Home Shopping Network for Traditional Purchase Orders Change. Transaction Set 860, Version 3030 ANSI Standard Version 3030 Segments used by Home Shopping Network for Traditional Purchase Orders Change. 2 SEGMENT ISA - INTERCHANGE CONTROL HEADER To start and identify

More information

810 Invoice. X12/V4010/810 : 810 Invoice Version: 2.0 Final

810 Invoice. X12/V4010/810 : 810 Invoice Version: 2.0 Final 810 Invoice X12/V4010/810 : 810 Invoice Version: 2.0 Final Author: D&H Distributors Company: D&H Distributors Publication: 8/15/2016 Modified: 8/12/2016 Notes EDI notes The EDI messages use UTF8/Unicode

More information

832 Price/Sales Catalog

832 Price/Sales Catalog 832 Price/Sales Catalog Functional Group ID=SC Transaction Layout: Heading: ARM Pos. Seg. Req. Loop Notes and Required No. ID Name Des. Max.Use Repeat Comments Required 010 ST Transaction Set Header M

More information

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0 860 Purchase Order Change Request (Buyer Initiated) X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 02/08/2017 1/26/2017 Purchase Order Change Request

More information

EDI Specifications Guide. 856 Customer Advance Ship Notice

EDI Specifications Guide. 856 Customer Advance Ship Notice 856 Customer Advance Ship Notice 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific

More information

850 Purchase Order. X12/V4010/850 : 850 Purchase Order. Version: 1.0 Final

850 Purchase Order. X12/V4010/850 : 850 Purchase Order. Version: 1.0 Final 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 1.0 Final Company: D&H Distributors Publication: 01/28/2015 Modified: 04/08/2016 Current: 04/08/2016 Notes EDI notes The EDI messages use

More information

EDI Specifications Guide. 855 Customer Purchase Order Acknowledgement

EDI Specifications Guide. 855 Customer Purchase Order Acknowledgement 855 Customer Purchase Order Acknowledgement 855 Purchase Order Acknowledgement- Functional Group=PR VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the

More information

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V5010/846: 846 Inventory Inquiry/Advice Author: SPS Commerce Company: Shoe Sensation Publication: 9/7/2016 846 Inventory Inquiry/Advice Functional Group= IB Purpose: This

More information

844 Product Transfer Account

844 Product Transfer Account 844 Product Transfer Account Adjustment Functional Group=CF This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer Account Adjustment Transaction

More information

861 Receiving Advice/Acceptance Certificate

861 Receiving Advice/Acceptance Certificate 861 Receiving Advice/Acceptance Certificate X12/V4010/511 Version: 1.1 Publication: 01.24.2013 www.flextronics.com Version Number Version Date Description of Change Reason of Change Author Change Reference

More information

832 Price/Sales Catalog

832 Price/Sales Catalog 832 Price/Sales Catalog Status: Final Author: Margie Waggoner Publication: 09/25/2007 Notes: This transaction set is used to send information to fulfillment customers about Ingram Entertainmen Inc. products

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order. Version: 2.5 Final

850 Purchase Order. X12/V4010/850: 850 Purchase Order. Version: 2.5 Final 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 2.5 Final Author: Insight Direct USA, Inc. Modified: 07/24/2008 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains

More information

Transaction Set 850 Version 4010VICS, Electronic Purchase Order

Transaction Set 850 Version 4010VICS, Electronic Purchase Order back to Vendor Guide Transaction Set 850 Version 4010VICS, Electronic Purchase Order Segment: ISA - INTERCHANGE CONTROL HEADER Level: ENVELOPE PURPOSE: To start and identify an interchange of one or more

More information

850 Purchase Order. Version: 1.0 Final. X12/V4010/850 : 850 Purchase Order. Advance Auto Parts

850 Purchase Order. Version: 1.0 Final. X12/V4010/850 : 850 Purchase Order. Advance Auto Parts 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 1.0 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 1/15/2013 Current: 10/10/2013 Table of Contents 850 Purchase

More information

Patrick Morin. EDI Implementation Guide for Purchase Order (850) Version

Patrick Morin. EDI Implementation Guide for Purchase Order (850) Version Patrick Morin EDI Implementation Guide for Purchase Order (850) Version 2015-04-21 Contents Contents 2 Introduction 4 Revisions 5 Contacts 6 Patrick Morin... 6 Alligacom Inc.... 6 General Information 7

More information

International Truck and Engine Corporation

International Truck and Engine Corporation International Truck and Engine Corporation EDI 870 -- Order Status Report VERSION: ANSI ASC X12 Version Release 3020 FINAL Publication Date: February 6, 2001 Trading Partner: Truck Marketing Created: January

More information

JR Simplot Agribusiness Ship Notice/Manifest

JR Simplot Agribusiness Ship Notice/Manifest JR Simplot Agribusiness - 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.0 Company: JR Simplot Modified: 8/28/2018 Table of Contents 856 Ship Notice/Manifest.....................................................................................................................

More information

879 - Price Information

879 - Price Information 879 - Price Information Author: DOT FOODS, INC. Publication: September 24, 2008 879 Price Information Functional Group=QG Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

4/4/2018 Purchase Order - 850

4/4/2018 Purchase Order - 850 850 Purchase Order Functional Group=PO Heading: Pos Id Segment Req Max Use Repeat Notes Usage 0200 BEG Beginning Segment for M 1 Must use Purchase Order 0600 PER Administrative O 3 Used Communications

More information

Zappos EDI Guideline. ANSI X Purchase Order. Version: 1.0

Zappos EDI Guideline. ANSI X Purchase Order. Version: 1.0 Zappos EDI Guideline ANSI X12-004010 850 Purchase Order Version: 1.0 Author: Zappos Created: 07/08/2011 Last updated: 05/29/2018 Electronic Data Interchange 850 Purchase Order (Outbound from Zappos, X12

More information

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 DOT FOODS, INC. Distributor 875 Page 1 875 Grocery Products Purchase Order Functional Group=OG This Draft Standard

More information

Purchase Order X12

Purchase Order X12 850 Heading: Purchase Order 005010 X12 Functional Group=PO Pos Id Segment Name Req Max Use Repeat Notes Usage 0200 BEG Beginning Segment for M 1 Must use Purchase Order 0600 PER Administrative O 3 Used

More information

849 Response to Product Transfer

849 Response to Product Transfer 849 Response to Product Transfer Account Adjustment Functional Group=CF This Draft Standard for Trial Use contains the format and establishes the data contents of the Response to Product Transfer Account

More information

862 Shipping Schedule

862 Shipping Schedule AN AIAG IMPLEMENTATION GUIDELINE VERSION 004 RELEASE 010 862 862 Shipping Schedule PREFACE This is the AIAG s recommended usage for the 862 - Shipping Schedule for ASC X12 version release 004010. Prior

More information

ELECTRONIC DATA INTERCHANGE. Implementation Guidelines Outbound Purchase Order

ELECTRONIC DATA INTERCHANGE. Implementation Guidelines Outbound Purchase Order ELECTRONIC DATA INTERCHANGE Implementation Guidelines 850 -- Outbound Purchase Order January 2003 Trading Partner EDI Implementation Guide General Overview Electronic Interchange (EDI) is the computer-to-computer

More information

Raw Loop Data Table of Contents

Raw Loop Data Table of Contents Raw Loop Data Table of Contents 12. RAW LOOP DATA... 2 12.1 BUSINESS DESCRIPTION... 2 12.2 BUSINESS MODEL... 3 12.3 MAPPING EXAMPLES... 4 12.4 DATA DICTIONARY... 7 12.4.1 850 Raw Loop Data Query (850RLDQ)

More information

Purchase Order X12

Purchase Order X12 850 Purchase Order 00500 X2 Functional Group=PO Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 0200 BEG Beginning Segment for M Must use Purchase Order 0600 PER Administrative O 3 Used Communications

More information

Introduction: Notes: Functional Group ID=RQ

Introduction: Notes: Functional Group ID=RQ 836 Procurement Notices Functional Group ID=RQ Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Procurement Notices Transaction Set (836) for

More information

Baker & Taylor 850 EDI Specifications

Baker & Taylor 850 EDI Specifications Baker & Taylor 850 EDI Specifications Version: 1.4 Final Created: 07/31/2003 Notes: Implementation Guide for Vendors 850 Purchase Order Version 4010 850 Purchase Order Functional Group=PO This Draft Standard

More information

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1 850 Purchase Order Functional Group=PO 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

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment 855 Purchase Order Acknowledgment Version: 004010 CNH_855v4010.ecs 1 Table of Contents 855 Purchase Order Acknowledgment... 4 ISA Interchange Control Header... 7 GS Functional Group Header... 9 ST Transaction

More information

Transaction Set 849 Response to Product Transfer Account Adjustment

Transaction Set 849 Response to Product Transfer Account Adjustment The Global Network for B2B Integration in High Tech Industries Transaction Set 849 Response to Product Transfer Account Adjustment Functional Group ID = CF X12 Version 004 Release 010 December 2002 2 Revision

More information

814 General Request, Response or Confirmation

814 General Request, Response or Confirmation 814 General Request, Response or Confirmation Introduction: Functional Group ID=GE This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response

More information