NAPA Inbound EDI 856 ANSI X12 v5010 Ship Notice...Nov 17, 2017 · 2.2 11/17/2017 Greg Edgar Updated document example 2.2 11/17/2017 Greg Edgar Updated the N1.04 element documentation

NAPA Inbound EDI 856ANSI X12 v5010 Ship

NoticeElectronic Data Interchange Implementation Guideline

Version: 2.4

Author: GPC EDI Shared Services Company: Genuine Parts Company Publication: 01/08/2019 Trading Partner: EDI Direction: From

Supplier To NAPA

NotesThis document outlines the GPC/NAPA requirements for the 856 ANSI X12 5010 Ship Manifest/Notice transactionset.

BUSINESS APPLICATION: NAPA Warehouse (Premier) and Drop Ship (Director) Shipments

EDI USAGE: NAPA Inbound 856 X12 5010

The information in this document is considered confidential and is to be distributed only to persons for whom it isintended. This information is for the exclusive use of the National Automotive Parts Association (NAPA), itsmembers, and business partners.

Testing Procedure:

1. GPC will generate and transmit, to the supplier, a TEST Purchase Order.2. The supplier will send back an EDI Functional Acknowledgement (997).3. The supplier has to verify the quality of the transmitted information and check if the integration of the POdocument in their system is good. 4. Steps 1 through 3 shall be repeated until each party is satisfied.5. The supplier will then send back an EDI ASN (856).6. GPC will transmit to the supplier an EDI Functional Acknowledgement (997).7. Steps 5 and 6 shall be repeated until both parties are satisfied.

Technical Parameters:

NAPA is using the following values for ISA Sender/Receiver Qualifier / IDs:Qualifier: ZZ / Sender/Receiver ID: NAPAQualifier: ZZ / Sender/Receiver IS: NAPAXP

NAPA is using the following values for GS Sender/Receiver IDs:Sender/Receiver ID: NAPASender/Receiver IS: NAPAXP

NAPA is using the following values for ISA Sender/Receiver Test Qualifier / IDs:Qualifier: ZZ Sender/Receiver ID: NAPATESTQualifier: ZZ Sender/Receiver ID: NAPAXPTXT

NAPA is using the following values for Test GS Sender/Receiver IDs:Sender/Receiver ID: NAPATESTSender/Receiver IS: NAPAXPTXT

GPC default EDI delimiters characters and EBCIDIC values:1. Segment Terminator - punctuation mark “^” (caret character - Hex 5E)2. Element Separator - punctuation mark “*” (asterisk character - Hex 2A) 3. Sub-Element Separator - punctuation mark “:” (colon character - Hex 3A)4. Repetition Separator – punctuation mark “|” (pipe character – Hex 7C)5. Decimal Indicator - punctuation mark “.” (dot character - Hex 2E)

Functional Acknowledgments:

The 997 (Functional Acknowledgments) are used by GPC to verify receipt of EDI documents sent to our suppliers.GPC will also create the 997 to acknowledge receipt of your documents within 24 hours. If a 997 is not received foryour EDI transmission(s), please contact GPC EDI Shared Service Support.

Please refer to the document titled "NAPA EDI Requirements" to understand how this NAPA EDI Implementationguide distinguishes the segments and elements used by NAPA.

For answers to any additional questions regarding this Implementation Guide, contact EDI Support at 770-661-8686.Questions can also be submitted to EDI Support via email at [email protected] (Please include your SupplierID on all emails).

Change Log

Version Date Author Description2.2 11/17/2017 Greg Edgar Updated document example2.2 11/17/2017 Greg Edgar Updated the N1.04 element documentation for the ST & BT2.2 11/17/2017 Greg Edgar Updated the GPC notes on the N1.02(BT) element2.2 11/17/2017 Greg Edgar Updated the N1.04 element documentation for SU2.3 09/12/2018 Greg Edgar Updated notes to remove business rules 2.3 09/12/2018 Greg Edgar Updated notes to remove validation notes2.3 09/12/2018 Greg Edgar Updated the GPC example of the document2.3 09/12/2018 Greg Edgar Updated notes on DTM segment2.3 09/12/2018 Greg Edgar Updates examples on LIN and SN1 segments2.3 09/12/2018 Greg Edgar Added Mandatory REF(CN) segment2.3 09/12/2018 Greg Edgar Added Mandatory N3 and N4 segments to Supplier address2.4 01/08/2019 Greg Edgar Updated comments on HL(Pack) for NXP documents

Ship Notice/Manifest - 856 i X12V5010Genuine Parts Company Confidential

These specifications are subject to further change at the discretion of Genuine Parts Company

Table of Contents

