IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS VEHICLE LOGISTICS VISTA ROUTING AND CARRIER INSTRUCTIONS (853) TRANSACTION SET

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

940 Warehouse Shipping Order

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

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

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

870 Order Status Report

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

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

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

824 Application Advice

810 IBM Subset - Invoice To Customer - (004010)

JR Simplot Agribusiness Ship Notice/Manifest

824 Application Advice

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

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

Introduction: Functional Group ID=GF

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

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

Purchase Order Change Request - Buyer Initiated

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

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

824 Application Advice

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.

850 Purchase Order

850 Purchase Order. Version: X12

990 Response to a Load Tender

846 RAPID Inventory Inquiry/Advice Standard

ELECTRONIC DATA INTERCHANGE. Implementation Guidelines Outbound Purchase Order

EDI Specifications Guide. 856 Customer Advance Ship Notice

International Truck and Engine Corporation

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

RCI 855 Purchase Order Acknowledgment

EDI Implementation Guide Version

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

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0

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

3. When the transaction set is accepted with data content change, the corrected data MUST be provided.

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

Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use

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

831 Application Control Totals

862 Shipping Schedule

CVS/Caremark. Implementation Guide. 830 Planning Schedule with Release Capability. Version X

830 Planning Schedule with Release Capability

867 Product Transfer and Resale Report Functional Group=PT

844 Product Transfer Account

855 Purchase Order Acknowledgment. United Natural Foods

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

ANSI X (Advance Shipment Notification) Outbound (from Eclipse) Version 4010

EDI Implementation Guide Version

824 Application Advice

820 Payment Order/Remittance Advice

849 Response to Product Transfer Account Adjustment

888 Item Maintenance Functional Group=QG

Introduction: Heading: Detail: Summary: Functional Group ID=TX

849 Response to Product Transfer

814 General Request, Response or Confirmation

DLMS Implementation Convention (IC) 888W Weapons System Data Change ADC 111, 167, 167A and 1043C DLM

846 Inventory Inquiry/Advice

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS CARRIER PAYMENT ORDER/REMITTANCE ADVICE (820) TRANSACTION SET

846 Inventory Inquiry/Advice

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

ANSI X12 version Receiving Advice/ Acceptance Certificate

816 Organizational Relationships

An example of a routing guide and its ASC X12 interpretation can be found at the back of this guideline.

874 Commodity Movement Services Response

CP EDI 824 Guidelines Version CP EDI 824 Guidelines (Version 4010)

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

860 Purchase Order Change Request - Buyer Initiated

Revised 11/15/17 Booking Confirmation EDI 301. Booking Confirmation. ANSI X Revised 11/15/17

940 Warehouse Shipping Order

861 Receiving Advice/Acceptance Certificate ANSI X.12 Version 5010

990 Response to a Load Tender

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

Product Transfer and Resale Report - 867

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

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

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

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

Golfsmith 846 EDI Guidelines

832 Price/Sales Catalog

International Truck and Engine Corporation

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

850 Purchase Order - v4030

ANSI X (Lockbox) Inbound (to Eclipse) Version 4010

Status Updates Auto Push Table of Contents

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING SCHEDULE (862) TRANSACTION SET

860 Purchase Order Change Request - Buyer Initiated

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

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

Implementation Guide For. Illinois. Electronic Data Interchange CPWB. Transaction Set ANSI ASC X12 Version Drop Request Version 2.

846 Inventory Inquiry/Advice

879 - Price Information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

850 Purchase Order X12 Version Version: 2.0

864 Text Message Mar 2016

EDI Specifications Guide. 832 Customer Price Sales Catalog

Inbound X Version 04010

873 Commodity Movement Services

Transcription:

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS VEHICLE LOGISTICS VISTA ROUTING AND CARRIER INSTRUCTIONS (853) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 004040

