LEAR CORPORATION IMPLEMENTATION GUIDELINES FOR AIAG (ASC X12) EDI CONVENTIONS SHIPPING SCHEDULE TRANSACTION SET (862)

Similar documents
BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

ANSI X12 version Planning Schedule with Release Capability

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

Invoice. Transaction Set (810) (Outbound from TI)

ANSI X12 ASN 856 Version

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

ANSI X12 version Advance Ship Notice

VERSION: ANSI X

856 Advanced Shipping Notices (ASN)

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

810 Invoice ANSI ASC X12 Version 4010

Electronic Data Interchange

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

ANSI X Product Transfer and Resale Report

Electronic Data Interchange

Portland General Electric Implementation Standard

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

Electronic Document Interchange Standards Version 5050

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

Mazda North American Operations EDI Supplier Documentation October 20, 2015

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

810 Invoice Revised 01/26/15

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

EDI GUIDELINES INVOICE 810 VERSION 4010

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

VOLVO Dealer Programs 810 Invoice EDI Guideline

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^ ^12345^ ^ ^

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

214 Transportation Carrier Shipment Status Message - LTL

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

856 Advance Ship Notice Supplier Implementation Guide November 2015

ADOBE ANSI X Version: 1.0

Bill of Lading Number REF Reference Identification M AN 1/30 MustUse

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Supply Chain Merchandise Logistics E-Commerce Purchase Order

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

Shipping Authorization -- EDI-862

856 Ship Notice/Manifest - R US CANADA

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

860 Purchase Order Change Request Buyer Initiated

810 Invoice ANSI X.12 Version 5010

214 Transportation Carrier Shipment Status Message

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

Customer EDI Guidelines United States 810 Invoice

ANSI X12 version Remittance Advice

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

EDI Specifications Advance Ship Notice (Supplier v4010)

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

EDI Specifications Invoice (Supplier v4010)

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

810 Invoice. Introduction: Heading: Functional Group ID=IN

VDP Program Vendor Guidelines

ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA

ANSI X12 version Text Message

867 Product Transfer and Resale Report Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

LOOP ID - N N9 Reference Identification O MSG Message Text O 1000

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

Adobe - EDIFACT D97.A ORDERS

824 Application Advice

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X

Note: The following information is required on all Merchandise Invoices:

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

PURCHASE ORDER RESPONSE

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

Staples Supplier Electronic Data Interchange Implementation Guide

945 Warehouse Shipping Advice

Purchase Orders Message ORDERS (EDIFACT D97A)

State of Tennessee Department of Revenue

Guardian Automotive Supplier Label Specification

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

ZF Group North American Operations. EDI Implementation Guide

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Bulk EDIFACT ASN MESSAGE FORMAT

EDI. Electronic Data Interchange

820 ANSI X12 Version

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

Trading Partner Labels Using Linear and 2D Symbols SPEC: AIAG B-10 Version: (06/04)

INVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May ANSI ASC X12 V.4030

810 - Invoice. Set Number Set Name - Invoice Functional Group - IN

CSX EDI 824 Application Advice Version:

Electronic Data Interchange EDI

Bar Code Label Requirements January 2014

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

MERITOR. EDI Business Process Guide

322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY

NIST. ASC X Transaction Set 846P. Federal Implementation Guideline. Inventory Inquiry/Advice. Implementation Convention

Implementation Guideline

Transcription:

LEAR CORPORATION IMPLEMENTATION GUIDELINES FOR AIAG (ASC X12) EDI CONVENTIONS SHIPPING SCHEDULE TRANSACTION SET (862) LEAR CORPORATION ITC 24467 WEST TEN MILE RD SOUTHFIELD, MI 48034 ASC X12 VERSION/RELEASE 003060

862 SHIPPING SCHEDULE / PRODUCTION SCHEDULE This standard contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange(EDI) also know as Electronic Commerce(EC) environment. The transaction set can be used by 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 schedules requirements on a more frequent basis than 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.

