implementation guidelines for ansi asc x12 edi ......loop id - jit 96 24 120 jit just-in-time...

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS

SHIPPING SCHEDULE (862) TRANSACTION SET

FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 002040CHRY

FCA US - Shipping Schedule

862 Shipping Schedule

Functional Group ID=SS

Introduction:

This standard provides the format and establishes the data contents of a shipping schedule transaction set within the context of an electronic data interchange (EDI) environment. The shipping schedule transaction set provides the ability for a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources.

The use of this transaction set will facilitate the practice of Just In Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g.daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.

Notes:

With the launch of Common Ship/Delivery Schedule (CSDS), plants may establish ship and delivery windows which do not necessarily differ by total transit time. In addition, window times within each day and by day of the week may differ. FCA has changed the 862 format to provide transportation suppliers with both shipment based information and delivery based information to facilitate smooth, on-time delivery to its plants. Please refer to Example 7 - Common SDS.

The supplier or carrier should be aware of the following things when programming for this implementation guide

- The date (FST04) and time (FST07) indicated in the FST segment represent when the supplier should SHIP the parts, not when the supplier should deliver the parts to FCA.

- The elements BSS05 and BSS06 represent the horizon start and horizon end dates with a 30 calendar day schedule.

- The resource authorization date (ATH02) is the day prior to the 30 calendar day schedule.

- In the Beginning Segment - Shipping Schedule (BSS), a code value of '04' (Change) in the BSS01 element will be issued for the transmission of requirement changes for selected part numbers only; a code value of '02' (Add) in the BSS01 element will be issued for adding new part numbers or shipment requirements sent in a previous 862 transaction; a code value of '03' (Delete) in the BSS01 element will be issued for removing a part or shipment requirement sent on a previous 862 transaction. Data for other part numbers previously transmitted and not included in this transmission must be retained.

04/17/2019 V/R 002040CHRY 1 FCA US


- Daily adjustments will not be shown in the SHP segment but will be included in the Quantity element (ATH03) of the ATH segment to provide the net adjusted cum requirements. The adjustment no longer needs to be calculated to provide net requirements.

FCA US utilizes an accum based releasing (EDI 830 and 862) process, if your system takes the data and makes a calculation, you should always know where you are.

The calculation is:ATH03 + Today’s FST01 (if there’s no requirement for ‘today’, use FST01 = 0 ) = total amount that should have been shipped by the end of the day on which the EDI 830 was generated.

SHP~02(Cumulative Quantity)~The amount shipped to date ((CHAMPS YTD) if there’s no SHP~02 segment, CHAMPS YTD = 0)~051~99991230~~99991231

SHP~02, element 02 - (ATH03 + Today’s FST01) = status.

If the status is 0, you have fulfilled the current requirement.

If status is less than 0, you have not met the current requirement.

If the status more than 0, you have shipped more than the current requirement.

Metered Parts Kanban Ship Schedule (MSDS)The Metered Parts Kanban Ship Schedule (MSDS) is intended to enable the Split ASN process. The Split ASN process using Kanban is intended to allow an offsite faciility to receive full truckloads of material from suppliers and meter the material to the plant using the MSDS. Material will arrive to the facility a day ahead of when it is to be delivered to the plant. Having projections available prior to the trucks arriving at the offsite facility will allow the trucks to be unloaded and split for the next day's shipments.

DEVIATION TABLE FOR THE DETAIL AREA:1: The NTE segment is used to show the type of SDS part (test, information, or Just In Time).2: This PER segment will provide contact information for the specific part shown in the LIN segment.3. The DTM segment was added to the JIT loop in order to facilitate more flexible shipment/delivery requirements as part of the Common SDS (CSDS) Rewrite.

NOTE: Through this document, 'USER STATUS' and 'USER ATTRIBUTES' refer to the FCA implementation.

Notes about the format of this implementation guide:

1. The requirements contained herein have not changed, with the exception of anything that may appear in the History of Changes section below.2. The term 'Base Status' refers to the requirements as defined by the ASC X12 Standards Organization.3. The terms 'User Status' and 'User Attributes' refer to FCA requirements.4. Data segment sequence tables for each hierarchical level will no longer be presented at the beginning of each hierarchical level. The data segment sequence tables for each hierarchical level will now be presented at the beginning. 5. Segment Syntax and Semantic notes as defined by ASC X12 will now be included where in the 'old' format they were not.

04/17/2019 V/R 002040CHRY 2 FCA US


6. Element Description as defined by ASC X12 will now be included where in the 'old' format they were not. 7. Many comments that relate to a particular code value will now appear underneath the code value description, where previously the comments would appear to the right.

History of Changes:

01/13/2004:Add comments and example (8) for Metered Parts Kanban SDS.

03/01/2004:Add comments and example (9) for Customer EDI.

09/30/2004:Add functionality for (new example) Assembly Kanban: add PO4 segment, add codes to REF segment

07/19/2005:Add code 'A' (Immediate) to forecast qualifier (FST02) for Kanban.

08/04/2005:Add N1 loop for plant extension ship to locations

08/20/2006:Add transportation mode 'I' to both TD5 segments

04/11/2007:Add requirements and example (8) for Web Based Module Ordering (WBMO)

11/15/2007:Transition to Chrysler LLC with removal of references to Daimler

09/21/2010:Name change from Chrysler LLC to ChryslerUpdated Address

10/20/2010:Minor Edits

10/30/2014:Removed requirements and example for Web Based Module Ordering (WBMO).This Is No Longer Supported

03/31/2015:Detail - NTE02 Added New Local Code 'I'Name Change To FCA US

03/10/2017:Detail - REF01 Added Note to Qualifier 'RL'

01/14/2019Detail - Corrected reference of '04000KB' to '04000'KN'

04/17/2019 V/R 002040CHRY 3 FCA US


04/17/2019:Added Notes for Accum Calculation

Heading:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments6 010 ST Transaction Set Header M M 1

7 020 BSS Beginning Segment for Shipping Schedule

M M 1

030 DTM Date/Time/Period O Not Used 10

040 NTE Note/Special Instruction F Not Used 100

043 REF Reference Numbers O Not Used >1

045 PID Product/Item Description O Not Used >1

LOOP ID - N1 200

9 050 N1 Name O 1

060 N2 Additional Name Information O Not Used 2

070 N3 Address Information O Not Used 1

080 N4 Geographic Location O Not Used 1

090 REF Reference Numbers O Not Used 12

100 PER Administrative Communications Contact

O Not Used 3

110 FOB F.O.B. Related Instructions O Not Used 1

Detail:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments

LOOP ID - LIN 10000

11 010 LIN Item Identification O 1

14 020 UIT Unit Detail M M 1

15 030 NTE Note/Special Instruction O 1

16 040 PER Administrative Communications Contact

O 6

17 050 PO4 Item Physical Details O >1

060 PKG Marking, Packaging, Loading O Not Used >1

19 070 REF Reference Numbers O 12

080 SDP Ship/Delivery Pattern O Not Used 1

LOOP ID - N1 200

20 081 N1 Name O 1

082 N2 Additional Name Information O Not Used 2

083 N3 Address Information O Not Used 2

084 N4 Geographic Location O Not Used 1


086 PER Administrative Communications Contact

O Not Used 3

088 FOB F.O.B. Related Instructions O Not Used 1

LOOP ID - FST 100

04/17/2019 V/R 002040CHRY 4 FCA US


21 090 FST Forecast Schedule O 1

23 100 DTM Date/Time/Period O 999999

110 SDQ Destination Quantity O Not Used 999999

