862 Shipping Schedule

Transcription

1 862 Shipping Schedule This document contains the format and establishes the data content of the Shipping Schedule. The 862 shall not be used to authorize labor, materials or other resources. The use of the 862 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 consolidate scheduling organization. GENERAL This document is based on the X12 standards for Electronic Data Interchange (EDI) for the 862 Shipping Schedule transaction, as set forward in Version Release of the standards document. COMMUNICATIONS The 862 EDI file will be available to suppliers through DaimlerChrysler's Electronic Business Message exchange (EBMX). For more information on EBMX, use the following link: Links to websites are subject to change without notice. The element and sub-element terminators used in the 862 transaction will be a hexadecimal '7E' (i.e. a tilde ~ ) and a hexadecimal 5E (i.e. up carrot ^ ) respectively. The segment terminator used in the 862 transaction will be a hexadecimal 1C. Detroit Diesel uses the ID code of DDC63001 in the ISA record with a qualifier of ZZ. Receiver codes will be the supplier number at DDC with the prefix DDC. Last Revision Date: 1/22/07 Page 1 of 16

2 Transaction Overview SEG. ID NAME REQ. MAX USE LOOP REPEAT ST Transaction Set Header M 1 BSS Beginning Segment For Shipping Schedule/Production M 1 Sequence LOOP ID- N1 200 N1 Name O 1 REF Reference Numbers O 12 PER Administrative Communications Contact O 3 LOOP ID- LIN 1000 LIN Item Identification M 1 UIT Unit Detail M 1 SUB-LOOP ID- LIN/FST 100 FST Forecast Schedule O 1 SUB-LOOP ID- LIN/SHP 10 SHP Shipped/Received Information O 1 CTT Transaction Totals M 1 SE Transaction Set Trailer M 1 Codes used in the ATTRIBUTES field for each segment: First Column: M = Mandatory O = Optional X = Conditional Second Column: Nx = Numeric (x= decimal place) R =Decimal ID = ID code AN = Alphanumeric DT = Date (usually YYMMDD) TM = Time (usually HHMM or HHMMSS) Page 2 of 16

3 Segment: ST Transaction Set Header Level: Header Loop: N/A Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number. Semantic: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definitions. Notes: The transaction Set Control Number (ST02) in this header must match the Transaction Set Control Number (SE02) in the Transaction Set Trailer (SE). ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set. For this transaction, it will be 862. ST Transaction Set Control Number Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. A unique number assigned to each transaction set within a functional group. M AN 4/9 Page 3 of 16

4 Segment: BSS Beginning Segment Sequence Level: Header Loop: N/A Usage: Mandatory Purpose: To transmit identifying numbers, dates and other basic data relating to the transaction set. Syntax: 1. R0708: At least one of BSS07 or BSS08 is required. Semantic: 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: Either BSS07 or BSS08 must be used, but not both. BSS Transaction Set Purpose Code M ID 2/2 Code uniquely purpose of transaction set. Detroit Diesel will always send 05 (replacement schedule). BSS Reference Number Reference number or ID number as defined for a particular transaction set, or as specified A unique number assigned to each transaction set within a functional group. BSS Date Schedule generation date. BSS Schedule Type Qualifier Code identifying the type of dates used when defining a shipping/delivery time in a scheduling or forecast. Detroit Diesel will always send DL (Delivery-based Date) BSS Date Schedule begin date BSS Date Schedule end date BSS Release Number Number identifying a release against a PO previously placed by the parties involved in the transaction. M AN 1/30 M DT 6/6 M ID 2/2 M DT 6/6 M DT 6/6 X AN 1/30 BSS Reference Number X AN 1/30 BSS Contract number O AN 1/30 BSS Purchase Order Number Identifying number for Purchase Order assigned by the orderer/purchaser BSS Schedule Quantity Qualifier Code identifying the type of quantities used when defining a schedule or forecast. DDC will send A (Actual Discreet Quantities) O AN 1/22 O ID 1/1 Page 4 of 16