853 Routing and Carrier Instruction Introduction: Functional Group ID=RI This X12 Transaction Set contains the format and establishes the data contents of the Routing and Carrier Instruction Transaction Set (853) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the sender with the capability to transmit detailed routing and carrier information pertinent to a route. This transaction set only provides routing information and does not convey information about a shipping event or provide shipping authorization. Notes: The FCA US Vehicle Logistics (VISTA) system will use the 853 to convey route description data and route composition data. 08/17/2010: Name change from DaimlerChrysler to Chrysler Updated Address 03/05/2015: Name Change To FCA US Heading: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments 3 0100 ST Transaction Set Header M M 1 4 0200 BGN Beginning Segment M M 1 0300 NTE Note/Special Instruction O Not 100 0400 G62 Date/Time O Not 10 LOOP ID - N1 200 5 0500 N1 Name M M 1 0600 N2 Additional Name Information O Not 2 0700 N3 Address Information O Not 2 0800 N4 Geographic Location O Not 1 0900 REF Reference Identification O Not 12 1000 PER Administrative Communications Contact O Not 3 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - TD5 200000 6 0100 TD5 Carrier Details (Routing Sequence/Transit Time) M M 1 03/05/2015 V/R 004040 1 FCA US

0200 TD3 Carrier Details (Equipment) O Not 12 0300 TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not 5 0400 NTE Note/Special Instruction O Not 100 8 0500 REF Reference Identification O 200 0600 MEA Measurements O Not 40 0700 FK Factor O Not 1 11 0800 G62 Date/Time O 10 LOOP ID - N1 200 0900 N1 Name O Not 1 1000 N2 Additional Name Information O Not 2 1100 N3 Address Information O Not 2 1200 N4 Geographic Location O Not 1 1300 REF Reference Identification O Not 12 1400 PER Administrative Communications Contact O Not 3 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments 12 0100 CTT Transaction Totals M M 1 n1 13 0200 SE Transaction Set Trailer M M 1 Transaction Set Notes 1. The number of line items (CTT01) is the accumulation of the number of TD5 segments. Hash total (CTT02) is not used in this transaction set. 03/05/2015 V/R 004040 2 FCA US

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. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ST01 143 Transaction Set Identifier Code M 1 ID 3/3 M Code uniquely identifying a Transaction Set 853 Routing and Carrier Instruction ST02 329 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 ST03 1705 Implementation Convention Reference O 1 AN 1/35 Not 03/05/2015 V/R 004040 3 FCA US

Segment: BGN Beginning Segment Position: 0200 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a transaction set Syntax Notes: 1 If BGN05 is present, then BGN04 is required. Semantic Notes: 1 BGN02 is the transaction set reference number. 2 BGN03 is the transaction set date. 3 BGN04 is the transaction set time. 4 BGN05 is the transaction set time qualifier. 5 BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BGN01 353 Transaction Set Purpose Code M 1 ID 2/2 M Code identifying purpose of transaction set 05 Replace BGN02 127 Reference Identification M 1 AN 1/50 M Reference information as defined for a particular Transaction Set or as specified by the This reference number will be the date, time and a sequence number: YYYYMMDDHHMM99999999 BGN03 373 Date M 1 DT 8/8 M Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Transaction set create date BGN04 337 Time X 1 TM 4/8 Not BGN05 623 Time Code O 1 ID 2/2 Not BGN06 127 Reference Identification O 1 AN 1/50 Not BGN07 640 Transaction Type Code O 1 ID 2/2 Not BGN08 306 Action Code O 1 ID 1/2 Not BGN09 786 Security Level Code O 1 ID 2/2 Not 03/05/2015 V/R 004040 4 FCA US