LOOP ID - JIT 96

24 120 JIT Just-In-Time Schedule O 1


25 135 DTM Date/Time/Period O 999999

26 140 ATH Resource Authorization O 1

LOOP ID - SHP 10

28 150 SHP Shipped/Received Information O 1


170 TD1 Carrier Details (Quantity and Weight) O Not Used 1

30 175 TD5 Carrier Details (Routing Sequence/Transit Time)

O 1

180 TD3 Carrier Details (Equipment) O Not Used 1

Summary:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments32 010 CTT Transaction Totals M M 1

34 020 SE Transaction Set Trailer M M 1

04/17/2019 V/R 002040CHRY 5 FCA US


Segment: ST Transaction Set Header

Position: 010Loop:

Level: HeadingUsage: Mandatory

Max Use: 1Purpose: To indicate the start of a transaction set and to assign a control number

Syntax Notes:Semantic Notes:

Comments: 1 The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).

Business Rules: Variable Name: STSTNotes: The transaction set control number (ST02) in this header must match the

transaction set control number (SE02) in the transaction set trailer (SE).

Example:ST~862~910601111

Data Element SummaryRef. Data Base User Des. Element Name Attributes Attributes

ST01 143 Transaction Set Identifier Code M ID 3/3 M

Code uniquely identifying a Transaction Set

862 X12.37 Shipping Schedule

ST02 329 Transaction Set Control Number M AN 4/9 M AN 9/9

Identifying control number assigned by the originator for a transaction set.

A unique control number (Same as SE02).

04/17/2019 V/R 002040CHRY 6 FCA US


Segment: BSS Beginning Segment for Shipping Schedule

Position: 020Loop:

Level: HeadingUsage: Mandatory

Max Use: 1Purpose: To indicate the beginning of a shipping schedule.

Syntax Notes: 1 At least one of BSS07 or BSS08 is required.Semantic Notes:

Comments: 1 Use BSS02 to indicate a document number.2 Use BSS03 to indicate the date of this document.3 Use BSS05 to indicate the schedule horizon start date (the date when the

schedule begins.)4 Use BSS06 to indicate the schedule horizon end date (the date when the

schedule ends.)5 BSS08 is the identifying number for a forecast assigned by the

orderer/purchaser.Notes: This segment indicates whether the schedule is shipment or kanban based.

The BSS01 element shows what action is to be taken with this transaction in regard to previous shipping schedules.

Example:BSS~05~910601111~910603~SH~910603~910702~~9106011-11


BSS01 353 Transaction Set Purpose Code M ID 2/2 M

Code identifying purpose of transaction set

02 Add

03 Delete

04 Change

05 Replace

BSS02 127 Reference Number M AN 1/30 M AN 6/30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

The schedule issue date in YYDDDHHMM format

For KANBAN, the schedule issue date will be in YYMMDD format.

BSS03 373 Date M DT 6/6 M

Date (YYMMDD)

Current date.

BSS04 675 Schedule Type Qualifier M ID 2/2 M

04/17/2019 V/R 002040CHRY 7 FCA US


Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast

KB Kanban Signal

SH Shipment Based


Date (YYMMDD)

First day of the thirty calendar day schedule.

For KANBAN, the current date.


Date (YYMMDD)

Last day of the thirty calendar day schedule.

For KANBAN, the current date.

BSS07 328 Release Number C AN 1/30 Not Used

BSS08 127 Reference Number C AN 1/30 AN 6/30


Same as BSS02.

BSS09 367 Contract Number O AN 1/30 Not Used

BSS10 324 Purchase Order Number O AN 1/22 Not Used

BSS11 676 Schedule Quantity Qualifier O ID 1/1 Not Used

04/17/2019 V/R 002040CHRY 8 FCA US


Segment: N1 Name

Position: 050Loop: N1 Optional

Level: HeadingUsage: Optional

Max Use: 1Purpose: 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.

Notes: Three iterations of the N1 loop in the heading area will be used to identify the Shipping Schedule Issuer, the Release Supplier, and the Ship To location. The Ultimate Destination (MA) is not used within the Shipping Schedule.

Example:N1~SI~~92~04000N1~SU~~92~10167ABN1~ST~~92~09106N1~SF~~92~10167AC


N101 98 Entity Identifier Code M ID 2/2 M

Code identifying an organizational entity or a physical location.

SF Ship From

SI Shipping Schedule Issuer

ST Ship To

SU Supplier/Manufacturer

N102 93 Name C AN 1/35 Not Used

N103 66 Identification Code Qualifier C ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

92 Assigned by Buyer

N104 67 Identification Code C ID 2/17 ID 5/17

Code identifying a party.

For FCA issued schedules:If N101 = 'SI', this contains '04000' = FCA Assembly Division; For KANBAN, this element will contain '04000KN'; For Metered Parts Kanban, this element will contain '04000MK';If N101 = 'ST', the FCA assigned receiving plant code;

04/17/2019 V/R 002040CHRY 9 FCA US


If N101 = 'SU', the FCA assigned supplier code of the release supplier. For Metered Parts Kanban, this will be the supplier code or pool point location;If N101 = 'SF', the FCA assigned supplier code of the ship-from location;

For Customer EDI schedules where FCA is the supplier:If N101 = 'SI', the FCA assigned code for the trading partner issuing the schedule;If N101 = 'ST', the FCA assigned code for the ship to location;If N101 = 'SU', the FCA assigned supplier code of the release supplier. For Customer EDI, '04006';

04/17/2019 V/R 002040CHRY 10 FCA US


Segment: LIN Item Identification

Position: 010Loop: LIN Optional

Level: DetailUsage: Optional

Max Use: 1Purpose: To specify basic item identification data

Syntax Notes: 1 If LIN04 is present, then LIN05 is required.2 If LIN06 is present, then LIN07 is required.3 If LIN08 is present, then LIN09 is required.4 If LIN10 is present, then LIN11 is required.5 If LIN12 is present, then LIN13 is required.6 If LIN14 is present, then LIN15 is required.7 If LIN16 is present, then LIN17 is required.8 If LIN18 is present, then LIN19 is required.9 If LIN20 is present, then LIN21 is required.10 If LIN22 is present, then LIN23 is required.11 If LIN24 is present, then LIN25 is required.12 If LIN26 is present, then LIN27 is required.13 If LIN28 is present, then LIN29 is required.14 If LIN30 is present, then LIN31 is required.

Semantic Notes:Comments: 1 See the Data Dictionary for a complete list of ID's.

2 LIN01 is the line item identification3 LIN02 through LIN31 provide for fifteen (15) different product/service ID's

for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.

Notes: This is a mandatory segment and is used to identify the part number.

Clarification on the specification of part number:

When FCA issues the schedule:- BP = FCA part number

When FCA receives the schedule:- BP = Customer part number- VP = FCA part number

Examples:LIN~~BP~04080192AA LIN~~BP~BUYERPART~VP~VENDORPART (Customer EDI)


LIN01 350 Assigned Identification O AN 1/6 Not Used

04/17/2019 V/R 002040CHRY 11 FCA US


LIN02 235 Product/Service ID Qualifier M ID 2/2 M

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP Buyer's Part Number

LIN03 234 Product/Service ID M AN 1/30 M AN 8/30

Identifying number for a product or service

FCA part number.

LIN04 235 Product/Service ID Qualifier O ID 2/2


For KANBAN use only.

JN Job Number

VP Vendor's (Seller's) Part Number

LIN05 234 Product/Service ID C AN 1/30 AN 8/30


