MFG830S Manufacturing Release 2001 01052010...MFG830S_2001_01052010 - MR (X12-2001) - 2 - January 5,...

This document contains proprietary and confidential information that may not be disclosed without the prior written permission of Nissan North America. Unauthorized use or misuse of this information and its contents is strictly prohibited. Nissan North America vigorously protects its rights.

Nissan North America EDI

Implementation Guide

MFG830S_2001_01052010 Material Release (Manufacturing)

ANSI X-12 Version 2001

Revised on January 5, 2010

MFG830S_2001_01052010 - MR (X12-2001) - 1 - January 5, 2010

Nissan North America Manufacturing EDI



830 Material Release for Manufacturing

Functional Group ID=PO Introduction: This Standard for contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations. The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders. Nissan's use of the 830 most closely matches (3) above Notes: Key Point: ANSI version 2001 Use with Nissan ENVELOPE guideline Nissan Pos. Seg. Req. Loop Notes and Attribute No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BFR Beginning Segment for Planning Schedule M 1 LOOP ID - N1 1 Must Use 090 N1 Name - Supplier Code O 1 LOOP ID - N1 1 Must Use 090 N1 Name - Nissan Analyst O 1 140 PER Administrative Communications Contact -

Nissan Release Sr AnalystO 3

LOOP ID - LIN 10000 M 300 LIN Item Identification M 1 M 310 UNT Unit of Measure M 1 Must Use 330 J2X Item Description O 1 450 PER Administrative Communications Contact -

Nissan Parts Order AnalystO 1

LOOP ID - N1 1 510 N1 Name - Dock Location O 1

MFG830S_2001_01052010 - MR (X12-2001) - 2 - January 5, 2010




LOOP ID - SDP 104 M 580 SDP Ship/Delivery Pattern M 1 M 590 FST Forecast Schedule M 104 610 ATH Resource Authorization O 2 650 TD5 Carrier Details (Routing Sequence/Transit

Time) O 1

680 MAN Marks and Numbers O 1 M 690 CTT Transaction Totals M 1 M 700 SE Transaction Set Trailer M 1

MFG830S_2001_01052010 - MR (X12-2001) - 3 - January 5, 2010




Segment: ST Transaction Set Header Position: 010 Loop: Level: Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes:

Notes: Sample Data ST*830*0001

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M ST01 143 Transaction Set Identifier Code M ID 3/3M ST02 329 Transaction Set Control Number M AN 4/9 Key Point: Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set. Must match the number in SE02. '0001' through '999999999' FOR ENVELOPING SPECIFICATIONS PLEASE REFER TO THE NNA MANUFACTURING EDI IMPLEMENTATION GUIDE FOR ENVELOPING ANSI X-12

MFG830S_2001_01052010 - MR (X12-2001) - 4 - January 5, 2010




Segment: BFR Beginning Segment for Planning Schedule Position: 020 Loop: Level: Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship or

delivery based forecast; and related forecast envelope dates Syntax Notes: 1 At least one of BFR02 or BFR03 is required.

Notes: Sample Data BFR*00**070101*DL*A*070101*070109*070101**DP

BFR*04**070101*DL*A*070101*070109*070101**SP BFR*05**070101*DL*A*070101*070109*070101**CP

Data Element Summary

User Ref. Data Attribute Des. Element Name Attributes M BFR01 353 Transaction Set Purpose Code M ID 2/2 Key Point: For this transaction, Nissan has redefined ANSI codes used as follows:

00 Original Key Point: Nissan has redefined '00' as Non-Sequenced Delivery

04 Change Key Point: Nissan uses '04' to mean Sequenced Delivery

05 Replace Key Point: Nissan has defined '05' as Modular Sequenced Delivery

BFR03 328 Release Number C AN 6/6 Key Point: Nissan populates this element with release create date (YYMMXX) where XX

is an alphanumeric release number suffix.M BFR04 675 Schedule Type Qualifier M ID 2/2 Key Point: Schedule is based on the date that the parts are to arrive at the delivery

