Shipping Schedule ANSI X This standard is an agreement
|
|
- Jeffery Dean
- 7 years ago
- Views:
Transcription
1 MAGNA-GAZ JOINT SUPPLY ORGANIZATION (MGJSO) STANDARD JSO-N Supersedes: Shipping Schedule ANSI X This standard is an agreement The reproduction, distribution and utilization this document as well as the communication its contents to others without explicit authorization is prohibited. Offenders will be held liable for the payment damages. All rights reserved in the event the grant a patent, utility model or design. - Date 1
2 STANDARD JSO-N Purpose This describes the specifications the GAZ group cars division for the usage ANSI X message to outline the requirements for the shipping schedule. Revisions since previous version Date 2
3 STANDARD JSO-N Documents quoted Please refer to the following provisions for additional information for EDI data exchange between GAZ and its suppliers. JSO-N Material Release EDIFACT DELFOR D.97A JSO-N Shipping Schedule Message EDIFACT DELJIT D.97A JSO-N Dispatch Advice Message EDIFACT DESADV D.97A JSO-N Planning Schedule ANSI X JSO-N Shipping Schedule ANSI X JSO-N Ship Notice Manifest ANSI X References in the text will be as follows: JSO-P-xxx Working Instructions (AA) or Process descriptions (PZB) quoted in the standard are only for internal usage. Date 3
4 STANDARD JSO-N Index 1. MESSAGE DEFINITION Principles References Field Application MESSAGE DESCRIPTION EXAMPLE OF MESSAGE... Date 4
5 STANDARD JSO-N Message Definition 1.1 Principles The shipping schedule message is intended to: specify requirements based on the delivery conditions define the aspects that guarantee synchronization between GAZ and its suppliers. 1.2 References The content this message is based on: the message structure as defined by ANSI X12 for the Shipping Schedule Message 862 as published in version 004, release 010. the agreement between the Trading Partners on the data elements to be used, their unique definition, their representation and their values (coded or clear form) as identified in this document. 1.3 Field Application The following definition a Shipping Schedule Message in ANSI X12 format is applicable for the interchange shipping instructions issued by GAZ for material deliveries. Date 5
6 STANDARD JSO-N Message Description Following pages contain a full description ANSI X message as implemented by GAZ and its suppliers. All segments are included regardless whether used or not used in the interchange with GAZ and its suppliers. Counter No Tag St MaxOcc Level Content ISA M 1 0 Interchange Control Header GS C Functional Group Header ST M 1 0 Transaction Set Header BSS M 1 0 Beginning Segment for Shipping ScheduleProduction Sequence DTM O 10 1 DateTime Reference 0050 N1 O N1-N2-N3-N4-REF-PER-FOB N1 M 1 1 Name N2 O 2 2 Additional Name Information N3 O 2 2 Address Information N4 O 1 2 Geographic Location REF O 12 2 Reference Identification PER O 3 2 Administrative Communications Contact FOB O 1 2 F.O.B. Related Instructions 0010 LIN M LIN-UIT-PKG-PO4-PRS-QTY-REF-PER-SDP-FST-SHP-TD1-TD3-TD LIN M 1 1 Item Identification UIT M 1 2 Unit Detail PKG O >1 2 Marking, Packaging, Loading PO4 O >1 2 Item Physical Details PRS O 1 2 Part Release Status QTY O 1 2 Quantity REF O 12 2 Reference Identification PER O 1 2 Administrative Communications Contact SDP O 1 2 ShipDelivery Pattern 0080 FST O FST-DTM-SDQ-JIT FST M 1 2 Forecast Schedule DTM O >1 3 DateTime Reference SDQ O >1 3 Destination Quantity 0110 JIT O 96 3 JIT-REF 0110 JIT M 1 3 Just-In-Time Schedule REF O Reference Identification 0140 SHP O 10 2 SHP-REF SHP M 1 2 ShippedReceived Information REF O 12 3 Reference Identification TD1 O 1 2 Carrier Details (Quantity and Weight) TD3 O 1 2 Carrier Details (Equipment) TD5 O 1 2 Carrier Details (Routing SequenceTransit Time) CTT O 1 0 Transaction Totals SE M 1 0 Transaction Set Trailer GE C 1 0 Functional Group Trailer IEA M 1 0 Interchange Control Trailer Date 6
7 STANDARD JSO-N ISA M 1 0 Interchange Control Header Tag Name St Format St Format Usage Remark ISA I01 Authorization Information M ID 22 M ID 22 I02 Authorization Information M AN 1010 M AN 1010 I03 Security Information M ID 22 M ID 22 I04 Security Information M AN 1010 M AN 1010 I05 Interchange ID M ID 22 M ID 22 I06 Interchange Sender ID M AN 1515 M AN 1515 I05 Interchange ID M ID 22 M ID 22 I07 Interchange Receiver ID M AN 1515 M AN 1515 I08 Interchange Date M DT 66 M DT 66 I09 Interchange Time M TM 44 M TM 44 I10 I11 Interchange Control s Identifier Interchange Control Version Number M ID 11 M ID 11 M ID 55 M ID 55 I12 Interchange Control Number M N0 99 M N0 99 I13 Acknowledgment Requested M ID 11 M ID 11 I14 Usage Indicator M ID 11 M ID 11 I15 Component Element Separator M AN 11 M AN 11 ISA*00* *00* *01*XXXXXXXXXXXXXXX*01*XXXXXXXXXXXXXXX*070808*1646*U*00401* *0*P*:! Date 7
8 STANDARD JSO-N GS C Functional Group Header Tag Name St Format St Format Usage Remark GS 479 Functional Identifier Code M ID 22 M ID 22 SH = shipment 142 Application Sender's Code M AN 215 M AN 215 mutually defined code 124 Application Receiver's Code M AN 215 M AN 215 mutually defined code 373 Date M DT 88 M DT 88 interchange creation date 337 Time M TM 48 M TM 48 interchange creation time 28 Group Control Number M N0 19 M N0 19 Counter; 1 st message = 1, 2 nd message = 2, up to Responsible Agency Code M ID 12 M ID Version Release Industry Identifier Code M AN 112 M AN 112 GS*SH*SENDER-EDI-CODE*RECEIVER-EDI-CODE* *1646*1*X*004010! Date 8
9 STANDARD JSO-N ST M 1 0 Transaction Set Header Tag Name St Format St Format Usage Remark ST 143 Transaction Set Identifier Code M ID 33 M ID Transaction Set Control Number ST*862*1! M AN 49 M AN 49 Date 9
10 STANDARD JSO-N BSS M 1 0 Beginning Segment for Shipping ScheduleProduction Sequence Tag Name St Format St Format Usage Remark BSS 353 Transaction Set Purpose Code M ID 22 M ID = replace 127 Reference Identification M AN 130 M AN 130 GAZ assigned release number 373 Date M DT 88 M DT 88 date call-f creation 675 Schedule Type M ID 22 M ID 22 SH = shipment based 373 Date M DT 88 M DT 88 horizon start date 373 Date M DT 88 M DT 88 horizon end date 328 Release Number C AN 130 C AN 130 GAZ assigned rlease number 127 Reference Identification C AN 130 C AN Contract Number O AN 130 O AN Purchase Order Number O AN 122 O AN Schedule Quantity O ID 11 O ID 11 A = actual discrete quantity BSS*05* * *SH* * * ****A! Date 10
11 STANDARD JSO-N N1 O N1-N2-N3-N4-REF-PER-FOB N1 M 1 1 Name Tag Name St Format St Format Usage Remark N1 98 Entity Identifier Code M ID 23 M ID 23 MT = release issuer ST = ship to SF = ship from (plant) SU = supplier, manufacturer 93 Name C AN 160 C AN 160 when N101 = MI: buyer name when N101 = ST: Nizhny Novgorod GAZ when N101 = SF: supplier-plant when N101 = SU: supplier party 66 Identification Code C ID 12 C ID Identification Code C AN 280 C AN Entity Relationship Code O ID 22 O ID Entity Identifier Code O ID 23 O ID 23 N1*MI*BUYERPARTY! N1*ST*NIZHNY NOVGOROD GAZ! N1*SF*SUPPLIERPLANT! N1*SU*SUPPLIERPARTY Date 11
12 STANDARD JSO-N LIN M LIN-UIT-PKG-PO4-PRS-QTY-REF-PER-SDP-FST-SHP-TD1- TD3-TD LIN M 1 1 Item Identification Tag Name St Format St Format Usage Remark LIN 350 Assigned Identification O AN 120 O AN 120 call-f line item number 235 ProductService ID M ID 22 M ID 22 BP = buyers part number 234 ProductService ID M AN 148 M AN 148 GAZ assigned part number 235 ProductService ID C ID 22 C ID 22 PO = purchase order number 234 ProductService ID C AN 148 C AN 148 GAZ purchase order number 235 ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID ProductService ID C AN 148 C AN ProductService ID C ID 22 C ID 22 Date 12
13 STANDARD JSO-N Tag Name St Format St Format Usage Remark 234 ProductService ID C AN 148 C AN 148 LIN*1*BP* AA*PO*A1A2A3A4A5! Date 13
14 STANDARD JSO-N LIN M LIN-UIT-PKG-PO4-PRS-QTY-REF-PER-SDP-FST-SHP-TD1- TD3-TD UIT M 1 2 Unit Detail Tag Name St Format St Format Usage Remark UIT C001 Composite Unit Measure M M PC = pieces 355 Unit or Basis for Measurement Code M ID 22 M ID Exponent O R 115 O R Multiplier O R 110 O R Unit or Basis for Measurement Code O ID 22 O ID Exponent O R 115 O R Multiplier O R 110 O R Unit or Basis for Measurement Code O ID 22 O ID Exponent O R 115 O R Multiplier O R 110 O R Unit or Basis for Measurement Code O ID 22 O ID Exponent O R 115 O R Multiplier O R 110 O R Unit or Basis for Measurement Code O ID 22 O ID Exponent O R 115 O R Multiplier O R 110 O R Unit Price C R 117 C R Basis Unit Price Code O ID 22 O ID 22 UIT*PC! Date 14
15 STANDARD JSO-N LIN M LIN-UIT-PKG-PO4-PRS-QTY-REF-PER-SDP-FST-SHP-TD1- TD3-TD REF O 12 2 Reference Identification Tag Name St Format St Format Usage Remark REF 128 Reference Identification M ID 23 M ID 23 DK = dock number 127 Reference Identification C AN 130 C AN 130 code identifying the receiving dock at the plant 352 Description C AN 180 C AN 180 C040 Reference Identifier O O 128 Reference Identification M ID 23 M ID Reference Identification M AN 130 M AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN 130 REF*DK*DOCK-9! Date 15
16 STANDARD JSO-N LIN M LIN-UIT-PKG-PO4-PRS-QTY-REF-PER-SDP-FST-SHP-TD1- TD3-TD PER O 1 2 Administrative Communications Contact Tag Name St Format St Format Usage Remark PER 366 Contact Function Code M ID 22 M ID 22 BD = buyer or department 93 Name O AN 160 O AN 160 buyer name 365 Communication Number C ID 22 C ID 22 EM = electronic mail 364 Communication Number C AN 180 C AN 180 address 365 Communication Number C ID 22 C ID 22 FX = fax 364 Communication Number C AN 180 C AN 180 fax number 365 Communication Number C ID 22 C ID 22 TE = telephone 364 Communication Number C AN 180 C AN 180 telephone number 443 Contact Inquiry Reference O AN 120 O AN 120 PER*BD*JOHNBROWN*EM*JOHN.BROWN@GAZAUTO.COM*FX* *TE* ! Date 16
17 STANDARD JSO-N FST O FST-DTM-SDQ-JIT FST M 1 2 Forecast Schedule Tag Name St Format St Format Usage Remark FST 380 Quantity M R 115 M R 115 actual discrete quantity, as qualified in BSS Forecast M ID 11 M ID 11 C = firm 681 Forecast Timing M ID 11 M ID 11 D = discrete 373 Date M DT 88 M DT 88 shipment date 373 Date O DT 88 O DT DateTime C ID 33 C ID = requested ship date 337 Time C TM 48 C TM Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN Planning Schedule Type Code O ID 22 O ID 22 FST*99999*C*D* **010! Date 17
18 STANDARD JSO-N JIT O 96 3 JIT-REF 0110 JIT M 1 3 Just-In-Time Schedule Tag Name St Format St Format Usage Remark JIT 380 Quantity M R 115 M R 115 Quantity to be shipped 337 Time M TM 48 M TM (start business day) JIT*99999*0800! Date 18
19 STANDARD JSO-N JIT O 96 3 JIT-REF REF O Reference Identification Tag Name St Format St Format Usage Remark REF 128 Reference Identification M ID 23 M ID 23 DK = dock number 127 Reference Identification C AN 130 C AN 130 dock number 352 Description C AN 180 C AN 180 C040 Reference Identifier O O 128 Reference Identification M ID 23 M ID Reference Identification M AN 130 M AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN 130 REF*DK*DOCK-9! Date 19
20 STANDARD JSO-N SHP O 10 2 SHP-REF SHP M 1 2 ShippedReceived Information Tag Name St Format St Format Usage Remark SHP 673 Quantity O ID 22 O ID = discrete quantity 02 = cumulative quantity 380 Quantity C R 115 C R DateTime C ID 33 C ID 33 when SHP01 = 01 XXX = outstanding quantity XXX = urgent delivery quantity when SHP01 = 02 XXX = cumulative quantity scheduled since start date 011 = cumulative quantity shipped since start date 050 = cumulative quantity received since start date 373 Date C DT 88 C DT 88 when SHP01: start horizon date 337 Time C TM 48 C TM 48 not used 373 Date O DT 88 O DT 88 when SHP01 = 02: when SHP03 = 011: suppliers last ship date when SHP03 = 050: GAZ last receipt date 337 Time O TM 48 O TM 48 SHP*01*999999*XXX* ** ! SHP*02*999999*011*** ! Date 20
21 STANDARD JSO-N SHP O 10 2 SHP-REF REF O 12 3 Reference Identification Tag Name St Format St Format Usage Remark REF 128 Reference Identification M ID 23 M ID 23 SI = shippers identifying number for the shipment 127 Reference Identification C AN 130 C AN 130 dispatch note number the last ASN booked 352 Description C AN 180 C AN 180 C040 Reference Identifier O O 128 Reference Identification M ID 23 M ID Reference Identification M AN 130 M AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN Reference Identification C ID 23 C ID Reference Identification C AN 130 C AN 130 REF*SI* ! Date 21
22 STANDARD JSO-N SE M 1 0 Transaction Set Trailer Tag Name St Format St Format Usage Remark SE 96 Number Included Segments M N0 110 M N Transaction Set Control Number SE*1*XXXX! M AN 49 M AN 49 Date 22
23 STANDARD JSO-N GE C 1 0 Functional Group Trailer Tag Name St Format St Format Usage Remark GE 97 Number Transaction Sets Included M N0 16 M N Group Control Number M N0 19 M N0 19 GE*1*1! Date 23
24 STANDARD JSO-N IEA M 1 0 Interchange Control Trailer Tag Name St Format St Format Usage Remark IEA I16 Number Included Functional Groups M N0 15 M N0 15 I12 Interchange Control Number M N0 99 M N0 99 IEA*1* ! Date 24
25 STANDARD JSO-N Example Message Following example is only illustrative and does not necessarily reflect an existing situation. It may never be used as a basis for programming or implementing this message. ISA*00* *00* *01*XXXXXXXXXXXXXXX*01*XXXXXXXXXXXXXXX*070808*1646*U*00401* *0*P*:! GS*SH*SENDER-EDI-CODE*RECEIVER-EDI-CODE* *1646*1*X*004010! ST*862*1! BSS*05* * *SH* * * ****A! N1*MI*BUYERPARTY! N1*ST*NIZHNY NOVGOROD GAZ! N1*SF*SUPPLIERPLANT! N1*SU*SUPPLIERPARTY LIN*1*BP* AA*PO*A1A2A3A4A5! UIT*PC! REF*DK*DOCK-9! PER*BD*JOHNBROWN*EM*JOHN.BROWN@GAZAUTO.COM*FX* *TE* ! FST*99999*C*D* **010! JIT*99999*0800! REF*DK*DOCK-9! SHP*01*0*XXX* ** ! [XXX=qualifier for outstanding quantity] SHP*01*100*XXX* ** ! [XXX=qualifier for urgent delivery quantity] SHP*02*133*XXX*** ! [XXX=qualifier for cumulative quantity scheduled since start date] SHP*02*10500*011*** ! SHP*02*101*050***200807! REF*SI* ! SE*1*1! GE*1*1! IEA*1* ! Date
ANSI X12 version 4010 830 Planning Schedule with Release Capability
ANSI X12 version 4010 830 Planning Schedule with Release Capability VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 04/07/00 Trading Partner: All 830 All Partners 4010 Inbound.rtf 1 830 Planning
More informationBORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE
BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE 1 Implementation Guideline 830 3-Jun-15 830 BorgWarner Material Release v004010 Functional Group ID=PS Introduction: This Standard contains
More information850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft
850 Purchase Order X12/V4030/850: 850 Purchase Order Version: 1.0 Draft Author: Supplier Automation Trading Partner: Ross Stores, Inc. Notes: This is the standard guide prepared by JPMC/Xign for Merchandise
More information856 Advanced Shipping Notices (ASN)
NEXTEER Supplier Information Packet 856 Advanced Shipping Notices (ASN) Revised March, 2010 s GENERAL INFORMATION This packet is to provide information to Nexteer and SteeeringMex Direct Suppliers who
More informationToyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira
Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira Forward The widespread implementation of EDI (Electronic Data Interchange) throughout
More informationElectronic Data Interchange
Electronic Data Interchange Transaction Set: 856 Supplier Advance Ship Notice ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
More informationElectronic Data Interchange
Electronic Data Interchange Transaction Set: 850 Supplier Purchase Order ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
More informationANSI X12 version 4010 856 Advance Ship Notice
ANSI X12 version 4010 856 Advance Ship Notice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 05/01/07 Trading Partner: All 856 All Partners 4010 Outbound.rtf 1 856 Ship Notice/Manifest Functional
More informationANSI X12 ASN 856 Version 002040
ADVANCE SHIP NOTICE MESSAGE ANSI X12 ASN 856 Version 002040 V01 23/08/12 Page 1/36 Property of VALEO Duplication Prohibited Table of Contents 1 THE ADVANCE SHIP NOTICE MESSAGE...4 1.1 Introduction...4
More informationPos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000
810 Invoice Introduction: Functional Group ID=IN This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data
More informationInvoice. Transaction Set (810) (Outbound from TI)
Invoice Transaction Set (810) (Outbound from TI) ANSI X12 Version Format: 3020 Date: October 1996 Copyright 1996 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in
More informationElectronic Document Interchange Standards Version 5050
Yazaki North America, Inc. Electronic Document Interchange Standards Version 5050 Dear Supplier. Enclosed you will find current versions of our EDI Document Guidelines for our Suppliers that are shipping
More information846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007
846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007 The following is an outline of what is expected when receiving VICS
More informationMazda North American Operations EDI Supplier Documentation October 20, 2015
EDI Supplier Documentation October 20, 2015 March 2006 Revision History Merged separate files into this one document Sept 13, 2007 Revised 856 BSN, Element 02, on page 101 Aug 18, 2008 Revised sample 830
More information2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY
2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH
More informationVERSION: ANSI X-12 004010
855 Purchase Order Acknowledgment VERSION: ANSI X-12 004010 Author: Family Dollar Stores FDS 855 layout ( VMI Order s) 1 For internal only 855 Purchase Order Acknowledgment Functional Group=PR This Draft
More informationX12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O)
X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O) 861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC This Draft Standard for Trial Use contains the
More information214 Transportation Carrier Shipment Status Message - LTL
214 Transportation Carrier Shipment Status Message - LTL Lowe's 214 - LTL Shipment Status Message Version: 4010 Author: Lowe's Companies, Inc Modified: 2/27/2013 Notes: This 214 Implementation Guide should
More information810 Invoice ANSI ASC X12 Version 4010
810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855
More informationEDI GUIDELINES INVOICE 810 VERSION 4010
EDI GUIDELINES INVOICE 810 VERSION 4010 Rev. 7/23/2013 GLOSSARY OF TERS Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each preceded by an element separator,
More informationEDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)
EDI IMPLEMENTATION GUIDE 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel) Revision Date: November 7, 2013 Regular (Non Steel) Rev 6 X12 004010 pg. 1 856 Ship Notice/Manifest Introduction: Functional
More informationImplementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier
Implementation Guidelines: ANSI X12 Transaction Set 850 (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg
More informationImplementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS 004010 824 S
Implementation Guidelines: ANSI X12 Transaction Set 824 DOCUMENT NUMBER: ICS 004010 824 S ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg Masters Effective Date:
More informationCVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X12-4010
CVS/Caremark Implementation Guide 810 RX DC Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ST Transaction Set Header... 2 BIG Beginning Segment for Invoice...
More informationDart Container Corporation. EDI 810 Outbound Invoice Version 4010
Dart Container Corporation EDI 810 Outbound Invoice Version 4010 HEADER SECTION ST - Transaction Set Header 01 Transaction Set Identifier N0 1/10 810 02 Transaction Set Control Number AN 4/9 Unique Sequence
More informationEDI GUIDELINES PURCHASE ORDER 850 VERSION 4010
EDI GUIDELINES PURCHASE RDER 850 VERSIN 4010 Rev. 7/23/2013 GLSSARY F TERS BLACKHAWK NETWRK s 850 GUIDELINES Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each
More information84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010. August 21, 2007
84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010 August 21, 2007 1 of 16 84 LUMBER EDI PROFILE 1. 84 LUMBER PERSONNEL Linda Smitley, EDI
More informationACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.
ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 *NOTES: PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS. EXISTING DOCUMENT - SEE HIGHLIGHTED FIELDS FOR NEW ADDITIONS PLEASE REVIEW
More information810 Invoice Revised 01/26/15
Functional Group ID=IN Introduction: This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange
More information860 Purchase Order Change Request Buyer Initiated
860 Purchase Order Change Request Buyer Initiated Set Number - 860 Set Name Purchase Order Change Request Buyer Initiated Functional Group - PC This Draft Standard for Trail Use contains the format and
More informationVOLVO Dealer Programs 810 Invoice EDI Guideline
VOLVO 1. 810 INVOICE General This document describes Volvo's application of the ANSI X12 transaction set. The specification offers a detailed description of those data elements which will be used. The
More informationEDIFACT DESADV D.97A for suppliers (Benteler Europe)
Message Implementation Guideline suppliers (Benteler Europe) based on DESADV Despatch advice message UN D.97A S3 Version: 1.1 Variant: 1 Issue date: 17.03.2015 Author: Benteler Deutschland GmbH 1 Introduction.
More informationANSI X12 4010 867 - Product Transfer and Resale Report
ANSI X12 4010 867 - Product Transfer and Resale Report Version: R8674010v1 Draft Modified: 10/27/2004 Notes: 10/26/2004 - In an effort to validate that 100% of a partners reporting locations have been
More informationEDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message
EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft Standard for Trial Use contains the format
More informationANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message
ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message Revised 01/04/11 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft
More informationDetail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header
820 Payment Order / Remittance Advice Segment ID Description Location ISA Interchange Control Header Heading GS Functional Group Header Heading ST Transaction Set Header Heading 1 BPR Beginning Segment
More informationEDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft
EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier
More informationEDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010
EDI GUIDELINES otor Carrier Load Tender 204 VERSION 004010 ASC X12 Version 4010 1 April 5, 2007 204 otor Carrier Load Tender Functional Group ID=S Introduction: This Draft Standard for Trial Use contains
More informationStaples Supplier Electronic Data Interchange Implementation Guide
Staples Supplier Electronic Data Interchange Implementation Guide June 2010 ANSI 4010 Revision 002.13 Staples Supplier EDI Implementation Guide Table of Contents GETTING STARTED WITH STAPLES...3 VAN (Value
More information810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:
810 Invoice X12/V4010/810 : 810 Invoice Version: 2.3 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 3/17/2014 Trading Partner: Notes: Table of Contents 810 Invoice... 1 ISA
More informationANSI X12 version 4010 864 Text Message
ANSI X12 version 4010 864 Text Message VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/22/00 Trading Partner: All Partners 864 All Partners 4010 Inbound.rtf 1 Superior Essex 864 Text Message
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 002040CHRY FCA
More informationBill of Lading Number REF02 127 Reference Identification M AN 1/30 MustUse
Updated 05/08/06 810 Invoice Version 005010 X12 Functional Group=IN BIG Beginning Segment for Invoice Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 BIG01 373 Date Description: Invoice Date
More informationANSI X12 version 4010 820 Remittance Advice
ANSI X12 version 4010 820 Remittance Advice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/18/00 Trading Partner: All Notes: Remittance Advice 820's are transmitted with payment to the
More information3/31/08 ALTRA INDUSTRIAL MOTION Invoice - 810. Inbound 810 X12 4010. Page 1 Created by Ralph Lenoir
Inbound 810 X12 4010 Page 1 DOCUMENT OVERVIEW This document contains the requirements for the standard EDI 810 document in ANSI version 4010 as d by ALTRA INDUSTRIAL MOTION. It describes the layout, syntax,
More informationTHE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A
THE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A Version 1.1 Author: Torbjörn Grahm / Encode AB Change log: 2015-03-02 Hans Sturesson Added status 3 on G12/SCC 1 P a g e THE DELIVERY FORECAST MESSAGE
More information997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.
This document defines Safeway Inc. s guidelines of EDI Transaction Set 824, Application Advice, VICS Version 004010. It does not vary from the X12/UCS/VICS standards. Only segments and elements that are
More information810 Invoice ANSI X.12 Version 5010
810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning
More informationThe EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.
EDI 810 File Format Direct Commerce (DCI) supports the EDI 810 format for uploaded invoice transactions. This document describes our implementation of the EDI 810 format for invoicing Carolinas Healthcare
More informationTHE INVOIC MESSAGE EANCOM97/EDIFACT D.96A
Polska THE INVOIC MESSAGE EAN97/EDIFACT D.96A Issue 1.0, 12.2013 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted
More informationSupply Chain Merchandise Logistics E-Commerce Purchase Order
Supply Chain Merchandise Logistics E-Commerce Purchase Order E-Commerce Purchase Order Page 1 of 53 Contents Introduction 3 E-Commerce ordering How Myer Orders merchandise 4 Purchase order format 4 Basic
More informationBulk EDIFACT ASN MESSAGE FORMAT
Bulk EDIFACT ASN MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS 9 th October, 2008 Page 1 of 17 Issue 2.1 TABLE OF CONTENTS 1. OVERVIEW... 3 1.1 Introduction... 3 2. SEGMENTS LAYOUT... 4 2.1 Legend...
More informationHella EDIFACT INVRPT
Message Documentation Hella EDIFACT INVRPT based on INVRPT Inventory report message UN D.97A S3 Structure Chart Branching Diagram Segment Details Version: 97 Variant: A Issue date: 28.08.2007 Top of Page
More informationKANSAS CITY SOUTHERN EDI On-Boarding Guide
KANSAS CITY SOUTHERN EDI On-Boarding Guide EDI Standards and Requirements v1.0 2015 by Kansas City Southern 1 Table of Contents 1.0 INTRODUCTION... 3 1.1 INTRODUCTION... 3 1.2 PURPOSE OF THE DOCUMENT...
More informationAdobe - EDIFACT D97.A ORDERS
Adobe - EDIFACT D97.A ORDERS Purchase Order Message Shrink Wrap Product Version: UNEDIFACT D97A ORDERS Company: Adobe Modified: 9/30/2015 Table of Contents ORDERS Purchase order message... 1 UNB INTERCHANGE
More informationADOBE ANSI X12 810 4010. Version: 1.0
ADOBE ANSI X12 810 4010 Version: 1.0 Author: Adobe Systems Modified: 06/15/2009 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of
More informationCustomer EDI Guidelines United States 810 Invoice
Customer EDI Guidelines United States 810 Invoice Author: CSC Consulting EMD 810_USA.doc 1 For internal only 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes
More informationShipping Authorization -- EDI-862
TRUCK MANUFACTURING BUSINESS PROCESS GUIDE Version 002040 April 11, 2016 EDI 862 Ship Schedule Document Number: PUR-2040 Revision: 3.0 Revision Date: April 11, 2016 Written by: Susan Ewing Reviewed/ Approved
More informationNAF Nätverk för Affärsutveckling i Försörjningskedjan
VCC EDI DEMANDS Training session in Chengdu and Shanghai 2012 ----------------------------------------------------- Eric Ristenstrand VCC Elsa Nylander VCC Yang Huang (Tony) VCC Sten Lindgren Odette Sweden
More informationVDP Program Vendor Guidelines
AutoZone Merchandising Systems Vendor Reference VDP Program Vendor Guidelines (EDI X12 version 004010) Revised by Dept. 8309 EDI group February 2007 Portions of this document contain hyperlinks that are
More informationAMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS
SECTION PAGE ---------------------------------------------- ----- APPLICATION GUILDELINE : Summary of Data to be Included in the Application Advice.. 824.2 Detailed Documentation of the 824 Transaction
More informationUnified Grocers 820 EFT Specifications Remittance Advice Document Structure
Unified Grocers 820 EFT Specifications Remittance Advice Document Structure LEVEL SEGMENT NAME Req Max Use Envelope Header ISA Interchange Header M 1 GS Group Header M 1 ST Transaction Set Header M 1 Loop
More information824 Application Advice
824 Application Advice X12/V4040/824: 824 Application Advice Version: 2.1 Final Author: Insight Direct USA, Inc. Modified: 10/12/2006 824 Application Advice Functional Group=AG This Draft Standard for
More informationBIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010
BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010 Last revised 3/2/2015 9:47:55 AM - 1 - Summary of Changes 2012 Changes Return merchandise must be on
More informationPortland General Electric Implementation Standard
Portland General Electric Implementation Standard for Electronic Data Interchange TRANSACTION SET 810 Ver/Rel 004010 Invoice Inbound from Vendor 8104010I 1 August 18, 2004 810 Invoice Functional Group
More information856 Ship Notice/Manifest - R US CANADA
856 Ship Notice/Manifest - R US CANADA Introduction: Functional Group ID=SH This Implementation Guide contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856)
More informationEDI and IDOC Implementation for SAP Sales Order Processing Peter Sammons, IT Architect, Courier Corporation
[ EDI and IDOC Implementation for SAP Sales Order Processing Peter Sammons, IT Architect, Courier Corporation [ Learning Points What is EDI. What are IDOCs. Configuring SAP for EDI. Managing IDOCs in SAP
More informationZF Group North American Operations. EDI Implementation Guide
EDI Implementation Guide EDIFACT DESADV D.97A Version 1.4 Authors: ZF NAO EDI Team Publication Date: April 10, 2003 Created: April 10, 2003 Modified: June 7, 2005 Table of Contents Introduction... 1 ZF
More informationPURCHASE ORDER RESPONSE
EDI GUIDELINE for PURCHASE ORDER RESPONSE Message Type ORDRSP Version 1 Release 921 07/00 Seite 1 Table of Contents PURCHASE ORDER RESPONSE Message Layout Diagram... 3 Explanatory Requirements... 3 Segment
More information856 Advance Ship Notice Supplier Implementation Guide November 2015
856 Advance Ship Notice Supplier Implementation Guide November 2015 856 Ship Notice/Manifest INTRODUCTION This implementation guideline for the 856 Ship Notice/Manifest electronic data interchange (EDI)
More informationHIPAA EDI Companion Guide for 835 Electronic Remittance Advice
HIPAA EDI Companion Guide for 835 Electronic Remittance Advice ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 (TR3) Version 005010X221A1 Companion Guide Version: 2.0 Disclosure
More informationCVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X12-4010
CVS/Caremark Implementation Guide 852 Product Activity Data Warehouse Movement Version X12-4010 852 Mapping Specifications v4010 i Table of Contents 852 Product Activity Data... 1 ST Transaction Set Header...
More informationImplementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)
Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound (v2002) ICS Interchange Control Structures Functional Group ID= Introduction: The purpose of this standard is to
More informationEDI Specifications. 810 - Invoice (Supplier v4010)
(Supplier v400) December 200 80 Purchase rder - Functional Group=IN VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer Invoice
More informationEDI Specifications. 856 - Advance Ship Notice (Supplier v4010)
(Supplier v400) December 200 856 Ship Notice/anifest- Functional Group=SH VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer
More informationDELJIT D97A / CALDEL
CALL-OFF DELJIT D97A / CALDEL Message Implementation Guideline The detail description of DELJIT / CALDEL D97A message used for EDI communication between ŠKODA AUTO a. s. and its suppliers Call-offs of
More informationPARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland
PARTY INFORMATION MESSAGE PARTIN Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and accepted
More informationTo indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^20001022^12345^20000930^0000123456^
Invoice (810) VICS 004010 The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided. BIG Beginning
More informationProduce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)
Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN) About this Guidance Document (Revision 1.0) Guidelines are generally accepted, informally standardized
More informationINVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland
INVENTORY REPORT MESSAGE INVRPT Version 1.2 EANCOM 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and
More informationEDI. Overview. A Practical Guide to EDI and the TrueCommerce EDI Platform
EDI Overview A Practical Guide to EDI and the TrueCommerce EDI Platform The purpose of this paper is to provide an overview of EDI or Electronic Data Interchange. It explains the technology, the benefits
More informationUltramar Ltd IMPLEMENTATION GUIDE
IMPLEMENTATION GUIDE for electronic data interchange November 2002 TABLE OF CONTENTS INTRODUCTION... 1 KEY CONTACTS... 1 EDI STANDARDS... 1 DOCUMENT PROCESSING FREQUENCY... 1 RESPONSIBILITY FOR COMMUNICATION
More informationPurchase Orders Message ORDERS (EDIFACT D97A)
Purchase Orders Message ORDERS (EDIFACT D97A) VERSION: 1.0 Author: Seagate B2B Notes: EDIFACT ORDERS Message to be d with OEM, Distribution or Retail partners. ORDERS Purchase Order Message... Page UNB
More informationForecast / Planning Business Models
Forecast / Planning Business Models Draft February 1996 Preface Purpose: The purpose of this document is to model the flow of documents used in some common business processes for forecasting. Any implementation
More informationElectronic Data Interchange (EDI) Standards 810 Invoice Version 4010
Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010 Approved: 07/26/2010 Authors: Dave Danko HCR ManorCare is a leading provider of short and long term medical and rehabilitation care.
More informationMERITOR. EDI Business Process Guide
MERITOR EDI Business Process Guide CVA=Commercial Vehicle Aftermarket CVS=Commercial Vehicle Systems September 2012 Business Process Guide Page 1 of 8 Table of Contents 1 Business Process Overview... 3
More informationElectronic Data Interchange EDI
Electronic Data Interchange EDI What is EDI? Electronic Data Interchange is the computer to computer exchange of business documents in standard formats between companies. The EDI standards are developed
More informationORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version 92.1. 02/2011 Page 1
EDI GUIDELINE for ORDERS 92.1 Message Type ORDERS, ORDCHG Version 1 Release 921 02/2011 Page 1 Table of Contents PURCHASE ORDER Message Layout Diagram... 3 Explanatory Requirements... 3 Segment / Element
More informationS.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT
S.2 STRUCTURE OF AN EDIFACT TRANSMISSION This section is substantially based on the ISO 9735 document: EDIFACT application level syntax rules, first released on 1988-07-15, amended and reprinted on 1990-11-01,
More information810 Invoice. Introduction: Heading: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA
ASN HDMA Electronic Data Interchange (EDI) Guidelines for the Advance Ship Notice to Support Implementation of DSCSA HDMA Electronic Data Interchange (EDI) Guidelines for the Advance Ship Notice to Support
More informationNow, suppliers can also select EDI as a method for receiving Change and Cancel Orders.
850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
More informationProduct Information CDI Premium EDI module
CDI EDI with the TSI EDI communications capabilities, allows you to send receive orders, invoices etc with your customers and vendors. EDI software will greatly enhance the distribution process. These
More informationEDI Compliance Report
The EDI Deenvelope business processes (that is, X12Deenvelope, EDIFACTDeenvelope, CIIDeenvelope) perform a compliance check to verify absolute adherence to the supported EDI standards, including ANSI X12,
More informationDRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA
DRS Defect Report Inbound 322 DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA TABLE OF CONTENTS Revision History...3 DRS Defect Report
More information810 - Invoice. Set Number - 810 Set Name - Invoice Functional Group - IN
810 - Invoice Set Number - 810 Set Name - Invoice Functional Group - IN This standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More information322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY
ELECTRONIC DATA INTERCHANGE (EDI) 322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY USING ASC X12 TRANSACTION SET 322 VERSION 004010 07/01/04 2 Table of Contents Introduction... 3 Sample 322... 4 The
More informationConsignment No: Receiving Plant (Customer): example customer customer's street 57a 98765 City of customer GB
EDI Waybill Supplier Plant: 56931 -Number: Example Plant Description 1 Example Supplier Example City GB Consignment No: Receiving Plant (Customer): -Number: example customer customer's street 5a 9865 City
More informationNote: The following information is required on all Merchandise Invoices:
810 NORDSTROM CANADA Invoice Functional Group=IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the
More informationORDERS Purchase Order Message
ORDERS Purchase Order Message UN/EDIFACT Version D.93A ERICO International 31700 Solon Rd. Solon, OH 44139 ii Preface Purpose and Scope The purpose of this guide is to provide ERICO s trading partners
More information