If LIN04 = 'JN', for KANBAN use only: KANBAN Job Number;

If LIN04 = 'VP', for Customer EDI only: FCA part number.

LIN06 235 Product/Service ID Qualifier O ID 2/2


For KANBAN use only.

JS Job Sequence Number

LIN07 234 Product/Service ID C AN 1/30


For KANBAN use only: KANBAN Job Sequence Number

LIN08 235 Product/Service ID Qualifier O ID 2/2 Not Used

LIN09 234 Product/Service ID C AN 1/30 Not Used







04/17/2019 V/R 002040CHRY 12 FCA US


















04/17/2019 V/R 002040CHRY 13 FCA US


Segment: UIT Unit Detail


Level: DetailUsage: Mandatory

Max Use: 1Purpose: To specify item unit data


Comments:Notes: This is a mandatory segment and indicates the unit of measure for all quantities

relating to the line item.

Example:UIT~EA


UIT01 355 Unit or Basis for Measurement Code M ID 2/2 M

Code identifying the basic unit of measurement.

EA Each

UIT02 212 Unit Price C R 1/14 Not Used

UIT03 639 Basis of Unit Price Code O ID 2/2 Not Used

04/17/2019 V/R 002040CHRY 14 FCA US


Segment: NTE Note/Special Instruction



Max Use: 1Purpose: To transmit information in a free-form format, if necessary, for comment or special

instructionSyntax Notes:

Semantic Notes:Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12

standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

Notes: This segment is used to provide part information: if the part is a Just In Time part or test part. Not used for Kanban.

Only 1 NTE segment would be created for a particular part.

Note: This segment will be eliminated in the future.

Examples:NTE~LIN~TNTE~LIN~J


NTE01 363 Note Reference Code O ID 3/3

Code identifying the functional area or purpose for which the note applies

LIN Line Item

NTE02 3 Free Form Message M AN 1/60 M AN 1/1

Free-form text

I RILC Routes

J Just In Time

S Supplier Information

T Part In Test Mode

Indicated part is in test mode. Supplier should not ship.

04/17/2019 V/R 002040CHRY 15 FCA US


Segment: PER Administrative Communications Contact



Max Use: 6Purpose: To identify a person or office to whom administrative communications should be

directedSyntax Notes: 1 If PER03 is present, then PER04 is required.

Semantic Notes:Comments:

Notes: This segment is used to convey information about the contact person.

Examples:PER~EX~CONTACT USING PLANT~TE~3139565741PER~EX~DON LAWES~TE~3139561107


PER01 366 Contact Function Code M ID 2/2 M

Code identifying the major duty or responsibility of the person or group named

EX Expeditor

PER02 93 Name O AN 1/35 AN 1/19

Free-form name

The name of the contact person.

PER03 365 Communication Number Qualifier O ID 2/2

Code identifying the type of communication number

TE Telephone

PER04 364 Communication Number C AN 7/256 AN 10/256

Complete communications number including country or area code when applicable

The telephone number of the contact person.

PER05 365 Communication Number Qualifier O ID 2/2

Code identifying the type of communication number

PER06 364 Communication Number O AN 7/256

Complete communications number including country or area code when applicable

04/17/2019 V/R 002040CHRY 16 FCA US


Segment: PO4 Item Physical Details



Max Use: >1Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the

itemSyntax Notes: 1 If PO402 is present, then PO403 is required.

2 If PO405 is present, then at least one of PO406 or PO407 is required.3 If PO408 is present, then PO409 is required.4 If PO413 is present, then at least one of PO410 PO411 or PO412 is required.

Semantic Notes:Comments: 1 PO403 - The "Unit of Measure Code" (Element #355) in this segment position is

for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. Example: If the carton contains 24 12-Ounce packages, it would be described as follows: Element 356 = 24; Element 357 = 12; Element 355 = OZ.

2 PO410 defines the unit of measure for PO408, PO409, and PO410.


PO401 356 Pack O N0 1/6

Number of inner pack units per outer pack unit

PO402 357 Size O R 1/8 Not Used

PO403 355 Unit or Basis for Measurement Code C ID 2/2

Code identifying the basic unit of measurement.

PO404 103 Packaging Code O ID 5/5 Not Used

PO405 187 Weight Qualifier O ID 1/2 Not Used

PO406 384 Gross Weight per Pack C R 1/9 Not Used

PO407 355 Unit or Basis for Measurement Code C ID 2/2 Not Used

PO408 385 Gross Volume per Pack O R 1/9 Not Used


PO410 82 Length C R 1/6 Not Used

PO411 189 Width C R 1/8 Not

04/17/2019 V/R 002040CHRY 17 FCA US


Used

PO412 65 Height C R 1/6 Not Used


04/17/2019 V/R 002040CHRY 18 FCA US


Segment: REF Reference Numbers



Max Use: 12Purpose: To specify identifying numbers.


Comments:Notes: Used to identify the receiving dock, line feed, or drop point of the Ship To

location.

Examples:REF~DK~MAINREF~LF~0001REF~RL~25H1


REF01 128 Reference Number Qualifier M ID 2/2 M

Code qualifying the Reference Number.

DK Dock Number

LF Assembly Line Feed Location

M1 Material Storage Location

RL Reserve Assembly Line Feed Location

Drop Zone

RU Route Number

REF02 127 Reference Number M AN 1/30 M AN 1/8


The FCA assigned name for the location described in REF01.

For Assembly Kanban:If REF01 = 'RL', the bay within the plant (i.e. nearest pole);If REF01 = 'LF', the station;If REF01 = 'RU', the internal plant route;If REF01 = 'M1', the material storage location;

REF03 352 Description O AN 1/80 Not Used

04/17/2019 V/R 002040CHRY 19 FCA US


Segment: N1 Name

Position: 081Loop: N1 Optional


Max Use: 1Purpose: 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.

Notes: This N1 will be used only for those suppliers that should ship to a plant extension.

The N1 loop in the detail area is used to identify physical locations for Ship From, Ship To and the FCA plant for which the material is ultimately intended.

The Ship To location will usually be the FCA plant or a plant extension.

These values must be echoed back to FCA in the ASN (856). If these codes are not accurate, contact your buyer.

Example:

N1~ST~~92~04010 (FCA plant or plant extension)


N101 98 Entity Identifier Code M ID 2/2 M

Code identifying an organizational entity or a physical location.

ST Ship To

N102 93 Name C AN 1/35 Not Used

N103 66 Identification Code Qualifier C ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

92 Assigned by Buyer

N104 67 Identification Code C ID 2/17

Code identifying a party.

04/17/2019 V/R 002040CHRY 20 FCA US


Segment: FST Forecast Schedule

Position: 090Loop: FST Optional


Max Use: 1Purpose: To specify the forecasted dates and quantities

Syntax Notes: 1 If either FST06 or FST07 is present, then the other is required.2 If either FST08 or FST09 is present, then the other is required.

Semantic Notes:Comments: 1 As qualified by FST02 and FST03, FST04 represents either a discrete forecast

date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval.

2 If FST03 - "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.

3 FST06 - To qualify time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock, to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as "AM" or "PM".

Notes: One FST segment represents one of the thirty calendar days for FCA plants.

Examples:FST~100~C~D~910303~~010~0800FST~100~C~D~910322FST~0~C~D~910323FST~1366~D~D~910325FST~360~D~D~910326~~010~0800


FST01 380 Quantity M R 1/10 M R 1/8

Numeric value of quantity

Cumulative quantity for the day.

FST02 680 Forecast Qualifier M ID 1/1 M

Code specifying the sender's confidence level of the forecast data.

A Immediate

For Kanban only: will be used for Hot Pick List - Immediate/Emergency requirements.

C Firm

D Planning

FST03 681 Forecast Timing Qualifier M ID 1/1 M

Code specifying interval grouping of the forecast

D Discrete

04/17/2019 V/R 002040CHRY 21 FCA US


FST04 373 Date M DT 6/6 M

Date (YYMMDD)

If FST03 = 'D', the day the parts are scheduled for shipment.

FST05 373 Date O DT 6/6 Not Used

FST06 374 Date/Time Qualifier C ID 3/3

Code specifying type of date or time, or both date and time

010 Requested Ship

FST07 337 Time C TM 4/4

Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through 235959)