Segment: N1 Name Position: 0500 Loop: N1 Mandatory Level: Heading Usage: Mandatory 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. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N101 98 Entity Identifier Code M 1 ID 2/3 M Code identifying an organizational entity, a physical location, property or an individual CA Carrier N102 93 Name X 1 AN 1/60 Not N103 66 Identification Code Qualifier X 1 ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 93 Code assigned by the organization originating the transaction set N104 67 Identification Code X 1 AN 2/80 Code identifying a party or other code N105 706 Entity Relationship Code O 1 ID 2/2 Not N106 98 Entity Identifier Code O 1 ID 2/3 Not 03/05/2015 V/R 004040 5 FCA US

Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 0100 Loop: TD5 Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify the carrier and sequence of routing and provide transit time information Syntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required. 2 If TD502 is present, then TD503 is required. 3 If TD507 is present, then TD508 is required. 4 If TD510 is present, then TD511 is required. 5 If TD513 is present, then TD512 is required. 6 If TD514 is present, then TD513 is required. 7 If TD515 is present, then TD512 is required. Semantic Notes: 1 TD515 is the country where the service is to be performed. Comments: 1 When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TD501 133 Routing Sequence Code O 1 ID 1/2 Not TD502 66 Identification Code Qualifier X 1 ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 2 Standard Carrier Alpha Code (SCAC) TD503 67 Identification Code X 1 AN 2/80 Not TD504 91 Transportation Method/Type Code X 1 ID 1/2 Not TD505 387 Routing X 1 AN 1/35 Free-form description of the routing or requested routing for shipment, or the originating carrier's identity TD506 368 Shipment/Order Status Code X 1 ID 2/2 Not TD507 309 Location Qualifier O 1 ID 1/2 Code identifying type of location OR Origin (Shipping Point) TD508 310 Location Identifier X 1 AN 1/30 Code which identifies a specific location Route Origin Code 03/05/2015 V/R 004040 6 FCA US

TD509 731 Transit Direction Code O 1 ID 2/2 Not TD510 732 Transit Time Direction Qualifier O 1 ID 2/2 Code specifying the value of time used to measure the transit time SD Surface Days TD511 733 Transit Time X 1 R 1/4 The numeric amount of transit time TD512 284 Service Level Code X 1 ID 2/2 Not TD513 284 Service Level Code X 1 ID 2/2 Not TD514 284 Service Level Code O 1 ID 2/2 Not TD515 26 Country Code O 1 ID 2/3 Not 03/05/2015 V/R 004040 7 FCA US

Segment: REF Reference Identification Position: 0500 Loop: TD5 Mandatory Level: Detail Usage: Optional Max Use: 200 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: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF01 128 M 1 ID 2/3 M Code qualifying the Reference Identification 17 Client Reporting Category AFW Point of Origination AFX Point of Destination AGL Order Origination Code FJ Line Item Control Number QY Service Performed Code UQ Section Number ZZ Mutually Defined REF02 127 Reference Identification X 1 AN 1/50 Reference information as defined for a particular Transaction Set or as specified by the If REF01 = 'AFW', the route origin code; If REF01 = 'AFX', the route destination code; If REF01 = 'AGL', the vehicle shipping order ('Y' = standard route, '1' = first alternate route, '2' = second alternate route, '3' = third alternate route); If REF01 = 'FJ', the route (segment) control code ('X' = Exclude if prior route composition exist, 'S' = Select missing route segment, 'A' = Always include in missing link route composition) If REF01 = 'UQ', the route segment origin code. If REf01 = '17', the carrier report flag ('P' = payment, 'T' = track, 'N' = no track/no pay) If REF01 = 'QY', the move service type: AF ADD FUEL BK BOOKING CB CHARGE-BATTERY CC COMMUN-CHARGE 03/05/2015 V/R 004040 8 FCA US

CL CLEARANCE CS INTERIOR-CLEANING DP DEALER PICKUP DS DINOL-STICKER HC HOMOLOGATION HL HAULAWAY IN INSPECTION LD LOADING LH RAIL LINE HAUL LS PROPERTY-LEASE MM MISCELLANEOUS OF OCEAN FREIGHT PH PAPER HANGING PL PLACARDING PP PORT-PROCESSING RI ROLL-IN RL RELEASING RP REPLACE-PLACARD RS RAIL STORAGE SD STAGE-FOR-DELV SH SHUTTLE SR SPECIAL-REPORTS ST SERV-STORAGE SW RAIL-SWITCHING TC TERMINAL-CHARGE UL UNLOADING WA WAX-ALL WB WAX-UNDER-HOOD WE WAX-ENGINE WH WHARFAGE WS WASH WT WAX-WHEELS WU WAX-UNDERBODY WV WAX-VHCL-BODY WW WASH-WAX REF03 352 Description X 1 AN 1/80 A free-form description to clarify the related data elements and their content If REF01 = 'AFW' or 'AFX', the operational variable (version) related to the route; If REF01 = 'UQ', the operational variable (version) related to the segment; If REF01 = 'ZZ', possible three iterations of route description text; REF04 C040 Reference Identifier O 1 To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier C04001 128 M ID 2/3 M Code qualifying the Reference Identification UQ Section Number 03/05/2015 V/R 004040 9 FCA US

