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

Transcription

1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING SCHEDULE (862) DAIMLERCHRYSLER CORPORATION INFORMATION TECHNOLOGY MANAGEMENT 800 CHRYSLER DRIVE AUBURN HILLS, MI CIMS ANSI ASC X12 VERSION/RELEASE CHRY

2 DaimlerChrysler Corporation 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 Carrier Ship/Delivery Schedule (CSDS), plants may establish ship and delivery windows which do not necessarily differ by total transit time. In addition, widow times within each day and by day of the week may differ. DaimlerChrysler 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 - Carrier 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 DaimlerChrysler. - 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. 09/09/2002 DaimlerChrysler Corporation

3 DaimlerChrysler Corporation - 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. For Suppliers to Mitsubishi Motors Manufacturing of America (MMMA) Component Supply Agreement (CSA) Suppliers will be receiving the Shipping Schedule (862) and sending the Ship Notice (856) through the DaimlerChrysler EDI System. The 862 will contain the MMMA Release Authorization Number (RAN) and a carrier route code for every delivery. They must be returned in the 856. 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 TD5 was added to indicate the method of transportation and intransit hours. For MMMA, the TD5 segment will be after the DTM segment in the FST loop instead of after the TD1 segment at the end of the LIN loop. 4. The DTM segment was added to the JIT loop in order to facilitate more flexible shipment/delivery requirements as part of the Carrier SDS (CSDS) Rewrite. NOTE: Through this document, 'USER STATUS' and 'USER ATTRIBUTES' refer to the DaimlerChrysler implementation. Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BSS Beginning Segment for Shipping Schedule M 1 Not Used 030 DTM Date/Time/Period O 10 Not Used 040 NTE Note/Special Instruction F 100 LOOP ID - N N1 Name O 1 Not Used 060 N2 Additional Name Information O 2 Not Used 070 N3 Address Information O 1 Not Used 080 N4 Geographic Location O 1 Not Used 090 REF Reference Numbers O 12 Not Used 100 PER Administrative Communications Contact O 3 Not Used 110 FOB F.O.B. Related Instructions O 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - LIN LIN Item Identification O 1 M 020 UIT Unit Detail M 1 09/09/ DaimlerChrysler Corporation

4 DaimlerChrysler Corporation 030 NTE Note/Special Instruction O PER Administrative Communications Contact O 6 Not Used 050 PO4 Item Physical Details O >1 Not Used 060 PKG Marking, Packaging, Loading O >1 070 REF Reference Numbers O 12 Not Used 080 SDP Ship/Delivery Pattern O 1 LOOP ID - FST FST Forecast Schedule O DTM Date/Time/Period O TD5 Carrier Details (Routing Sequence/Transit Time) O 1 Not Used 110 SDQ Destination Quantity O LOOP ID - JIT JIT Just-In-Time Schedule O 1 Not Used 130 REF Reference Numbers O DTM Date/Time/Period O ATH Resource Authorization O 1 LOOP ID - SHP SHP Shipped/Received Information O 1 Not Used 160 REF Reference Numbers O 12 Not Used 170 TD1 Carrier Details (Quantity and Weight) O TD5 Carrier Details (Routing Sequence/Transit Time) O 1 Not Used 180 TD3 Carrier Details (Equipment) O 1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 CTT Transaction Totals M 1 M 020 SE Transaction Set Trailer M 1 09/09/ DaimlerChrysler Corporation

5 DaimlerChrysler Corporation Segment: ST Transaction Set Header Position: 010 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: 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). Notes: 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* Data Element Summary Ref. Data Des. Element Name Attributes M ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 862 X12.37 Shipping Schedule M ST Transaction Set Control Number M AN 9/9 Identifying control number assigned by the originator for a transaction set. A unique control number (Same as SE02). 09/09/ DaimlerChrysler Corporation