Requested ship time.

FST08 128 Reference Number Qualifier C ID 2/2 Not Used

FST09 127 Reference Number C AN 1/30 Not Used

AN 7/30

04/17/2019 V/R 002040CHRY 22 FCA US


Segment: DTM Date/Time/Period

Position: 100Loop: FST Optional


Max Use: 999999Purpose: To specify pertinent dates and times

Syntax Notes: 1 At least one of DTM02 or DTM03 is required.Semantic Notes:

Comments:Notes: For Common SDS, the segment will be used for delivery date and time when only

one shipment for the day.

Example:DTM~002~930730~0930~CT


DTM01 374 Date/Time Qualifier M ID 3/3 M


002 Delivery Requested

DTM02 373 Date C DT 6/6

Date (YYMMDD)

Date qualified by DTM01.

DTM03 337 Time C TM 4/4


DTM04 623 Time Code O ID 2/2

Code identifying the time.

CD Central Daylight Time

CT Central Time

04/17/2019 V/R 002040CHRY 23 FCA US


Segment: JIT Just-In-Time Schedule

Position: 120Loop: JIT Optional


Max Use: 1Purpose: To identify the specific shipping/delivery time in terms of a 24-hour clock and the

associated quantity.Syntax Notes:

Semantic Notes:Comments:

Notes: The JIT loop is used when there are more than one shipment for the day specified in the FST. All times are Eastern Time.

Used by Metered Parts Kanban.

Not used by (traditional) Kanban.

Example:JIT~100~0800


JIT01 380 Quantity M R 1/10 M


Quantity to be shipped.

JIT02 337 Time M TM 4/4 M


Time of Shipment in 24 hour clock (HHMM).

04/17/2019 V/R 002040CHRY 24 FCA US


Segment: DTM Date/Time/Period

Position: 135Loop: JIT Optional


Max Use: 999999Purpose: To specify pertinent dates and times

Syntax Notes: 1 At least one of DTM02 or DTM03 is required.Semantic Notes:

Comments:


DTM01 374 Date/Time Qualifier M ID 3/3 M


002 Delivery Requested

DTM02 373 Date C DT 6/6

Date (YYMMDD)

DTM03 337 Time C TM 4/4


DTM04 623 Time Code O ID 2/2

Code identifying the time.

04/17/2019 V/R 002040CHRY 25 FCA US


Segment: ATH Resource Authorization



Max Use: 1Purpose: To specify resource authorizations (i.e., finished labor, material, etc.) in the

planning scheduleSyntax Notes: 1 At least one of ATH02 or ATH03 is required.

2 If ATH03 is present, then ATH05 is required.3 If ATH04 is present, then ATH05 is required.

Semantic Notes:Comments: 1 It is imperative that negotiations defining financial commitment have previously

occurred and are agreed to by both buyer and seller.2 ATH02 - Resource Authorization Thru-Date: The date through which the buyer

authorizes the seller to commit the resource defined in element ATH01.3 ATH03 - Current Cumulative Requirements Quantity: The cumulative quantity

that has been authorized to-date from the cumulative start-date (ATH05) through the resource authorization thru-date (ATH02).

4 ATH04 - Maximum Cumulative Requirements Quantity: The maximum cumulative quantity that has been authorized to-date from the cumulative start-date (ATH05) through the resource authorization thru-date (ATH02). This is a high water mark. If the forecast decreases, the current cumulative requirements quantity also decreases, but the maximum cumulative requirements quantity does not decrease.

5 ATH05 - Cumulative Start-Date: The date where the cumulative quantity count starts. This date might be the start-date of a contract period, a calendar or fiscal year, or other.

Notes: The quantity fields in this segment are always cumulative quantities.

Not used by KANBAN.

Example:ATH~PQ~910303~13186~~900715


ATH01 672 Resource Authorization Code M ID 2/2 M

Code identifying the resource which the buyer is authorizing the seller to commit to

PQ Cumulative Quantity Required Prior to First Schedule Period

ATH02 373 Date C DT 6/6

Date (YYMMDD)

This is the day prior to the thirty calendar day forecast.

ATH03 380 Quantity C R 1/10


04/17/2019 V/R 002040CHRY 26 FCA US


This is the cum quantity that has been authorized from the start date (ATH05) through the end date (ATH02). This is a signed field.

ATH04 380 Quantity O R 1/10 Not Used

ATH05 373 Date C DT 6/6

Date (YYMMDD)

CUM start date.

04/17/2019 V/R 002040CHRY 27 FCA US


Segment: SHP Shipped/Received Information

Position: 150Loop: SHP Optional


Max Use: 1Purpose: To specify shipment and/or receipt information

Syntax Notes: 1 If SHP01 is present, then SHP02 is required.2 If SHP03 is present, then SHP04 is required.

Semantic Notes:Comments: 1 The SHP segment is used to communicate shipment, delivery, or receipt

information and may include discrete or cumulative quantities, dates, and times.2 If SHP01 = "02", "07", "08", "09", or "10" (indicating cumulative quantities),

then SHP04 and SHP06 are required to identify the start and end dates of the quantity count.

3 SHP04 - The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).

4 SHP06 - The cumulative quantity end date.Notes: This segment is used to give information on either the last shipment shipped or

the cumulative quantity shipped to date.

Not used by KANBAN.

Examples:SHP~01~856~011~910302SHP~02~13251~051~900715~~910302


SHP01 673 Quantity Qualifier O ID 2/2

Code specifying the type of quantity

01 Discrete Quantity

(i. e., CHAMPS last shipped quantity)

02 Cumulative Quantity

(i. e., CHAMPS YTD shipped quantity)

SHP02 380 Quantity C R 1/10


For SHP01. This is a signed field.

SHP03 374 Date/Time Qualifier O ID 3/3


If SHP01 = '01', use '011';If SHP01 = '02', use '051'.

04/17/2019 V/R 002040CHRY 28 FCA US


011 Shipped

051 Cumulative Quantity Start

SHP04 373 Date C DT 6/6

Date (YYMMDD)

If SHP01 = '01', this is supplier's 'Last Ship Date' from CHAMPS;If SHP01 = '02', this is the 'Beginning Inventory Date' (Same as ATH05).

SHP05 337 Time O TM 4/4 Not Used

SHP06 373 Date C DT 6/6

Date (YYMMDD)

Used if SHP01 = '02' for the 'Last Supplier Ship Date'.

SHP07 337 Time O TM 4/4 Not Used

04/17/2019 V/R 002040CHRY 29 FCA US


Segment: TD5 Carrier Details (Routing Sequence/Transit Time)



Max Use: 1Purpose: To specify the carrier and sequence of routing and provide transit time information

Syntax Notes: 1 At least one of TD502 TD504 or TD505 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.

Semantic Notes: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.