MFG830S_2001_01052010 - MR (X12-2001) - 5 - January 5, 2010




destination DL Delivery BasedM BFR05 676 Schedule Quantity Qualifier M ID 1/1 A Actual Discrete QuantitiesM BFR06 373 Date - Horizon Start M DT 6/6 Key Point: First date in release horizon (YYMMDD)M BFR07 373 Date - Horizon End M DT 6/6 Key Point: Last date in release horizon (YYMMDD)M BFR08 373 Date - Release Generation M DT 6/6 Key Point: Date release was generated (YYMMDD) BFR10 367 Contract Number - Nissan Facility ID O AN 2/2 Key Point: 'CP' = Canton Plant

'DP' = Decherd Plant 'SP' = Smyrna Plant

MFG830S_2001_01052010 - MR (X12-2001) - 6 - January 5, 2010




Segment: N1 Name - Supplier Code Position: 090 Loop: N1 Optional (Must Use) Level: Usage: Optional (Must Use) Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required.

Notes: Sample Data N1*SU**92*1234567

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/2 SU Supplier/Manufacturer N103 66 Identification Code Qualifier C ID 1/2 92 Assigned by Buyer or Buyer's Agent N104 67 Identification Code - Supplier Code assigned by Nissan C AN 2/9

MFG830S_2001_01052010 - MR (X12-2001) - 7 - January 5, 2010




Segment: N1 Name - Nissan Analyst Position: 090 Loop: N1 Optional (Must Use) Level: Usage: Optional (Must Use) Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required.

Notes: Sample Data N1*MI*NISSAN

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/2 MI Planning Schedule/Material Release Issuer N102 93 Name C AN 1/25 Key Point: Always 'Nissan'

MFG830S_2001_01052010 - MR (X12-2001) - 8 - January 5, 2010




Segment: PER Administrative Communications Contact - Nissan Release Sr Analyst Position: 140 Loop: N1 Optional (Must Use) Level: Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If PER03 is present, then PER04 is required.

Notes: Sample Data PER*OD*SR. ANALYST*TE*123-456-7890

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 OD Order Department PER02 93 Name O AN 1/13 PER03 365 Communication Number Qualifier O ID 2/2 TE Telephone PER04 364 Communication Number C AN 7/12

MFG830S_2001_01052010 - MR (X12-2001) - 9 - January 5, 2010




Segment: LIN Item Identification Position: 300 Loop: LIN Mandatory Level: Usage: Mandatory Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If LIN04 is present, then LIN05 is required. 2 If LIN06 is present, then LIN07 is required. 3 If LIN08 is present, then LIN09 is required. 4 If LIN10 is present, then LIN11 is required. 5 If LIN12 is present, then LIN13 is required. 6 If LIN14 is present, then LIN15 is required. 7 If LIN16 is present, then LIN17 is required. 8 If LIN18 is present, then LIN19 is required. 9 If LIN20 is present, then LIN21 is required. 10 If LIN22 is present, then LIN23 is required. 11 If LIN24 is present, then LIN25 is required. 12 If LIN26 is present, then LIN27 is required. 13 If LIN28 is present, then LIN29 is required. 14 If LIN30 is present, then LIN31 is required.

Notes: Sample Data LIN**BP*30412 Q1052*PO*PR00009076

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M LIN02 235 Product/Service ID Qualifier M ID 2/2 BP Buyer's Part NumberM LIN03 234 Product/Service ID - Part Number assigned by Nissan M AN 1/19 LIN04 235 Product/Service ID Qualifier O ID 2/2 PO Purchase Order Number LIN05 234 Product/Service ID - Purchase Order Number assigned

by NissanC AN 1/10

MFG830S_2001_01052010 - MR (X12-2001) - 10 - January 5, 2010




Segment: UNT Unit of Measure Position: 310 Loop: LIN Mandatory Level: Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: 1 If UNT03 is present, then UNT02 is required.