6 DaimlerChrysler Corporation Segment: BSS Beginning Segment for Shipping Schedule Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: 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. For Mitsubishi Motors Manufacturing of America (MMMA), code "01" = Cancel is used for cancelling specific RAN numbers. EXAMPLE: BSS*05* *910603*SH*910603*910702** Data Element Summary Ref. Data Des. Element Name Attributes M BSS Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 01 Cancellation 02 Add 03 Delete 04 Change 05 Replace For Mitsubishi Motors Manufacturing of America (MMMA) use only. Used for cancelling specific RAN numbers. M BSS Reference Number M AN 9/9 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 09/09/ DaimlerChrysler Corporation

7 DaimlerChrysler Corporation For KANBAN, the schedule issue date will be in YYMMDD format. M BSS Date M DT 6/6 Date (YYMMDD) Current date. M BSS Schedule Type Qualifier M ID 2/2 Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast KB SH Kanban Signal Shipment Based M BSS Date M DT 6/6 Date (YYMMDD) First day of the thirty calendar day schedule. For KANBAN, the current date. M BSS Date M DT 6/6 Date (YYMMDD) Last day of the thirty calendar day schedule. For KANBAN, the current date. Not Used BSS Release Number C AN 1/30 Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction BSS Reference Number C AN 9/9 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Same as BSS02. Not Used BSS Contract Number O AN 1/30 Contract number Not Used BSS Purchase Order Number O AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser Not Used BSS Schedule Quantity Qualifier O ID 1/1 Code identifying the type of quantities used when defining a schedule or forecast 09/09/ DaimlerChrysler Corporation

8 DaimlerChrysler Corporation Segment: N1 Name Position: 050 Loop: N1 Optional Level: Heading Usage: Optional 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. 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. EXAMPLES: N1*SI**92*04000 N1*SU**92*10167AB N1*ST**92*09106 N1*SF**92*10167AC Data Element Summary Ref. Data Des. Element Name Attributes M N Entity Identifier Code M ID 2/2 Code identifying an organizational entity or a physical location. SF SI ST SU Ship From Shipping Schedule Issuer Ship To Supplier/Manufacturer Not Used N Name C AN 1/35 Free-form name N Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer N Identification Code C ID 5/7 Code identifying a party. If N101 = "SI", this contains "04000" = DaimlerChrysler Assembly Division; For KANBAN, this element will contain "04000KB" If N101 = "ST", the DaimlerChrysler-assigned receiving plant code; 09/09/ DaimlerChrysler Corporation

9 DaimlerChrysler Corporation If N101 = "SU", the DaimlerChrysler-assigned supplier code of the release supplier. If N101 = "SF", the DaimlerChrysler-assigned supplier code of the ship -from location. 09/09/ DaimlerChrysler Corporation

10 DaimlerChrysler Corporation Segment: LIN Item Identification Position: 010 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: 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 identification 3 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 DaimlerChrysler or MMMA part number. EXAMPLES: LIN**BP* AA LIN**BP*M V (MMMA) Data Element Summary Ref. Data Des. Element Name Attributes Not Used LIN Assigned Identification O AN 1/6 Alphanumeric characters assigned for differentiationwithin a transaction set. M LIN Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number M LIN Product/Service ID M AN 8/10 Identifying number for a product or service 09/09/ DaimlerChrysler Corporation

11 DaimlerChrysler Corporation DaimlerChrysler or MMMA part number. LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) For KANBAN use only. JN Job Number LIN Product/Service ID C AN 8/10 Identifying number for a product or service For KANBAN use only: KANBAN Job Number LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) For KANBAN use only. JS Job Sequence Number LIN Product/Service ID C AN 1/30 Identifying number for a product or service For KANBAN use only: KANBAN Job Sequence Number Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 09/09/ DaimlerChrysler Corporation

12 DaimlerChrysler Corporation Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service Not Used LIN Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not Used LIN Product/Service ID C AN 1/30 Identifying number for a product or service 09/09/ DaimlerChrysler Corporation