Notes: The data contained in the TD5 segment is information for carrier use when shipping to FCA.

Not used by KANBAN.

Examples:TD5~~~~M~~~~~~SH~0006TD5~~~~GR~~~~~~SH~0012


TD501 133 Routing Sequence Code O ID 1/2 Not Used

TD502 66 Identification Code Qualifier C ID 1/2 Not Used

TD503 67 Identification Code C ID 2/17 Not Used

TD504 91 Transportation Method/Type Code C ID 1/2

Code specifying the method or type of transportation for the shipment

* Pending Data Maintenance request at ANSI ASC X12, code values not assigned.

AC Air Charter

AE Air Express

D Parcel Post

DD Dedicated Delivery Service *

E Expedited Truck

GG Geographic Shipping/Receiving *

GR Geographic Receiving *

04/17/2019 V/R 002040CHRY 30 FCA US


GS Geographic Shipping *

I Common Irregular Carrier

LT Less Than Trailer Load (LTL)

M Motor (Common Carrier)

O Containerized Ocean

PD Parcel Delivery *

RR Roadrailer *

U Private Parcel Service

(UPS)

VE Vessel, Ocean

X Intermodal (Piggyback)

(TOFC/CO-FC)

TD505 387 Routing C AN 1/35 Not Used

TD506 368 Shipment/Order Status Code O ID 2/2 Not Used

TD507 309 Location Qualifier O ID 1/2 Not Used

TD508 310 Location Identifier C AN 1/25 Not Used

TD509 731 Transit Direction Code O ID 2/2 Not Used

TD510 732 Transit Time Direction Qualifier O ID 2/2

Code specifying the value of time used to measure the transit time

SH Surface Hours

TD511 733 Transit Time C R 1/4 R 4/4

The numeric amount of transit time

Integer number of intransit hours (no decimals).

04/17/2019 V/R 002040CHRY 31 FCA US


Segment: CTT Transaction Totals

Position: 010Loop:

Level: SummaryUsage: Mandatory

Max Use: 1Purpose: To transmit a hash total for a specific element in the transaction set

Syntax Notes: 1 If CTT03 is present, then CTT04 is required.2 If CTT05 is present, then CTT06 is required.

Semantic Notes:Comments: 1 This segment is intended to provide hash totals to validate transaction

completeness and correctness.Notes: This segment is mandatory and allows the receiver to perform checks for

completeness and correctness of this transaction set.

Example:CTT~10~298335


CTT01 354 Number of Line Items M N0 1/6 M N0 1/4

Total number of line items in the transaction set

Total Number of 'LIN' segments.

CTT02 347 Hash Total O R 1/10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

Example:

-.0018 First occurrence of value being hashed. .18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence of value being hashed. ------- 1855 Hash total prior to truncation. 855 Hash total after truncation to three-digit field.

The Hash Total of all quantities released (FST01).

CTT03 81 Weight O R 1/8 Not Used

CTT04 355 Unit or Basis for Measurement Code C ID 2/2 Not Used

CTT05 183 Volume O R 1/8 Not Used

CTT06 355 Unit or Basis for Measurement Code C ID 2/2 Not Used

04/17/2019 V/R 002040CHRY 32 FCA US


CTT07 352 Description O AN 1/80 Not Used

04/17/2019 V/R 002040CHRY 33 FCA US


Segment: SE Transaction Set Trailer

Position: 020Loop:

Level: SummaryUsage: Mandatory

Max Use: 1Purpose: 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.

Notes: The transaction set control number value in this trailer must match the same element value in the transaction set header (ST02).

Example:SE~372~910601111


SE01 96 Number of Included Segments M N0 1/6 M

Total number of segments included in a transaction set including ST and SE segments

The count of all segments in this transaction set including the 'ST' and 'SE' segments.

SE02 329 Transaction Set Control Number M AN 4/9 M

Identifying control number assigned by the originator for a transaction set.

Same as ST02.

04/17/2019 V/R 002040CHRY 34 FCA US

FCA US – Shipping Schedule�

01/22/2019 V/R 002040CHRY 34 FCA US

Example 1: Just In Time Shipping Schedule EDI Format Interpretation ST~862~0001 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0001 BSS~05~110601111~110603~SH~110603~110702~~110601111 Transaction Set Purpose Code = “05” (Replace) Reference Number = 110601111 Date = 06/03/2011 Schedule Type Qualifier = “SH” (Shipment Based) Date = 06/03/2011 Date = 07/02/2011 Reference Number = 110601111 N1~SI~~92~04000 Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000 N1~SU~~92~10167AA Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 10167AA N1~ST~~92~09106 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 09106 LIN~~BP~04080192AA Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04080192AA UIT~EA Unit or Basis for Measurement Code = “EA” (Each) NTE~LIN~T Note Reference Code = “LIN” (Line Item) “T” = (Part In Test Mode) PER~EX~DON LAWES~TE~3139561107 Contact Function Code = “EX” (Expeditor) Name = DON LAWES Communication Number Qualifier = “TE” (Telephone) Communication Number = 3139561107 REF~DK~MAIN Reference Number Qualifier = “DK” (Dock Number) Reference Number = MAIN


01/22/2019 V/R 002040CHRY 35 FCA US

Example 1: Just In Time Shipping Schedule (continued) EDI Format Interpretation FST~100~C~D~110603~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/03/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~100~C~D~110604~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/04/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~200~C~D~110605 Quantity = 200 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/05/2011 JIT~100~0800 Quantity = 100 Time = 8:00 AM JIT~100~1100 Quantity = 100 Time = 11:00 AM FST~100~C~D~110606~~010~1100 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/06/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM FST~100~C~D~110607~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/07/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~100~C~D~110610~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/10/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~250~C~D~110613~~010~0800 Quantity = 250 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/13/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM


01/22/2019 V/R 002040CHRY 36 FCA US

Example 1: Just In Time Shipping Schedule (continued) EDI Format Interpretation FST~100~C~D~110614~~010~1000 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/14/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 10:00 AM FST~275~C~D~110617~~010~0900 Quantity = 275 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/17/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~110618~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/18/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~110619~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/19/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~110620~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 06/20/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~200~C~D~110701~~010~0800 Quantity = 200 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 07/01/2011 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM ATH~PQ~110602~13200~~100715 Resource Authorization Code = “PQ” (Cumulative Quantity Required Prior to First Schedule Period) Date = 06/02/2011 Quantity = 13200 Date = 07/15/2010


01/22/2019 V/R 002040CHRY 37 FCA US

Example 1: Just In Time Shipping Schedule (continued) EDI Format Interpretation SHP~01~100~011~110602 Quantity Qualifier = “01” (Discrete Quantity) Quantity = 100 Date/Time Qualifier = “011” (Shipped) Date = 06/02/2011 SHP~02~13251~051~100715~~110602 Quantity Qualifier = “02” (Cumulative Quantity) Quantity = 1810 Date/Time Qualifier = “051” (Cumulative Quantity Start) Date = 07/15/2010 Date = 06/02/2011 CTT~1~1825 Number of Line Items = 1 Hash Total = 1825 SE~30~0001 Number of Included Segments = 30 Transaction Set Control Number = 0001


01/22/2019 V/R 002040CHRY 38 FCA US

Example 2: Kanban EDI Format Interpretation ST~862~0002 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0002 BSS~05~080701~080701~KB~080701~080701~~080701 Transaction Set Purpose Code = “05” (Replace) Reference Number = 080701 Date = 07/01/2008 Schedule Type Qualifier = “KB” (Kanban Signal) Date = 07/01/2008 Date = 07/01/2008 Reference Number = 080701 N1~SI~~92~04000KN Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000KN N1~SU~~92~38303 Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 38303 N1~ST~~92~05207 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 05207 LIN~~BP~0QT41CA1AA~JN~0000000100~JS~0000000001 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0QT41CA1AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000001 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~215~C~D~080313 Quantity = 215 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008