SEGMENT USAGE OVERVIEW HEADER SEGMENT DESCRIPTION TABLE ST M TRANSACTION SET HEADER BSS M BEGINNING SEGMENT FOR SHIPPING SCHEDULE/ PRODUCTION SEQUENCE DTM O DATE/TIME REFERENCE N1 O NAME DETAIL SEGMENT DESCRIPTION TABLE LIN M ITEM IDENTIFICATION UIT O UNIT DETAIL REF O REFERENCE IDENTIFICATION PER O ADMINISTRATIVE COMMUNICATIONS CONTACT FST O FORECAST SCHEDULE SHP O SHIPPED / RECEIVED INFORMATION SUMMARY SEGMENT DESCRIPTION TABLE CTT O TRANSACTION TOTALS SE O TRANSACTION SET TRAILER

HEADER SEGMENT DESCRIPTION TABLE SEGMENT REQD DESCRIPTION ST M TRANSACTION SET HEADER BSS M BEGINNING SEGMENT FOR SHIPPING SCHEDULE/ PRODUCTION SEQUENCE DTM O DATE/TIME REFERENCE N1 O NAME N2 O ADDITIONAL NAME INFORMATION NOT USED N3 O ADDRESS INFORMATION NOT USED N4 O GEOGRAPHIC LOCATION NOT USED REF O REFERENCE IDENTIFICATION NOT USED PER O ADMINISTRATIVE COMMUNICATIONS CONTACT NOT USED FOB O F.O.B. RELATED INFORMATION NOT USED

SEGMENT: MAX USAGE/LOOPS: ST - TRANSACTION SET HEADER Heading 1/None Indicate the start of a transaction set and to assign a control number. The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE) segment. EXAMPLE: ST*862*0001 N/L ST01 143 Transaction Set ID Code M ID 03/03 Use "862" ST02 239 Transaction Set Control Number M AN 04/09 A unique control number (same as SE02)

SEGMENT: BSS - BEGINNING SEGMENT FOR SHIPPING/PRODUCTION SEQUENCE Header MAX USAGE/LOOPS: 1/None Transmit identifying numbers, dates, and other basic data relating to the 862 transaction set. Element BFR04 indicates planning schedule is shipment based (SH) or delivery based (DL). EXAMPLES: BSS*05**970804*SH*970804*971027 N/L Shipment based BSS*05**970804*DL*970804*971027 N/L Delivery based BSS01 353 Transaction Set Purpose M ID 02/02 "00" = Original "05" = Replace BSS02 127 Forecast Order Number M AN 01/30 Document number BSS03 373 Document Creation Date M DT 06/06 Format (YYMMDD) BSS04 675 Schedule Type Qualifier M DT 06/06 DL = delivery based SH = shipment based KB = KANBAN Signal BSS05 373 Horizon Start Date M DT 06/06 Format (YYMMDD) BSS06 373 Horizon End Date M DT 06/06 Format (YYMMDD) BSS07 328 Release Number X AN 01/30 BSS08 127 Reference Identification O AN 01/30 Same as BSS02 BSS09 367 Contact Number O AN 01/30 not used BSS10 324 Purchase Order Number O ID 01/22 not used BSS11 676 Schedule Quantity Qualifier O ID 01/01 not used

SEGMENT: DTM - DATE / TIME REFERENCE MAX USAGE/LOOPS: Heading 2/None Specify pertinent dates and times Use a date/time qualifier (DTM01) value of "097" to specify the creation date of document. EXAMPLE: DTM*097*970805*230045**19 N/L DTM01 374 Date/Time Qualifier M ID 03/03 "097" DTM02 373 Date X DT 06/06 Date (YYMMDD) DTM03 337 Time X TM 04/06 Time (HHMMSS) HH = hour MM = minutes SS = seconds DTM04 623 Time Zone Qualifier O ID 02/02 not used DTM05 624 Century O NO 02/02 "19" = first two characters in the designation of the year (CCYY) DTM06 1250 Date Time Period Format Qualifier not used DTM07 1251 Date Time Period not used

SEGMENT: N1 - NAME Header MAX USAGE/LOOPS: 1/200 Identify the party by type of organization, name, and code. The N1 loop in the heading area is used to identify the release issuer and the supplier being released to. EXAMPLES: N1*MI**92**LSC40 N/L N1*SF**92**20005 N/L N1*ST*LEAR CORPORATION*92**LSC40 N/L N101 98 Entity Identifer Code M ID 02/02 "MI" = Material Release Issuer "ST" = Ship To Location "SF" = Ship From Location "SU" = Supplier N102 93 Organization Name X AN 01/35 N103 66 Identification Code Qualifier X ID 01/02 "92" = Assigned By Buyer "01" = DUNS Number N104 67 Identification Code X AN 02/20 If N101 = (MI) this element would contain the Lear plant number associated with the "ST" destination N105 706 Entity Relationship Code O ID 02/02 not used N106 98 Entity Identifier Code O ID 02/02 not used