13 DaimlerChrysler Corporation Segment: UIT Unit Detail Position: 020 Loop: LIN Optional Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify item unit data Syntax Notes: Semantic Notes: Comments: Notes: This is a mandatory segment and indicates the unit of measure for all quantities relating to the line item. EXAMPLE: UIT*EA Data Element Summary Ref. Data Des. Element Name Attributes M UIT Unit or Basis for Measurement Code M ID 2/2 Code identifying the basic unit of measurement. EA Each Not Used UIT Unit Price C R 1/14 Price per unit of product, service, commodity, etc. Not Used UIT Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item 09/09/ DaimlerChrysler Corporation

14 DaimlerChrysler Corporation Segment: NTE Note/Special Instruction Position: 030 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax 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 MMMA or Kanban. Only 1 NTE segment would be created for a particular part. Note: This segment will be eliminated in the future. EXAMPLES: NTE*LIN*T NTE*LIN*J Data Element Summary Ref. Data Des. Element Name Attributes NTE Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies LIN Line Item M NTE02 3 Free Form Message M AN 1/1 Free-form text J S T Just In Time Supplier information Part in test mode 09/09/ DaimlerChrysler Corporation

15 DaimlerChrysler Corporation Segment: PER Administrative Communications Contact Position: 040 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 6 Purpose: To identify a person or office to whom administrative communications should be directed Syntax 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* PER*EX*DON LAWES*TE* Data Element Summary Ref. Data Des. Element Name Attributes M PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named EX Expeditor PER02 93 Name O AN 1/19 Free-form name The name of the contact person. PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number TE Telephone PER Communication Number C AN 10/10 Complete communications number including country or area code when applicable The telephone number of the contact person. 09/09/ DaimlerChrysler Corporation

16 DaimlerChrysler Corporation Segment: REF Reference Numbers Position: 070 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 12 Purpose: To specify identifying numbers. Syntax Notes: Semantic Notes: Comments: Notes: Used to identify the receiving dock, line feed, or drop point of the Ship To location. EXAMPLES: REF*DK*MAIN REF*LF*0001 REF*RL*25H1 Data Element Summary Ref. Data Des. Element Name Attributes M REF Reference Number Qualifier M ID 2/2 Code qualifying the Reference Number. DK LF RL Dock Number Assembly Line Feed Location Reserve Assembly Line Feed Location M REF Reference Number M AN 1/8 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. The DaimlerChrysler-assigned name for the location described in REF01. Not Used REF Description O AN 1/80 A free-form description to clarify the related data elements and their content 09/09/ DaimlerChrysler Corporation

17 DaimlerChrysler Corporation Segment: FST Forecast Schedule Position: 090 Loop: FST Optional Level: Detail Usage: Optional Max Use: 1 Purpose: 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 DaimlerChrysler plants. MMMA will use the FST to distinguish the RAN number for each shipment. MMMA will not use the JIT segment. Instead a set of FST/DTM/TD5 segments will be used for each shipment. If a shipment will result in multiple deliveries, then multiple FST/DTM/TD5 segment sets will still be used. (See Transaction Set Example #2). EXAMPLES: FST*100*C*D*910303**010*0800 FST*100*C*D* FST*0*C*D* FST*1366*D*D* FST*360*D*D*910326**010*0800 FST*360*C*D*921113**010*1400*RE*AB12345 (MMMA) Data Element Summary Ref. Data Des. Element Name Attributes M FST Quantity M R 1/8 Numeric value of quantity Cumulative quantity for the day. M FST Forecast Qualifier M ID 1/1 Code specifying the sender's confidence level of the forecast data. 09/09/ DaimlerChrysler Corporation

18 DaimlerChrysler Corporation C D Firm Planning M FST Forecast Timing Qualifier M ID 1/1 Code specifying interval grouping of the forecast D Discrete M FST Date M DT 6/6 Date (YYMMDD) If FST03 = "D", the day the parts are scheduled for shipment. Not Used FST Date O DT 6/6 Date (YYMMDD) FST Date/Time Qualifier C ID 3/3 Code specifying type of date or time, or both date and time 010 Requested Ship FST Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) Requested ship time. FST Reference Number Qualifier C ID 2/2 Code qualifying the Reference Number. For MMMA only RE Release Number Release Number (RAN) for MMMA FST Reference Number C AN 7/7 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. For MMMA only: MMMA RAN number. 09/09/ DaimlerChrysler Corporation