Notes: Sample Data UNT*EA

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M UNT01 355 Unit or Basis for Measurement Code M ID 2/2 EA Each

MFG830S_2001_01052010 - MR (X12-2001) - 11 - January 5, 2010




Segment: J2X Item Description Position: 330 Loop: LIN Mandatory Level: Usage: Optional (Must Use) Max Use: 1 Purpose: Syntax Notes:

Notes: Sample Data J2X**F*LH WIDGET

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes J2X02 349 Item Description Type O ID 1/1 F Free-formM J2X03 372 Lading Liability Code - Nissan's Part Description M AN 1/25 Key Point: For this transaction, Nissan has redefined the J2X03 element to be Nissan's part

desription

MFG830S_2001_01052010 - MR (X12-2001) - 12 - January 5, 2010




Segment: PER Administrative Communications Contact - Nissan Parts Order Analyst Position: 450 Loop: LIN Mandatory Level: Usage: Optional Max Use: 1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If PER03 is present, then PER04 is required.

Notes: Sample Data PER*EX*PO ANALYST*TE*123-456-7890

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 EX Expeditor PER02 93 Name O AN 1/13 PER03 365 Communication Number Qualifier O ID 2/2 TE Telephone PER04 364 Communication Number C AN 7/12

MFG830S_2001_01052010 - MR (X12-2001) - 13 - January 5, 2010




Segment: N1 Name - Dock Location Position: 510 Loop: N1 Optional Level: Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required.

Notes: Sample Data N1*ST*DOCK 2

N1*ST*DOCK 12

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/2 ST Ship To N102 93 Name - Dock Location C AN 1/7

MFG830S_2001_01052010 - MR (X12-2001) - 14 - January 5, 2010




Segment: SDP Ship/Delivery Pattern Position: 580 Loop: SDP Mandatory Level: Usage: Mandatory Max Use: 1 Purpose: To identify specific ship/delivery requirements Syntax Notes:

Notes: Sample Data SDP*B*F

SDP*Y*Y

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M SDP01 678 Ship/Delivery or Calendar Pattern Code M ID 1/1 B Monday through Saturday Y None (Also Used to Cancel or Override a Previous

Pattern)M SDP02 679 Ship/Delivery Pattern Time Code M ID 1/1 F As Directed Y None (Also Used to Cancel or Override a Previous

Pattern)

MFG830S_2001_01052010 - MR (X12-2001) - 15 - January 5, 2010




Segment: FST Forecast Schedule Position: 590 Loop: SDP Mandatory Level: Usage: Mandatory Max Use: 104 Purpose: To specify the forecasted dates and quantities Syntax Notes: 1 If FST06 is present, then FST07 is required.

Notes: Sample Data FST*1176*C*D*070202**002*0700*DO*SA15812

FST*1176*Z*D*070121**002*0700*DO*DA01175 FST*1176*Z*D*070121**002*0700*DO*CA01175 FST*1176*D*D*070212 FST*1176*D*F*070211*070228

Data Element Summary

User Ref. Data Attribute Des. Element Name Attributes M FST01 380 Quantity M R 1/10M FST02 680 Forecast Qualifier M ID 1/1 Key Point: Understanding this qualifier is key to understanding Nissan’s Parts Ordering

business process. The diagram in Appendix B illustrates this process. Each time a release is issued, each requirement has a date, quantity, and qualifier associated with the quantity. The Daily Ordering System (DOS) covers a horizon of dates which varies by part and is determined by several factors including transit time. The releases resulting from the DOS will generally cover a minimal number of days up to about 10 days in some cases. Once per week Nissan runs its "Extended Daily Ordering System" - Extended DOS. Nissan’s intent is to provide as much information as possible (e.g. up to six months) to the supplier related to the future requirements for each part. The Extended DOS release generally only occurs once per week. This is to minimize EDI costs for Nissan and the supplier. Nissan uses the following qualifiers: 'C' New Firm Order 'Z' Prior Firm Order 'D' Planning/Forecast In both the DOS and Extended DOS release all three qualifiers may occur. Requirements close to the date of production will be firm 'Z' and requirements at the distant end of the horizon will tend to be planning/forecast 'D'. On virtually every release, there will be some requirements which change from planning/forecast to firm for the very first time, those will have a qualifier of