856 Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Loop Hierarchical Level [Shipment] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Loop Party Identification [BT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Party Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Loop Party Identification [SU] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Party Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Loop Hierarchical Level [Order] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information [PK] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information [IV] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information [PD] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information [SU] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Loop Party Identification [ST] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Party Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Loop Hierarchical Level [Tare/Pallet] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PAL Pallet Type and Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Loop Hierarchical Level [Pack] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1

. . . . . 4

. . . . . 8

. . . . 10

. . . . 11

. . . . 13

. . . . 14

. . . . 16

. . . . 18

. . . . 19

. . . . 20

. . . . 21

. . . . 22

. . . . 23

. . . . 24

. . . . 25

. . . . 26

. . . . 27

. . . . 28

. . . . 29

. . . . 30

. . . . 31

. . . . 32

. . . . 33

. . . . 34

. . . . 35

. . . . 36

. . . . 37

. . . . 38

. . . . 39

. . . . 40

. . . . 42

. . . . 43

. . . . 44

. . . . 45

. . . . 46

. . . . 47

. . . . 48

. . . . 49

Ship Notice/Manifest - 856 ii X12V5010Genuine Parts Company Confidential


MEA Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Loop Hierarchical Level [Item] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . 50

. . . . 51

. . . . 53

. . . . 54

. . . . 55

. . . . 56

. . . . 58

. . . . 59

. . . . 60

. . . . 61

. . . . 62

. . . . 63

Ship Notice/Manifest - 856 1 X12V5010Genuine Parts Company Confidential


856 Ship Notice/ManifestFunctional Group=SH

Purpose: This X12 Transaction Set contains the format and establishes the data contents of the ShipNotice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to list the contents of a shipment of goods as well as additionalinformation relating to the shipment, such as order information, product description, physical characteristics, type ofpackaging, marking, carrier information, and configuration of goods within the transportation equipment. Thetransaction set enables the sender to describe the contents and configuration of a shipment in various levels of detailand provides an ordered flexibility to convey information. The sender of this transaction is the organizationresponsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers ofthe transaction set. The receiver of this transaction set can be any organization having an interest in the contents ofa shipment or information about the contents of a shipment.

GPC Example:GPC Example:Sample ASN (Pack Level) for NAPA Drop Ship (Director) and JOEI orders:

ISA*00* *00* *nn*partnerid *ZZ*NAPA *180912*0749*|*00501*000101693*0*P*>^GS*SH*partnerid*NAPA*20180912*0749*101693*X*005010^ST*856*136321^BSN*00*639938*20180912*0749*0001^HL*1**S*1^TD1*PLT90*1****G*15*LB^TD5**2*UPSN^REF*BM*0174053^REF*CN*1234567^DTM*011*20180911^DTM*067*20180916^FOB*PO^N1*BT*NAPA ATLANTA STORE 069*92*ATL00069^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^N1*SU*Supplier Name*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^HL*2*1*O*1^PRF*18040429OD000BSM45417***20180911^REF*PK*R43357^REF*PD*JOEI^REF*SU*STR^N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^N3*1504 ALEXANDERSTREET^N4*COLUMBUS*GA*31904^HL*3*2*T*1^MAN*GM*00107844501156605856^PAL*4****15*01^HL*4*3*P*1^MEA*WT*G*15*LB^TD1*BOX25*1^MAN*CP*1Z3163790372804018^HL*5*4*I*0^LIN*1*PI*RAY*BP*2136912*PL*00001*VP*R-42033^SN1**1*EA**1*EA^PID*F****FOR ALT^CTT*1*1^SE*37*136321^GE*1*101693ÎEA*1*000101693^

Sample ASN (Pack Level) for NAPA Drop Ship (Director) and JOEI orders:

ISA*00* *00* *nn*partnerid *ZZ*NAPA *180912*0749*|*00501*000101693*0*P*>^GS*SH*partnerid*NAPA*20180912*0749*101693*X*005010^ST*856*136321^BSN*00*639938*20180912*0749*0001^HL*1**S*1^TD1*PLT90*1****G*15*LB^TD5**2*UPSN^REF*BM*0174053^REF*CN*1234567^DTM*011*20180911^DTM*067*20180916^FOB*PO^N1*BT*NAPA ATLANTA STORE 069*92*ATL00069^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^N1*SU*Supplier Name*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^HL*2*1*O*1^PRF*18040429OD000BSM45417***20180911^REF*PK*R43357^REF*PD*JOEI^REF*SU*STR^N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^N3*1504 ALEXANDERSTREET^N4*COLUMBUS*GA*31904^HL*3*2*T*1^MAN*GM*00107844501156605856^PAL*4****15*01^HL*4*3*P*1^MEA*WT*G*15*LB^TD1*BOX25*1^MAN*CP*1Z3163790372804018^HL*5*4*I*0^LIN*1*PI*RAY*BP*2136912*PL*00001*VP*R-42033^SN1**1*EA**1*EA^PID*F****FOR ALT^CTT*1*1^SE*37*136321^GE*1*101693ÎEA*1*000101693^



Sample ASN (no Pack Level) for NAPA Warehouse (Premier) orders (at Order Level, Ship To N1.04 = 00999):

ISA*00* *00* *nn*partnerid *ZZ*NAPA *180912*0710*<*00501*500000275*0*P*>^GS*SH*partnerid*NAPA*20180912*0710*280*X*005010^ST*856*500002103^BSN*00*DD00174053*20180912*070506*0001^HL*1**S^TD1*CTN*1^TD5**2*FDEG^REF*BM*0174053^REF*CN*1234567^DTM*011*20180911^FOB*PO^N1*BT*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^N1*SU*Supplier Name*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^HL*2*1*O^PRF*18013597OD000NBC34342***20180907^REF*PK*174053^REF*PD*FD487^REF*SU*STR^N1*ST*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^HL*3*2*P^TD1*CTN*1^MAN*CP*430714258548^HL*4*3*I^LIN*1*PI*NBC*BP*851500*PL*00001*VP*94085910^SN1**1*EA^PID*F****85-1500 2/6/40/200A 12V DGTL WC NAPA CA^CTT*1*1^SE*32*500002103^GE*1*280ÎEA*1*500000275^

Sample ASN (no Pack Level) for NAPA Warehouse (Premier) orders (at Order Level, Ship To N1.04 = 00999):

ISA*00* *00* *nn*partnerid *ZZ*NAPA *180912*0710*<*00501*500000275*0*P*>^GS*SH*partnerid*NAPA*20180912*0710*280*X*005010^ST*856*500002103^BSN*00*DD00174053*20180912*070506*0001^HL*1**S^TD1*CTN*1^TD5**2*FDEG^REF*BM*0174053^REF*CN*1234567^DTM*011*20180911^FOB*PO^N1*BT*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^N1*SU*Supplier Name*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^HL*2*1*O^PRF*18013597OD000NBC34342***20180907^REF*PK*174053^REF*PD*FD487^REF*SU*STR^N1*ST*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^HL*3*2*P^TD1*CTN*1^MAN*CP*430714258548^HL*4*3*I^LIN*1*PI*NBC*BP*851500*PL*00001*VP*94085910^SN1**1*EA^PID*F****85-1500 2/6/40/200A 12V DGTL WC NAPA CA^CTT*1*1^SE*32*500002103^GE*1*280ÎEA*1*500000275^

Heading:Pos Id Segment Name Req Max Use Repeat Notes0100 ISA Interchange Control Header M 1 0200 GS Functional Group Header M 1 0300 ST Transaction Set Header M 1 0400 BSN Beginning Segment for Ship Notice M 1

Detail:Pos Id Segment Name Req Max Use Repeat Notes

LOOP ID - HL 1 C2/0100L LOOP ID - HL 1 C2/0100L

0200 HL Hierarchical Level M 1 C2/02001200 TD1 Carrier Details (Quantity and Weight) O 20 1300 TD5 Carrier Details (Routing Sequence/Transit

Time)M 12

1900 REF Reference Information M 1 1900 REF Reference Information M >1 3700 DTM Date/Time Reference M 1 3700 DTM Date/Time Reference O 9

Pos Id Segment Name Req Max Use Repeat Notes



3800 FOB F.O.B. Related Instructions M 1 LOOP ID - N1 1 LOOP ID - N1 1

4100 N1 Party Identification M 1 4300 N3 Party Location O 2 4400 N4 Geographic Location O 1

LOOP ID - N1 199 LOOP ID - N1 199

4900 N1 Party Identification M 1 5100 N3 Party Location M 2 5200 N4 Geographic Location M 1


7200 HL Hierarchical Level M 1 C2/72007600 PRF Purchase Order Reference M 1 8900 REF Reference Information [PK] M 1 9000 REF Reference Information [IV] O 1 9100 REF Reference Information [PD] M 1 9200 REF Reference Information [SU] M 12

LOOP ID - N1 200 LOOP ID - N1 200

11500 N1 Party Identification M 1 11700 N3 Party Location O 2 11800 N4 Geographic Location O 1


13800 HL Hierarchical Level M 1 C2/1380017200 MAN Marks and Numbers Information M >1 17500 PAL Pallet Type and Load Characteristics O 1


20000 HL Hierarchical Level O 1 C2/2000020700 MEA Measurements O 40 21000 TD1 Carrier Details (Quantity and Weight) O 20 23400 MAN Marks and Numbers Information O >1


26200 HL Hierarchical Level M 1 C2/2620026300 LIN Item Identification M 1 26400 SN1 Item Detail (Shipment) M 1 26800 PID Product/Item Description O 200

Summary:Pos Id Segment Name Req Max Use Repeat Notes0100 CTT Transaction Totals M 1 N3/01000200 SE Transaction Set Trailer M 1 0300 GE Functional Group Trailer M 1 0400 IEA Interchange Control Trailer M 1



ISA Interchange Control Header Pos: 0100 Max: 1Heading - Mandatory

Loop: N/A Elements: 16

Purpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegments

GPC Example:GPC Example:ISA*00* *00* *nn*partnerid *ZZ*NAPA *110825*1018*|*00501*300001416*0*P*:ÎSA*00* *00* *nn*partnerid *ZZ*NAPA *110825*1018*|*00501*300001416*0*P*:^

Element Summary: Ref Id Element Name Req Type Min/Max UsageISA01 I01 Authorization Information Qualifier

Description: Code identifying the type ofinformation in the AuthorizationInformationGPC Notes: NAPA requires code '00'GPC Notes: NAPA requires code '00'

M ID 2/2 Must use

CodeList Summary (Total Codes: 7, Included: 1)Code Name00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information

Description: Information used foradditional identification or authorization ofthe interchange sender or the data in theinterchange; the type of information is setby the Authorization Information Qualifier(I01)GPC Notes: Not used by NAPAGPC Notes: Not used by NAPA

M AN 10/10 Used

ISA03 I03 Security Information Qualifier

Description: Code identifying the type ofinformation in the Security InformationGPC Notes: NAPA requires code '00'GPC Notes: NAPA requires code '00'

M ID 2/2 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information

Description: This is used for identifyingthe security information about theinterchange sender or the data in theinterchange; the type of information is setby the Security Information Qualifier (I03)GPC Notes: Not used by NAPAGPC Notes: Not used by NAPA

M AN 10/10 Used

ISA05 I05 Interchange ID Qualifier

Description: Code indicating thesystem/method of code structure used todesignate the sender or receiver IDelement being qualified

M ID 2/2 Must use

Ref Id Element Name Req Type Min/Max Usage



GPC Notes: This is the Supplier EDI ISASender ID Qualifier. Any valid ANSI X12codes are acceptable.

GPC Notes: This is the Supplier EDI ISASender ID Qualifier. Any valid ANSI X12codes are acceptable.All valid standard codes are used.(Total Codes: 41)

ISA06 I06 Interchange Sender ID

Description: Identification codepublished by the sender for other partiesto use as the receiver ID to route data tothem; the sender always codes this valuein the sender ID elementGPC Notes: This is the Supplier definedEDI ISA Sender ID.GPC Notes: This is the Supplier definedEDI ISA Sender ID.

M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier

Description: Code indicating thesystem/method of code structure used todesignate the sender or receiver IDelement being qualifiedGPC Notes: This is NAPA EDI ISAReceiver ID Qualifier. NAPA is usingvalue 'ZZ' for ISA.07

GPC Notes: This is NAPA EDI ISAReceiver ID Qualifier. NAPA is usingvalue 'ZZ' for ISA.07

M ID 2/2 Must use

CodeList Summary (Total Codes: 41, Included: 1)Code NameZZ Mutually Defined

ISA08 I07 Interchange Receiver ID

Description: Identification codepublished by the receiver of the data;When sending, it is used by the sender astheir sending ID, thus other partiessending to them will use this as areceiving ID to route data to themGPC Notes: This is NAPA EDI ISAReceiver ID. NAPA is using value 'NAPA'for ISA.08. NAPA is using value'NAPAXP' for the NAPA Xpress Program.

GPC Notes: This is NAPA EDI ISAReceiver ID. NAPA is using value 'NAPA'for ISA.08. NAPA is using value'NAPAXP' for the NAPA Xpress Program.

M AN 15/15 Must use

ISA09 I08 Interchange Date

Description: Date of the interchange

M DT 6/6 Must use

ISA10 I09 Interchange Time

Description: Time of the interchange

M TM 4/4 Must use

ISA11 I65 Repetition Separator

Description: Type is not applicable; therepetition separator is a delimiter and nota data element; this field provides thedelimiter used to separate repeatedoccurrences of a simple data element or acomposite data structure; this value mustbe different than the data element

M 1/1 Must use




separator, component element separator,and the segment terminatorGPC Notes: NAPA is using the pipe ( | )character.GPC Notes: NAPA is using the pipe ( | )character.

ISA12 I11 Interchange Control Version Number

Description: Code specifying the versionnumber of the interchange controlsegments

M ID 5/5 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code Name00501 Standards Approved for Publication by ASC X12 Procedures Review Board

through October 2003

ISA13 I12 Interchange Control Number

Description: A control number assignedby the interchange senderGPC Notes: NAPA requires that ISAControl Number does not repeat within 90days.

GPC Notes: NAPA requires that ISAControl Number does not repeat within 90days.

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested

Description: Code indicating sender'srequest for an interchangeacknowledgment

M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name0 No Interchange Acknowledgment Requested

ISA15 I14 Interchange Usage Indicator

Description: Code indicating whetherdata enclosed by this interchangeenvelope is test, production or information

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 2)Code NameP Production DataT Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; thecomponent element separator is adelimiter and not a data element; this fieldprovides the delimiter used to separatecomponent data elements within acomposite data structure; this value mustbe different than the data elementseparator and the segment terminatorGPC Notes: NAPA is using Coloncharacter (Hex 3A) for the ComponentElement Separator.