19 DaimlerChrysler Corporation Segment: DTM Date/Time/Period Position: 100 Loop: FST Optional Level: Detail Usage: Optional Max Use: Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: For MMMA for delivery date and time for the RAN in the preceding FST segment. The delivery date and time must be printed on the bar coded label for that RAN. For Carrier SDS, the segment will be used for delivery date and time when only one shipment for the day. EXAMPLES: DTM*002*930730*0930*CT Data Element Summary Ref. Data Des. Element Name Attributes M DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 002 Delivery Requested DTM Date C DT 6/6 Date (YYMMDD) Date qualified by DTM01. DTM Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) DTM Time Code O ID 2/2 Code identifying the time. For MMMA only. CD Central Daylight Time CT Central Time 09/09/ DaimlerChrysler Corporation

20 DaimlerChrysler Corporation Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 105 Loop: FST Optional Level: Detail Usage: Optional 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 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 MMMA. For MMMA, the TD5 segment is used to show the SCAC code and the routing code for the pick up carrier. The TD5 segment in the FST loop will only be used for DSM shipments. Not used by KANBAN. EXAMPLES: TD5**2*GXCC*DD* (MMMA) Data Element Summary Ref. Data Des. Element Name Attributes Not Used TD Routing Sequence Code O ID 1/2 Code describing the relationship of a carrier to a specific shipment movement TD Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) For MMMA use only. 2 Standard Carrier Alpha Code (SCAC) TD Identification Code C ID 2/17 Code identifying a party. For MMMA use only: SCAC code for the pick up carrier. TD Transportation Method/Type Code C ID 1/2 Code specifying the method or type of transportation for the shipment 09/09/ DaimlerChrysler Corporation

21 DaimlerChrysler Corporation AC AE D Air Charter Air Express Parcel Post DD Dedicated Delivery Service * E Expedited Truck GG Geographic Shipping/Receiving * GR Geographic Receiving * GS Geographic Shipping * LT M O PC Less Than Trailer Load (LTL) Motor (Common Carrier) (Trailer Load) Containerized Ocean Private Carrier PD Parcel Delivery * R Rail RR Roadrailer * U VE X Private Parcel Service (UPS) Vessel, Ocean Intermodal (Piggyback) (TOFC/CO-FC) TD Routing C AN 1/35 Free-form description of the routing or requested routing for shipment, or the originating carrier's identity For MMMA use only: The Routing Code to be sent on the ASN (856). Not Used TD Shipment/Order Status Code O ID 2/2 Code indicating the status of an order or shipment Not Used TD Location Qualifier O ID 1/2 Code identifying type of Location Identifier (310) used. Not Used TD Location Identifier C AN 1/25 Code which identifies a specific location Not Used TD Transit Direction Code O ID 2/2 The point of origin and point of direction Not Used TD Transit Time Direction Qualifier O ID 2/2 Code specifying the value of time used to measure the transit time Not Used TD Transit Time C R 1/4 The numeric amount of transit time 09/09/ DaimlerChrysler Corporation

22 DaimlerChrysler Corporation Segment: JIT Just-In-Time Schedule Position: 120 Loop: JIT Optional Level: Detail Usage: Optional Max Use: 1 Purpose: 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. Not used by MMMA or KANBAN. EXAMPLE: JIT*100*0800 Data Element Summary Ref. Data Des. Element Name Attributes M JIT Quantity M R 1/10 Numeric value of quantity Quantity to be shipped. M JIT Time M TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) Time of Shipment in 24 hour clock (HHMM). 09/09/ DaimlerChrysler Corporation