DETAIL SEGMENT DESCRIPTION TABLE SEGMENT REQD DESCRIPTION LIN M ITEM IDENTIFICATION UIT O UNIT DETAIL PKG O PARKING, PACKAGING, LOADING NOT USED PO4 O ITEM PHYSICAL MARKINGS NOT USED PRS O PART RELEASE STATUS NOT USED QTY O QUANTITYNOT USED REF O REFERENCE IDENTIFICATION PER O ADMINISTRATIVE COMMUNICATIONS CONTACT SDP O SHIP/DELIVERY PATTERN NOT USED FST O FORECAST SCHEDULE DTM O DATE/TIME REFERENCE NOT USED SDQ O DESTINATION QUANTITY NOT USED JIT O JUST-IN-TIME SCHEDULE NOT USED REF O REFERENCE IDENTIFICATION NOT USED SHP O SHIPPED / RECEIVED INFORMATION REF O REFERENCE IDENTIFICATION NOT USED TD1 O CARRIER DETAILS(QUANTITY AND WEIGH) NOT USED TD2 O CARRIER DETAILS(EQUIPMENT) NOT USED TD3 O CARRIER DETAILS(ROUTING SEQ/TRANSIT TIME) NOT USED

SEGMENT: MAX USAGE/LOOPS: EXAMPLE: LIN - ITEM IDENTIFICATION Detail 200000/None Specify basic item identification data This segment is used for the part number information such as Lear part number, purchase order, engineering level, model year. LIN**BP*05003670*PO*277634*RY*7*EC*12345 N/L LIN01 350 Assigned Identification O AN 01/20 not used LIN02 235 Product/Service ID Qualifier M ID 02/02 "BP" Buyer part number LIN03 234 Product Service ID M AN 01/40 Lear part number LIN04 through LIN31 Provide 14 additional pairs of Product/Service ID Qualifiers and Product/Service ID's to further describe the line item. The below code list applies to each occurrence of data element 235 in these pairs. NOTE: "CN" = Commodity Name "CR" = Contract Number "DR" = Drawing Revision Number "EC" = Engineering Change Level "KP" = Kanban Plan Number "PL" = Purchase's Order Line Number "PR" = Process Number "PO" = Purchase Order Number "RN" = Release Number "RY" = Record Keeping Or Model Year "VP" = Vendor's (Seller's) Part Number

SEGMENT: MAX USAGE/LOOP: UIT - UNIT DETAIL Detail 1/None Specify item unit data This segment indicates the unit of measure for all quantities relating to the line item. EXAMPLE: UIT*EA N/L UIT01 355 Unit Or Basis For Measurement Code M ID 02/02 See list below UIT02 212 Unit Price X R 01/17 not used UIT03 639 Basis Of Unit Price Code O ID 02/02 not used SAMPLE UNIT OF MEASURE CODES: EA = Each PK = Package CA = Case LO = Lot PL = Pallet

SEGMENT: MAX USAGE/LOOP: REF - REFERENCE IDENTIFICATION Detail 12/LIN Transmit identifying numbers associated with the item identified in the LIN record. This segment is used to identify the dock code or last bill of lading number processed. EXAMPLES: REF*DK*MAIN N/L REF*BL*1234567890 N/L REF01 128 Reference Identification Qualifier M ID 02/03 See note 1 REF02 127 Reference Identification X AN 01/30 REF03 352 Description X AN 01/80 not used NOTE: "DK" = Dock Number "JH" = Tag Number(KANBAN Card) "KB" = Beginning Kanban Serial Number "KE" = Ending Kanban Serial Number "K6" = Purchase Description "LF" = Line Feed Assembly Location "LS" = Bar Coded Serial Number "RL" = Reserve Line Feed Assembly Location "BL" = Bill of Lading

