nissan mexico, s - iconnect-corp.comiconnect-corp.com/specs/vendors/nissan/nissan_861_004010.pdf090...

ANSI ASC-X12 v4010

Receiving Advice/Acceptance Certificate– 861

Ateb Implementation Guideline NISSAN MEXICO of 21

NISSAN MEXICO, S.A. de C.V.

EDI 861 – Receiving Advice/Acceptance Certificate

VERSION: ANSI ASC X12 Version Release 4010

Developed By: Ateb Servicios, S.A. de C.V. Revision Number: 1.0 Revision Date: September 24, 2004

Reviewed / Approved by: Written by: Nissan México ATEB/mph

This Document Applies to: EDI 861 Implementation Guide

This document is restricted and may not be sent outside NISSAN MEXICO or reproduced without permission from NISSAN MEXICO. Suppliers are required to assume all patent liability. This document is controlled electronically and all printed copies or copies otherwise saved from this location are considered uncontrolled. Copyright 2004 NISSAN MEXICO.

ANSI ASC-X12 v4010



861 Receiving Advice/Acceptance Certificate.

Functional Group=RC

This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary list the contents of a shipment of goods as well as additional information relating to the shipment, such as order iand established business and industry practice relative to the notification of receipt or formal acceptance of goods and services.

1) Heading: Pos Id Segment Name Req Max

Use Repeat Notes Usage

010 ST Transaction Set Header M 1 Used

020 BRA Beginning Segment for Receiving Advice or Acceptance Certificate

M 1 Used

030 CUR Currency O 1 Not Used

040 REF Reference Identification C >1 Used

050 PER Administrative Communications Contact O 3 Not Used

060 DTM Date/Time Reference M 10 Used

070 PRF Purchase Order Reference O 25 Not Used

080 TD1 Carrier Detils (Quantity and Weight) O 2 Not Used

090 TD5 Carrier Detils (Routing Sequence/Transit Time) O 12 Not Used

100 TD3 Carrier Detils (Equipment) O 12 Not Used

110 TD4 Carrier Detils (Special Handiling, or Hazardous Materials, or Both)

O 5 Not Used

120 MEA Measurements O 40 Not Used

LOOP ID N1 LOOP ID O 200 190 C1/130

130 N1 Name C 1 Used

140 N2 Additional Name Information O 2 Not Used

150 N3 Address Information O 2 Not Used

160 N4 Geographic Location O 1 Not Used

170 REF Reference Identification O 100 Not Used


190 FOB F.O.B. Related Instructions O 1 Not Used

LOOP ID LM LOOP ID O 10 210 C1/200

200 LM Code Source Information O 1 Not Used

210 LQ Industry Code M 100 Not Used

ANSI ASC-X12 v4010



2) Detail: Pos Id Segment Name Req Max


LOOP ID RCD LOOP ID O 200000 310 C2/010

010 RCD Receiving Conditions C 1 Used

020 SN1 Item Detail (Shipment) O 1 Used

030 CUR Currency O 1 Not Used

040 LIN Item Identification C 100 Used

050 PID Product/Item Description C 1000 Used

060 PO4 Item Physical Details O 100 Not Used

070 REF Reference Identification C 12 Used


090 DTM Date/Time Reference O 10 Not Used

100 PRF Purchase Order Reference O 25 Not Used

110 MEA Measurements O 40 Not Used 120 FOB F.O.B. Related Instructions O 1 Not Used 130 TD1 Carrier Detils (Quantity and Weight) O 20 Not Used 140 TD5 Carrier Detils (Routing Sequence/Transit Time) O 12 Not Used

150 TD3 Carrier Detils (Equipment) O 12 Not Used

160 TD4 Carrier Detils (Special Handiling, or Hazardous Materials, or Both)

O 5 Not Used

170 SAC Service, Promotion, Allowance, or Charge Information O 10 Not Used

180 MAN Marks and Numbers >1




LOOP ID SLN LOOP ID O 100 240 C2/210

210 SLN Subline Item Detail O 1 Not Used