23 DaimlerChrysler Corporation Segment: DTM Date/Time/Period Position: 135 Loop: JIT Optional Level: Detail Usage: Optional Max Use: Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes M DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 002 Delivery Requested DTM Date C DT 6/6 Date (YYMMDD) DTM Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) DTM Time Code O ID 2/2 Code identifying the time. 09/09/ DaimlerChrysler Corporation

24 DaimlerChrysler Corporation Segment: ATH Resource Authorization Position: 140 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule Syntax 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** Data Element Summary Ref. Data Des. Element Name Attributes M ATH Resource Authorization Code M ID 2/2 Code identifying the resource which the buyer is authorizing the seller to commit to PQ Cumulative Quantity Required Prior to First Schedule Period ATH Date C DT 6/6 Date (YYMMDD) This is the day prior to the thirty calendar day forecast. 09/09/ DaimlerChrysler Corporation

25 DaimlerChrysler Corporation ATH Quantity C R 1/10 Numeric value of quantity This is the cum quantity that has been authorized from the start date (ATH05) through the end date (ATH02). This is a signed field. Not Used ATH Quantity O R 1/10 Numeric value of quantity ATH Date C DT 6/6 Date (YYMMDD) CUM start date. 09/09/ DaimlerChrysler Corporation

26 DaimlerChrysler Corporation Segment: SHP Shipped/Received Information Position: 150 Loop: SHP Optional Level: Detail Usage: Optional Max Use: 1 Purpose: 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* SHP*02*13251*051*900715** Data Element Summary Ref. Data Des. Element Name Attributes SHP 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) SHP Quantity C R 1/8 Numeric value of quantity For SHP01. This is a signed field. SHP Date/Time Qualifier O ID 3/3 Code specifying type of date or time, or both date and time If SHP01 = "01", use "011"; If SHP01 = "02", use "051". 09/09/ DaimlerChrysler Corporation

27 DaimlerChrysler Corporation 011 Shipped 051 Cumulative Quantity Start SHP 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). Not Used SHP Time O TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) SHP Date C DT 6/6 Date (YYMMDD) Used if SHP01 = "02" for the "Last Supplier Ship Date". Not Used SHP Time O TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) 09/09/ DaimlerChrysler Corporation

28 DaimlerChrysler Corporation Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 175 Loop: LIN Optional Level: Detail Usage: Optional 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 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 DaimlerChrysler. MMMA does not use the TD5 segment after the TD1 Segment (see FST loop). Not used by KANBAN. EXAMPLES: TD5****M******SH*0006 TD5****GR******SH*0012 Data Element Summary Ref. Data Des. Element Name Attributes Not Used TD Routing Sequence Code O ID 1/2 Code describing the relationship of a carrier to a specific shipment movement Not Used TD Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) Not Used TD Identification Code C ID 2/17 Code identifying a party. TD 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 09/09/ DaimlerChrysler Corporation

29 DaimlerChrysler Corporation AE D Air Express Parcel Post DD Dedicated Delivery Service * E Expedited Truck GG Geographic Shipping/Receiving * GR Geographic Receiving * GS Geographic Shipping * LT M O Less Than Trailer Load (LTL) Motor (Common Carrier) Containerized Ocean PD Parcel Delivery * RR Roadrailer * U VE X Private Parcel Service (UPS) Vessel, Ocean Intermodal (Piggyback) (TOFC/CO-FC) Not Used TD Routing C AN 1/35 Free-form description of the routing or requested routing for shipment, or the originating carrier's identity Not Used TD Shipment/Order Status Code O ID 2/2 Code indicating the status of an order or shipment Not Used TD Location Qualifier O ID 1/2 Code identifying type of Location Identifier (310) used. Not Used TD Location Identifier C AN 1/25 Code which identifies a specific location Not Used TD Transit Direction Code O ID 2/2 The point of origin and point of direction TD Transit Time Direction Qualifier O ID 2/2 Code specifying the value of time used to measure the transit time SH Surface Hours TD Transit Time C R 4/4 The numeric amount of transit time Integer number of intransit hours (no decimals). 09/09/ DaimlerChrysler Corporation