5 Segment: N1 Name Level: Header Loop: N1 Repeat: 200 Usage: Mandatory Purpose: To identify a party by type of organization, name and code. Syntax: 1. R0203: At least one of N102 or N103 is required. 2. P0304: If either N103 or N104 is present, then the other is required. Comments: A. 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 loop in the header area can be used to identify the shipping schedule issuer, the supplier, and the ship-to and ship-from locations. N Entity Identifier Code M ID 2/2 Code identifying an organizational entity, a physical location, or an individual. DDC will use the below codes: ST: Ship to SF: Ship from SU: Supplier/Manufacturer SI: Shipping Schedule Issuer. N Entity Name Free-form name A unique number assigned to each transaction set within a functional group. N Identification Code Qualifier Code designating the system/method of code structure used for Identification Code (N104) DDC will use 92 (Assigned by Buyer) N Identification Code Code identifying a party (or other code). PDC (Canton) = Redford = MBE DDR Mexico = MBT Transmissions Kontane = MBE Kontane = MBE Canton = Menlo Logistics= DDC Reman Central Emporia = Butler Inland DDA = Distributor number and location (used if direct ship) X AN 1/35 X ID 1/2 X AN 2/17 Page 5 of 16

6 Segment: REF Reference Numbers Level: Header Loop: N1 Usage: Optional 2 Purpose: To specify identifying numbers. Syntax: 1. R0203: At least one of REF02 or REF03 is required. REF Reference Number Qualifier M ID 2/2 Code qualifying the reference number (127). DDC will use DK (Dock Number) REF Reference Number Reference number or ID number as defined for a particular transaction set, or as specified by the reference number qualifier (126). DDC will always send the dock number. Redford Plant = Dock1 North Dock Redford Plant = Dock2 South Dock Redford Plant = Dock6 West Dock Redford Plant = Dock7 Non-Production Dock Redford Plant = MBDOCK MBE Dock Canton PDC Plant = Dock9 Canton MTU-DD PDC Plant = Dock99 Canton MBE Plant = Dock9 MBE Kontane Logistics Plant = Kontane MBT Transmissions Kontane Plant = Kontane MBE DDR Mexico Plant = DDRM Menlo Logistics Plant = Menlo DDC Reman Central Plant = Reman Cent Butler Inland DDA Plant = DockButler X AN 1/30 REF Description X AN 1/80 Page 6 of 16

7 Segment: PER Administrative Communications Contact Level: Header Loop: N1 Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed. Syntax: 1. P0304: If either PER03 or PER04 is present, then the other is required. PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named. DDC will use EX (Expeditor) PER02 93 Name Free-form name. DDC will send the name of the expeditor. PER Communication Number Qualifier Code identifying the type of communication number. DDC will send TE (Area Code & Phone Num.) PER Communication Number Complete communications number including country or area code when applicable. DDC will send expeditor s phone number. O AN 1/35 X ID 2/2 X AN 1/25 Page 7 of 16

8 LIN Item Identification Segment: Level: Detail Loop: LIN Repeat: Usage: Mandatory Purpose: To specify basic item identification data. Syntax: 1. C0405: If LIN04 is present, then LIN05 is required. NOTE: The same rule is in effect for LIN06/07, LIN08/09, LIN10/11, and so on up to LIN30/31. Semantic: 1. LIN01 is the line item identification. Comments: A. See the Data Dictionary for a complete list of ID s. B. LIN02 through LIN31 provide for 15 different product/service ID s for each item. C. DDC does not use combinations past LIN04/05. LIN Assigned Identification O AN 1/11. LIN Product/Service ID Qualifier Code identifying the type/source of the descriptive number used in Product/Service ID (234) DDC will send BP (Buyer s Part Number) LIN Product/Service ID Identifying number of a product or service. DDC will send part number assigned by DDC. LIN Product/Service ID Qualifier Code identifying the type/source of the descriptive number used in Product/Service ID (234) DDC will send RY (Model Year) LIN Product/Service ID Identifying number of a product or service. DDC will send model year in CCYY format. M ID 2/2 M AN 1/30 M ID 2/2 M AN 1/30 Page 8 of 16

9 UIT Unit Detail Segment: Level: Detail Loop: LIN Usage: Mandatory Purpose: To specify item unit detail. Syntax: 1. C0302: If UIT03 is present, then UIT02 is required. Notes: This segment indicates the unit of measurement for all quantities relating to the line item. UIT Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. DDC will send the PO unit of measure. UIT Unit Price X R 1/14 UIT Basis of Unit Price Code Code identifying the type of unit price for an item. O ID 2/2 Page 9 of 16