220 PID Product/Item Description O 1000 Not Used




LOOP ID N1 LOOP ID O 200 310 C2/250

250 N1 Name O 1 Not Used

260 N2 Additional Name Information O 2 Not Used

270 N3 Address Information O 2 Not Used

280 N4 Geographic Location O 1 Not Used

290 REF Reference Identification O 100 Not Used


310 FOB F.O.B. Related Instructions O 1 Not Used

ANSI ASC-X12 v4010



3) Summary: Pos Id Segment Name Req Max


010 CTT Transaction Totals O 1 Not Used

020 SE Transaction Set Trailer M 1 Used

Notes: 1/020 This transaction set is a receiving advice unless BRA04 contains a value of “8”. When BRA04 contains a value of “8”, the transaction set is an Acceptance Certificate and the units received is the units accepted. 3/010 The number of line items (CTT01) is the accumulation of the number of RCD segments. If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

Trading Partner:

Within this Implementation Guide, ASC-X12 Position Numbers have been sequenced to reflect an RCD Loop illustrated at the Receiving Conditions of the quantity and number of units shipped and accepted.

ANSI ASC-X12 v4010



ISA Interchange Control Header

User Option (Usage): Used To start and identify an interchange of zero or more functional groups and interchange-related control segments.

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition ISA01 101 Authorization Information Qualifier M ID 2/2 “00” ISA02 I02 Authorization Information M AN 10/10 10 Blanks ISA03 I03 Security Information Qualifier M ID 2/2 “00” ISA04 I04 Security Information M AN 10/10 10 Blanks ISA05 I05 Interchange ID Qualifier M ID 2/2 “ZZ” ISA06 I06 Interchange Sender ID M ID 15/15 “MX23 MX2302” ISA07 I05 Interchange ID Qualifier M ID 2/2 “ZZ” ISA08 I07 Interchange Receiver ID M ID 15/15 “MXZZ MXZZ001 ” ISA09 I08 Interchange Date M DT 6/8 20030730 ISA10 I09 Interchange Time M TM 4/4 1020 ISA11 I10 Interchange Control Standard ID M ID 1/1 “U” ISA12 I11 Interchange Control Version ID M ID 5/5 “00302” ISA13 I12 Interchange Control Number M NO 9/9 000000005 ISA14 I13 Acknowledgment Requested M ID 1/1 ‘0’ ISA15 I14 Use Indicator M ID 1/1 “P”=Prod. “T”= Test ISA16 I15 Component Element Separator M AN 1/1 Hex(6A)

Trading Partner: Example: ISA*00* *00* *ZZ*MX23 MX2302 *ZZ*MXG6 MXG6001 *040923*1254*U*00302*000000184*1*P*>~

Pos: 00 Max: 1 Enveloping – Mandatory

Loops: N/A Elements: 16 Loops: N/A Elements: 7

ANSI ASC-X12 v4010



GS Functional Group Header

User Option (Usage): Used To indicate the beginning of a functional group and to provide control information.,

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition GS01 479 Functional Identifier Code M ID 2/2 “RC” for 861 GS02 142 Application Sender’s Code M AN 2/12 MX2302 GS03 124 Application Receiver’s Code M AN 2/12 MX11ZZ GS04 029 Date M DT 8/8 20040730 GS05 030 Time M TM 4/4 1020 GS06 028 Group Control Number M NO 1/9 7 GS07 455 Responsible Agency Code M ID 1/2 “X” GS08 480 Version/Release/Industry Identifier Code M AN 1/12 “004010”

Semantics: 04. GS04 is the group date 05. GS05 is the group time 06. The data interchange control number GS06 in this header must be identical to the same data element in the associated

functional group trailer, GE02.

Comments: 00. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.

Trading Partner: Example: GS*RC*MX2302*MXG6001*20040923*1254*54*X*004010~

Pos: 020 Max: >1 Enveloping – Mandatory


Pos: 00 Max: >1 Enveloping – Mandatory


ANSI ASC-X12 v4010



ST Transaction Set Header