30 DaimlerChrysler Corporation Segment: CTT Transaction Totals Position: 010 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 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* Data Element Summary Ref. Data Des. Element Name Attributes M CTT Number of Line Items M N0 1/4 Total number of line items in the transaction set Total Number of "LIN" segments. CTT 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: First occurrence of value being hashed..18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed Fourth occurrence of value being hashed Hash total prior to truncation. 855 Hash total after truncation to three-digit field. The Hash Total of all quantities released (FST01). Not Used CTT03 81 Weight O R 1/8 Numeric value of weight Not Used CTT Unit or Basis for Measurement Code C ID 2/2 Code identifying the basic unit of measurement. Not Used CTT Volume O R 1/8 Value of volumetric measure Not Used CTT Unit or Basis for Measurement Code C ID 2/2 Code identifying the basic unit of measurement. 09/09/ DaimlerChrysler Corporation

31 DaimlerChrysler Corporation Not Used CTT Description O AN 1/80 A free-form description to clarify the related data elements and their content 09/09/ DaimlerChrysler Corporation

32 DaimlerChrysler Corporation Segment: SE Transaction Set Trailer Position: 020 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. 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* Data Element Summary Ref. Data Des. Element Name Attributes M SE01 96 Number of Included Segments M N0 1/6 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. M SE Transaction Set Control Number M AN 4/9 Identifying control number assigned by the originator for a transaction set. Same as ST02. 09/09/ DaimlerChrysler Corporation

33 EXAMPLE 1: Just In Time Shipping Schedule ST*862* ASC X12 Transaction Set = 862 (Shipping Schedule) Transaction Set Control Number = BSS*05* *910603*SH*910603*910702** Transaction Set Purpose = 05 (Replace) Reference Number = Transaction Set Control Number Current Date = 06/03/91 Shipment Based Horizon Start Date = 06/03/91 Horizon End Date = 07/02/91 Program Number = Transaction Set Control Number N1*SI**92*04000 Shipping Schedule Issuer = (DaimlerChrysler Corporation) N1*SU**92*10167AA DaimlerChrysler-assigned Supplier Code = Release Point Suffix = AA N1*ST**92*09106 DaimlerChrysler-assigned Receiving Plant Code = LIN**BP* AA UIT*EA NTE*LIN*T Customer-assigned Part Number = AA Unit of Measure = Each Line Item Part in test mode PER*EX*DON LAWES*TE* Expeditor = Don Lawes Telephone Number = REF*DK*MAIN FST*100*C*D*910603**010*0800 Dock Name = MAIN Daily Firm Shipment Quantity = 100 Shipment Date = 06/03/91 Shipment Time = 8:00 a.m. 09/09/

34 EXAMPLE 1 (continued) FST*100*C*D*910604**010*0800 Daily Firm Shipment Quantity = 100 Shipment Date = 06/04/91 Shipment Time = 8:00 a.m. FST*200*C*D* Daily Firm Shipment Quantity = 200 Shipment Date = 06/05/91 JIT*100*0800 Shipment Quantity = 100 Shipment Time = 8:00 a.m. JIT*100*1100 Shipment Quantity = 100 Shipment Time = 11:00 a.m. FST*100*C*D*910606**010*1100 FST*100*C*D*910607**010*0800 FST*100*C*D*910610**010*0800 FST*250*C*D*910613**010*0800 FST*100*C*D*910614**010*1000 FST*275*C*D*910617**010*0900 Daily Firm Shipment Quantity = 100 Shipment Date = 06/06/91 Shipment Time = 11:00 a.m. Daily Firm Shipment Quantity = 100 Shipment Date = 06/07/91 Shipment Time = 8:00 a.m. Daily Firm Shipment Quantity = 100 Shipment Date = 06/10/91 Shipment Time = 8:00 a.m. Daily Firm Shipment Quantity = 250 Shipment Date = 06/13/91 Shipment Time = 8:00 a.m. Daily Firm Shipment Quantity = 100 Shipment Date = 06/14/91 Shipment Time = 10:00 a.m. Daily Firm Shipment Quantity = 275 Shipment Date = 06/17/91 Shipment Time = 9:00 a.m. 09/09/