C04002 127 Reference Identification M AN 1/50 M Reference information as defined for a particular Transaction Set or as specified by the If REF04(01) = 'UQ', the route segment destination. C04003 128 X ID 2/3 Code qualifying the Reference Identification 55 Sequence Number C04004 127 Reference Identification X AN 1/50 Reference information as defined for a particular Transaction Set or as specified by the If REF04(03) = '55', the route segment sequence number. C04005 128 X ID 2/3 Not C04006 127 Reference Identification X AN 1/50 Not 03/05/2015 V/R 004040 10 FCA US

Segment: G62 Date/Time Position: 0800 Loop: TD5 Mandatory Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of G6201 or G6203 is required. 2 If either G6201 or G6202 is present, then the other is required. 3 If either G6203 or G6204 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes G6201 432 Date Qualifier X 1 ID 2/2 Code specifying type of date 01 Cancel After This Date 07 Effective Date G6202 373 Date X 1 DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year If G6201 = '07', the effective date of the route; If G6201 = '01', the termination date of the route. G6203 176 Time Qualifier X 1 ID 1/2 Not G6204 337 Time X 1 TM 4/8 Not G6205 623 Time Code O 1 ID 2/2 Not 03/05/2015 V/R 004040 11 FCA US

Segment: CTT Transaction Totals Position: 0100 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CTT01 354 Number of Line Items M 1 N0 1/6 M Total number of line items in the transaction set CTT02 347 Hash Total O 1 R 1/10 Not CTT03 81 Weight X 1 R 1/10 Not CTT04 355 Unit or Basis for Measurement Code X 1 ID 2/2 Not CTT05 183 Volume X 1 R 1/8 Not CTT06 355 Unit or Basis for Measurement Code X 1 ID 2/2 Not CTT07 352 Description O 1 AN 1/80 Not 03/05/2015 V/R 004040 12 FCA US

Segment: SE Transaction Set Trailer Position: 0200 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SE01 96 Number of Included Segments M 1 N0 1/10 M Total number of segments included in a transaction set including ST and SE segments SE02 329 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 03/05/2015 V/R 004040 13 FCA US

Example 1: Route Description Table EDI Format ST~853~0001 BGN~05~20111022090400000001~20111022 N1~CA~~93~45678 Interpretation Transaction Set Identifier Code = 853 (Routing and Carrier Instruction) Transaction Set Control Number = 0001 Transaction Set Purpose Code = 05 (Replace) Reference Identification = 20111022090400000001 Date = 10/22/2011 Entity Identifier Code = CA (Carrier) Identification Code Qualifier = 93 (Code assigned by the organization originating the transaction set) Identification Code = 45678 TD5~~~~~4~~OR~4 Routing = 4 Location Qualifier = OR (Origin <Shipping Point>) Location Identifier = 4 REF~AFW~4~002 REF~AFX~4R~002 REF~AGL~Y = AFW (Point of Origination) Reference Identification = 4 Description = 002 = AFX (Point of Destination) Reference Identification = 4R Description = 002 = AGL (Order Origination Code) Reference Identification = Y REF~ZZ~~(COMJ) TO NWRK DE (CR) NEWRK DE TO CHCGO (CNW) WST = ZZ (Mutually Defined) Description = (COMJ) TO NWRK DE (CR) NEWRK DE TO CHCGO (CNW) WST REF~ZZ~~CH IL (CASF) TO N IL DLR G62~01~20110901 G62~07~20111031 = ZZ (Mutually Defined) Description = CH IL (CASF) TO N IL DLR Date Qualifier = 01 (Cancel After This Date) Date = 09/01/2011 Date Qualifier = 07 (Effective Date) Date = 10/31/2011 03/05/2015 V/R 004040 14 FCA US