01/22/2019 V/R 002040CHRY 39 FCA US

Example 2: Kanban (continued) EDI Format Interpretation LIN~~BP~04575361AB~JN~0000000100~JS~0000000002 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575361AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000002 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~F45C3 Reference Number Qualifier = “DK” (Dock Number) Reference Number = F45C3 FST~1000~C~D~080313 Quantity = 1000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 LIN~~BP~04575362AB~JN~0000000100~JS~0000000003 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575362AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000003 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~F46D4 Reference Number Qualifier = “DK” (Dock Number) Reference Number = F46D4 FST~300~C~D~080313 Quantity = 300 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008


01/22/2019 V/R 002040CHRY 40 FCA US

Example 2: Kanban (continued) EDI Format Interpretation LIN~~BP~04575670AB~JN~0000000100~JS~0000000004 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575670AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000004 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~C75T7 Reference Number Qualifier = “DK” (Dock Number) Reference Number = C75T7 FST~1000~C~D~080313 Quantity = 1000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 LIN~~BP~04580743~JN~0000000100~JS~0000000005 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580743 Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000005 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~C98G5 Reference Number Qualifier = “DK” (Dock Number) Reference Number = C98G5 FST~5000~C~D~080313 Quantity = 5000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008


01/22/2019 V/R 002040CHRY 41 FCA US

Example 2: Kanban (continued) EDI Format Interpretation LIN~~BP~04580770AA~JN~0000000100~JS~0000000006 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580770AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000006 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~100~C~D~080313 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 LIN~~BP~04580772AA~JN~0000000100~JS~0000000007 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580772AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000007 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~800~C~D~080313 Quantity = 800 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008


01/22/2019 V/R 002040CHRY 42 FCA US

Example 2: Kanban (continued) EDI Format Interpretation LIN~~BP~04591184~JN~0000000100~JS~0000000008 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04591184 Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000008 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~700~C~D~080313 Quantity = 700 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 LIN~~BP~0RB261X9AB~JN~0000000100~JS~0000000009 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0RB261X9AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000009 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~600~C~D~080313 Quantity = 600 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008


01/22/2019 V/R 002040CHRY 43 FCA US

Example 2: Kanban (continued) EDI Format Interpretation LIN~~BP~0RB221X9AB~JN~0000000100~JS~0000000010 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0RB221X9AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000010 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~500~C~D~080313 Quantity = 500 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 LIN~~BP~0QQ06DX9AA~JN~0000000100~JS~0000000011 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0QQ06DX9AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000011 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~215~C~D~080313 Quantity = 215 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 03/13/2008 CTT~11~10430 Number of Line Items = 11 Hash Total = 10430 SE~51~0002 Number of Included Segments = 51 Transaction Set Control Number = 0002


01/22/2019 V/R 002040CHRY 44 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) EDI Format Interpretation ST~862~0003 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0003 BSS~05~102830556~101009~SH~101009~101121~~102830556 Transaction Set Purpose Code = “05” (Replace) Reference Number = 102830556 Date = 10/09/2010 Schedule Type Qualifier = “SH” (Shipment Based) Date = 10/09/2010 Date = 11/21/2010 Reference Number = 102830556 N1~SI~~92~04000 Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000 N1~SU~~92~05203 Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 05203 N1~ST~~92~04088 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04088 LIN~~BP~04781103AB Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04781103AB UIT~EA Unit or Basis for Measurement Code = “EA” (Each) PER~EX~LOCAL CONTROL CONTA~TE~2345678945 Contact Function Code = “EX” (Expeditor) Name = LOCAL CONTROL CONTA Communication Number Qualifier = “TE” (Telephone) Communication Number = 2345678945 REF~DK~T4 Reference Number Qualifier = “DK” (Dock Number) Reference Number = T4 REF~RL~B16S Reference Number Qualifier = “RL” (Reserve Assembly Line Feed Location) Reference Number = B16S


01/22/2019 V/R 002040CHRY 45 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation N1~ST~~92~04088A Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04088A FST~104~C~D~101009 Quantity = 104 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/09/2010 JIT~28~1100 Quantity = 28 Time = 11:00 AM DTM~002~101010~1000 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/10/2010 Time = 10:00 AM JIT~20~1400 Quantity = 20 Time = 2:00 PM DTM~002~101010~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/10/2010 Time = 1:00 PM JIT~28~1700 Quantity = 28 Time = 5:00 PM DTM~002~101010~1600 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/10/2010 Time = 4:00 PM JIT~4~2000 Quantity = 4 Time = 8:00 PM DTM~002~101010~1900 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/10/2010 Time = 7:00 PM JIT~24~2300 Quantity = 24 Time = 11:00 PM DTM~002~101010~2200 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/10/2010 Time = 10:00 PM


01/22/2019 V/R 002040CHRY 46 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation FST~104~C~D~101010 Quantity = 104 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/10/2010 JIT~28~1100 Quantity = 28 Time = 11:00 AM DTM~002~101011~1000 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/11/2010 Time = 10:00 AM JIT~20~1400 Quantity = 20 Time = 2:00 PM DTM~002~101011~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/11/2010 Time = 1:00 PM JIT~28~1700 Quantity = 28 Time = 5:00 PM DTM~002~101011~1600 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/11/2010 Time = 4:00 PM JIT~4~2000 Quantity = 4 Time = 8:00 PM DTM~002~101011~1900 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/11/2010 Time = 7:00 PM JIT~24~2300 Quantity = 24 Time = 11:00 PM DTM~002~101011~2200 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/11/2010 Time = 10:00 PM FST~336~C~D~101011~~010~1100 Quantity = 336 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/11/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM


01/22/2019 V/R 002040CHRY 47 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation DTM~002~101012~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/12/2010 Time = 1:00 PM FST~104~C~D~101012 Quantity = 104 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/12/2010 JIT~28~1100 Quantity = 28 Time = 11:00 AM DTM~002~101013~1000 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/13/2010 Time = 10:00 AM JIT~20~1400 Quantity = 20 Time = 2:00 PM DTM~002~101013~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/13/2010 Time = 1:00 PM JIT~28~1700 Quantity = 28 Time = 5:00 PM DTM~002~101013~1600 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/13/2010 Time = 4:00 PM JIT~4~2000 Quantity = 4 Time = 8:00 PM DTM~002~101013~1900 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/13/2010 Time = 7:00 PM JIT~24~1100 Quantity = 24 Time = 11:00 PM DTM~002~101013~2200 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/13/2010 Time = 10:00 PM


01/22/2019 V/R 002040CHRY 48 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation FST~428~C~D~101013~~010~1100 Quantity = 428 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/13/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101016~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/16/2010 Time = 1:00 PM FST~412~C~D~101016~~010~1100 Quantity = 412 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/16/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101017~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/17/2010 Time = 1:00 PM FST~496~C~D~101017~~010~1100 Quantity = 496 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/17/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101018~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/18/2010 Time = 1:00 PM FST~512~C~D~101018~~010~1100 Quantity = 512 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/18/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101019~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 10/19/2010 Time = 1:00 PM


01/22/2019 V/R 002040CHRY 49 FCA US



01/22/2019 V/R 002040CHRY 50 FCA US