35 EXAMPLE 1 (continued) FST*100*C*D*910618**010*0900 FST*100*C*D*910619**010*0900 FST*100*C*D*910620**010*0900 FST*200*C*D*910701**010*0800 FST*200*D*D*910703**010*0800 FST*200*D*D*910705**010*0800 Daily Firm Shipment Quantity = 100 Shipment Date = 06/18/91 Shipment Time = 9:00 a.m. Daily Firm Shipment Quantity = 100 Shipment Date = 06/19/91 Shipment Time = 9:00 a.m. Daily Firm Shipment Quantity = 100 Shipment Date = 06/20/91 Shipment Time = 9:00 a.m. Daily Firm Shipment Quantity = 200 Shipment Date = 07/01/91 Shipment Time = 8:00 a.m. Daily Planning Quantity = 200 Shipment Date = 07/03/91 Shipment Time = 8:00 a.m. Daily Planning Quantity = 200 Shipment Date = 07/05/91 Shipment Time = 8:00 a.m. FST*692*D*D* Daily Planning Quantity = 692 Shipment Date = 07/09/91 FST*322*D*D* Daily Planning quantity = 322 Shipment Date = 07/24/91 ATH*PQ*910602*13200** Resource Authorization (PQ) = Cumulative Year-To-Date requirements Previous to First Schedule Period Cumulative Through Date = 06/02/91 Cumulative Required Quantity = 13,200 Cumulative Start (Plant Inventory) Date = 07/15/90 09/09/

36 EXAMPLE 1 (continued) SHP*01*100*011* Discrete Quantity (of last shipment) = 100 Ship Date/Time (last shipment)= 06/02/91 SHP*02*13251*051*900715** TD5****RR*****SH*0006 Cumulative YEAR-TO-DATE shipped quantity = 13,251 Cumulative Quantity Start Date = 07/15/90 Cumulative Through Date = 11/30/92 Shipment Time = 9:00 a.m. RAN = WT37362 Shipping Mode = Roadrailer Transit time = 6 surface hours CTT*1*4209 Total number of LIN segments = 1 Total sum of all quantities in elements FST01 = 4,209 SE*35* Total number of segments = 35 Transaction Set Control Number = /09/

37 EXAMPLE 2: Component Supply Agreement Shipping Schedule for Mitsubishi Motors Manufacturing of America (One Shipment Multiple Deliveries) ST*862* ASC X12 Transaction Set = 862 (Shipping Schedule) Transaction Set Control Number = BSS*05* *921113*SH*921130*921130** Transaction Set Purpose = 05 (Replace) Reference Number = Current Date = 11/13/92 Shipment Based Schedule Horizon Start Date = 11/30/92 Horizon End Date = 11/30/92 N1*SI**92*04000 Shipping Schedule Issuer = (DaimlerChrysler Corporation) N1*SU**92*10167 DaimlerChrysler-assigned Supplier Code = N1*ST**92*04506 DaimlerChrysler-assigned Receiving Plant Code = LIN**BP*M V UIT*EA Customer-assigned Part Number = M V Unit of Measure = Each PER*EX*DON LAWES*TE* Expeditor = Don Lawes Telephone Number = FST*100*C*D*921130**010*0900*RE*WT37361 Daily Firm Shipment Quantity = 100 Shipment Date = 11/30/92 Shipment Time = 9:00 a.m. RAN = WT37361 DTM*002*921130*1600*CT Requested Delivery Date = 11/30/92 Delivery Time = 4:00 PM (Central Time) 09/09/