MFG830S_2001_01052010 - MR (X12-2001) - 16 - January 5, 2010




'C'. The only way to distinguish between a DOS and Extended DOS release is by considering the difference between the BFR07 - Horizon End Date and today's date. If BFR07 is more than 30 days into the future it is an Extended DOS release.

C Firm D Planning Z Mutually DefinedM FST03 681 Forecast Timing Qualifier M ID 1/1 D Discrete F Flexible Interval (from Date X through Date Y)M FST04 373 Date M DT 6/6 Key Point: Discrete delivery date or first date of forecast interval (YYMMDD) FST05 373 Date O DT 6/6 Key Point: Last date of forecast interval (YYMMDD) FST06 374 Date/Time Qualifier O ID 3/3 002 Delivery Requested FST07 337 Time C TM 4/4 Key Point: Delivery request time (HHMM) FST08 128 Reference Number Qualifier O ID 2/2 DO Delivery Order Number FST09 127 Reference Number - RAN C AN 1/30 Key Point: Receipt Authorization Number (RAN)

Position 1 of the RAN will designate the facility that the RAN is created for. 'C' = Canton 'D' = Decherd 'S' = Smyrna Position 2 of the RAN will be a sequence letter, which will be incremented when the sequence number rolls over (omitting I and O). Positions 3 - 7 will be the sequence number - when the sequence number rolls to 0 the sequence letter will be incremented and the sequence number set to 1. Position 8 will be the RAN type with the values listed below: A = Additional or Add RAN B = Bulk material C = Coil Steel

MFG830S_2001_01052010 - MR (X12-2001) - 17 - January 5, 2010




P = Steel master RAN R = Repair S = Sample T = Trial V = Service Z = Balance out / Break pack

MFG830S_2001_01052010 - MR (X12-2001) - 18 - January 5, 2010




Segment: ATH Resource Authorization Position: 610 Loop: LIN Mandatory Level: Usage: Optional Max Use: 2 Purpose: To specify resource authorizations (i.e., finished labor, material, etc.) in the planning

schedule Syntax Notes: 1 At least one of ATH02 or ATH03 is required. 2 If ATH03 is present, then ATH05 is required. 3 If ATH04 is present, then ATH05 is required.

Notes: Key Point The intent of the ATH segment is to convey Nissan’s financial commitment for the raw

materials (qualifier = ‘MT’) or the commitment for the fabrication of actual finished parts (qualifier = ‘FI’). The ATH segment is not always transmitted. For example sequenced parts will never have ATH, and Trial RAN’s (RAN ending in ‘T’) will not have ATH until near start of Production (SOP) date.

Sample Data ATH*FI*070217*3528**070211

ATH*MT*070310*10584**070218

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M ATH01 672 Resource Authorization Code M ID 2/2 FI Finished (Labor, Material, and Overhead/Burden) MT Material ATH02 373 Date - Authorization Through Date C DT 6/6 ATH03 380 Quantity - Required C R 1/10 ATH05 373 Date C DT 6/6

MFG830S_2001_01052010 - MR (X12-2001) - 19 - January 5, 2010




Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 650 Loop: LIN Mandatory Level: Usage: Optional Max Use: 1 Purpose: To specify the carrier and sequence of routing and provide transit time information Syntax Notes: 1 At least one of TD502 TD504 or TD505 is required. 2 If TD502 is present, then TD503 is required. 3 If TD507 is present, then TD508 is required. 4 If TD510 is present, then TD511 is required.

Notes: Sample Data TD5*B***M

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M TD501 133 Routing Sequence Code M ID 1/2 B Origin/Delivery Carrier (Any Mode) TD504 91 Transportation Method/Type Code C ID 1/2 M Motor (Common Carrier)