01/22/2019 V/R 002040CHRY 51 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation FST~732~C~D~101031~~010~1100 Quantity = 732 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 10/31/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101101~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 11/01/2010 Time = 1:00 PM FST~760~C~D~101101~~010~1100 Quantity = 760 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 11/01/2010 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM DTM~002~101102~1300 Date/Time Qualifier = “002” (Delivery Requested) Date = 11/02/2010 Time = 1:00 PM ATH~PQ~101006~1800~~100817 Resource Authorization Code = “PQ” (Cumulative Quantity Required Prior to First Schedule Period) Date = 10/06/2010 Quantity = 1800 Date = 08/17/2010 SHP~01~80~011~101006 Quantity Qualifier = “01” (Discrete Quantity) Quantity = 80 Date/Time Qualifier = “011” (Shipped) Date = 10/06/2010 SHP~02~1810~051~100817~~101006 Quantity Qualifier = “02” (Cumulative Quantity) Quantity = 1810 Date/Time Qualifier = “051” (Cumulative Quantity Start) Date = 08/17/2010 Date = 10/06/2010 TD5~~~~M~~~~~~SH~24 Transportation Method/Type Code = “M” (Motor <Common Carrier>) Transit Time Direction Qualifier = “SH” Surface Hours) Transit Time = 24 CTT~1~8792 Number of Line Items = 1 Hash Total = 8792


01/22/2019 V/R 002040CHRY 52 FCA US

Example 3: Common Ship & Delivery Schedule (CSDS) (continued) EDI Format Interpretation SE~80~0003 Number of Included Segments = 80 Transaction Set Control Number = 0003


01/22/2019 V/R 002040CHRY 53 FCA US

Example 4: Metered Parts Kanban SDS EDI Format Interpretation ST~862~0004 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0004 BSS~05~040108~040108~KB~040108~040108~~040108 Transaction Set Purpose Code = “05” (Replace) Reference Number = 040108 Date = 01/08/2004 Schedule Type Qualifier = “KB” (Kanban Signal) Date = 01/08/2004 Date = 01/08/2004 Reference Number = 040108 N1~SI~~92~04000MK Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000MK N1~SU~~92~38303 Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 38303 N1~ST~~92~05207 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 05207 LIN~~BP~0QT41CA1AA~JN~0000000100~JS~0000000001 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0QT41CA1AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000001 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~48~C~D~040108 Quantity = 48 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004


01/22/2019 V/R 002040CHRY 54 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation JIT~28~1100 Quantity = 28 Time = 11:00 AM JIT~20~1400 Quantity = 20 Time = 2:00 PM LIN~~BP~04575361AB~JN~0000000100~JS~0000000002 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575361AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000002 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~58~C~D~040108 Quantity = 58 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~33~1100 Quantity = 33 Time = 11:00 AM JIT~25~1400 Quantity = 25 Time = 2:00 PM LIN~~BP~04575362AB~JN~0000000100~JS~0000000003 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575362AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000003 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~F46D4 Reference Number Qualifier = “DK” (Dock Number) Reference Number = F46D4


01/22/2019 V/R 002040CHRY 55 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation FST~58~C~D~040108 Quantity = 58 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~33~1100 Quantity = 33 Time = 11:00 AM JIT~25~1400 Quantity = 25 Time = 2:00 PM LIN~~BP~04575670AB~JN~0000000100~JS~0000000004 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04575670AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000004 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~C75T7 Reference Number Qualifier = “DK” (Dock Number) Reference Number = C75T7 FST~1000~C~D~040108 Quantity = 1000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~500~1100 Quantity = 500 Time = 11:00 AM JIT~500~1400 Quantity = 500 Time = 2:00 PM LIN~~BP~04580743~JN~0000000100~JS~0000000005 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580743 Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000005 UIT~EA Unit or Basis for Measurement Code = “EA” (Each)


01/22/2019 V/R 002040CHRY 56 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation REF~DK~C98G5 Reference Number Qualifier = “DK” (Dock Number) Reference Number = C98G5 FST~5000~C~D~040108 Quantity = 5000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~1000~0800 Quantity = 1000 Time = 8:00 AM JIT~1000~1100 Quantity = 1000 Time = 11:00 AM JIT~1000~1200 Quantity = 1000 Time = 12:00 PM JIT~1000~1400 Quantity = 1000 Time = 2:00 PM JIT~1000~1600 Quantity = 1000 Time = 4:00 PM LIN~~BP~04580770AA~JN~0000000100~JS~0000000006 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580770AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000006 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~100~C~D~040108 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~75~1100 Quantity = 75 Time = 11:00 AM JIT~25~1400 Quantity = 25 Time = 2:00 PM


01/22/2019 V/R 002040CHRY 57 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation LIN~~BP~04580772AA~JN~0000000100~JS~0000000007 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04580772AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000007 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~800~C~D~040108 Quantity = 800 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~200~0900 Quantity = 200 Time = 9:00 AM JIT~200~1200 Quantity = 200 Time = 12:00 PM JIT~200~1500 Quantity = 200 Time = 3:00 PM JIT~200~1900 Quantity = 200 Time = 7:00 AM LIN~~BP~04591184~JN~0000000100~JS~0000000008 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04591184 Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000008 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6


01/22/2019 V/R 002040CHRY 58 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation FST~800~C~D~040108 Quantity = 800 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~200~1100 Quantity = 200 Time = 11:00 AM JIT~200~1400 Quantity = 200 Time = 2:00 PM JIT~200~1800 Quantity = 200 Time = 6:00 PM JIT~200~2000 Quantity = 200 Time = 8:00 PM LIN~~BP~0RB261X9AB~JN~0000000100~JS~0000000009 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0RB261X9AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000009 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~200~C~D~040108 Quantity = 200 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~150~1100 Quantity = 150 Time = 11:00 AM JIT~50~1400 Quantity = 50 Time = 2:00 PM


01/22/2019 V/R 002040CHRY 59 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation LIN~~BP~0RB221X9AB~JN~0000000100~JS~0000000010 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0RB221X9AB Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000010 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6 FST~500~C~D~040108 Quantity = 500 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~200~1100 Quantity = 200 Time = 11:00 AM JIT~200~1400 Quantity = 200 Time = 2:00 PM JIT~100~1600 Quantity = 100 Time = 4:00 PM LIN~~BP~0QQ06DX9AA~JN~0000000100~JS~0000000011 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 0QQ06DX9AA Product/Service ID Qualifier = “JN” (Job Number) Product/Service ID = 0000000100 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 0000000011 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) REF~DK~A05B6 Reference Number Qualifier = “DK” (Dock Number) Reference Number = A05B6


01/22/2019 V/R 002040CHRY 60 FCA US

Example 4: Metered Parts Kanban SDS (continued) EDI Format Interpretation FST~215~C~D~040108 Quantity = 215 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 01/08/2004 JIT~75~1100 Quantity = 75 Time = 11:00 AM JIT~75~1400 Quantity = 75 Time = 2:00 PM JIT~65~1800 Quantity = 65 Time = 6:00 PM CTT~11~8779 Number of Line Items = 11 Hash Total = 8779 SE~82~0004 Number of Included Segments = 82 Transaction Set Control Number = 0004


01/22/2019 V/R 002040CHRY 61 FCA US