GPC Notes: NAPA is using Coloncharacter (Hex 3A) for the ComponentElement Separator.

M 1/1 Must use






GS Functional Group Header Pos: 0200 Max: 1Heading - Mandatory


Purpose: To indicate the beginning of a functional group and to provide control information

GPC Example:GPC Example:GS*SH*partnerid*NAPA*20110825*1018*1341*X*005010^GS*SH*partnerid*NAPA*20110825*1018*1341*X*005010^

Element Summary: Ref Id Element Name Req Type Min/Max UsageGS01 479 Functional Identifier Code

Description: Code identifying a group ofapplication related transaction sets

M ID 2/2 Must use

CodeList Summary (Total Codes: 260, Included: 1)Code NameSH Ship Notice/Manifest (856)

GS02 142 Application Sender's Code

Description: Code identifying partysending transmission; codes agreed to bytrading partnersGPC Notes: This is Supplier defined EDIGS Sender ID.GPC Notes: This is Supplier defined EDIGS Sender ID.

M AN 2/15 Must use

GS03 124 Application Receiver's Code

Description: Code identifying partyreceiving transmission; codes agreed toby trading partnersGPC Notes: This is NAPA EDI GSReceiver ID. NAPA is using value 'NAPA'for GS.03. NAPA is using value 'NAPAXP'for the NAPA Xpress Program.

GPC Notes: This is NAPA EDI GSReceiver ID. NAPA is using value 'NAPA'for GS.03. NAPA is using value 'NAPAXP'for the NAPA Xpress Program.

M AN 2/15 Must use

GS04 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year

M DT 8/8 Must use

GS05 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

M TM 4/8 Must use

GS06 28 Group Control Number

Description: Assigned number originated

M N0 1/9 Must use




and maintained by the senderGPC Notes: The number is sequentiallyassigned by the Sender, starting with onewithin each Interchnage. For eachInterchange, the first Functional Group,set control number will be 0001 andincremented by one for each additionalFunctional Group within the Interchange.

GPC Notes: The number is sequentiallyassigned by the Sender, starting with onewithin each Interchnage. For eachInterchange, the first Functional Group,set control number will be 0001 andincremented by one for each additionalFunctional Group within the Interchange.

GS07 455 Responsible Agency Code

Description: Code identifying the issuerof the standard; this code is used inconjunction with Data Element 480

M ID 1/2 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameX Accredited Standards Committee X12

GS08 480 Version / Release / Industry IdentifierCode

Description: Code indicating the version,release, subrelease, and industryidentifier of the EDI standard being used,including the GS and GE segments; ifcode in DE455 in GS segment is X, thenin DE 480 positions 1-3 are the versionnumber; positions 4-6 are the release andsubrelease, level of the version; andpositions 7-12 are the industry or tradeassociation identifiers (optionally assignedby user); if code in DE455 in GS segmentis T, then other formats are allowed

M AN 1/12 Must use

CodeList Summary (Total Codes: 54, Included: 1)Code Name005010 Standards Approved for Publication by ASC X12 Procedures Review Board

through October 2003



ST Transaction Set Header Pos: 0300 Max: 1Heading - Mandatory


Purpose: To indicate the start of a transaction set and to assign a control number

GPC Example:GPC Example:ST*856*0001^ST*856*0001^

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 318, Included: 1)Code Name856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set GPC Notes: The number is sequentiallyassigned by the Sender, starting with onewithin each Functional group. For eachFunctional group, the first Transaction setcontrol number will be 0001 andincremented by one for each additionalTransaction set within the Functionalgroup.

GPC Notes: The number is sequentiallyassigned by the Sender, starting with onewithin each Functional group. For eachFunctional group, the first Transaction setcontrol number will be 0001 andincremented by one for each additionalTransaction set within the Functionalgroup.

M AN 4/9 Must use



BSN Beginning Segment for ShipNotice

Pos: 0400 Max: 1Heading - Mandatory


Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

GPC Example:GPC Example:BSN*00*20207073*20110825*1018*0001^BSN*00*20207073*20110825*1018*0001^

Element Summary: Ref Id Element Name Req Type Min/Max UsageBSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 66, Included: 1)Code Name00 Original

BSN02 396 Shipment Identification

Description: A unique control numberassigned by the original shipper to identifya specific shipment GPC Notes: Bill of LadingGPC Notes: Bill of Lading

M AN 2/30 Must use

BSN03 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year GPC Notes: Date ASN was created (CCYYMMDD)GPC Notes: Date ASN was created (CCYYMMDD)

M DT 8/8 Must use

BSN04 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99) GPC Notes: Time ASN was created(HHMM)GPC Notes: Time ASN was created(HHMM)

M TM 4/8 Must use

BSN05 1005 Hierarchical Structure Code

Description: Code indicating thehierarchical application structure of atransaction set that utilizes the HLsegment to define the structure of thetransaction set GPC Notes: Pick and Pack StructureGPC Notes: Pick and Pack Structure

M ID 4/4 Must use




CodeList Summary (Total Codes: 81, Included: 1)Code Name0001 Shipment, Order, Packaging, Item



Loop Hierarchical Level [Shipment] Pos: 0100 Repeat: 1Mandatory

Loop: HL Elements: N/A

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