MFG830S_2001_01052010 - MR (X12-2001) - 20 - January 5, 2010




Segment: MAN Marks and Numbers Position: 680 Loop: LIN Mandatory Level: Usage: Optional Max Use: 1 Purpose: To indicate identifying marks and numbers for shipping containers Syntax Notes:

Notes: Key Point The MAN segment is not always transmitted. However, when transmitted, it's intended to

communicate to the supplier the data which must be printed on the part identification barcode label in the special data section. Please see Nissan Packaging Guideline for additional information.

Sample Data MAN*PB*AA 042 D56A A24R!

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M MAN01 88 Marks and Numbers Qualifier M ID 1/2 PB Premarked by BuyerM MAN02 87 Marks and Numbers M AN 1/20

MFG830S_2001_01052010 - MR (X12-2001) - 21 - January 5, 2010




Segment: CTT Transaction Totals Position: 690 Loop: Level: Usage: Mandatory Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If CTT03 is present, then CTT04 is required. 2 If CTT05 is present, then CTT06 is required.

Notes: Sample Data CTT*1

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M CTT01 354 Number of Line Items M N0 1/6 Key Point: Total number of LIN loops in the transaction set

MFG830S_2001_01052010 - MR (X12-2001) - 22 - January 5, 2010




Segment: SE Transaction Set Trailer Position: 700 Loop: Level: Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments). Syntax Notes:

Notes: Key Point SE*42*0001

Data Element Summary User Ref. Data Attribute Des. Element Name Attributes M SE01 96 Number of Included Segments M N0 1/6 Key Point: Total number of segments included in a transaction set including ST and SE

segments.M SE02 329 Transaction Set Control Number M AN 4/9 Key Point: Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set. Must match the number in ST02. '0001' through '999999999'

MFG830S_2001_01052010 - MR (X12-2001) - 23 - January 5, 2010




Appendix A-1: Sample Transaction (DOS) Purpose: This appendix shows a sample DOS Release. ISA*00* *00* *01*054481205 *01*123456789 *070101*1200*U*00200*000000001*0*P*@! GS*PO*054481205*123456789*070101*1200*1*X*002001! ST*830*0001!

BFR*00**070101*DL*A*070101*070107*070101**SP! N1*SU**92*12345671! N1*MI*NISSAN!

PER*OD*SR. ANALYST*TE*123-456-7890! LIN**BP*30412 Q1052*PO*PR00009076!

UNT*EA! J2X**F*LH WIDGET! PER*EX*PO ANALYST*TE*123-456-7890! N1*ST*DOCK 2! SDP*B*F!

FST*1176*C*D*070104**002*0700*DO*SA00003! SDP*B*F!

FST*1176*Z*D*070102**002*0700*DO*SA00001! FST*1176*Z*D*070103**002*0700*DO*SA00002!

SDP*Y*Y!

FST*1176*D*D*070105**002*0700! FST*1176*D*D*070106**002*0700! FST*1176*D*D*070107**002*0700!

ATH*FI*070110*3528**070101! ATH*MT*070125*10584**070111! TD5*B***M!

MAN*PB*AA 042 D56A A24R! CTT*1!

SE*25*0001! GE*1*1! IEA*1*000000001!

MFG830S_2001_01052010 - MR (X12-2001) - 24 - January 5, 2010




Appendix A-2: Sample Transaction (Extended DOS) Purpose: This appendix shows a sample Extended DOS Release. Sample: ISA*00* *00* *01*054481205 *01*123456789 *070101*1200*U*00200*000000001*0*P*@! GS*PO*054481205*123456789*070101*1200*1*X*002001! ST*830*0001!

BFR*00**070101*DL*A*070101*070630*070101**SP! N1*SU**92*12345671! N1*MI*NISSAN!

PER*OD*SR. ANALYST*TE*123-456-7890! LIN**BP*30412 Q1052*PO*PR00009076!