User Option (Usage): Used To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition ST01 143 Transaction Set Identifier Code M ID 3/3 Used 1

Description: Code uniquely identifying a Transaction Set. Code Name 861 = X12 Receiving Advice/Acceptance Certificate

ST02 329 Transaction Set Control Number M AN 4/9 Used 1

Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Semantics: 01. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 861 selects the Receiving Advice/Acceptance Certificate transaction set).

Trading Partner: Example: ST*861*0064~

Pos: 010 Max: 1 Heading – Mandatory

Loops: N/A Elements: 2

ANSI ASC-X12 v4010



BRA Beginning Segment for Receiving Advice

or Acceptance Certificate. User Option (Usage): Used To Indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date and time.

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition BRA01 127 Reference Identification M AN 1/30 Used 1

Description: Reference Information as defined for A particular Transaction Set or as specified by The Reference Identification Qualifier

BRA02 373 Date M DT 8/8 Used 1

Description: Current Date (YYYYMMDD). BRA03 353 Transaction Set Purpose Code M ID 2/2 Used 1

Description: Code identifying purpose of transaction set. Code Name 00 = Original

BRA04 962 Receiving Advice or Acceptance M ID 1/1 Used 1 Certificate Type Code Description: Code dentifying Reciving Advice Code Name 1 = Receiving Dock Advice

BRA05 337 Time M TM 4/8 Used 1

Description: Current Time (HHMMSS) Expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H =hours (00-23), M = minutes (00-59), S =integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Semantics: 02. BRA02 is the date that the receiving advice transaction set is created. 05. BRA05 is the time that the receiving advice transaction set is created.

NISSAN MEXICO Example: BRA*000350*20040923*00*1*1253~



ANSI ASC-X12 v4010



REF Reference Identification

User Option (Usage): Used To specify identifying Information. Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition REF01 128 Reference Number Qualifier M ID 2/3 Used 1

Description: Code qualifying the Reference Identification. Code Name BM = Bill of Lading Number

REF02 127 Reference Number C AN 1/30 Used 1 Description: Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Syntax: 02. R0203 - At least one of REF02 or REF03 is required

Semantics: 04. REF04 - Contains data relating to the value cited in REF02.

NISSAN MEXICO: Example: REF~BM~97314’

Pos: 040 Max: >1 Header – Conditional


ANSI ASC-X12 v4010



DTM Date/Time Reference

User Option (Usage): Used To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition DTM01 374 Date/Time Qualifier M ID 3/3 Used 1

Description: Code specifying type of date or time, or both date and time. Code Name 011 = Shipped

DTM02 373 Date C DT 8/8 Used 1

Description: Current Date (YYYYMMDD). DTM03 337 Time C TM 4/8 Used 1

Description: Current Time (HHMMSS) Expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H =hours (00-23), M = minutes (00-59), S =integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Syntax: 02. R020306 - At least one of DTM02, DTM03, DTM06 is required 06. P0607 - If either DTM06, DTM07 is present, then the other is required

NISSAN MEXICO: Example: DTM~011~2004093~105400’



ANSI ASC-X12 v4010



Loop N1

Used at SHIPMENT level - To identify a party by type of organization, name and code

Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 130 N1 Name O 1 Used

N1 Name

User Option (Usage): Used To identify a party by type of organization, name and code Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition N101 98 Entity Identifier Code M ID 2/3 Used 1

Description: Code identifying an organizational entity, a physical location, or an individual Code Name SU = Supplier 16 = Plant

N103 66 Identification Code Qualifier C ID 1/2 Used 1

Description: Code designating the system/method of code structure used for Identification Code (67). Code Name 92 = Assigned by Buyer or Buyer's Agent

N104 67 Identification Code C AN 1/80 Used 1

Description: Code identifying a party or other code. Code Name P = CIVAC M= MOTOR N = Aguascalientes

Syntax: 02. R0203 - At least one of N102 or N103 is required 03. P0304 - If either N103 or N104 is present, then the other is required