GPC Example:GPC Example:HL*1**S*1^TD1*PLT90*1*****5*ZZ^TD5**2*RALT^REF*CN*1234567^REF*BM*20207073^DTM*011*20110825^DTM*067*20110830^FOB*PO^N1*BT*NAPA ATLANTA DC*92*ATL00999^N1*SU*Supplier Name*92*Supplier ID^

HL*1**S*1^TD1*PLT90*1*****5*ZZ^TD5**2*RALT^REF*CN*1234567^REF*BM*20207073^DTM*011*20110825^DTM*067*20110830^FOB*PO^N1*BT*NAPA ATLANTA DC*92*ATL00999^N1*SU*Supplier Name*92*Supplier ID^

GPC Notes:GPC Notes:Shipment Level is MANDATORY.Shipment Level is MANDATORY.

Loop Summary: Pos Id Segment Name Req Max Use Repeat0200 HL Hierarchical Level M 1 1200 TD1 Carrier Details (Quantity and Weight) O 20 1300 TD5 Carrier Details (Routing Sequence/Transit Time) M 12 1900 REF Reference Information M 1 1900 REF Reference Information M >1 3700 DTM Date/Time Reference M 1 3700 DTM Date/Time Reference O 9 3800 FOB F.O.B. Related Instructions M 1 4000 Loop N1 M 14800 Loop N1 M 199



HL Hierarchical Level Pos: 0200 Max: 1Detail - Mandatory

Loop: HL Elements: 4


GPC Example:GPC Example:HL*1**S*1^HL*1**S*1^

GPC Notes:GPC Notes:The HL segment is used to identify levels of detail information using a hierarchical structure. HL.01 shall contain aunique number for each occurrence of the HL segment within the transaction set. The value assigned to the firstHL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.HL.02 identifies the hierarchical ID of the HL segment to which it is subordinate(child of). HL.02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has noparent. HL.03 identifies the application content of the series of segments following the current HL segment up tothe next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Order, Tare/Pallet, Pack andItem.

The HL segment is used to identify levels of detail information using a hierarchical structure. HL.01 shall contain aunique number for each occurrence of the HL segment within the transaction set. The value assigned to the firstHL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.HL.02 identifies the hierarchical ID of the HL segment to which it is subordinate(child of). HL.02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has noparent. HL.03 identifies the application content of the series of segments following the current HL segment up tothe next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Order, Tare/Pallet, Pack andItem.

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure GPC Notes: The value for this level(Shipment) is '1'.GPC Notes: The value for this level(Shipment) is '1'.

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to GPC Notes: Number representing theParent Level's HL.01 number.GPC Notes: Number representing theParent Level's HL.01 number.

O AN 1/12 Used

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 250, Included: 1)Code NameS Shipment

HL04 736 Hierarchical Child Code

Description: Code indicating if there arehierarchical child data segmentssubordinate to the level being described GPC Notes: This indicates there aresubordinate Hierarchical Data segmentsto this level.

GPC Notes: This indicates there aresubordinate Hierarchical Data segmentsto this level.

O ID 1/1 Used

CodeList Summary (Total Codes: 2, Included: 1)



Code Name1 Additional Subordinate HL Data Segment in This Hierarchical Structure.



TD1 Carrier Details (Quantity andWeight)

Pos: 1200 Max: 20Detail - Optional


Purpose: To specify the transportation details relative to commodity, weight, and quantity

GPC Example:GPC Example:TD1*PLT90*1*****5*ZZ^TD1*PLT90*1*****5*ZZ^

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD101 103 Packaging Code

Description: Code identifying the type ofpackaging; Part 1: Packaging Form, Part2: Packaging Material; if the Data Elementis used, then Part 1 is always required

O AN 3/5 Must use

CodeList Summary (Total Codes: 155, Included: 2)Code NameCTN CartonPLT Pallet

CodeList Summary (Total Codes: 57, Included: 1)Code Name90 Standard

TD102 80 Lading Quantity

Description: Number of units (pieces) ofthe lading commodity GPC Notes: Pallet CountGPC Notes: Pallet Count

X N0 1/7 Must use

TD106 187 Weight Qualifier

Description: Code defining the type ofweight

O ID 1/2 Used

CodeList Summary (Total Codes: 52, Included: 2)Code NameG Gross WeightN Actual Net Weight

TD107 81 Weight

Description: Numeric value of weight

X R 1/10 Used

TD108 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

X ID 2/2 Used

CodeList Summary (Total Codes: 844, Included: 5)Code Name01 Actual Pounds

Code Name



GR GramKG KilogramLB PoundZZ Mutually Defined



TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 1300 Max: 12Detail - Mandatory


Purpose: To specify the carrier and sequence of routing and provide transit time information

GPC Example:GPC Example:TD5**2*RALT^TD5**2*NONE^TD5**2*RALT^TD5**2*NONE^

GPC Notes:GPC Notes:NAPA and NAPAXP request the vendor to utilize the SCAC code if available.NAPA and NAPAXP request the vendor to utilize the SCAC code if available.

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

M ID 1/2 Must use

CodeList Summary (Total Codes: 241, Included: 1)Code Name2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code

Description: Code identifying a party orother code GPC Notes: SCAC Code or use "NONE"if no SCAC availableGPC Notes: SCAC Code or use "NONE"if no SCAC available

M AN 2/80 Must use



REF Reference Information Pos: 1900 Max: 1Detail - Mandatory


Purpose: To specify identifying information

GPC Example:GPC Example:REF*BM*20207073^REF*BM*20207073^

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification GPC Notes: One of these values must besent. NAPA can accept any of the threevalues. The order of preference is BM, 08,2I.

GPC Notes: One of these values must besent. NAPA can accept any of the threevalues. The order of preference is BM, 08,2I.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1731, Included: 3)Code Name08 Carrier Assigned Package Identification Number

Description: A reference number assigned by a carrier to uniquely identify a singlepackage

2I Tracking NumberBM Bill of Lading Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: NAPA requires Bill of LadingNumberGPC Notes: NAPA requires Bill of LadingNumber

X AN 1/50 Must use



REF Reference Information Pos: 1900 Max: >1Detail - Mandatory



GPC Example:GPC Example:REF*CN*1234567^REF*CN*1234567^


Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1731, Included: 1)Code NameCN Carrier's Reference Number (PRO/Invoice)


Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: NAPA requires Carrier ProNumberGPC Notes: NAPA requires Carrier ProNumber

X AN 1/50 Must use



DTM Date/Time Reference Pos: 3700 Max: 1Detail - Mandatory


Purpose: To specify pertinent dates and times

GPC Example:GPC Example:DTM*011*20110825^DTM*011*20110825^

GPC Notes:GPC Notes:This is the date the shipment leaves the vendors facility.This is the date the shipment leaves the vendors facility.

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1280, Included: 1)Code Name011 Shipped

DTM02 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year GPC Notes: Shipped Date (CCYYMMDD)GPC Notes: Shipped Date (CCYYMMDD)

M DT 8/8 Must use



DTM Date/Time Reference Pos: 3700 Max: 9Detail - Optional


Purpose: To specify pertinent dates and times

GPC Example:GPC Example:DTM*067*20110830^DTM*067*20110830^

GPC Notes:GPC Notes:This is the date the NAPA DC or Store expects to receive the shipment. This is a new field that must be utilized ifthe vendor participates in the NAPA Xpress Program.This is the date the NAPA DC or Store expects to receive the shipment. This is a new field that must be utilized ifthe vendor participates in the NAPA Xpress Program.

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Used

CodeList Summary (Total Codes: 1280, Included: 1)Code Name067 Current Schedule Delivery

DTM02 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year GPC Notes: Expected Receive Date(CCYYMMDD)GPC Notes: Expected Receive Date(CCYYMMDD)

M DT 8/8 Used



FOB F.O.B. Related Instructions Pos: 3800 Max: 1Detail - Mandatory


Purpose: To specify transportation instructions relating to shipment

GPC Example:GPC Example:FOB*PO^FOB*PO^

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges GPC Notes: DF - This code is used toidentify shipments that will contain afreight charge on the actual invoice.BP - This code is used to identifyshipments where NAPA will pay the actualfreight charge for UPS shipments�TP -This code is used to identify shipmentshere a Third Party pays the freightcharges for the shipmentPS - This code is used to identifyshipments that will contain a freightcharge on the actual invoice which will bepaid by the seller.