10 FST Forecast Schedule Segment: Level: Detail Loop: LIN/FST Repeat: 100 Usage: Optional Purpose: To specify the forecasted dates and quantities. Syntax: 1. P0607: If either FST06 or FST07 is present, then the other is required. 2. P0809: if either FST08 or FST09 is present, then the other is required. Semantic: 1. If FST03 = F (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. Comments: A. 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 the flexible interval. B. 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 JIT requirements. As an alternative, the ship/delivery pattern sequence (SDP) may be used to define an approximate time, such as AM or PM. Notes: At least one FST loop is required. FST Quantity M R 1/15 Numeric value of quantity Quantity interpretation based on code in element BSS11 FST Forecast Qualifier Code specifying the sender s confidence level of the forecast data. DDC will send one of the below: C: Firm D: Planning FST Forecast Timing Qualifier Code specifying interval grouping of the forecast. DDC will send one of the below: D: Discrete W: Weekly M: Monthly M ID 1/1 M ID 1/1 DDC will indicate FIRM, DISCRETE quantities to cover a 9-day horizon, a 3-week horizon, and a 4-month PLANNING horizon to cover a subsequent 5-month approximate horizon. The first weekly quantity of the 3 weekly buckets will represent the balance of the week not completed by the 9 daily buckets. The first monthly quantity of the 4 monthly buckets will present the balance of the current month. For Service Suppliers (44707)- A DISCRETE quantity in the first bucket represents PAST DUE. FST Date Schedule/Forecast Date YYMMDD Format M DT 6/6 BSS04 will always be DL. However, its interpretation varies depending on the values found in the FST03 element. When FST03 is D, the FST04 date is the ON DOCK delivery date. When it is W, the FST04 date is Page 10 of 16

11 the Monday of the planned delivery week and not the ON DOCK date. When it is M, the FST04 date is the planned delivery month and not the ON DOCK date. FST Date M DT 6/6 FST Date/Time Qualifier X ID 3/3 FST Time X TM 4/6 FST Reference Number Qualifier X ID 2/2 FST Reference Number X AN 1/30 Page 11 of 16

12 Segment: SHP Shipped/Received Information Level: Detail Loop: LIN/SHP Repeat: 10 Usage: Optional Purpose: To specify shipment and/or receipt information. Syntax: 1. C0102: If SHP01 is present, then SHP02 is required. 2. C0403: If SHP04 is present, then SHP03 is required. Semantic: 1. SHP04- The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03). 2. SHP06- The cumulative quantity end date. Comments: A. The SHP segment is used to communicate shipment, delivery, or receipt information and may include discrete or cumulative quantities, dates, and times. B. If SHP01 = 02, 07, 08, 09, or 10 (indicating cumulative quantities) Notes: The year-to-date Received Cumulative Quantity will be reset every year. Inventory suppliers will know DDC has begun a new model year when the year in the SHP04 segment changes. SHP Quantity Identifier O ID 2/2 Code specifying the type of quantity DDC will send of the below: 01- Discreet Quantity 02- Cumulative Quantity SHP Quantity Numeric value of quantity DDC will send the received quantity. SHP Date/Time Qualifier Code specifying type of date or time, or both date and time. DDC will send one of the below: 50- Last Receipt Date 51- Start Date for Cumulative Period. X R 1/15 X ID 3/3 SHP Date O DT 6/6 As defined by qualifier in SHP03 Format: YYMMDD SHP Time O TM 4/6 SHP Date O DT 6/6 Last receipt date FORMAT: YYMMDD SHP Time O TM 4/6 Page 12 of 16

13 CTT Transaction Totals Segment: Level: Summary Loop: N/A Usage: Mandatory Purpose: To transmit a hash total for a specific element in the transaction set Set Notes: 1. The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, has total (CTT02) is the sum of the value of the quantities (FST01) for each FST segment. Comments: A. This segment is intended to provide hash totals to validate transaction completeness and correctness. CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set. Total number of LIN segments CTT Hash Total Sum of values of the specified data element. All values in the date element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the leftmost digits if the sum is greater than the maximum size of the hash total of the data element. Hash total of quantity requested for shipment (FST01). O R 1/10 Page 13 of 16

14 Segment: SE Transaction Set Trailer Level: Header Loop: N/A Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number. Semantic: 2. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definitions. Notes: The transaction Set Control Number (ST02) in this header must match the Transaction Set Control Number (SE02) in the Transaction Set Trailer (SE). SE01 96 Number of Included Segments Total number of segments included in the transaction set including ST and SE segments. M N0 1/6 SE Transaction Set Control Number Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. This number must be the same as ST02. M AN 4/9 Page 14 of 16