NISSAN MEXICO: Example: N1*SU**92*000350~ N1*16**92*N~

Pos: 130 Max: 200 Header – Conditional

Loops: N1 Elements: N/A


Loops: N1 Elements: 6

ANSI ASC-X12 v4010



Loop RCD

User Option (Usage): Used To report receiving conditions and spedify contested quantities.

Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 010 RCD Receiving Conditions C 1 Used

020 SN1 Item Detail (Shipment) C 1 Used

040 LIN Item Identification C 100 Used

050 PID Product/Item Description C 1000 Used

070 REF Reference Identification C 12 Used

RCD Receiving Conditions

User Option (Usage): Used To report receiving conditions and spedify contested quantities. Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition RCD02 663 Quantity Unit Received or Accepted C R9 1/9 Used 1

Description: Number of Units Received or Accepted

RCD03 C001 Composite Unit of Measure C 355 Unit or Basis for Measurement Code M AN 1/2 Used 1

Description: Code specifying the units in which a Value is being expressed, or manner in which a Measurement has been taken. Code Name PC = Pices

Syntax: 02. P0203 - If either RCD02 or RCD03 is present, then the other is required.

NISSAN MEXICO: Example: RCD**150*PC~

Pos: 010 Max: 200000 Detail – Conditional

Loops: RCD Elements: N/A


Loops: RCD Elements: 21

ANSI ASC-X12 v4010



SN1 Item Detail (Shipment)

User Option (Usage): Used at the ITEM Level - To specify line item detail relative to shipment

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition SN102 382 Number of Units Shipped M R9 1/9 Used 1

Description: Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.

SN103 355 Unit or Basis for Measurement Code M ID 2/2 Used 1

Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Code Name PC = Piece

Syntax: 01. P0506 - If either SN105 or SN106 is present, then all are required

Semantics: 01. SN101 is the ship notice line item identification.

Comments: 03. SN103 defines the unit of measurement for both SN102 and SN104.

NISSAN MEXICO: Example: SN1**150*PC~



ANSI ASC-X12 v4010



LIN Item Identification

User Option (Usage): Used at the ITEM Level - To specify basic item identification data.

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition LIN02 235 Product/Service ID Qualifier M ID 2/2 Used 1

Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234). Code Name UF = User-Defined Shipping container Identifier

LIN03 234 Product/Service ID M AN 1/48 Used 1 Description: Identifying number for a product or service.

LIN04 235 Product/Service ID Qualifier M ID 2/2 Used 1

Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234). Code Name ZZ = RAN Received in ASN



Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234). Code Name AW = RAN Confirmed



Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234). Code Name PD = Part Number Received in ASN




ANSI ASC-X12 v4010



LIN10 235 Product/Service ID Qualifier M ID 2/2 Used 1 Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234). Code Name PU = Part Confirmed

LIN11 234 Product/Service ID M AN 1/48 Used 1

Description: Identifying number for a product or service.

Syntax: 04. P0405 - If either LIN04 or LIN05 is present, then the other is required 06. P0607 - If either LIN06 or LIN07 is present, then the other is required 08. P0809 - If either LIN08 or LIN09 is present, then the other is required 10. P1011 - If either LIN10 or LIN11 is present, then the other is required

NISSAN MEXICO: Example: LIN**UF*FA3 0000201*ZZ*RG62229*AW*RG62229*PD*30432F4200*PU*30432F4200~

ANSI ASC-X12 v4010



PID Product/Item Description

User Option (Usage): Used To describe a product or process in coded or free-form format. Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition PID01 349 Item Description Type M AN 1/1 Used 1

Description: Code indicating the format of a description Code Name F = Free-Form

PID04 751 Product Description Code C AN 1/12 Used 1 Description: A code from an industry code list which provides specific data about a product characteristic. Code Name 01 = Item Accepted without error 02-13 = Item Accepted with error

PID05 352 Product Description C AN 1/80 Used 1

Description: A free-form description to clarify the relates data elementes and their content.

NISSAN MEXICO: Example: PID*F***01*REGISTRO CONFIRMADO SIN ERROR~



