LVS/ET Division. 862 Shipping Schedule

Transcription

1 LVS/ET Division 862 Shipping Schedule ANSI X12 Version v4010 Revised 3/20/2007 Page 1 of 19

2 862 Shipping Schedule Transaction Layout: Heading: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 010 ST Transaction Set Header M 1 Required 020 BSS Beginning segment of shipping Schedule M 1 LOOP ID N1 200 Required 050 N1 Name O 1 Required 090 REF Reference Identification O 12 Required 100 PER Administrative Communication Contac O 3 Detail: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples LOOP ID LIN Required 010 LIN Item Identification M 1 Required 020 UIT Unit Detail M REF Reference Identification O 12 LOOP ID FST 100 Required 080 FST Forecast Schedule O 1 Note 1. LOOP ID JIT JIT Just In Time Schedule O REF Reference Identification O 500 LOOP ID SHP SHP Shipped/Received Information O REF Reference Identification O 12 Summary: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 010 CTT Transaction Totals O 1 Note 2. Required 020 SE Transaction Set Trailer M 1 Notes and 1. For Segment requirements, refer to the column titled ARM Req in the table above for those segments that are required in the Transaction. 2. For Element requirements, refer to the column titled ARM Req in the elements table for each segment detailed in the pages that follow. If the segment is used, then these elements are required. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 2 of 19

3 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition. ST*862*13579~ Required ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. Required ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 3 of 19

4 Segment: BSS Beginning Segment for Shipping Schedule/Production Sequence Position: 020 Loop: Level: Heading Usage: Mandatory Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Syntax Notes: At least one of BSS07 or BSS08 is required. Semantic Notes: 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). BSS*05* * *DL* * *****A~ BSS*00* * *KB* * *****A~ Required BSS Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 00 Original 01 Cancellation 05 Replace Required BSS Schedule Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as Required BSS specified by the Reference Identification Qualifier Schedule Date Date expressed as CCYYMMDD M DT 8/8 Required 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 DL Delivery Based KB Kanban Signal Required BSS Horizon Start Date M DT 8/8 Date expressed as CCYYMMDD Required BSS Horizon End Date M DT 8/8 Date expressed as CCYYMMDD BSS Release Number X AN 1/30 Number identifying a release against a Purchase Order previously placed by BSS the parties involved in the transaction Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as BSS specified by the Reference Identification Qualifier Purchase Order Number O AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser This element represents the Blanket PO number, but may be overridden by a Required BSS PO number indicated in the LIN segment Schedule Quantity Qualifier O ID 1/1 Code identifying the type of quantities used when defining a schedule or forecast A Actual Discrete Quantities lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 4 of 19

5 Segment: N1 Name Position: 050 Loop: N1 Optional Level: Heading 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. N1*SF**92*73708~ N1*SI**92*1316~ N1*ST**92*1316~ N1*SU**92*73708~ Required N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual ST Ship To SI Schedule Issuer SU Supplier/Manufacturer SF Ship From Location N Name X AN 1/60 Free-form name Required N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 12 Telephone Number (Phone) 92 Assigned by Buyer or Buyer's Agent ZZ Mutually Defined Required N Identification Code X AN 2/80 Code identifying a party or other code lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 5 of 19

6 Segment: REF Reference Identification Position: 090 Loop: N1 Optional Level: Heading 2 Purpose: To specify identifying information Syntax Notes: REF*DK*WK1~ REF*LF*L103~ Required REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification DK Dock Number LF Assembly Line Feed Location Required REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 6 of 19

7 Segment: PER Administrative Communications Contact Position: 100 Loop: N1 Optional Level: Heading Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: If either PER03 or PER04 is present, then the other is required. PER*PL*JOE SMITH*TE* *EM*JOE.SMITH@ARVINMERITOR.COM PER*ZZ*EDI CONTACT*EM*LVSEDI@ARVINMERITOR.COM Required PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named PL Plant Contact ZZ EDI Contact Required PER02 93 Name Free-form name O AN 1/60 Required PER Communication Number Qualifier Code identifying the type of communication number X ID 2/2 TE Telephone EM Required PER Communication Number X AN 1/80 Complete communication number including country or area code when applicable id for communication. PER Communication Number Qualifier Code identifying the type of communication number X ID 2/2 EM PER Communication Number X AN 1/80 id for communication. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 7 of 19