15 Sample Transmission ISA~00~ ~00~ ~ZZ~DDC63001 ~ZZ~DDC1234 ~040706~0040~U~00304~ ~0~P~^ GS~SS~DDC63001~DDC1234~040706~0040~579~X~ ST~862~2834 BSS~05~ ~040706~DL~040706~041130~ R S~~~3026~A N1~SF~ANY COMPANY USA~92~1234 N1~ST~DETROIT DIESEL REDFORD~92~63001 N1~SI~ DETROIT DIESEL CANTON~92~44707 N1~SU~ ANY COMPANY USA~92~1234 REF~DK~DOCK6 PER~EX~JOE DDC EMPLOYEE LIN~~BP~ ~RY~2004 FST~1083~D~M~ FST~1404~D~M~ FST~7703~D~M~ SHP~01~5000~050~ SHP~02~30000~051~ CTT~1~10190 SE~17~2834 GE~1~579 IEA~1~ ISA~00~ ~00~ ~ZZ~DDC63001 ~ZZ~DDC15685 ~040708~0047~U~00304~ ~0~P~^ GS~SS~DDC63001~DDC15685~040708~0047~289~X~ ST~862~0486 BSS~05~ ~040708~DL~040708~041130~R P~~~13554~A N1~SF~ANY COMPANY USA~92~15685 N1~ST~DETROIT DIESEL REDFORD~92~63001 N1~SI~ DETROIT DIESEL REDFORD~92~63001 N1~SU~ ANY COMPANY USA~92~15685 REF~DK~DOCK6 PER~EX~DONNA ROHLOFF LIN~~BP~ ~RY~2004 FST~118~C~D~ FST~5~C~D~ FST~3~C~D~ FST~24~C~W~ FST~78~D~M~ FST~41~D~M~ FST~84~D~M~ FST~32~D~M~ SHP~01~100~050~ SHP~02~369~051~ CTT~1~385 SE~20~0486 ST~862~0487 BSS~05~ ~040708~DL~040708~041130~R P~~~7711~A N1~SF~WATSON ENGINEERING, INC~92~15685 N1~ST~DETROIT DIESEL REDFORD~92~63001 REF~DK~DOCK6 PER~EX~DONNA ROHLOFF LIN~~BP~ ~RY~2004 FST~18~C~W~ FST~25~C~W~ FST~90~D~M~ FST~95~D~M~ FST~148~D~M~ FST~69~D~M~ SHP~01~189~050~ SHP~02~744~051~ LIN~~BP~ ~RY~2004 FST~71~C~D~ FST~66~C~W~ FST~1~C~W~ FST~10~D~M~ FST~69~D~M~ Page 15 of 16

16 Page 16 of 16 FST~125~D~M~ FST~72~D~M~ SHP~01~126~050~ SHP~02~281~051~ LIN~~BP~ ~RY~2004 FST~31~C~W~ FST~12~C~W~ FST~36~C~W~ FST~117~D~M~ FST~41~D~M~ FST~83~D~M~ FST~83~D~M~ SHP~01~70~050~ SHP~02~353~051~ LIN~~BP~ ~RY~2004 FST~16~D~M~ FST~13~D~M~ FST~28~D~M~ SHP~01~51~050~ SHP~02~103~051~ LIN~~BP~ ~RY~2004 FST~265~C~D~ FST~317~C~D~ FST~389~C~D~ FST~352~C~W~ FST~712~C~W~ FST~805~C~W~ FST~3269~D~M~ FST~5733~D~M~ FST~3106~D~M~ FST~3722~D~M~ SHP~01~895~050~ SHP~02~19793~051~ LIN~~BP~ ~RY~2004 FST~2~D~M~ FST~26~D~M~ SHP~01~210~050~ SHP~02~0~051~ LIN~~BP~ ~RY~2004 FST~8140~C~D~ FST~6264~C~D~ FST~5040~C~D~ FST~6336~C~W~ FST~12672~C~W~ FST~21096~D~M~ FST~23328~D~M~ FST~19080~D~M~ FST~25848~D~M~ SHP~01~1680~050~ SHP~02~144312~051~ CTT~7~ SE~82~0487 GE~2~289 IEA~1~