GPC Notes: DF - This code is used toidentify shipments that will contain afreight charge on the actual invoice.BP - This code is used to identifyshipments where NAPA will pay the actualfreight charge for UPS shipments�TP -This code is used to identify shipmentshere a Third Party pays the freightcharges for the shipmentPS - This code is used to identifyshipments that will contain a freightcharge on the actual invoice which will bepaid by the seller.

M ID 2/2 Must use

CodeList Summary (Total Codes: 31, Included: 6)Code NameBP Paid by Buyer

Description: The buyer agrees to the transportation payment term requiring thebuyer to pay transportation charges to a specified location (origin or destinationlocation)

CC CollectDF Defined by Buyer and SellerPO Prepaid OnlyPS Paid by Seller

Description: The seller agrees to the transportation payment term requiring theseller to pay transportation charges to a specified location (origin or destinationlocation)

TP Third Party Pay



Loop Party Identification [BT] Pos: 4000 Repeat: 1Mandatory

Loop: N1 Elements: N/A

Purpose: To identify a party by type of organization, name, and code

GPC Example:GPC Example:N1*BT*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^

N1*BT*NAPA ATLANTA DC*92*ATL00999^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N4*NORCROSS*GA*30071^

GPC Notes:GPC Notes:The N1 "BT - Bill To" loop/segment is required by NAPA.The N1 "BT - Bill To" loop/segment is required by NAPA.

Loop Summary: Pos Id Segment Name Req Max Use Repeat4100 N1 Party Identification M 1 4300 N3 Party Location O 2 4400 N4 Geographic Location O 1



N1 Party Identification Pos: 4100 Max: 1Detail - Mandatory

Loop: N1 Elements: 4


GPC Example:GPC Example:N1*BT*NAPA ATLANTA DC*92*ATL00999^N1*BT*NAPA ATLANTA DC*92*ATL00999^

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1500, Included: 1)Code NameBT Bill-to-Party

N102 93 Name

Description: Free-form name GPC Notes: NAPA DC Name. Returnfrom the N1.02 (BY) element sent on theoriginal 850 document.

GPC Notes: NAPA DC Name. Returnfrom the N1.02 (BY) element sent on theoriginal 850 document.

X AN 1/60 Must use

N103 66 Identification Code Qualifier


X ID 1/2 Must use

CodeList Summary (Total Codes: 241, Included: 1)Code Name92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code

Description: Code identifying a party orother code GPC Notes: This will be the DCabbreviation + "00999" for DC Stockorders. For all other orders use the DCabbreviation + the actual store number. Itmust match the value sent on 850Purchase Order in N1.04 (BY) element.The NAPA store number is always 5 digits(2 leading zeros followed by the 3 digitstore number).

GPC Notes: This will be the DCabbreviation + "00999" for DC Stockorders. For all other orders use the DCabbreviation + the actual store number. Itmust match the value sent on 850Purchase Order in N1.04 (BY) element.The NAPA store number is always 5 digits(2 leading zeros followed by the 3 digitstore number).

X AN 2/80 Must use



N3 Party Location Pos: 4300 Max: 2Detail - Optional


Purpose: To specify the location of the named party

GPC Example:GPC Example:N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^N3*5420 PEACHTREE INDUSTRIAL BOULEVARD^

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information


O AN 1/55 Optional



N4 Geographic Location Pos: 4400 Max: 1Detail - Optional


Purpose: To specify the geographic place of the named party

GPC Example:GPC Example:N4*NORCROSS*GA*30071^N4*NORCROSS*GA*30071^

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

X ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used



Loop Party Identification [SU] Pos: 4800 Repeat: 199Mandatory



GPC Example:GPC Example:N1*SU*Supplier NAPNET ID*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^

N1*SU*Supplier NAPNET ID*92*Supplier ID^N3*555 OAK STREET^N4*SOMEWHERE*GA*31904^

GPC Notes:GPC Notes:This N1 "SU - Supplier" loop/segment is required by NAPA.This N1 "SU - Supplier" loop/segment is required by NAPA.

Loop Summary: Pos Id Segment Name Req Max Use Repeat4900 N1 Party Identification M 1 5100 N3 Party Location M 2 5200 N4 Geographic Location M 1






GPC Example:GPC Example:N1*SU*Supplier NAPANET ID*92*Supplier ID^N1*SU*Supplier NAPANET ID*92*Supplier ID^



M ID 2/3 Must use

CodeList Summary (Total Codes: 1500, Included: 1)Code NameSU Supplier/Manufacturer

N102 93 Name

Description: Free-form name GPC Notes: NAPA assigned 8 characterID provided in the N1.02 (SU) element onthe outbound 850 document.

GPC Notes: NAPA assigned 8 characterID provided in the N1.02 (SU) element onthe outbound 850 document.

X AN 1/60 Must use



X ID 1/2 Must use



Description: Code identifying a party orother code GPC Notes: For JOEI orders only. JOEIthree chracter warehouse code (Returnfrom the N1.04 (SU) on the JOEI PO)

GPC Notes: For JOEI orders only. JOEIthree chracter warehouse code (Returnfrom the N1.04 (SU) on the JOEI PO)

X AN 2/80 Must use



N3 Party Location Pos: 5100 Max: 2Detail - Mandatory



GPC Example:GPC Example:N3*555 OAK STREET^N3*555 OAK STREET^

GPC Notes:GPC Notes:NAPA and NAPA Xpress requires this field is populated with the physical location of the supplier warehouse.NAPA and NAPA Xpress requires this field is populated with the physical location of the supplier warehouse.



M AN 1/55 Must use



O AN 1/55 Optional



N4 Geographic Location Pos: 5200 Max: 1Detail - Mandatory



GPC Example:GPC Example:N4*SOMEWHERE*GA*31904^N4*SOMEWHERE*GA*31904^

GPC Notes:GPC Notes:NAPA and NAPA Xpress requires this field is populated with the physical location of the supplier warehouse.NAPA and NAPA Xpress requires this field is populated with the physical location of the supplier warehouse.



O AN 2/30 Used



X ID 2/2 Used



O ID 3/15 Used



Loop Hierarchical Level [Order] Pos: 7100 Repeat: 1Mandatory



GPC Example:GPC Example:HL*2*1*O*1^PRF*05832797OD000ZZZ04269***20110823^REF*PK*199430^REF*IV*000741957_049**20110825^REF*PD*FD054^REF*SU*STR^N1*ST*NAPA AUTO PARTS ATL069*ZZ*00069^

HL*2*1*O*1^PRF*05832797OD000ZZZ04269***20110823^REF*PK*199430^REF*IV*000741957_049**20110825^REF*PD*FD054^REF*SU*STR^N1*ST*NAPA AUTO PARTS ATL069*ZZ*00069^

GPC Notes:GPC Notes:Order Level is MANDATORY. There can be multiple Orders on the same Shipment (ASN) but you can not mixdifferent shipping locations within the same ASN.Order Level is MANDATORY. There can be multiple Orders on the same Shipment (ASN) but you can not mixdifferent shipping locations within the same ASN.

Loop Summary: Pos Id Segment Name Req Max Use Repeat7200 HL Hierarchical Level M 1 7600 PRF Purchase Order Reference M 1 8900 REF Reference Information [PK] M 1 9000 REF Reference Information [IV] O 1 9100 REF Reference Information [PD] M 1 9200 REF Reference Information [SU] M 12 11400 Loop N1 M 200






GPC Example:GPC Example:HL*2*1*O*1^HL*2*1*O*1^


Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use


Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to GPC Notes: This data element containsthe value of the HL.01 in the parentShipment level HL segment, asappropriate to the transaction setstructure.

GPC Notes: This data element containsthe value of the HL.01 in the parentShipment level HL segment, asappropriate to the transaction setstructure.

M AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 250, Included: 1)Code NameO Order


Description: Code indicating if there arehierarchical child data segmentssubordinate to the level being described

M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name1 Additional Subordinate HL Data Segment in This Hierarchical Structure.



PRF Purchase Order Reference Pos: 7600 Max: 1Detail - Mandatory


Purpose: To provide reference to a specific purchase order

GPC Example:GPC Example:PRF*05832797OD000ZZZ04269***20110823^PRF*05832797OD000ZZZ04269***20110823^