8 Segment: LIN Item Identification Position: 010 Loop: LIN Mandatory Level: Detail Usage: Mandatory Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. 2 If either LIN06 or LIN07 is present, then the other is required. LIN**BP*V L*PO*AF63682*EC*A~ LIN Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set Required 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 Required LIN Product/Service ID Identifying number for a product or service M AN 1/48 ArvinMeritor Part Number LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) PO Purchase Order Number LIN Product/Service ID X AN 1/48 Identifying number for a product or service ArvinMeritor Purchase Order Number LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) EC Engineering Change Level LIN Product/Service ID X AN 1/48 Identifying number for a product or service Part Engineering Change Level lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 8 of 19

9 Segment: UIT Unit Detail Position: 020 Loop: LIN Mandatory Level: Detail Usage: Mandatory Purpose: To specify item unit data UIT*LB~ Required UIT01 C001 Composite Unit of Measure M To identify a composite unit of measure Required C 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 EA Each LB Pound PC Piece lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 9 of 19

10 Segment: REF Reference Identification Position: 050 Loop: LIN Optional Level: Detail 2 Purpose: To specify identifying information Syntax Notes: REF*KB*6114~ REF*KE*6115~ Required REF Reference Identification Qualifier Code qualifying the Reference Identification M ID 2/3 KB Beginning Kanban Serial Number KE Ending Kanban Serial Number Required REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier If REF01 = "KB", then this is the beginning Kanban number in a range, or a discrete Kanban number. If REF01 = "KE", then this is the ending Kanban number in the range. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 10 of 19

11 Segment: FST Forecast Schedule Position: 080 Loop: FST Optional Level: Detail Purpose: To specify the forecasted dates and quantities FST*250*C*D* ~ Required FST Quantity Numeric value of quantity M R 1/15 Required FST Forecast Qualifier M ID 1/1 Code specifying the sender's confidence level of the forecast data or an action associated with a forecast A Immediate C Firm D Planning Required FST Forecast Timing Qualifier M ID 1/1 Code specifying interval grouping of the forecast D Discrete Required FST Date M DT 8/8 Date expressed as CCYYMMDD Delivery Date lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 11 of 19

12 Segment: JIT Just-In-Time Schedule Position: 110 Loop: JIT Optional Level: Detail Purpose: To identify the specific shipping/delivery time in terms of a 24-hour clock and identify the associated quantity JIT*125*0700~ JIT*125*1400~ Required JIT Quantity M R 1/15 Numeric value of quantity JIT Delivery Quantity Required JIT Time M TM 4/8 Time expressed in 24-hour clock time as follows: HHMM JIT Delivery Time lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 12 of 19

13 Segment: REF Reference Identification Position: 120 Loop: JIT Optional Level: Detail Max Use: 500 Purpose: To specify identifying information Syntax Notes: REF*KB* ~ REF*KE* ~ Required REF Reference Identification Qualifier Code qualifying the Reference Identification M ID 2/3 KB Beginning Kanban Serial Number KE Ending Kanban Serial Number Required REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier If REF01 = "KB", then this is the beginning Kanban number in a range, or a discrete Kanban number. If REF01 = "KE", then this is the ending Kanban number in the range. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 13 of 19