ANSI ASC-X12 v4010



REF Reference Identification

User Option (Usage): Used To specify identifying Information. Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition REF01 128 Reference Number Qualifier M ID 2/3 Used 1

Description: Code qualifying the Reference Identification. Code Name OQ = Order Number RV = Receiving Number

REF02 127 Reference Number C AN 1/30 Used 1 Description: Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Syntax: 02. R0203 - At least one of REF02 or REF03 is required

Semantics: 04. REF04 - Contains data relating to the value cited in REF02.

NISSAN MEXICO: Example: REF*OQ*603825~ REF*RV*271920~



ANSI ASC-X12 v4010



SE Transaction Set Trailer

User Option (Usage): Used To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition SE01 96 Number of Included Segments M N0 1/10 Used 1

Description: Total number of segments included in a transaction set including ST and SE segments.

SE02 329 Transaction Set Control Number M AN 4/9 Used 1

Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Comments: 00. SE is the last segment of each transaction set.

NISSAN MEXICO: Example: SE*13*0064~

Pos: 020 Max: 1 Summary – Mandatory


ANSI ASC-X12 v4010



GE Functional Group Trailer

User Option (Usage): Used To indicate the end of a functional group and to provide control information.,

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition GE01 97 Number of Transaction Sets Included M N0 1/6 “1” GE02 28 Group Control Number M N0 1/9 “1”

Semantics: 00. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated

functional group header, GS06.

Comments: 00. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to

maximize functional group integrity. The control number is the same as that used in the corresponding header.

NISSAN MEXICO: Example: GE*1*54~



ANSI ASC-X12 v4010



IEA Interchange Control Trailer

User Option (Usage): Used To define the end of an interchange of zero or more functional groups and interchange related control segment.

Element Summary: Ref Id Element Name Req Type Min/Max Usage Repetition IEA01 116 Number of Included Functional Group M N0 1/5 “1” IEA02 112 Interchange Control Number M N0 9/9 “1”

NISSAN MEXICO: Example: IEA*1*000000184~



ANSI ASC-X12 v4010



NISSAN MEXICO

APPENDIX of EXAMPLES

NOTE: This document is to be used in conjunction with the NISSAN MEXICO 861 Implementation Guideline to Ilustrate

examples and functional definition of this transaction set.

861 Example I: Receiving Advice/Acceptance Certificate

1. ST*861*0064~ 2. BRA*000350*20040923*00*1*1253~ 3. REF*BM*142311~ 4. DTM*011*20040923*1253~ 5. N1*SU**92*999999~ 6. N1*16**92*N~ 7. RCD**150*PC~ 8. SN1**150*PC~ 9. LIN**UF*FA3 0000201*ZZ*RG62229*AW*RG62229*PD*30432F4200*PU*30432F4200~ 10. PID*F***01*REGISTRO CONFIRMADO SIN ERROR~ 11. REF*OQ*603825~ 12. REF*RV*271920~ 13. SE*13*0064~

861 EDI Example with Enveloping: Receiving Advice/Acceptance Certificate

ISA*00* *00* *ZZ*MX23 MX2302 *ZZ*MXG6 MXG6001

*040923*1254*U*00302*000000184*1*P*>~

GS*RC*MX2302*MXG6001*20040923*1254*54*X*004010~

ST*861*0064~

BRA*000350*20040923*00*1*1253~

REF*BM*142311~

DTM*011*20040923*1253~

N1*SU**92*000350~

N1*16**92*N~

RCD**150*PC~

SN1**150*PC~

LIN**UF*FA3 0000201*ZZ*RG62229*AW*RG62229*PD*30432F4200*PU*30432F4200~

PID*F***01*REGISTRO CONFIRMADO SIN ERROR~

REF*OQ*603825~

REF*RV*271920~

SE*13*0064~

GE*1*54~

IEA*1*000000184~

nissan mexico, s - iconnect-corp.comiconnect-corp.com/specs/vendors/nissan/nissan_861_004010.pdf090...

Documents