Element Summary: Ref Id Element Name Req Type Min/Max UsagePRF01 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaser GPC Notes: Purchase Order Number(sent on 850 in BEG.03)GPC Notes: Purchase Order Number(sent on 850 in BEG.03)

M AN 1/22 Must use

PRF04 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year GPC Notes: Purchase Order Date (senton 850 in BEG.05)GPC Notes: Purchase Order Date (senton 850 in BEG.05)

M DT 8/8 Must use



REF Reference Information [PK] Pos: 8900 Max: 1Detail - Mandatory



GPC Example:GPC Example:REF*PK*199430^REF*PK*199430^



M ID 2/3 Must use

CodeList Summary (Total Codes: 1731, Included: 1)Code NamePK Packing List Number


Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: Packing Slip NumberGPC Notes: Packing Slip Number

M AN 1/50 Must use



REF Reference Information [IV] Pos: 9000 Max: 1Detail - Optional



GPC Example:GPC Example:REF*IV*000741957_049^REF*IV*000741957_049^

GPC Notes:GPC Notes:This segment is recommended by NAPA. It contains the Invoice Number. If Invoice Number is available, pleasesend it.This segment is recommended by NAPA. It contains the Invoice Number. If Invoice Number is available, pleasesend it.



O ID 2/3 Optional

CodeList Summary (Total Codes: 1731, Included: 1)Code NameIV Seller's Invoice Number


Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: Invoice NumberGPC Notes: Invoice Number

O AN 1/50 Optional



REF Reference Information [PD] Pos: 9100 Max: 1Detail - Mandatory



GPC Example:GPC Example:Director Orde: REF*PD*FD054^JOEI Order: REF*PD*JOEI^Premier Order: REF*PD*00765^SPOM Order: REF*PD*SPOM^NAPA Xpress Order: REF*PD*NXP^

Director Orde: REF*PD*FD054^JOEI Order: REF*PD*JOEI^Premier Order: REF*PD*00765^SPOM Order: REF*PD*SPOM^NAPA Xpress Order: REF*PD*NXP^



M ID 2/3 Must use

CodeList Summary (Total Codes: 1731, Included: 1)Code NamePD Promotion/Deal Number


Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: Factory Order Program Code(sent on 850 in SI.03). This is a fivecharacter code sent on ALL orders tosignify the program an order is beingplaced in accordance with as detereminedby NAPA and the supplier.Example Director Order: FD054Eample JOEI Order: JOEIExample Premier Order: 00765Example SPOM order: SPOMExample NAPAXPRESS order: NXP

GPC Notes: Factory Order Program Code(sent on 850 in SI.03). This is a fivecharacter code sent on ALL orders tosignify the program an order is beingplaced in accordance with as detereminedby NAPA and the supplier.Example Director Order: FD054Eample JOEI Order: JOEIExample Premier Order: 00765Example SPOM order: SPOMExample NAPAXPRESS order: NXP

M AN 1/50 Must use



REF Reference Information [SU] Pos: 9200 Max: 12Detail - Mandatory



GPC Example:GPC Example:REF*SU*STR^ or REF*SU*DC^ REF*SU*STR^ or REF*SU*DC^



M ID 2/3 Must use

CodeList Summary (Total Codes: 1731, Included: 1)Code NameSU Special Processing Code


Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier GPC Notes: Shipping DestinationIf outbound 850 - PO N9.02 = "DC" thenREF.02 = "DC".If Outbound 850 - PO N9.02 = "JD" or"SJD" then REF.02 = "STR"

GPC Notes: Shipping DestinationIf outbound 850 - PO N9.02 = "DC" thenREF.02 = "DC".If Outbound 850 - PO N9.02 = "JD" or"SJD" then REF.02 = "STR"

M AN 1/50 Must use



Loop Party Identification [ST] Pos: 11400 Repeat: 200Mandatory



GPC Example:GPC Example:N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^N3*1504 ALEXANDERSTREET^N4*COLUMBUS*GA*31904^

N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^N3*1504 ALEXANDERSTREET^N4*COLUMBUS*GA*31904^

GPC Notes:GPC Notes:This segment should match the information in the N1 ST loop in the 850 Purchase Order.This segment should match the information in the N1 ST loop in the 850 Purchase Order.

Loop Summary: Pos Id Segment Name Req Max Use Repeat11500 N1 Party Identification M 1 11700 N3 Party Location O 2 11800 N4 Geographic Location O 1






GPC Example:GPC Example:N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^N1*ST*NAPA AUTO PARTS ATL069*92*ATL00069^



M ID 2/3 Must use

CodeList Summary (Total Codes: 1500, Included: 1)Code NameST Ship To

N102 93 Name

Description: Free-form name GPC Notes: NAPA Store/Jobber Name ifASN is for a Director or JOEI type order(sent on 850 in N1.ST segment, N1.02element)NAPA DC Name if ASN is for a Premiertype order (sent on 850 in N1.STsegment, N1.02 element)

GPC Notes: NAPA Store/Jobber Name ifASN is for a Director or JOEI type order(sent on 850 in N1.ST segment, N1.02element)NAPA DC Name if ASN is for a Premiertype order (sent on 850 in N1.STsegment, N1.02 element)

X AN 1/60 Must use



X ID 1/2 Must use



Description: Code identifying a party orother code GPC Notes: This is NAPA Store Number- a required number to be sent on 856from the original 850 Purchase Order inN1.04 (ST qualifier). It is the locationwhere the Supplier should ship theproduct, the ultimate receiver of theproduct. This will be the DC abbreviation+ "00999" for DC Stock orders. For allother orders use the DC abbreviation +the actual store number. The NAPA storenumber is always 5 digits (2 leading zeros

GPC Notes: This is NAPA Store Number- a required number to be sent on 856from the original 850 Purchase Order inN1.04 (ST qualifier). It is the locationwhere the Supplier should ship theproduct, the ultimate receiver of theproduct. This will be the DC abbreviation+ "00999" for DC Stock orders. For allother orders use the DC abbreviation +the actual store number. The NAPA storenumber is always 5 digits (2 leading zeros

X AN 2/80 Must use




followed by the 3 digit store number).followed by the 3 digit store number).



N3 Party Location Pos: 11700 Max: 2Detail - Optional



GPC Example:GPC Example:N3*1504 ALEXANDERSTREET^N3*1504 ALEXANDERSTREET^

GPC Notes:GPC Notes:NAPA and NAPA Xpress recommends this field is populated with the correct value sent on the 850.NAPA and NAPA Xpress recommends this field is populated with the correct value sent on the 850.



M AN 1/55 Must use



O AN 1/55 Used



N4 Geographic Location Pos: 11800 Max: 1Detail - Optional



GPC Example:GPC Example:N4*COLUMBUS*GA*31904^N4*COLUMBUS*GA*31904^

GPC Notes:GPC Notes:NAPA and NAPA Xpress recommends this field is populated with the correct value sent on the 850.NAPA and NAPA Xpress recommends this field is populated with the correct value sent on the 850.



O AN 2/30 Used



X ID 2/2 Used



O ID 3/15 Used



Loop Hierarchical Level[Tare/Pallet]

Pos: 13700 Repeat: 1Mandatory



GPC Example:GPC Example:HL*3*2*T*1^MAN*GM*00106545432002633752^PAL*6****32*01^

HL*3*2*T*1^MAN*GM*00106545432002633752^PAL*6****32*01^

GPC Notes:GPC Notes:Tare Level is MANDATORY and contains the Pallet identification.Tare Level is MANDATORY and contains the Pallet identification.

Loop Summary: Pos Id Segment Name Req Max Use Repeat13800 HL Hierarchical Level M 1 17200 MAN Marks and Numbers Information M >1 17500 PAL Pallet Type and Load Characteristics O 1






GPC Example:GPC Example:HL*3*2*T*1^HL*3*2*T*1^



M AN 1/12 Must use


Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to GPC Notes: This data element containsthe value of the HL.01 in the parent Orderlevel HL segment, as appropriate to thetransaction set structure.

GPC Notes: This data element containsthe value of the HL.01 in the parent Orderlevel HL segment, as appropriate to thetransaction set structure.

M AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 250, Included: 1)Code NameT Shipping Tare



M ID 1/1 Must use




MAN Marks and NumbersInformation

Pos: 17200 Max: >1Detail - Mandatory


Purpose: To indicate identifying marks and numbers for shipping containers