Example 1: Route Description Table (continued) EDI Format Interpretation TD5~~~~~4~~OR~4 Routing = 4 Location Qualifier = OR (Origin <Shipping Point>) Location Identifier = 4 REF~AFW~4~001 REF~AFX~41~001 REF~AGL~Y = AFW (Point of Origination) Reference Identification = 4 Description = 001 = AFX (Point of Destination) Reference Identification = 41 Description = 001 = AGL (Order Origination Code) Reference Identification = Y REF~ZZ~~(COMJ) PRT BLTMR TO JESSUP MD (CSX) TO WALLBRDG OH = ZZ (Mutually Defined) Description = (COMJ) PRT BLTMR TO JESSUP MD (CSX) TO WALLBRDG OH REF~ZZ~~RELOAD (CSXT) TO CHCGO IL (BN) KNSS CTY MO (CASF) = ZZ (Mutually Defined) Description = RELOAD (CSXT) TO CHCGO IL (BN) KNSS CTY MO (CASF) REF~ZZ~~TO DLR G62~01~20110901 G62~07~20111031 = ZZ (Mutually Defined) Description = TO DLR Date Qualifier = 01 (Cancel After This Date) Date = 09/01/2011 Date Qualifier = 07 (Effective Date) Date = 10/31/2011 CTT~2 Number of Line Items = 2 SE~23~0001 Number of Included Segments = 23 Transaction Set Control Number = 0001 03/05/2015 V/R 004040 15 FCA US

Example 2: Route Composition Table EDI Format ST~853~0002 BGN~05~20111022092000000002~20111022 N1~CA~~93~45678 TD5~~2~COMJ~~4~~OR~4~~SD~1 REF~17~P REF~AFW~4~001 REF~AFX~4R~001 REF~QY~HL REF~UQ~234000700~001~UQ:221190000:55:01 Interpretation Transaction Set Identifier Code = 853 (Routing and Carrier Instruction) Transaction Set Control Number = 0002 Transaction Set Purpose Code = 05 (Replace) Reference Identification = 20111022092000000002 Date = 10/22/2011 Entity Identifier Code = CA (Carrier) Identification Code Qualifier = 93 (Code assigned by the organization originating the transaction set) Identification Code = 45678 Identification Code Qualifier = 2 (Standard Carrier Alpha Code <SCAC>) Identification Code = COMJ Routing = 4 Location Qualifier = OR (Origin <Shipping Point>) Location Identifier = 4 Transit Time Direction Qualifier = SD (Surface Days) Transit Time = 1 = 17 (Client Reporting Category) Reference Identification = P = AFW (Point of Origination) Reference Identification = 4 Description = 001 = AFX (Point of Destination) Reference Identification = 4R Description = 001 = QY (Service Performed Code) Reference Identification = HL = UQ (Section Number) Reference Identification = 234000700 Description = 001 Reference Identifier = UQ:221190000:55:01 03/05/2015 V/R 004040 16 FCA US

Example 2: Route Composition Table (continued) EDI Format TD5~~2~CR--~~4~~OR~4~~SD~3 REF~17~P REF~AFW~4~002 REF~AFX~41~002 REF~QY~HL REF~UQ~234000700~001~UQ:236389000:55:01 Interpretation Identification Code Qualifier = 2 (Standard Carrier Alpha Code <SCAC>) Identification Code = CR-- Routing = 4 Location Qualifier = OR (Origin <Shipping Point>) Location Identifier = 4 Transit Time Direction Qualifier = SD (Surface Days) Transit Time = 3 = 17 (Client Reporting Category) Reference Identification = P = AFW (Point of Origination) Reference Identification = 4 Description = 002 = AFX (Point of Destination) Reference Identification = 41 Description = 002 = QY (Service Performed Code) Reference Identification = HL = UQ (Section Number) Reference Identification = 234000700 Description = 001 Reference Identifier = UQ:236389000:55:01 CTT~2 Number of Line Items = 2 SE~17~0002 Number of Included Segments = 17 Transaction Set Control Number = 0002 03/05/2015 V/R 004040 17 FCA US