Example 5: Assembly Kanban SDS EDI Format Interpretation ST~862~0005 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0005 BSS~05~040929~040929~KB~040929~040929~~040929 Transaction Set Purpose Code = “05” (Replace) Reference Number = 040929 Date = 09/29/2004 Schedule Type Qualifier = “KB” (Kanban Signal) Date = 09/29/2004 Date = 09/29/2004 Reference Number = 040929 N1~SI~~92~04000KN Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000KN N1~SU~~92~38303 Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 38303 N1~ST~~92~04025 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04025 LIN~~BP~06506048AA~~~JS~20 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 06506048AA Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 20 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) PO4~1000~~EA Pack = 1000 Unit or Basis for Measurement Code = EA REF~DK~44 Reference Number Qualifier = “DK” (Dock Number) Reference Number = 44 REF~RL~B27 Reference Number Qualifier = “RL” (Reserve Assembly Line Feed Location) Reference Number = B27


01/22/2019 V/R 002040CHRY 62 FCA US

Example 5: Assembly Kanban SDS (continued) EDI Format Interpretation REF~LF~1577L Reference Number Qualifier = “LF” (Assembly Line Feed Location) Reference Number = 1577L REF~RU~TEXTRN Reference Number Qualifier = “RU” (Route Number) Reference Number = TEXTRN REF~M1~T1-10 Reference Number Qualifier = “M1” (Material Storage Location) Reference Number = T1-10 FST~1000~C~D~040929 Quantity = 1000 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 09/29/2004 JIT~1000~1400 Quantity = 1000 Time = 2:00 PM LIN~~BP~06101446~~~JS~70 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 06101446 Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 70 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) PO4~900~~EA Pack = 900 Unit or Basis for Measurement Code = EA REF~DK~44 Reference Number Qualifier = “DK” (Dock Number) Reference Number = 44 REF~RL~B18 Reference Number Qualifier = “RL” (Reserve Assembly Line Feed Location) Reference Number = B18 REF~LF~1598L Reference Number Qualifier = “LF” (Assembly Line Feed Location) Reference Number = 1598L REF~RU~TEXTRN Reference Number Qualifier = “RU” (Route Number) Reference Number = TEXTRN REF~M1~M1-5 Reference Number Qualifier = “M1” (Material Storage Location) Reference Number = M1-5


01/22/2019 V/R 002040CHRY 63 FCA US

Example 5: Assembly Kanban SDS (continued) EDI Format Interpretation FST~1800~C~D~040929 Quantity = 1800 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 09/29/2004 JIT~1800~1400 Quantity = 1800 Time = 2:00 PM LIN~~BP~06505837AA~~~JS~412 Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 06505837AA Product/Service ID Qualifier = “JS” (Job Sequence Number) Product/Service ID = 412 UIT~EA Unit or Basis for Measurement Code = “EA” (Each) PO4~500~~EA Pack = 500 Unit or Basis for Measurement Code = EA REF~DK~44 Reference Number Qualifier = “DK” (Dock Number) Reference Number = 44 REF~RL~C19 Reference Number Qualifier = “RL” (Reserve Assembly Line Feed Location) Reference Number = C19 REF~LF~1646L Reference Number Qualifier = “LF” (Assembly Line Feed Location) Reference Number = 1646L REF~RU~TEXTRN Reference Number Qualifier = “RU” (Route Number) Reference Number = TEXTRN REF~M1~T1-4 Reference Number Qualifier = “M1” (Material Storage Location) Reference Number = T1-4 FST~1500~C~D~040929 Quantity = 1500 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 09/29/2004 JIT~1500~1400 Quantity = 1500 Time = 2:00 PM CTT~3~4300 Number of Line Items = 3 Hash Total = 4300


01/22/2019 V/R 002040CHRY 64 FCA US

Example 5: Assembly Kanban SDS (continued) EDI Format Interpretation SE~37~0005 Number of Included Segments = 37 Transaction Set Control Number = 0005


01/22/2019 V/R 002040CHRY 65 FCA US

Example 6: Shipments to Plant Extensions EDI Format Interpretation ST~862~0006 Transaction Set Identifier Code = “862” (X12.37 Shipping Schedule) Transaction Set Control Number = 0006 BSS~05~052130407~050801~SH~050801~050830~~052130407 Transaction Set Purpose Code = “05” (Replace) Reference Number = 052130407 Date = 08/01/2005 Schedule Type Qualifier = “SH” (Shipment Based) Date = 08/01/2005 Date = 08/30/2005 Reference Number = 052130407 N1~SI~~92~04000 Entity Identifier Code = “SI” (Shipping Schedule Issuer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 04000 N1~SU~~92~10167AA Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 10167AA N1~ST~~92~09106 Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 09106 LIN~~BP~04080192AA Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = 04080192AA UIT~EA Unit or Basis for Measurement Code = “EA” (Each) NTE~LIN~T Note Reference Code = “LIN” (Line Item) “T” = (Part In Test Mode) PER~EX~DON LAWES~TE~3139561107 Contact Function Code = “EX” (Expeditor) Name = DON LAWES Communication Number Qualifier = “TE” (Telephone) Communication Number = 3139561107 REF~DK~MAIN Reference Number Qualifier = “DK” (Dock Number) Reference Number = MAIN


01/22/2019 V/R 002040CHRY 66 FCA US

Example 6: Shipments to Plant Extensions (continued) EDI Format Interpretation N1~ST~~92~09106A Entity Identifier Code = “ST” (Ship To) Identification Code Qualifier = “92” (Assigned by Buyer) Identification Code = 09106A FST~100~C~D~050801~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/01/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~100~C~D~050802~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/02/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~200~C~D~050803 Quantity = 200 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/03/2005 JIT~100~0800 Quantity = 100 Time = 8:00 AM JIT~100~1100 Quantity = 100 Time = 11:00 AM FST~100~C~D~050804~~010~1100 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/04/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 11:00 AM FST~100~C~D~050805~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/05/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~100~C~D~050808~~010~0800 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/08/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM


01/22/2019 V/R 002040CHRY 67 FCA US

Example 6: Shipments to Plant Extensions (continued) EDI Format Interpretation FST~250~C~D~050809~~010~0800 Quantity = 250 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/09/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM FST~100~C~D~050810~~010~1000 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/10/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 10:00 AM FST~275~C~D~050811~~010~0900 Quantity = 275 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/11/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~050812~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/12/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~050815~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/15/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~100~C~D~050816~~010~0900 Quantity = 100 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/16/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 9:00 AM FST~200~C~D~050817~~010~0800 Quantity = 200 Forecast Qualifier = “C” (Firm) Forecast Timing Qualifier = “D” (Discrete) Date = 08/17/2005 Date/Time Qualifier = “010” (Requested Ship) Time = 8:00 AM


01/22/2019 V/R 002040CHRY 68 FCA US

Example 6: Shipments to Plant Extensions (continued) EDI Format Interpretation ATH~PQ~110602~13200~~100715 Resource Authorization Code = “PQ” (Cumulative Quantity Required Prior to First Schedule Period) Date = 06/02/2011 Quantity = 13200 Date = 07/15/2010 SHP~01~100~011~110602 Quantity Qualifier = “01” (Discrete Quantity) Quantity = 100 Date/Time Qualifier = “011” (Shipped) Date = 06/02/2011 SHP~02~13251~051~100715~~110602 Quantity Qualifier = “02” (Cumulative Quantity) Quantity = 1810 Date/Time Qualifier = “051” (Cumulative Quantity Start) Date = 07/15/2010 Date = 06/02/2011 CTT~1~1825 Number of Line Items = 1 Hash Total = 1825 SE~35~0006 Number of Included Segments = 35 Transaction Set Control Number = 0006

implementation guidelines for ansi asc x12 edi ......loop id - jit 96 24 120 jit just-in-time...

Documents