38 EXAMPLE 2 (continued) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*100*C*D*921130**010*0901*RE*WT37362 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:01 a.m. RAN = WT37362 DTM*002*921201*1600*CT Requested Delivery Date = 12/01/93 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*100*C*D*921130**010*0902*RE*WT37363 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:02 a.m. RAN = WT37363 DTM*002*921202*1600*CT Requested Delivery Date = 12/02/92 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*100*C*D*921130**010*0903*RE*WT37364 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:03 a.m. RAN = WT37364 DTM*002*921203*1600*CT Requested Delivery Date = 12/03/92 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = /09/

39 EXAMPLE 2 (continued) FST*100*C*D*921130**010*0904*RE*WT37365 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:04 a.m. RAN = WT37365 DTM*002*921204*1600*CT Requested Delivery Date = 12/04/92 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*150*C*D*921130**010*0905*RE*ST00628 Daily Firm Shipment Quantity = 150 Shipment Date = Shipment Time = 9:05 a.m. RAN = ST00628 DTM*002*921207*0800*CT Requested Delivery Date = 12/07/92 Delivery Time = 8:00 AM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*100*C*D*921130**010*0906*RE*ST00629 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:06 a.m. RAN = ST00629 DTM*002*921207*1100*CT Requested Delivery Date = 12/07/92 Delivery Time = 11:00 AM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*100*C*D*921130**010*0907*RE*ST00630 Daily Firm Shipment Quantity = 100 Shipment Date = Shipment Time = 9:07 a.m. RAN = ST /09/

40 EXAMPLE 2 (continued) DTM*002*921207*1600*CT Requested Delivery Date = 12/07/92 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = FST*75*C*D*921130**010*0908*RE*ST00631 Daily Firm Shipment Quantity = 75 Shipment Date = Shipment Time = 9:08 a.m. RAN = ST00631 DTM*002*921208*1600*CT Requested Delivery Date = 12/08/92 Delivery Time = 4:00 PM (Central Time) TD5**2*GXCC*LT* ATH*PQ*921112*13200** Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = Resource Authorization (PQ) = Cumulative Year-To-Date requirements Previous to First Schedule Period Cumulative Through Date = 11/12/92 Cumulative Required Quantity = 13,200 Cumulative Start (Plant Inventory) Date = 07/15/92 SHP*01*100*011* Discrete Quantity (of last shipment) = 100 Ship Date/Time (last shipment) = 11/12/92 SHP*02*13251*051*920715** Cumulative YEAR-TO-DATE shipped quantity = 13,251 Cumulative Quantity Start Date = 07/15/92 Cumulative Quantity End Date = 11/12/92 09/09/

41 EXAMPLE 2 (continued) LIN**BP*M V UIT*EA Customer-assigned Part Number = M V Unit of Measure = Each PER*EX*DON LAWES*TE* Expeditor = Don Lawes Telephone Number = FST*100*C*D*921130**010*0900*RE*ST00675 Daily Firm Shipment Quantity = 100 Shipment Date = 11/30/92 Shipment Time = 9:00 a.m. RAN = ST00675 DTM*002*921209*1500*CT Requested Delivery Date = 12/09/92 Delivery Time = 3:00 PM (Central Time) TD5**2*GXCC*LT* ATH*PQ*921112*1200** Carrier SCAC Code = GXCC Mode = Less That Truckload Routing Code = Resource Authorization (PQ) = Cumulative Year-To-Date requirements Previous to First Schedule Period Cumulative Through Date = 11/12/92 Cumulative Required Quantity = 1,200 Cumulative Start (Plant Inventory) Date = 07/15/92 SHP*01*20*011* Discrete Quantity (of last shipment) = 20 Ship Date/Time (last shipment) = 11/12/92 SHP*02*1200*051*920715** Cumulative YEAR-TO-DATE shipped quantity = 1,200 Cumulative Quantity Start Date = 07/15/92 Cumulative Quantity End Date = 11/12/92 09/09/