GPC Example:GPC Example:MAN*GM*00106545432002633752^MAN*GM*00106545432002633752^

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 21, Included: 2)Code NameCP Carrier-Assigned Package ID NumberGM EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment GPC Notes: If the MAN.01 is 'CP'' thenthe MAN.02 should be the carrier packageID. If the MAN.01 is 'GM' then the MAN.02must be the SSCC18 label number.

GPC Notes: If the MAN.01 is 'CP'' thenthe MAN.02 should be the carrier packageID. If the MAN.01 is 'GM' then the MAN.02must be the SSCC18 label number.

M AN 1/48 Must use



PAL Pallet Type and LoadCharacteristics



Purpose: To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of theload and the pallet

GPC Example:GPC Example:PAL*6****32*01^PAL*6****32*01^

Element Summary: Ref Id Element Name Req Type Min/Max UsagePAL01 883 Pallet Type Code

Description: Code indicating the type ofpallet All valid standard codes are used.(Total Codes: 9)

O ID 1/2 Used

PAL05 395 Unit Weight

Description: Numeric value of weight perunit GPC Notes: NAPA requests the weightGPC Notes: NAPA requests the weight

X R 1/8 Used

PAL06 355 Unit or Basis for Measurement Code


X ID 2/2 Used

CodeList Summary (Total Codes: 844, Included: 1)Code Name01 Actual Pounds



Loop Hierarchical Level [Pack] Pos: 19900 Repeat: 1Optional



GPC Example:GPC Example:HL*4*3*P*1^MEA*WT*G*10*LB^TD1*WRP79*10^MAN*GM*00106545432002677814^

HL*4*3*P*1^MEA*WT*G*10*LB^TD1*WRP79*10^MAN*GM*00106545432002677814^

GPC Notes:GPC Notes:*** This HL level (Pack) is NOT used for the NXP program at this time ***

If Pack Level is present it must contains the Pack Identification. If all Parts on the same Tare/Pallet have the same NAPA Part Numbers, than NAPA does not require the PackLevel.

*** This HL level (Pack) is NOT used for the NXP program at this time ***

If Pack Level is present it must contains the Pack Identification. If all Parts on the same Tare/Pallet have the same NAPA Part Numbers, than NAPA does not require the PackLevel.

Loop Summary: Pos Id Segment Name Req Max Use Repeat20000 HL Hierarchical Level O 1 20700 MEA Measurements O 40 21000 TD1 Carrier Details (Quantity and Weight) O 20 23400 MAN Marks and Numbers Information O >1



HL Hierarchical Level Pos: 20000 Max: 1Detail - Optional



GPC Example:GPC Example:HL*4*3*P*1^HL*4*3*P*1^

GPC Notes:GPC Notes:Not used for NXP program at this timeNot used for NXP program at this time



M AN 1/12 Must use


Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to GPC Notes: This data element containsthe value of the HL.01 in the parentPallet/Tare level HL segment, asappropriate to the transaction setstructure.

GPC Notes: This data element containsthe value of the HL.01 in the parentPallet/Tare level HL segment, asappropriate to the transaction setstructure.

O AN 1/12 Used



M ID 1/2 Must use

CodeList Summary (Total Codes: 250, Included: 1)Code NameP Pack



O ID 1/1 Used




MEA Measurements Pos: 20700 Max: 40Detail - Optional


Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, andweights(See Figures Appendix for example of use of C001)

GPC Example:GPC Example:MEA*WT*G*10*LB^MEA*WT*G*10*LB^


Element Summary: Ref Id Element Name Req Type Min/Max UsageMEA01 737 Measurement Reference ID Code

Description: Code identifying the broadcategory to which a measurement applies

O ID 2/2 Used

CodeList Summary (Total Codes: 165, Included: 1)Code NameWT Weights

MEA02 738 Measurement Qualifier

Description: Code identifying a specificproduct or process characteristic to whicha measurement applies

O ID 1/3 Used

CodeList Summary (Total Codes: 998, Included: 1)Code NameG Gross Weight

MEA03 739 Measurement Value

Description: The value of themeasurement GPC Notes: WeightGPC Notes: Weight

X R 1/20 Used

MEA04 C001 Composite Unit of Measure

Description: To identify a composite unitof measure (See Figures Appendix forexamples of use)

X Comp Used

MEA04-01 355 Unit or Basis for Measurement Code


M ID 2/2 Must use

CodeList Summary (Total Codes: 844, Included: 1)Code NameLB Pound



TD1 Carrier Details (Quantity andWeight)



Purpose: To specify the transportation details relative to commodity, weight, and quantity

GPC Example:GPC Example:TD1*WRP79*10^TD1*WRP79*10^


Element Summary: Ref Id Element Name Req Type Min/Max UsageTD101 103 Packaging Code

Description: Code identifying the type ofpackaging; Part 1: Packaging Form, Part2: Packaging Material; if the Data Elementis used, then Part 1 is always required GPC Notes: Any valid code fromComposites Code List 103 is acceptable.ie. “BOX34” for card-board box, "WRP79”for plastic wrapped. If Code_List_103_02is not known, use code '71' (not otherwisespecified).

GPC Notes: Any valid code fromComposites Code List 103 is acceptable.ie. “BOX34” for card-board box, "WRP79”for plastic wrapped. If Code_List_103_02is not known, use code '71' (not otherwisespecified).

O AN 3/5 Must use

CodeList Summary (Total Codes: 155, Included: 17)Code NameBAG BagBBL BarrelBDL BundleBOT BottleBOX BoxBSK Basket or hamperBXI Box, with inner containerBXT BucketCAN CanCAS CaseCCS Can CaseCNT ContainerCTN CartonMIX Mixed Container Types

Description: More than one type of container is included in a shipment (shipmentcould consist of 3 pieces that include 1 box, 1 crate, and 1 basket)

PCS PiecesPKG PackageWRP Wrapped

CodeList Summary (Total Codes: 57, Included: 5)Code Name25 Corrugated or Solid

Code Name



34 Fibre (Paperboard)71 Not Otherwise Specified76 Paper79 Plastic

TD102 80 Lading Quantity

Description: Number of units (pieces) ofthe lading commodity GPC Notes: Number for packages of thetype specified in TD1.01GPC Notes: Number for packages of thetype specified in TD1.01

X N0 1/7 Must use



MAN Marks and NumbersInformation

Pos: 23400 Max: >1Detail - Optional


Purpose: To indicate identifying marks and numbers for shipping containers

GPC Example:GPC Example:MAN*GM*00106545432002677814^MAN*GM*00106545432002677814^


Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 21, Included: 2)Code NameCP Carrier-Assigned Package ID NumberGM EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment GPC Notes: If the number is a GM typethem map the SSCC-18 Shipping LabelNumber. If the number is a CP type, thenmap the Carrier assigned packagenumber.

GPC Notes: If the number is a GM typethem map the SSCC-18 Shipping LabelNumber. If the number is a CP type, thenmap the Carrier assigned packagenumber.

M AN 1/48 Must use



Loop Hierarchical Level [Item] Pos: 26100 Repeat:199995

MandatoryLoop: HL Elements: N/A


GPC Example:GPC Example:HL*5*4*I*0^LIN*001*PI*ADO*BP*AD7574*PL*1^SN1**5*EA**8*EA**BP^PID*F****PD*Disc Brake - AD^

HL*5*4*I*0^LIN*001*PI*ADO*BP*AD7574*PL*1^SN1**5*EA**8*EA**BP^PID*F****PD*Disc Brake - AD^

GPC Notes:GPC Notes:Here are the guidelines that apply to the 856 document..• Must contain information on any part number that is on the original Purchase Order.• If you defer items to another shipping facility for ANY reason (this means that the item will not be shipped fromyour facility), you should indicate this in the 856. If you are in the regular habit of splitting our POs betweenmultiple shipping points, you must indicate at least once,that the parts have been deferred to another location. When in doubt, the Distribution Point that is CLOSEST toyour actual computer system should take the responsibility of notifying us of the deferred item status.• The basic rule is that every part number we order from you must be acknowledged.