UNT*EA! J2X**F*LH WIDGET! PER*EX*PO ANALYST*TE*123-456-7890! N1*ST*DOCK 2! SDP*B*F!

FST*1176*C*D*070104**002*0700*DO*SA00003! SDP*B*F!

FST*1176*Z*D*070102**002*0700*DO*SA00001! FST*1176*Z*D*070103**002*0700*DO*SA00002!

SDP*Y*Y!

FST*1176*D*D*070105**002*0700! FST*1176*D*D*070106**002*0700! FST*1176*D*D*070107**002*0700!

SDP*Y*Y!

FST*10584*D*F*070108*070131! FST*12936*D*F*070201*000228! FST*14112*D*F*070301*000331! FST*12936*D*F*070401*000430! FST*13599*D*F*070501*000531! FST*10120*D*F*070601*000630!

MFG830S_2001_01052010 - MR (X12-2001) - 25 - January 5, 2010




ATH*FI*070110*3528**070101! ATH*MT*070125*10584**070111! TD5*B***M!

MAN*PB*AA 042 D56A A24R! CTT*1!

SE*32*0001! GE*1*1! IEA*1*000000001!

MFG830S_2001_01052010 - MR (X12-2001) - 26 - January 5, 2010




Appendix B: DOS and Extended DOS Process

Purpose: This appendix illustrates the process of DOS (Daily Order System) and Extended DOS. Diagram:

Order Status (FST02)Month 1 2 3 4 5 6Day 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 …

Day1 'Z' 'Z' 'C' 'D' 'D' 'D'2 'Z' 'Z' 'C' 'D' 'D' 'D'3 'Z' 'Z' 'C' 'D' 'D' 'D'4 'Z' 'Z' 'C' 'D' 'D' 'D'5 'Z' 'Z' 'C' 'D' 'D' 'D' 'D' 'D' 'D' 'D' 'D' 'D'6 'Z' 'Z' 'C' 'D' 'D' 'D'7 'Z' 'Z' 'C' 'D' 'D' 'D'8 'Z' 'Z' 'C' 'D' 'D' 'D'9 'Z' 'Z' 'C' 'D' 'D' 'D'

10 'Z' 'Z' 'C' 'D' 'D' 'D'

'C' New Firm Order'Z' Prior Firm Order'D' Planning/Forecast'D' Planning/Forecast (Extended Monthly Forecast)

EDI Transmission

Extended DOS

DOS

DOS

MFG830S_2001_01052010 - MR (X12-2001) - 27 - January 5, 2010




Revision History Jan 5, 2010: Revised from the previous Implementation Guideline. Oct 8, 2007: Revised from the previous Implementation Guide. Nov 11, 2008: Final corrections and approval for publication. Nov 06, 2009: Removed out-dated phone number for Nissan Helpdesk. Jan 05, 2010: Upgraded to EDISIM ver 6.86

MFG830S_2001_01052010 - MR (X12-2001) - 28 - January 5, 2010




Contact New Trading Partner: If you are a new trading partner in the EDI Certification process and have a question or a request, please send an email to the following address. [email protected]

Inbound Test Transaction Transmission Request (Nissan to Trading Partner) Outbound Test Transaction Validation Request (Trading Partner to Nissan) Other Questions

Existing Trading Partner: If you are an existing (already certified) trading partner with Nissan and have a production problem or a question, please call to the following number. Nissan North America Helpdesk: 1-800-514-8061

Inbound Production Transaction Retransmission Request (Nissan to Trading Partner) Outbound Production Transaction Confirmation Request (Trading Partner to Nissan) VAN Change Request Other Production Issues and Questions

MFG830S Manufacturing Release 2001 01052010...MFG830S_2001_01052010 - MR (X12-2001) - 2 - January 5,...

Documents

Transcript of MFG830S Manufacturing Release 2001 01052010...MFG830S_2001_01052010 - MR (X12-2001) - 2 - January 5,...