14 Segment: SHP Shipped/Received Information Position: 140 Loop: SHP Optional Level: Detail 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. 3 If SHP04 is present, then SHP03 is required. Semantic Notes: SHP04 is the date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03). SHP06 is the cumulative quantity end date. The SHP segment is used to communicate shipment, delivery, or receipt information and may include discrete or cumulative quantities, dates, and times. If SHP01 equals "02", then SHP04 and SHP06 are required to identify the start and end dates of the quantity count. SHP*01*900*050* ~ SHP*02*30523*051* ** ~ Required SHP Quantity Qualifier Code specifying the type of quantity O ID 2/2 01 Discrete Quantity 02 Prior Cum Required Required SHP Quantity Numeric value of quantity X R 1/15 Required SHP Date/Time Qualifier Code specifying type of date or time, or both date and time X ID 3/3 050 Received 051 Cumulative Quantity Start Required SHP Date X DT 8/8 Date expressed as CCYYMMDD If SHP03 = "050", this date is the Last Shipment Received Date. If SHP03 = SHP "051", this date is the Cumulative Quantity Start date. Date O DT 8/8 Date expressed as CCYYMMDD If SHP03 = "051", this date is the Cumulative Quantity End Date. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 14 of 19

15 Segment: REF Reference Identification Position: 150 Loop: SHP Optional Level: Detail 2 Purpose: To specify identifying information Syntax Notes: At least one of REF02 or REF03 is required. SHP*01*900*050* ~ REF*SI*284721*LAST RCVD SHIPPER ID~ SHP*02*30523*051* ** ~ REF*ZZ*19064*CUM RCVD QTY~ REF*ZZ*11459*PAST DUE QTY~ Required REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification SI Shipper's Identifying Number for Shipment (SID) A unique number (to the shipper) assigned by the shipper to identify the shipment If SHP03 = "050", this is the Last Shipment ID Received. ZZ PAST DUE QTY Contains the past due quantity. A positive number will indicate the past due quantity; a negative number will indicate the quantity the supplier is over shipped. (Note: The past due quantity does not take into account any in-transit shipments or shipments not yet received in the ArvinMeritor system at the time the schedule is created.) If SHP03 = "051", this is the Cum received Qty and Past Due Qty ZZ CUM RCVD QTY Contains the cumulative quantity received including the last shipment referenced in the SHP*01 segment Required REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Required REF Description X AN 1/80 Description for the data specified in the REF02. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 15 of 19

16 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Purpose: To transmit a hash total for a specific element in the transaction set CTT*7*4538~ Required CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set CTT Hash Total O R 1/10 Sum of values of the FST quantities. lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 16 of 19

17 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory 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) SE*34*13579~ Required SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments Required SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 17 of 19

18 862 Shipping Schedule v4010 Example: ISA*00* *00* *ZZ* LVS *ZZ* *070306*1122*U*00401* *0*P*:~ GS*SS* * * *1122*1013*X*004010~ ST*862* ~ BSS*00* * *DL* * ** ~ N1*SF**92* ~ N1*SI**92*0999~ N1*ST**92*0999~ N1*SU**92* ~ PER*ZZ*EDI LIN**BP* *PO*123432~ UIT*EA~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*12786*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*13609*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*13609*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ SHP*01*9105*050* ~ REF*SI* A0207*LAST RCVD SHIPPER ID~ SHP*02*346961*051* ** ~ REF*ZZ*346961*CUM RCVD QTY~ REF*ZZ*0*PAST DUE QTY~ LIN**BP* *PO*123456~ UIT*EA~ FST*0*D*D* ~ FST*1758*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*17365*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ SHP*01*10850*050* ~ REF*SI* B0207*LAST RCVD SHIPPER ID~ SHP*02*328676*051* ** ~ REF*ZZ*315440*CUM RCVD QTY~ REF*ZZ*13236*PAST DUE QTY~ 862v4010 Revised 3/20/2007 Page 18 of 19

19 Example (continued): LIN**BP* *PO*123456~ UIT*EA~ FST*0*D*D* ~ FST*2928*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*8781*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ FST*0*D*D* ~ SHP*01*16675*050* ~ REF*SI* B0207*LAST RCVD SHIPPER ID~ SHP*02*157330*051* ** ~ REF*ZZ*157330*CUM RCVD QTY~ REF*ZZ*0*PAST DUE QTY~ CTT*3*70836~ SE*73* ~ GE*1*1013~ IEA*1* ~ 862v4010 Revised 3/20/2007 Page 19 of 19