Here are the guidelines that apply to the 856 document..• Must contain information on any part number that is on the original Purchase Order.• If you defer items to another shipping facility for ANY reason (this means that the item will not be shipped fromyour facility), you should indicate this in the 856. If you are in the regular habit of splitting our POs betweenmultiple shipping points, you must indicate at least once,that the parts have been deferred to another location. When in doubt, the Distribution Point that is CLOSEST toyour actual computer system should take the responsibility of notifying us of the deferred item status.• The basic rule is that every part number we order from you must be acknowledged.

Loop Summary: Pos Id Segment Name Req Max Use Repeat26200 HL Hierarchical Level M 1 26300 LIN Item Identification M 1 26400 SN1 Item Detail (Shipment) M 1 26800 PID Product/Item Description O 200






GPC Example:GPC Example:HL*5*4*I*0^HL*5*4*I*0^



M AN 1/12 Must use


Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to GPC Notes: This data element containsthe value of the HL.01 in the parentPack/Carton level HL segment, asappropriate to the transaction setstructure.

GPC Notes: This data element containsthe value of the HL.01 in the parentPack/Carton level HL segment, asappropriate to the transaction setstructure.

M AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 250, Included: 1)Code NameI Item



M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name0 No Subordinate HL Segment in This Hierarchical Structure.



LIN Item Identification Pos: 26300 Max: 1Detail - Mandatory


Purpose: To specify basic item identification data

GPC Example:GPC Example:LIN*001*PI*ADO*BP*AD7574*PL*1^LIN*001*PI*ADO*BP*AD7574*PL*1^

Element Summary: Ref Id Element Name Req Type Min/Max UsageLIN01 350 Assigned Identification

Description: Alphanumeric charactersassigned for differentiation within atransaction set GPC Notes: Sequence of Packing ListGPC Notes: Sequence of Packing List

M AN 1/20 Must use

LIN02 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

M ID 2/2 Must use

CodeList Summary (Total Codes: 519, Included: 1)Code NamePI Purchaser's Item Code

LIN03 234 Product/Service ID

Description: Identifying number for aproduct or service GPC Notes: NAPA Line Abbreviation(supplier specific) from original PurchaseOrder (sent on 850, PO1.09 - ProductLine Abbreviation).

GPC Notes: NAPA Line Abbreviation(supplier specific) from original PurchaseOrder (sent on 850, PO1.09 - ProductLine Abbreviation).

M AN 1/48 Must use



M ID 2/2 Must use

CodeList Summary (Total Codes: 519, Included: 1)Code NameBP Buyer's Part Number


Description: Identifying number for aproduct or service GPC Notes: NAPA Part Number fromoriginal Purchase Order (sent on 850 inPO1.07 with qualifier "BP")

GPC Notes: NAPA Part Number fromoriginal Purchase Order (sent on 850 inPO1.07 with qualifier "BP")

M AN 1/48 Must use


Description: Code identifying the

M ID 2/2 Must use




type/source of the descriptive numberused in Product/Service ID (234)

CodeList Summary (Total Codes: 519, Included: 1)Code NamePL Purchaser's Order Line Number


Description: Identifying number for aproduct or service GPC Notes: Line Number of item onoriginal Purchase Order (sent on 850 inPO1.01)

GPC Notes: Line Number of item onoriginal Purchase Order (sent on 850 inPO1.01)

M AN 1/48 Must use



X ID 2/2 Optional

CodeList Summary (Total Codes: 519, Included: 1)Code NameVP Vendor's (Seller's) Part Number


Description: Identifying number for aproduct or service GPC Notes: This is the Vendor PartNumber. This field must be utilized if thevendor participates in the NAPA XpressProgram.

GPC Notes: This is the Vendor PartNumber. This field must be utilized if thevendor participates in the NAPA XpressProgram.

X AN 1/48 Optional



SN1 Item Detail (Shipment) Pos: 26400 Max: 1Detail - Mandatory


Purpose: To specify line-item detail relative to shipment

GPC Example:GPC Example:SN1**5*EA**8*EA^SN1**5*EA**8*EA^

GPC Notes:GPC Notes:This segment contains the unit of measure and the quantity actually shipped.This segment contains the unit of measure and the quantity actually shipped.

Element Summary: Ref Id Element Name Req Type Min/Max UsageSN102 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set GPC Notes: Quantity ShippedGPC Notes: Quantity Shipped

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken GPC Notes: Return the same Unit ofMeasure from the original 850 (PO1.03element)

GPC Notes: Return the same Unit ofMeasure from the original 850 (PO1.03element)All valid standard codes are used.(Total Codes: 844)

M ID 2/2 Must use

SN105 380 Quantity

Description: Numeric value of quantity GPC Notes: Quantity OrderedGPC Notes: Quantity Ordered

X R 1/15 Used

SN106 355 Unit or Basis for Measurement Code


X ID 2/2 Used

CodeList Summary (Total Codes: 844, Included: 7)Code NameCA CaseDR DrumEA EachEX Feet, Inches and FractionEY Feet, Inches and DecimalFT FootGA Gallon



PID Product/Item Description Pos: 26800 Max: 200Detail - Optional


Purpose: To describe a product or process in coded or free-form format

GPC Example:GPC Example:PID*F****Disc Brake - AD^PID*F****Disc Brake - AD^

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent GPC Notes: Free Form DescriptionGPC Notes: Free Form Description

X AN 1/80 Used



CTT Transaction Totals Pos: 0100 Max: 1Summary - Mandatory


Purpose: To transmit a hash total for a specific element in the transaction set

GPC Example:GPC Example:CTT*9*14^CTT*9*14^

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction set GPC Notes: The number of line itemspresent in the transaction set.GPC Notes: The number of line itemspresent in the transaction set.

M N0 1/6 Must use

CTT02 347 Hash Total

Description: Sum of values of thespecified data element. All values in thedata element will be summed withoutregard to decimal points (explicit orimplicit) or signs. Truncation will occur onthe left most digits if the sum is greaterthan the maximum size of the hash totalof the data element. Example: -.0018 Firstoccurrence of value being hashed. .18Second occurrence of value beinghashed. 1.8 Third occurrence of valuebeing hashed. 18.01 Fourth occurrence ofvalue being hashed. 18E2 Fifthoccurrence of value being hashed. --------1873 Hash Total GPC Notes: Sum of the SN1.02 ElementsGPC Notes: Sum of the SN1.02 Elements

O R 1/10 Used



SE Transaction Set Trailer Pos: 0200 Max: 1Summary - Mandatory


Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

GPC Example:GPC Example:SE*38*0001^SE*38*0001^

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set GPC Notes: This must be the samenumber as is in the ST segment (ST02)for the Transaction set.

GPC Notes: This must be the samenumber as is in the ST segment (ST02)for the Transaction set.

M AN 4/9 Must use



GE Functional Group Trailer Pos: 0300 Max: 1Summary - Mandatory


Purpose: To indicate the end of a functional group and to provide control information

GPC Example:GPC Example:GE*1*1341^GE*1*1341^

Element Summary: Ref Id Element Name Req Type Min/Max UsageGE01 97 Number of Transaction Sets Included

Description: Total number of transactionsets included in the functional group orinterchange (transmission) groupterminated by the trailer containing thisdata element

M N0 1/6 Must use

GE02 28 Group Control Number

Description: Assigned number originatedand maintained by the senderGPC Notes: This must be the samenumber as is in the GS segment (GS06)for the Functional group.

GPC Notes: This must be the samenumber as is in the GS segment (GS06)for the Functional group.

M N0 1/9 Must use



IEA Interchange Control Trailer Pos: 0400 Max: 1Summary - Mandatory


Purpose: To define the end of an interchange of zero or more functional groups and interchange-related controlsegments

GPC Example:GPC Example:IEA*1*300001416ÎEA*1*300001416^

Element Summary: Ref Id Element Name Req Type Min/Max UsageIEA01 I16 Number of Included Functional Groups

Description: A count of the number offunctional groups included in aninterchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number

Description: A control number assignedby the interchange senderGPC Notes: This must be the samenumber as is in the ISA segment (ISA13)for the Interchange.

GPC Notes: This must be the samenumber as is in the ISA segment (ISA13)for the Interchange.

M N0 9/9 Must use

Documents

NAPA Inbound EDI 856 ANSI X12 v5010 Ship Notice...Nov 17, 2017 · 2.2 11/17/2017 Greg Edgar Updated document example 2.2 11/17/2017 Greg Edgar Updated the N1.04 element documentation