SEGMENT: MAX USAGE/LOOP: PER - ADMINISTRATIVE COMMUNICATIONS CONTACT Detail 3/LIN Identify a person or office to whom administrative communications should be directed. This segment is used to convey the name and telephone number of the person responsible for this part at the plant named in the header N1 ST segment. EXAMPLE: PER*BD*MATERIALS DEPARTMENT*TE*6183371478 N/L PER*EX*RON MEYER*TE*6183371478 N/L PER01 366 Contact Function Code M ID 02/02 "BD"-Buyer name or department "EX"-Expediter PER02 93 Name (Free-Format) O AN 01/35 PER03 365 Communication Number Qualifier X ID 02/02 "EM"-Electronic Mail "FX"-Facsimile "TE"-Telephone number PER04 364 Communication Number X AN 01/80 PER05 365 Communication Number Qualifier X ID 02/02 not used PER06 364 Communication Number X AN 01/80 not used PER07 365 Communication Number Qualifier X ID 02/02 not used PER08 364 Communication Number X AN 01/80 not used PER09 443 Contact Inquiry Reference O AN 01/20 not used

SEGMENT: MAX UASGE/LOOP: FST - FORECAST SCHEDULE Detail 260/LIN/SDP Specify the forecasted dates and quantities This segment is required, although it allows for time to be specified in addition to the date, locations using that level of scheduling will use the Shipping Schedule Transaction Set (862) to convey this information. EXAMPLES: FST*10*C*D*970804 N/L FST*1366*D*D*970804 N/L FST01 380 Quantity M R 01/15 FST02 680 Forecast Qualifier M ID 01/01 "C" - Firm "D" - Planning "Z" - Use for zero quantities FST03 681 Forecast Timing Qualifier M ID 01/01 "D" - Discrete "Z" - Use for zero quantities FST04 373 Forecast Schedule Date M DT 06/06 (YYMMDD) FST05 373 Date O DT 06/06 not used FST06 374 Date/Time Qualifier X ID 03/03 not used FST07 337 Time X TM 04/08 not used FST08 128 Reference Identification Qualifier X ID 02/03 not used FST09 127 Reference Identification X AN 01/30 not used FST10 783 Planning Schedule Type Code O ID 02/02 not used

SEGMENT: MAX USAGE/LOOP SHP - SHIPPED/RECEIVED INFORMATION Detail 25/LIN/SHP Secify shipment and/or receipt information This segment is used to give information on either the last shipment received/shipped, or the cumulative quantity received/shipped as of a certain date. EXAMPLES: SHP*01*856*011*970803 N/L SHP*02*12384*051*970803 N/L SHP01 673 Quantity Qualifier O ID 02/02 "01"-Discrete quantity last received "02"-Cumulative quantity received SHP02 380 Quantity X R 01/15 SHP03 374 Date/Time Qualifier X ID 03/03 "011"-Shipped "050"-Received "051"-Cumulative quantity start date SHP04 373 Date X DT 06/06 SHP05 337 Time X TM 04/08 not used SHP06 373 Date O DT 06/06 not used SHP07 337 Time O TM 04/06 not used

SUMMARY SEGMENT DESCRIPTION TABLE SEGMENT REQD DESCRIPTION CTT O TRANSACTION TOTALS SE O TRANSACTION SET TRAILER

SEGMENT: CTT - TRANSACTION TOTALS MAX USAGE/LOOPS: Trailer 1/None Transmit a hash total for a specific elements in the transaction set. Provide number of LIN segments and the sum of the values in the FST01 elements. EXAMPLES: CTT*14*193999494 N/L CTT01 354 Number Of Line Items M NO 01/06 Number of LIN segments CTT02 347 Hash Totals M R 01/10 Total of quantities from FST01 CTT03 81 Weight X R 01/10 not used CTT04 355 Unit Or Basis For Measurement Code X ID 02/02 not used CTT05 183 Volume X R 01/08 not used CTT06 355 Unit Or Basis For Measurement Code X ID 02/02 not used CTT07 352 Description X AN 01/80 not used

SEGMENT: MAX USAGE/LOOPS: SE - TRANSACTION SET TRAILER Summary 1/None Indicate the end of a transaction set and provide the count of the transmitted segments including the "SE" and "ST" segments. EXAMPLE: SE*5*0001 N/L SE01 96 Number Of Included Segments M NO 01/10 Total number of segments SE02 329 Transaction Set Control Number M AN 04/09 Same as corresponding ST02