time and cost savings - pep boysadded the method of delivery code in the po1 segment. in addition,...

June 29, 2011 Dear Supplier Partner, Electronic Data Interchange (EDI) has proven to be one of the outstanding drivers in retail information technology systems resulting in time and cost savings for both retailers and suppliers. With these technologies and guidelines, Pep Boys can expedite merchandise flow to the selling floor, manage inventory better and process payments efficiently. Pep Boys continues to move forward with our initiative for all supplier partners to become 100% EDI compliant. Please review the EDI requirements attached and return the sign off form within 14 days of receiving this request. If necessary forward this request to the appropriate management level individual for approval If you are unable to meet the EDI requirements return the sign off form and state “not compliant”. We will work with you to contact an EDI provider to help you implement EDI requirements. Providing a timely response to this request will avoid non – compliant charge back penalties. Please return your responses to [email protected] . For a full review of our EDI, requirements and standards please reference our website at http://info.pepboys.com/ . Best regards, Diane Pizzarelli Manager, Supplier Relations 215- 430-9095 ext. 6785

mailto:[email protected]



http://info.pepboys.com/

2011 EDI UPDATES 7/5/11 New web portal allowance code W220 has been added to the available codes in the SAC02 segments in the 810 version 4010 and 4030. 7/5/11 New store list has been updated 9/14/11 New store list has been updated 9/27/11 EDI letter updated

2012 EDI UPDATES

7/23/12 Special Order EDI requirements updated – New special order ASN (856) and QOH (846) mapping guidelines have been added to the PDF. These documents will be rolled out to our existing special order vendors and will be a part of our new vendor special order testing.

Updated 7/19/2012

http://info.pepboys.com/schain/index.htm�

Pep Boys Vendor Number: ___________________________

Testing EDI Contact: Phone: E-mail:

Backup EDI Contact: Phone: E-mail:

1. Confirmed EDI capable and ready to test the 850** Test Date: Contact:

2. Confirmed to be EDI capable and ready to test the 997 Test Date: Contact:



5. Confirm transmit of 855 PO Acknowledgement within 24 hours of receipt of 850 PO: YES ____ NO ____

6. Are you capable of generating an 856 for special orders: YES____ NO____

7. Are you capable of providing QOH information: YES____ NO____

7A. How do you provide QOH information: 846____ FLAT FILE____ OTHER____If other please provide details below

8. Value Added Network (VAN):

9. Test mailbox Qualifier/ID:

10. Production mailbox Qualifier/ID (if different than test):

11. EDI Translation Software Pkg/3rd Party Supplier:

12. X12 Standards Version: 4030 VERSION SUPPORTED ONLY

13. If you are not EDI capable please provide explanation below.

Supplier Representative Signature Title Date Updated April 23, 2010

EDI Requirements Sign Off Document

Supplier Name:

I have read Pep Boys EDI Requirements and will validate that the above test dates will be met in order to comply with the EDI Requirements.

Please complete, sign and email this document to: [email protected]

Address:

City, State, Zip:

VENDOR'S INFORMATION PEP BOYS INFORMATION

INOVIS

INOVIS

PROVIDED UPON TESTING

01 / 007914401

ADDITIONS FOR SPECIAL ORDER EDI TRANSACTIONS Pep Boys has updated its mapping of the EDI X12 850 Purchase Order document to

accommodate the transmission Special Orders. We have made the following changes:

1. Added the PER and PID segments.

2. Added the code 'OS' for Special Orders in the BEG02.

3. Added the Method of Delivery Code in the PO1 segment.

In addition, we have the following requirements:

1. All EDI 850 Purchase Order documents must be acknowledged with an EDI X12

997 Functional Acknowledgement.

2. In addition, all Special Order documents must be acknowledged with an EDI X12

855 Purchase Order Acknowledgement document.

3. Within the 855 document, all Purchase Order lines must be acknowledged.

4. Pep Boys has a policy of shipping lines complete; we don't accept backorders on

Special Orders.

5. If a particular line item cannot be filled completely, the 855 document should

contain 0 in the ACK02 element.

6. Purchase Order Acknowledgements will be returned either the same day or with

in 24 hours of receipt of the PO.

7. Pep Boys 855 requires a 3 digit product code. This is a specific code for your

company. Please contact Pep Boys EDI Coordinator to receive your code before

testing.

Updated – September 13, 2010 2010

Special Order Delivery Methods These codes are sent out on the EDI PO and is required on the inbound 855 Code Name Fed Ex Service Type 01 Ships in 3 - 5 business days Fedex Ground 02 Ships next business day Fedex Priority Overnight 03 Expedite - 24/48 hour guarantee Fedex Priority Overnight 04 Two Day Air Fedex 2Day 05 International Ship Fedex International Economy 06 Your Truck 07 Pickup

Purchase Order - 850

PepBoys850_4030_v1_1FINAL.ecs 1 Ver 1.1

850 Purchase Order - v4030

X12/V4030/850

Version: 1.1 Final

Author: Inovis

Publication: April 1, 2008

Modified: 06/30/2008



Revision History

Date Version Revision Approved By

April 1, 2008 1.0 Initial Publication Diane Pizzarelli

June 30, 2008 1.1 Added BEG06 Added explanatory notes for special orders.

Diane Pizzarelli



850 Purchase Order

Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

User Note: PLEASE NOTE THAT IN 4030 THE ISA11 NO LONGER CONTAINS THE INTERCHANGE CONTROL

STANDARDS IDENTIFIER. IT IS NOW USED TO IDENTIFY THE REPETITION SEPARATOR.

Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage

ISA Interchange Control Header M 1 Must use

GS Functional Group Header M 1 Must use

0100 ST Transaction Set Header M 1 Must use

0200 BEG Beginning Segment for Purchase Order

M 1 Must use

0500 REF Reference Identification O >1 Used

0600 PER Administrative Communications Contact

O 3 Used

1300 ITD Terms of Sale/Deferred Terms of Sale

O >1 Used

1500 DTM Date/Time Reference O 10 Used

LOOP ID - N1 200

3100 N1 Name O 1 Used

3200 N2 Additional Name Information O 2 Used

3300 N3 Address Information O 2 Used

3400 N4 Geographic Location O >1 Used

3600 PER Administrative Communications Contact

O >1 Used

Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - PO1 100000 N2/0100L

0100 PO1 Baseline Item Data M 1 N2/0100 Must use

LOOP ID - PID 1000

0500 PID Product/Item Description O 1 Used

Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - CTT 1 N3/0100L

0100 CTT Transaction Totals O 1 N3/0100 Used

0300 SE Transaction Set Trailer M 1 Must use

GE Functional Group Trailer M 1 Must use

IEA Interchange Control Trailer M 1 Must use



ISA Interchange Control Header Pos: Max: 1

Heading - Mandatory

Loop: N/A Elements: 16 User Option (Usage): Must use 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

ISA01 I01 Authorization Information Qualifier Description: Code identifying the type of

information in the Authorization Information

M ID 2/2 Must use

Code Name

00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information Description: Information used for additional

identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier Description: Code identifying the type of

information in the Security Information

M ID 2/2 Must use

Code Name

00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information Description: This is used for identifying the

security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier Description: Code indicating the

system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use

Code Name

01 Duns (Dun & Bradstreet)

ZZ Mutually Defined

ISA06 I06 Interchange Sender ID Description: Identification code published by

the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401

M AN 15/15 Must use


system/method of code structure used to

M ID 2/2 Must use



designate the sender or receiver ID element being qualified All valid standard codes are used.

ISA08 I07 Interchange Receiver ID Description: Identification code published by

the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

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; the

repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

M 1/1 Must use

ISA12 I11 Interchange Control Version Number Description: Code specifying the version

number of the interchange control segments

M ID 5/5 Must use

Code Name

00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999

ISA13 I12 Interchange Control Number Description: A control number assigned by

the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code indicating sender's

request for an interchange acknowledgment

M ID 1/1 Must use

Code Name

1 Interchange Acknowledgment Requested

ISA15 I14 Usage Indicator Description: Code indicating whether data

enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use

Code Name

P Production Data

T Test Data

ISA16 I15 Component Element Separator Description: Type is not applicable; the

component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

M 1/1 Must use



GS Functional Group Header Pos: Max: 1

Heading - Mandatory

Loop: N/A Elements: 8 User Option (Usage): Must use To indicate the beginning of a functional group and to provide control information

Semantics:

1. GS04 is the group date.

2. GS05 is the group time.

3. 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:

1. 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.


GS01 479 Functional Identifier Code Description: Code identifying a group of

application related transaction sets

M ID 2/2 Must use

Code Name

PO Purchase Order (850)

GS02 142 Application Sender's Code Description: Code identifying party sending

transmission; codes agreed to by trading partners User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401

M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving

transmission; codes agreed to by trading partners

M AN 2/15 Must use

GS04 373 Date Description: Date expressed as

CCYYMMDD where CC represents the first two digits of the calendar year

M DT 8/8 Must use

GS05 337 Time Description: Time 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)

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 sender

GS07 455 Responsible Agency Code Description: Code identifying the issuer of

the standard; this code is used in conjunction with Data Element 480

M ID 1/2 Must use

Code Name

X Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version,

release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

M AN 1/12 Must use

Code Name

004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999



ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the start of a transaction set and to assign a control number

Semantics:

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition.

Example: ST*850*001


ST01 143 Transaction Set Identifier Code Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

Code Name

850 Purchase Order

ST02 329 Transaction Set Control Number Description: Identifying control number that

must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9 Must use



BEG Beginning Segment for Purchase Order

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5 User Option (Usage): Must use To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates

Semantics:

1. BEG05 is the date assigned by the purchaser to purchase order.

Example: BEG*00*NE*N8095301**20080115~


BEG01 353 Transaction Set Purpose Code Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

Code Name

00 Original

BEG02 92 Purchase Order Type Code Description: Code specifying the type of

Purchase Order

M ID 2/2 Must use

Code Name

NE New Order

OS Special Order

BEG03 324 Purchase Order Number Description: Identifying number for Purchase

Order assigned by the orderer/purchaser

M AN 8/8 Must use

BEG05 373 Date Description: Date expressed as


M DT 8/8 Must use

BEG06 367 Contract Number Description: Contract number User Note: Pep Boys-assigned Vendor Number. Used for Special Orders only.

O AN 10/10 Used



REF Reference Identification Pos: 0500 Max: >1

Heading - Optional

Loop: N/A Elements: 3 User Option (Usage): Used To specify identifying information

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

Semantics:

1. REF04 contains data relating to the value cited in REF02.

Example: REF*IA*1234567890~ REF*L1**FREE-FORM MESSAGE~

User Note: No REF segments will be sent for Special Orders.


REF01 128 Reference Identification Qualifier Description: Code qualifying the Reference

Identification

M ID 2/3 Must use

Code Name

IA Internal Vendor Number

L1 Letters or Notes

REF02 127 Reference Identification Description: Reference information as

defined for a particular Transaction Set or as specified by the Reference Identification Qualifier User Note: Used for vendor number assigned by Pep Boys (DC and Drop Ship only) only when REF01=IA

X AN 1/10 Used

REF03 352 Description Description: A free-form description to clarify

the related data elements and their content User Note: Used for free-form message only when REF01=L1

X AN 1/60 Used



PER Administrative Communications Contact

Pos: 0600 Max: 3

Heading - Optional

Loop: N/A Elements: 4 User Option (Usage): Used To identify a person or office to whom administrative communications should be directed

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.


Example: PER*CW*ABC SUPPLY*FX*8005551234~


PER01 366 Contact Function Code Description: Code identifying the major duty

or responsibility of the person or group named

M ID 2/2 Must use

Code Name

CW Confirmed With

PER02 93 Name Description: Free-form name

O AN 1/30 Used

PER03 365 Communication Number Qualifier Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

FX Facsimile

PER04 364 Communication Number Description: Complete communications

number including country or area code when applicable

X AN 1/10 Used



ITD Terms of Sale/Deferred Terms of Sale

Pos: 1300 Max: >1

Heading - Optional

Loop: N/A Elements: 5 User Option (Usage): Used To specify terms of sale

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.

2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.

3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics:

1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments:

1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.

Example: ITD*01*3*2**60**90

User Note: No ITD Segment will be sent for Special Orders.


ITD01 336 Terms Type Code Description: Code identifying type of

payment terms

O ID 2/2 Used

Code Name

01 Basic

ITD02 333 Terms Basis Date Code Description: Code identifying the beginning

of the terms period

O ID 1/2 Used

Code Name

3 Invoice Date

ITD03 338 Terms Discount Percent Description: Terms discount percentage,

expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

O R 1/6 Used

ITD05 351 Terms Discount Days Due Description: Number of days in the terms

discount period by which payment is due if terms discount is earned

X N0 1/3 Used

ITD07 386 Terms Net Days Description: Number of days until total

invoice amount is due (discount not applicable)

O N0 1/3 Used



DTM Date/Time Reference Pos: 1500 Max: 10

Heading - Optional

Loop: N/A Elements: 2 User Option (Usage): Used To specify pertinent dates and times

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Example: DTM*002*20080120~ DTM*010*20080115~ DTM*938*20080229~

User Note: 002 - Delivery Requested Date - is used for standard orders only. 010 - Requested Ship Date - is used for standard orders only. 938 - Order Date - is used for special orders only.


DTM01 374 Date/Time Qualifier Description: Code specifying type of date or

time, or both date and time

M ID 3/3 Must use

Code Name

002 Delivery Requested

010 Requested Ship

938 Order

DTM02 373 Date Description: Date expressed as


X DT 8/8 Used



N1 Name Pos: 3100 Max: 1

Heading - Optional

Loop: N1 Elements: 4 User Option (Usage): Used To identify a party by type of organization, name, and code

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments:

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

Example: N1*ST*PEP BOYS*92*14011~


N101 98 Entity Identifier Code Description: Code identifying an

organizational entity, a physical location, property or an individual

M ID 2/3 Must use

Code Name

ST Ship To

N102 93 Name Description: Free-form name

X AN 1/60 Used

N103 66 Identification Code Qualifier Description: Code designating the

system/method of code structure used for Identification Code (67) User Note: 92 - Assigned by Buyer - used for

standard orders only. ZZ - Mutually Defined - used for special orders only.

X ID 1/2 Used

Code Name

92 Assigned by Buyer or Buyer's Agent

ZZ Mutually Defined

N104 67 Identification Code Description: Code identifying a party or other

code User Note: Pep Boys Store Number

X AN 2/5 Used



N2 Additional Name Information

Pos: 3200 Max: 2

Heading - Optional

Loop: N1 Elements: 1 User Option (Usage): Used To specify additional names

Example: N2*ATLANTA DIST CNTR~

User Note: N2 segment not sent for special orders.


N201 93 Name Description: Free-form name

M AN 1/60 Must use



N3 Address Information Pos: 3300 Max: 2

Heading - Optional

Loop: N1 Elements: 2 User Option (Usage): Used To specify the location of the named party

Example: N3*2640 EAST 45TH STREET~


N301 166 Address Information Description: Address information

M AN 1/55 Must use

N302 166 Address Information Description: Address information

O AN 1/55 Used



N4 Geographic Location Pos: 3400 Max: >1

Heading - Optional

Loop: N1 Elements: 3 User Option (Usage): Used To specify the geographic place of the named party

Syntax Rules: 1. E0207 - Only one of N402 or N407 may be present.

2. C0605 - If N406 is present, then N405 is required.

3. C0704 - If N407 is present, then N404 is required.

Comments:

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.

Example: N4*LOS ANGELES*CA*90058~


N401 19 City Name Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code Description: Code (Standard State/Province)

as defined by appropriate government agency

X ID 2/2 Used

N403 116 Postal Code Description: Code defining international

postal zone code excluding punctuation and blanks (zip code for United States)

O ID 3/15 Used



PER Administrative Communications Contact

Pos: 3600 Max: >1

Heading - Optional

Loop: N1 Elements: 3 User Option (Usage): Used To identify a person or office to whom administrative communications should be directed

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.



Example: PER*ZZ**TE*2155551212~ PER*OC**AD*3055551234~

User Note: PER01 qualifier OC and PER03 qualifier AD will be used for special orders only.


PER01 366 Contact Function Code Description: Code identifying the major duty

or responsibility of the person or group named

M ID 2/2 Must use

Code Name

OC Order Contact

ZZ Mutually Defined

PER03 365 Communication Number Qualifier Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

AD Delivery Location Phone

TE Telephone

PER04 364 Communication Number Description: Complete communications

number including country or area code when applicable

X AN 1/10 Used



PO1 Baseline Item Data Pos: 0100 Max: 1

Detail - Mandatory

Loop: PO1 Elements: 13 User Option (Usage): Must use To specify basic and most frequently used line item data

Syntax Rules: 1. C0302 - If PO103 is present, then PO102 is required.

2. C0504 - If PO105 is present, then PO104 is required.

3. P0607 - If either PO106 or PO107 is present, then the other is required.










Comments:

1. See the Data Element Dictionary for a complete list of IDs.

2. PO101 is the line item identification.

3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Example: Standard Order - PO1*001*180*EA***BP*8006747*VP*PF52*UK*03666624066453~ Special Order - PO1*001*1*EA*****VP*PF52***TP*UMF*MD*01~

User Note: PO106/PO107 and PO110/PO111 not sent for special orders. PO112 thru PO115 not sent for standard orders.


PO101 350 Assigned Identification Description: Alphanumeric characters

assigned for differentiation within a transaction set

O AN 1/20 Used

PO102 330 Quantity Ordered Description: Quantity ordered

X R 1/15 Used

PO103 355 Unit or Basis for Measurement Code Description: Code specifying the units in

which a value is being expressed, or manner in which a measurement has been taken

O ID 2/2 Used

Code Name

EA Each

PO106 235 Product/Service ID Qualifier Description: Code identifying the

X ID 2/2 Used



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

Code Name

BP Buyer's Part Number

PO107 234 Product/Service ID Description: Identifying number for a product

or service

X AN 1/10 Used



X ID 2/2 Used

Code Name

VP Vendor's (Seller's) Part Number


or service

X AN 1/20 Used



X ID 2/2 Used

Code Name

UK EAN/UCC - 14

Description: Data structure for the 14 digit EAN.UCC (EAN

International.Uniform Code Council) Global Trade Identification Number (GTIN) PO111 234 Product/Service ID

Description: Identifying number for a product

or service

X AN 14/14 Used



X ID 2/2 Used

Code Name

TP Product Type Code


or service

X AN 1/48 Used



X ID 2/2 Used

Code Name

MD Method of Delivery Code


or service

X AN 1/48 Used

Code Name

01 Ships in 3 - 5 Business Days

02 Ships Next Business Day

03 Expedite - 24/48 Hour Guarantee

04 Two Day Air

05 International Ship

06 Your Truck

07 Pickup



PID Product/Item Description Pos: 0500 Max: 1

Detail - Optional

Loop: PID Elements: 2 User Option (Usage): Used To describe a product or process in coded or free-form format

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.

2. R0405 - At least one of PID04 or PID05 is required.

3. C0703 - If PID07 is present, then PID03 is required.



Semantics:

1. Use PID03 to indicate the organization that publishes the code list being referred to.

2. PID04 should be used for industry-specific product description codes.

3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.

4. PID09 is used to identify the language being used in PID05.

Comments:

1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.

3. PID07 specifies the individual code list of the agency specified in PID03.

Example: PID*F****PART DESCRIPTION~


PID01 349 Item Description Type Description: Code indicating the format of a

description

M ID 1/1 Must use

Code Name

F Free-form

PID05 352 Description Description: A free-form description to clarify

the related data elements and their content

X AN 1/25 Used



CTT Transaction Totals Pos: 0100 Max: 1

Summary - Optional

Loop: CTT Elements: 2 User Option (Usage): Used To transmit a hash total for a specific element in the transaction set

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.

2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments:

1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Example: CTT*5*90~


CTT01 354 Number of Line Items Description: Total number of line items in the

transaction set

M N0 1/6 Must use

CTT02 347 Hash Total Description: Sum of values of the specified

data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element. Example: -.0018 First occurrence of value being hashed. .18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence of value being hashed. --------- 1855 Hash Total User Note: Total Quantity in Line Items

O R 1/10 Used



SE Transaction Set Trailer Pos: 0300 Max: 1

Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Comments:

1. SE is the last segment of each transaction set.

Example: SE*15*001~


SE01 96 Number of Included Segments Description: Total number of segments

included in a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number Description: Identifying control number that


M AN 4/9 Must use



GE Functional Group Trailer Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of a functional group and to provide control information

Semantics:

1. 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:

1. 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.


GE01 97 Number of Transaction Sets Included Description: Total number of transaction

sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

M N0 1/6 Must use

GE02 28 Group Control Number Description: Assigned number originated


M N0 1/9 Must use



IEA Interchange Control Trailer Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments


IEA01 I16 Number of Included Functional Groups Description: A count of the number of

functional groups included in an interchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number Description: A control number assigned by


M N0 9/9 Must use

Purchase Order Acknowledgment - 855

855 Purchase Order Acknowledgment - v4030

X12/V4030/855

Version: 1.0 Final

Author: Inovis Publication: April 1, 2008

PepBoys855_4030_FINAL.ecs 1 Ver 1.0


Revision History

Date Version Revision Approved By April 1, 2008 1.0 Initial Publication Diane Pizzarelli



855 Purchase Order Acknowledgment Functional Group=PR

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership. User Note: PLEASE NOTE THAT IN 4030 THE ISA11 NO LONGER CONTAINS THE INTERCHANGE CONTROL STANDARDS IDENTIFIER. IT IS NOW USED TO IDENTIFY THE REPETITION SEPARATOR.

Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must use GS Functional Group Header M 1 Must use 0100 ST Transaction Set Header M 1 Must use 0200 BAK Beginning Segment for

Purchase Order Acknowledgment

M 1 Must use

LOOP ID - N1 200 3000 N1 Name O 1 Must use

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - PO1 100000 N2/0100L

0100 PO1 Baseline Item Data O 1 N2/0100 Must use LOOP ID - ACK 104

2700 ACK Line Item Acknowledgment O 1 Must use


Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - CTT 1 N3/0100L

0100 CTT Transaction Totals O 1 N3/0100 Must use 0300 SE Transaction Set Trailer M 1 Must use GE Functional Group Trailer M 1 Must use IEA Interchange Control Trailer M 1 Must use



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

L oop: N/A Elements: 16

User Option (Usage): Must use 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 ISA01 I01 Authorization Information Qualifier

Description: Code identifying the type of information in the Authorization Information

M ID 2/2 Must use

Code Name 00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information Description: Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier Description: Code identifying the type of information in the Security Information

M ID 2/2 Must use

Code Name 00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information Description: This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used.

M ID 2/2 Must use

ISA06 I06 Interchange Sender ID Description: Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use

Code Name 01 Duns (Dun & Bradstreet) ZZ Mutually Defined

ISA08 I07 Interchange Receiver ID M AN 15/15 Must use



Description: Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Pep Boys Production: 007914401


M DT 6/6 Must use


M TM 4/4 Must use

ISA11 I65 Repetition Separator Description: Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

M 1/1 Must use

ISA12 I11 Interchange Control Version Number Description: Code specifying the version number of the interchange control segments

M ID 5/5 Must use

Code Name 00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1999 ISA13 I12 Interchange Control Number

Description: A control number assigned by the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code indicating sender's request for an interchange acknowledgment All valid standard codes are used.

M ID 1/1 Must use

ISA15 I14 Usage Indicator Description: Code indicating whether data enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use

Code Name P Production Data T Test Data

ISA16 I15 Component Element Separator Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

M 1/1 Must use



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

L oop: N/A Elements: 8 User Option (Usage): Must use To indicate the beginning of a functional group and to provide control information Semantics:

1. GS04 is the group date. 2. GS05 is the group time. 3. 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:


Element Summary:

Ref Id Element Name Req Type Min/Max Usage GS01 479 Functional Identifier Code

Description: Code identifying a group of application related transaction sets

M ID 2/2 Must use

Code Name PR Purchase Order Acknowledgment (855)

GS02 142 Application Sender's Code Description: Code identifying party sending transmission; codes agreed to by trading partners

M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving transmission; codes agreed to by trading partners User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Pep Boys Production: 007914401

M AN 2/15 Must use

GS04 373 Date Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

M DT 8/8 Must use

GS05 337 Time Description: Time 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)

M TM 4/8 Must use

GS06 28 Group Control Number Description: Assigned number originated and maintained by the sender

M N0 1/9 Must use



GS07 455 Responsible Agency Code Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

M ID 1/2 Must use

Code Name X Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier CodeDescription: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

M AN 1/12 Must use

Code Name 004030 Draft Standards Approved for Publication by ASC X12 Procedures Review

Board through October 1999



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

L oop: N/A Elements: 2 User Option (Usage): Must use To indicate the start of a transaction set and to assign a control number Semantics:



Example: ST*855*0001~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a Transaction Set

M ID 3/3 Must use

Code Name 855 Purchase Order Acknowledgment

ST02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9 Must use



BAK Beginning Segment for Purchase Order Acknowledgment

Pos: 0200 Max: 1Heading - Mandatory

L oop: N/A Elements: 4

User Option (Usage): Must use To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates Semantics:

1. BAK04 is the date assigned by the purchaser to purchase order. 2. BAK08 is the seller's order number. 3. BAK09 is the date assigned by the sender to the acknowledgment.

Example: BAK*00*AC*1234567890*20080115~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage BAK01 353 Transaction Set Purpose Code

Description: Code identifying purpose of transaction set

M ID 2/2 Must use

Code Name 00 Original

BAK02 587 Acknowledgment Type Description: Code specifying the type of acknowledgment

M ID 2/2 Must use

Code Name AC Acknowledge - With Detail and Change

BAK03 324 Purchase Order Number Description: Identifying number for Purchase Order assigned by the orderer/purchaser

M AN 10/10 Must use

BAK04 373 Date Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

M DT 8/8 Must use



N1 Name Pos: 3000 Max: 1Heading - Optional

L oop: N1 Elements: 3 User Option (Usage): Must use To identify a party by type of organization, name, and code Syntax Rules:

1. R0203 - At least one of N102 or N103 is required. 2. P0304 - If either N103 or N104 is present, then the other is required.

Comments:


2. N105 and N106 further define the type of entity in N101. Example: N1*ST**ZZ*1234~ N1*VN**ZZ*000123456789~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage N101 98 Entity Identifier Code

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

M ID 2/3 Must use

Code Name ST Ship To VN Vendor

N103 66 Identification Code Qualifier Description: Code designating the system/method of code structure used for Identification Code (67)

X ID 1/2 Must use

Code Name ZZ Mutually Defined

N104 67 Identification Code Description: Code identifying a party or other code

X AN 4/12 Must use



PO1 Baseline Item Data Pos: 0100 Max: 1Detail - Optional

L oop: PO1 Elements: 8 User Option (Usage): Must use To specify basic and most frequently used line item data Syntax Rules:

1. C0302 - If PO103 is present, then PO102 is required. 2. C0504 - If PO105 is present, then PO104 is required. 3. P0607 - If either PO106 or PO107 is present, then the other is required. 4. P0809 - If either PO108 or PO109 is present, then the other is required. 5. P1011 - If either PO110 or PO111 is present, then the other is required. 6. P1213 - If either PO112 or PO113 is present, then the other is required. 7. P1415 - If either PO114 or PO115 is present, then the other is required. 8. P1617 - If either PO116 or PO117 is present, then the other is required. 9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required. 11. P2223 - If either PO122 or PO123 is present, then the other is required. 12. P2425 - If either PO124 or PO125 is present, then the other is required.

Comments:

1. See the Data Element Dictionary for a complete list of IDs. 2. PO101 is the line item identification. 3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU. Example: PO1*1*22****VP*9876543*MD*02*RR*123456~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage PO101 350 Assigned Identification

Description: Alphanumeric characters assigned for differentiation within a transaction set

O AN 1/20 Used

PO102 330 Quantity Ordered Description: Quantity ordered

X R 1/15 Must use

PO106 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name VP Vendor's (Seller's) Part Number

PO107 234 Product/Service ID Description: Identifying number for a product or service

X AN 1/15 Used

PO108 235 Product/Service ID Qualifier X ID 2/2 Used



Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Code Name MD Method of Delivery Code


X AN 1/48 Used

Code Name 01 Ships in 3 - 5 Business Days 02 Ships Next Business Day 03 Expedite - 24/48 Hour Guarantee 04 Two Day Air 05 International Ship 06 Your Truck 07 Pickup

PO110 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name RR Replacement Product Number


X AN 1/15 Used



ACK Line Item Acknowledgment Pos: 2700 Max: 1Detail - Optional

L oop: ACK Elements: 3 User Option (Usage): Must use To acknowledge the ordered quantities and specify the ready date for a specific line item Syntax Rules:

1. P0203 - If either ACK02 or ACK03 is present, then the other is required. 2. C0405 - If ACK04 is present, then ACK05 is required. 3. P0708 - If either ACK07 or ACK08 is present, then the other is required. 4. P0910 - If either ACK09 or ACK10 is present, then the other is required. 5. P1112 - If either ACK11 or ACK12 is present, then the other is required. 6. P1314 - If either ACK13 or ACK14 is present, then the other is required. 7. P1516 - If either ACK15 or ACK16 is present, then the other is required. 8. P1718 - If either ACK17 or ACK18 is present, then the other is required. 9. P1920 - If either ACK19 or ACK20 is present, then the other is required.

10. P2122 - If either ACK21 or ACK22 is present, then the other is required. 11. P2324 - If either ACK23 or ACK24 is present, then the other is required. 12. P2526 - If either ACK25 or ACK26 is present, then the other is required. 13. P2728 - If either ACK27 or ACK28 is present, then the other is required. 14. C282729 - If ACK28 is present, then ACK27 and ACK29 are required.

Semantics:

1. ACK29 Industry Reason Code may be used to identify the item status. In addition, it may be used in conjunction with ACK01 to further clarify the status.

Example: ACK*IA*15*EA~ ACK*IR*0*EA~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage ACK01 668 Line Item Status Code

Description: Code specifying the action taken by the seller on a line item requested by the buyer

M ID 2/2 Must use

Code Name IA Item Accepted IR Item Rejected

ACK02 380 Quantity Description: Numeric value of quantity User Note: If ACK01=IA, ACK02 should equal ordered quantity. If ACK01=IR, ACK02 should equal zero.

X R 1/15 Must use

ACK03 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

X ID 2/2 Must use

Code Name EA Each



N1 Name Pos: 3700 Max: 1Detail - Optional

L oop: N1 Elements: 3 User Option (Usage): Must use To identify a party by type of organization, name, and code Syntax Rules:

1. R0203 - At least one of N102 or N103 is required. 2. P0304 - If either N103 or N104 is present, then the other is required.

Comments:


2. N105 and N106 further define the type of entity in N101. Example: N1*MF**92*ABC~

Element Summary:



M ID 2/3 Must use

Code Name MF Manufacturer of Goods


X ID 1/2 Used

Code Name 92 Assigned by Buyer or Buyer's Agent


X AN 3/3 Used



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

L oop: CTT Elements: 1 User Option (Usage): Must use To transmit a hash total for a specific element in the transaction set Syntax Rules:

1. P0304 - If either CTT03 or CTT04 is present, then the other is required. 2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments:

1. This segment is intended to provide hash totals to validate transaction completeness and correctness. Example: CTT*4~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage CTT01 354 Number of Line Items

Description: Total number of line items in the transaction set

M N0 1/6 Must use



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

L oop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Comments:

1. SE is the last segment of each transaction set. Example: SE*11*0001~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage SE01 96 Number of Included Segments

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

M N0 1/10 Must use

SE02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9 Must use



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

L oop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of a functional group and to provide control information Semantics:


Comments:


Element Summary:

Ref Id Element Name Req Type Min/Max Usage GE01 97 Number of Transaction Sets Included

Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

M N0 1/6 Must use

GE02 28 Group Control Number Description: Assigned number originated and maintained by the sender

M N0 1/9 Must use



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

L oop: N/A Elements: 2 User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments Element Summary:

Ref Id Element Name Req Type Min/Max Usage IEA01 I16 Number of Included Functional Groups

Description: A count of the number of functional groups included in an interchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number Description: A control number assigned by the interchange sender

M N0 9/9 Must use



Sample 855 ISA*00* *00* *ZZ*YOURID *01*007914401 *080115*1450*^*00403*000000001*1*P*>~ GS*PR*YOURID*007914401*20080115*1450*000001*X*004030~ ST*855*0001~ BAK*00*AC*1234567890*20080115~ N1*ST**ZZ*1234~ N1*VN**ZZ*000123456789~ PO1*1*15****VP*9876543*MD*02*RR*123456~ ACK*IA*15*EA~ N1*MF**92*ABC~ CTT*1~ SE*9*0001~ GE*1*000001~ IEA*1*000000001~


Invoice - 810


810 Invoice - v4030

X12/V4030/810

Version: 1.1 Final

Author: Inovis

Publication: April 1, 2008

Modified: 04/23/2008

Invoice - 810


Revision History

Date Version Revision Approved By

April 1, 2008 1.0 Initial Publication Diane Pizzarelli

April 23, 2008 1.1 Added note to REF IA Diane Pizzarelli

Invoice - 810


810 Invoice

Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.

User Note: PLEASE NOTE THAT IN 4030 THE ISA11 NO LONGER CONTAINS THE INTERCHANGE CONTROL STANDARDS IDENTIFIER. IT IS NOW USED TO IDENTIFY THE REPETITION SEPARATOR.





0200 BIG Beginning Segment for Invoice

M 1 Must use

0500 REF Reference Identification O 12 Must use

LOOP ID - N1 200

0700 N1 Name O 1 Must use

1300 ITD Terms of Sale/Deferred Terms of Sale

O >1 Used

1500 FOB F.O.B. Related Instructions O 1 Used


LOOP ID - IT1 200000

0100 IT1 Baseline Item Data (Invoice) O 1 Must use

0400 TXI Tax Information O >1 Must use

LOOP ID - SAC >1

1800 SAC Service, Promotion, Allowance, or Charge Information

O 1 Used


0100 TDS Total Monetary Value Summary

M 1 Must use

0200 TXI Tax Information O >1 Used

LOOP ID - SAC >1

0400 SAC Service, Promotion, Allowance, or Charge Information

O 1 Used

LOOP ID - ISS >1

0600 ISS Invoice Shipment Summary O 1 Used

Invoice - 810


0700 CTT Transaction Totals O 1 N3/0700 Must use




Invoice - 810



Heading - Mandatory

Loop: N/A Elements: 16 User Option (Usage): Must use To start and identify an interchange of zero or more functional groups and interchange-related control segments


ISA01 I01 Authorization Information Qualifier Description: Code identifying the type of


M ID 2/2 Must use

Code Name


ISA02 I02 Authorization Information Description: Information used for additional

identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier Description: Code identifying the type of


M ID 2/2 Must use

Code Name


ISA04 I04 Security Information Description: This is used for identifying the

security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

M AN 10/10 Must use


system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used.

M ID 2/2 Must use

ISA06 I06 Interchange Sender ID Description: Identification code published by

the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

M AN 15/15 Must use


system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use

Code Name

01 Duns (Dun & Bradstreet)

ZZ Mutually Defined


Invoice - 810


Description: Identification code published by

the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401


M DT 6/6 Must use


M TM 4/4 Must use

ISA11 I65 Repetition Separator Description: Type is not applicable; the

repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

M 1/1 Must use

ISA12 I11 Interchange Control Version Number Description: Code specifying the version


M ID 5/5 Must use

Code Name

00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999

ISA13 I12 Interchange Control Number Description: A control number assigned by


M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code indicating sender's

request for an interchange acknowledgment All valid standard codes are used.

M ID 1/1 Must use

ISA15 I14 Usage Indicator Description: Code indicating whether data

enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use

Code Name

P Production Data

T Test Data

ISA16 I15 Component Element Separator Description: Type is not applicable; the

component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

M 1/1 Must use

Invoice - 810



Heading - Mandatory

Loop: N/A Elements: 8 User Option (Usage): Must use To indicate the beginning of a functional group and to provide control information

Semantics:

1. GS04 is the group date.


3. 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:



GS01 479 Functional Identifier Code Description: Code identifying a group of


M ID 2/2 Must use

Code Name

IN Invoice Information (810)

GS02 142 Application Sender's Code Description: Code identifying party sending

transmission; codes agreed to by trading partners

M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving

transmission; codes agreed to by trading partners User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401

M AN 2/15 Must use

GS04 373 Date Description: Date expressed as


M DT 8/8 Must use

GS05 337 Time Description: Time 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)

M TM 4/8 Must use

GS06 28 Group Control Number Description: Assigned number originated

M N0 1/9 Must use

Invoice - 810



GS07 455 Responsible Agency Code Description: Code identifying the issuer of

the standard; this code is used in conjunction with Data Element 480

M ID 1/2 Must use

Code Name


GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version,

release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

M AN 1/12 Must use

Code Name

004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

Invoice - 810



Heading - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the start of a transaction set and to assign a control number

Semantics:





ST01 143 Transaction Set Identifier Code Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

Code Name

810 Invoice

ST02 329 Transaction Set Control Number Description: Identifying control number that


M AN 4/9 Must use

Invoice - 810


BIG Beginning Segment for Invoice

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 4 User Option (Usage): Must use To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Semantics:

1. BIG01 is the invoice issue date.

2. BIG03 is the date assigned by the purchaser to purchase order.

3. BIG10 is the consolidated invoice number associated with the invoice identified in BIG02. When BIG07 contains code CI (Consolidated Invoice), BIG02 will contain the consolidated invoice number and BIG10 is not used.

Comments:

1. BIG07 is used only to further define the type of invoice when needed.

Example: BIG*20080215*123456789**N2726001***PR~


BIG01 373 Date Description: Date expressed as


M DT 8/8 Must use

BIG02 76 Invoice Number Description: Identifying number assigned by

issuer

M AN 1/22 Must use

BIG04 324 Purchase Order Number Description: Identifying number for Purchase

Order assigned by the orderer/purchaser

O AN 1/12 Must use

BIG07 640 Transaction Type Code Description: Code specifying the type of

transaction

O ID 2/2 Used

Code Name

PR Product (or Service)

Invoice - 810


REF Reference Identification Pos: 0500 Max: 12

Heading - Optional

Loop: N/A Elements: 2 User Option (Usage): Must use To specify identifying information


Semantics:


Example: REF*BM*25028001~ REF*IA*0033225100~

User Note: Two REF segments are required: one for Bill of Lading Number (BM) and one for Internal Vendor Number (IA).


REF01 128 Reference Identification Qualifier Description: Code qualifying the Reference

Identification

M ID 2/3 Must use

Code Name

BM Bill of Lading Number


User Note:

Vendor number assigned by Pep Boys REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or as specified by the Reference Identification Qualifier User Note: When REF01=IA, vendor number is comprised of first 7 digits from 850 REF IA followed by 100. The 810 REF IA must be 10 digits long and the final 3 digits are ‘100’.

X AN 1/12 Must use

Invoice - 810


N1 Name Pos: 0700 Max: 1

Heading - Optional

Loop: N1 Elements: 3 User Option (Usage): Must use To identify a party by type of organization, name, and code

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments:



Example: N1*ST**92*12345~


N101 98 Entity Identifier Code Description: Code identifying an

organizational entity, a physical location, property or an individual

M ID 2/3 Must use

Code Name

ST Ship To

N103 66 Identification Code Qualifier Description: Code designating the

system/method of code structure used for Identification Code (67)

X ID 1/2 Must use

Code Name

92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code Description: Code identifying a party or other

code

X AN 2/11 Must use

Invoice - 810


ITD Terms of Sale/Deferred Terms of Sale

Pos: 1300 Max: >1

Heading - Optional

Loop: N/A Elements: 9 User Option (Usage): Used To specify terms of sale

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.

2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.

3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics:

1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments:

1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.

User Note: Formats Accepted by Pep Boys: 1. XX% XX days (5% 30 Days) (use ITD 1,2,3,5) Example: ITD*08*15*5**30~ 2. XX% XXth Proxima (5% 15th proxima) (use ITD 1,2,3,13) *if delivery date is prior to the 25th of the month, payment is due by the XXth of the next month otherwise payment is due by the 15th of the following mth (Delivery mth+2) Example: ITD*09*1*5**********15~ 3. XX% XXth Proxima + XX Days (5% 15th proxima+30 days) (use ITD 1,2,3,5,13) *if delivery date is prior to the 25th of the month, payment is due by the XXth of the next month plus XX Days otherwise payment is due by the 15th of the following month(Delivery month+2) plus XX Days Example: ITD*09*8*5**30********15~ 4. Net XX Days (Net 30 Days) (use ITD 1,2,7. ITD11 optional) *a percent of invoice to-be-paid within XX days can be added to each ITD segment if needed(ITD11) 30 days 33%, 60 days 33%, 90 days 34%(total 100%) Example: ITD*05*2*****30****33~ ITD*05*2*****60****33~ ITD*05*2*****90****34~ 5. XX% XX Days, Net XX Days (5% 30 Days, Net 60 Days) (use ITD 1,2,3,5,7) Example: ITD*08*3*5**30**60~ 6. Net Date (Net 20080228) (use ITD 1,2,6) Example: ITD*05*4****20080228~ 7. XX% Date, Net Date (5% 20080301, Net 20080315) (use ITD 1,2,3,4,6) Example: ITD*08*4*5*20080301**20080315~

Invoice - 810


8. Installments - same as Net Date with % due added(Net 20080228 (xx%)) (use ITD 1,2,6,11) *a percent of invoice to-be-paid by the due date can be added to each ITD segment if needed(ITD-11) 20080228 33%, 20080328 33%, 20080428 34%(total 100%) Example: ITD*04*2****20080228*****33~ ITD*04*2****20080328*****33~ ITD*04*2****20080428*****34~


ITD01 336 Terms Type Code Description: Code identifying type of

payment terms

O ID 2/2 Must use

Code Name

04 Deferred or Installment

05 Discount Not Applicable

08 Basic Discount Offered

09 Proximo

ITD02 333 Terms Basis Date Code Description: Code identifying the beginning

of the terms period

O ID 1/2 Must use

Code Name

1 Ship Date

2 Delivery Date

3 Invoice Date

4 Specified Date

8 Invoice Transmission Date

15 Receipt of Goods

ITD03 338 Terms Discount Percent Description: Terms discount percentage,

expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

O R 1/6 Used

ITD04 370 Terms Discount Due Date Description: Date payment is due if discount

is to be earned expressed in format CCYYMMDD where CC represents the first two digits of the calendar year

X DT 8/8 Used

ITD05 351 Terms Discount Days Due Description: Number of days in the terms

discount period by which payment is due if terms discount is earned

X N0 1/3 Used

ITD06 446 Terms Net Due Date Description: Date when total invoice amount

becomes due expressed in format CCYYMMDD where CC represents the first two digits of the calendar year

O DT 8/8 Used

ITD07 386 Terms Net Days Description: Number of days until total

invoice amount is due (discount not applicable)

O N0 1/3 Used

ITD11 342 Percent of Invoice Payable Description: Amount of invoice payable

expressed in percent

X R 1/5 Used

ITD13 765 Day of Month Description: The numeric value of the day of

the month between 1 and the maximum day of the month being referenced

X N0 1/2 Used

Invoice - 810


FOB F.O.B. Related Instructions Pos: 1500 Max: 1

Heading - Optional

Loop: N/A Elements: 1 User Option (Usage): Used To specify transportation instructions relating to shipment

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.

2. C0405 - If FOB04 is present, then FOB05 is required.



Semantics:

1. FOB01 indicates which party will pay the carrier.

2. FOB02 is the code specifying transportation responsibility location.

3. FOB06 is the code specifying the title passage location.

4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.

Example: FOB*CC~


FOB01 146 Shipment Method of Payment Description: Code identifying payment terms

for transportation charges

M ID 2/2 Must use

Code Name

CC Collect

User Note:

Freight paid by Pep Boys PC Prepaid but Charged to Customer

User Note:

Vendor pays and bears freight, then bills Pep Boys PO Prepaid Only

User Note:

Vendor Pays freight, picks carrier, bears freight PP Prepaid (by Seller)

Description: Vendor pays freight, picks carrier TP Third Party Pay

Description: Outside party other than seller or recipient pays freight

Invoice - 810


IT1 Baseline Item Data (Invoice) Pos: 0100 Max: 1

Detail - Optional

Loop: IT1 Elements: 7 User Option (Usage): Must use To specify the basic and most frequently used line item data for the invoice and related transactions

Syntax Rules: 1. P020304 - If either IT102, IT103 or IT104 are present, then the others are required.

2. P0607 - If either IT106 or IT107 is present, then the other is required.










Semantics:

1. IT101 is the line item identification.

Comments:

1. Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs.

2. IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Example: IT1**5*EA*4.94**IN*8620482*VN*64102~

User Note: IT1 is positionally mapped. You MUST send the Buyer's Item Number (IN qualifier) in the IT106/07 pair and you MUST send the Vendor's Item Number (VN qualifier) in the IT108/09 qualifier. For special orders, if the Buyer's Item Number is not available the Vendor's Item Number may be used with both the IN and VN qualifiers.


IT102 358 Quantity Invoiced Description: Number of units invoiced

(supplier units)

X R 1/10 Must use

IT103 355 Unit or Basis for Measurement Code Description: Code specifying the units in


X ID 2/2 Must use

Code Name

EA Each

Invoice - 810


IT104 212 Unit Price Description: Price per unit of product,

service, commodity, etc.

X R 1/17 Must use

IT106 235 Product/Service ID Qualifier Description: Code identifying the


X ID 2/2 Must use

Code Name

IN Buyer's Item Number

IT107 234 Product/Service ID Description: Identifying number for a product

or service

X AN 1/48 Must use

IT108 235 Product/Service ID Qualifier Description: Code identifying the


X ID 2/2 Must use

Code Name

VN Vendor's (Seller's) Item Number

IT109 234 Product/Service ID Description: Identifying number for a product

or service

X AN 1/48 Must use

Invoice - 810


TXI Tax Information Pos: 0400 Max: >1

Detail - Optional

Loop: IT1 Elements: 2 User Option (Usage): Must use To specify tax information

Syntax Rules: 1. R020306 - At least one of TXI02, TXI03 or TXI06 is required.

2. P0405 - If either TXI04 or TXI05 is present, then the other is required.

3. C0803 - If TXI08 is present, then TXI03 is required.

Semantics:

1. TXI02 is the monetary amount of the tax.

2. TXI03 is the tax percent expressed as a decimal.

3. TXI07 is a code indicating the relationship of the price or amount to the associated segment.

Example: TXI*SA*150.12~


TXI01 963 Tax Type Code Description: Code specifying the type of tax

M ID 2/2 Must use

Code Name

EV Environmental Tax

User Note:

Fee per gallon on motor oils and petrochemicals FT Federal Excise Tax

User Note:

Federally mandated charges on specific items OH Other Taxes

User Note:

Use for disposal fees Use for tires

SA State or Provincial Fuel Tax

ZZ Mutually Defined

User Note:

Use for recycle tax TXI02 782 Monetary Amount

Description: Monetary amount X R 1/18 Must use

Invoice - 810


SAC Service, Promotion, Allowance, or Charge Information

Pos: 1800 Max: 1

Detail - Optional

Loop: SAC Elements: 5

User Option (Usage): Used To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.

2. P0304 - If either SAC03 or SAC04 is present, then the other is required.



5. C1110 - If SAC11 is present, then SAC10 is required.

6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.



Semantics:

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.

2. SAC05 is the total amount for the service, promotion, allowance, or charge.

3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

4. SAC08 is the allowance or charge rate per unit.

5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.

7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.

8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.

9. SAC16 is used to identify the language being used in SAC15.

Comments:

1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02.

2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.

Example: SAC*C*B750***995~


SAC01 248 Allowance or Charge Indicator M ID 1/1 Must use

Invoice - 810


Description: Code which indicates an

allowance or charge for the service specified

Code Name

C Charge

SAC02 1300 Service, Promotion, Allowance, or Charge Code Description: Code identifying the service,

promotion, allowance, or charge

X ID 4/4 Used

Code Name

B750 Core Charge

D240 Freight

User Note:

Charges associated with the transportation or movement of merchandise F050 Other (See related description)

User Note:

Racing H010 Special Buy

User Note:

Price reduction due to a special agreement between buyer and sales rep I430 Usage Plan Detail Charge

User Note:

Planogram ZZZZ Mutually Defined

User Note:

ECAT SAC05 610 Amount

Description: Monetary amount O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier Description: Code indicating on what basis

allowance or charge percent is calculated

X ID 1/1 Used

Code Name

3 Discount/Gross

SAC07 332 Percent Description: Percent expressed as a percent

X R 1/6 Used

Invoice - 810


TDS Total Monetary Value Summary

Pos: 0100 Max: 1

Summary - Mandatory

Loop: N/A Elements: 1 User Option (Usage): Must use To specify the total invoice discounts and amounts

Semantics:

1. TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).

2. TDS02 indicates the amount upon which the terms discount amount is calculated.

3. TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).

4. TDS04 indicates the total amount of terms discount.

Comments:

1. TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.

Example: TDS*16466851~


TDS01 610 Amount Description: Monetary amount

M N2 1/15 Must use

Invoice - 810


TXI Tax Information Pos: 0200 Max: >1

Summary - Optional

Loop: N/A Elements: 2 User Option (Usage): Used To specify tax information

Syntax Rules: 1. R020306 - At least one of TXI02, TXI03 or TXI06 is required.

2. P0405 - If either TXI04 or TXI05 is present, then the other is required.

3. C0803 - If TXI08 is present, then TXI03 is required.

Semantics:

1. TXI02 is the monetary amount of the tax.

2. TXI03 is the tax percent expressed as a decimal.

3. TXI07 is a code indicating the relationship of the price or amount to the associated segment.

Example: TXI*SA*150.12~


TXI01 963 Tax Type Code Description: Code specifying the type of tax

M ID 2/2 Must use

Code Name

EV Environmental Tax

User Note:

Fee per gallon on motor oils and petrochemicals FT Federal Excise Tax

User Note:

Federally mandated charges on specific items OH Other Taxes

User Note:

Use for disposal fees Use for tires

SA State or Provincial Fuel Tax

ZZ Mutually Defined

User Note:

Use for recycle tax TXI02 782 Monetary Amount

Description: Monetary amount X R 1/18 Used

Invoice - 810


SAC Service, Promotion, Allowance, or Charge Information

Pos: 0400 Max: 1

Summary - Optional

Loop: SAC Elements: 5

User Option (Usage): Used To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.





6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.



Semantics:

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.

2. SAC05 is the total amount for the service, promotion, allowance, or charge.

3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

4. SAC08 is the allowance or charge rate per unit.

5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.

7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.

8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.

9. SAC16 is used to identify the language being used in SAC15.

Comments:

1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02.

2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.

Example: SAC*C*B750***995~ SAC*A*A260****3*.25~


SAC01 248 Allowance or Charge Indicator M ID 1/1 Must use

Invoice - 810


Description: Code which indicates an

allowance or charge for the service specified

Code Name

A Allowance

C Charge

SAC02 1300 Service, Promotion, Allowance, or Charge Code Description: Code identifying the service,

promotion, allowance, or charge

X ID 4/4 Used

Code Name

A260 Advertising Allowance

B210 Co-op Credit

User Note:

Agreed $ amount that manufacturer will reimburse Pep Boys for advertising expenses

B750 Core Charge

C000 Defective Allowance

User Note:

Price reduction for merchandise not reasonably safe for use C300 Discount - Special

User Note:

Manager's Meeting C320 Display Allowance

D240 Freight

User Note:

Charges associated with the transportation or movement of merchandise E730 New Item Allowance

User Note:

Price reduction for carrying a new product E740 New Store Allowance

User Note:

Price reduction for opening a new store and stocking specific products F050 Other (See related description)

User Note:

Racing F670 Price and Marketing Allowance

User Note:

Enhanced Marketing Initiative F970 Rebate

User Note:

Refund resulting from purchase or tax G220 Racing Support Initiative

User Note:

Racing Support Initiative H010 Special Buy

User Note:

Price reduction due to a special agreement between buyer and sales rep I170 Trade Discount

User Note:

Producer discount given to Pep Boys as a promotional effort I430 Usage Plan Detail Charge

User Note:

Planogram I530 Volume Discount

User Note:

Invoice - 810


Price reduction in $ or % based on the quantity of goods purchased ZZZZ Mutually Defined

User Note:

ECAT SAC05 610 Amount

Description: Monetary amount O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier Description: Code indicating on what basis

allowance or charge percent is calculated

X ID 1/1 Used

Code Name

3 Discount/Gross

SAC07 332 Percent Description: Percent expressed as a percent

X R 1/6 Used

Invoice - 810


ISS Invoice Shipment Summary Pos: 0600 Max: 1

Summary - Optional

Loop: ISS Elements: 2 User Option (Usage): Used To specify summary details of total items shipped in terms of quantity, weight, and volume

Syntax Rules: 1. R010305 - At least one of ISS01, ISS03 or ISS05 is required.

2. P0102 - If either ISS01 or ISS02 is present, then the other is required.



Semantics:

1. ISS07 is the quantity of third party pallets.

2. ISS08 is the gross weight of third party pallets in pounds.

Example: ISS***27341.00*PN~


ISS03 81 Weight Description: Numeric value of weight

X R 1/10 Used

ISS04 355 Unit or Basis for Measurement Code Description: Code specifying the units in


X ID 2/2 Used

Code Name

PN Pounds Net

Invoice - 810



Summary - Optional

Loop: N/A Elements: 1 User Option (Usage): Must use To transmit a hash total for a specific element in the transaction set

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.

2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments:


Example: CTT*26~


CTT01 354 Number of Line Items Description: Total number of line items in the

transaction set

M N0 1/6 Must use

Invoice - 810



Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Comments:


Example: SE*223*1709~


SE01 96 Number of Included Segments Description: Total number of segments

included in a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number Description: Identifying control number that


M AN 4/9 Must use

Invoice - 810


GE Functional Group Trailer Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of a functional group and to provide control information

Semantics:


Comments:



GE01 97 Number of Transaction Sets Included Description: Total number of transaction

sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

M N0 1/6 Must use

GE02 28 Group Control Number Description: Assigned number originated


M N0 1/9 Must use

Invoice - 810


IEA Interchange Control Trailer Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2 User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments


IEA01 I16 Number of Included Functional Groups Description: A count of the number of

functional groups included in an interchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number Description: A control number assigned by


M N0 9/9 Must use

Invoice - 810


Sample 810 ISA*00* *00* *ZZ*YOURID *01*007914401 *080115*1450*^*00403*000000001*1*P*>~ GS*IN*YOURID*007914401*20080115*1450*000001*X*004030~ ST*810*1709~ BIG*20080215*123456789**N2726001***PR~ REF*BM*25028001~ REF*IA*0033225100~ N1*ST**92*12345~ ITD*08*15*5**30~ FOB*CC~ IT1**5*EA*4.94**IN*8620482*VN*64102~ TXI*SA*150.12~ SAC*C*B750***995~ TDS*2470~ ISS***27341.00*PN~ CTT*1~ SE*14*1709~ GE*1*000001~ IEA*1*000000001~

X12V4030

Inventory Inquiry/Advice-846

1

846 Inventory Inquiry/Advice

X12/V4030/846 : 846 Inventory Inquiry/Advice

2/6/2012

SPECIAL NOTE FOR PEPBOYS TRADING PARTNERS:

This transaction must be sent nightly, before 2am, 7 days a week.

X12V4030


2


Functional Group=IB

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice

Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be

used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser,

with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to

supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for

an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.






020 BIA Beginning Segment for

Inventory Inquiry/Advice

M 1 Must use



LOOP ID - LIN 10000

010 LIN Item Identification M 1 Must use

030 PID Product/Item Description O 200 Must use

LOOP ID - SLN 1000

280 SLN Subline Item Detail O 1 Must use

LOOP ID - QTY 99

320 QTY Quantity O 1 Must use






Notes: 3/010 Number of line items (CTT01) is the accumulation of number of LIN segments.

X12V4030


3


Mandatory

Loop: N/A Elements: 16

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


ISA01 I01 Authorization Information Qualifier

Description: Code to identify the type of


M ID 2/2 Must use

Code Name


ISA02 I02 Authorization Information

Description: Information used for additional

identification or authorization of the

interchange sender or the data in the

interchange; the type of information is set by

the Authorization Information Qualifier (I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier



M ID 2/2 Must use

Code Name


ISA04 I04 Security Information

Description: This is used for identifying the

security information about the interchange

sender or the data in the interchange; the type

of information is set by the Security

Information Qualifier (I03)

M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier

Description: Qualifier to designate the


designate the sender or receiver ID element

being qualified

M ID 2/2 Must use

ISA06 I06 Interchange Sender ID


the sender for other parties to use as the

receiver ID to route data to them; the sender

always codes this value in the sender ID

element

M AN 15/15 Must use





being qualified

M ID 2/2 Must use


ISA08 I07 Interchange Receiver ID


the receiver of the data; When sending, it is

used by the sender as their sending ID, thus

M AN 15/15 Must use

X12V4030


4

other parties sending to them will use this as a

receiving ID to route data to them

User Note:

Inovis Test: CLPEPBOYS

Pep Boys Test: 007914401T

Production: 007914401

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


M 1/1 Must use

ISA12 I11 Interchange Control Version Number

Description: Code specifying the version


M ID 5/5 Must use

Code Name

00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1999

ISA13 I12 Interchange Control Number

Description: A control number assigned by the

interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested

Description: Code sent by the sender to

request an interchange acknowledgment (TA1)

M ID 1/1 Must use

All valid standard codes are used.

ISA15 I14 Usage Indicator

Description: Code to indicate whether data

enclosed by this interchange envelope is test,

production or information

M ID 1/1 Must use

Code Name

P Production Data

T Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; the

component element separator is a delimiter and

not a data element; this field provides the

delimiter used to separate component data

elements within a composite data structure; this

value must be different than the data element

separator and the segment terminator

M 1/1 Must use

X12V4030


5


Mandatory


User Option (Usage): Must use Purpose: To indicate the beginning of a functional group and to provide control information


GS01 479 Functional Identifier Code

Description: Code identifying a group of


M ID 2/2 Must use

Code Name

IB Inventory Inquiry/Advice (846)

GS02 142 Application Sender's Code

Description: Code identifying party sending

transmission; codes agreed to by trading

partners

M AN 2/15 Must use

GS03 124 Application Receiver's Code

Description: Code identifying party receiving


partners

M AN 2/15 Must use

User Note:




GS04 373 Date

Description: Date expressed as CCYYMMDD

M DT 8/8 Must use

GS05 337 Time

Description: Time 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)

M TM 4/8 Must use

GS06 28 Group Control Number

Description: Assigned number originated and

maintained by the sender

M N0 1/9 Must use

GS07 455 Responsible Agency Code

Description: Code identifying the issuer of the

standard; this code is used in conjunction with

Data Element 480

M ID 1/2 Must use

Code Name


GS08 480 Version / Release / Industry Identifier Code

Description: Code indicating the version,

release, subrelease, and industry identifier of

the EDI standard being used, including the GS

and GE segments; if code in DE455 in GS

segment is X, then in DE 480 positions 1-3 are

M AN 1/12 Must use

X12V4030


6

the version number; positions 4-6 are the

release and subrelease, level of the version; and

positions 7-12 are the industry or trade

association identifiers (optionally assigned by

user); if code in DE455 in GS segment is T,

then other formats are allowed

Code Name

004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board

through October 1999

Semantics: 1. GS04 is the group date.


3. 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: 1. 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.

X12V4030


7


Heading - Mandatory


User Option (Usage): Must use

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


ST01 143 Transaction Set Identifier Code M ID 3/3 Must use


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

Code Name


ST02 329 Transaction Set Control Number M AN 4/9 Must use

Description: Identifying control number that must be unique within the transaction set functional

group assigned by the originator for a transaction set

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate

transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Example: ST*846*0001

X12V4030


8

BIA Beginning Segment for


Pos: 020 Max: 1

Heading - Mandatory



Purpose: To indicate the beginning of an Inventory Inquiry/Advice Transaction Set


BIA01 353 Transaction Set Purpose Code M ID 2/2 Must use



Code Name

08 Status

BIA02 755 Report Type Code M ID 2/2 Must use

Description: Code indicating the title or contents of a document, report or supporting item


Code Name

DD Distributor Inventory Report

BIA03 127 Reference Identification M AN 1/30 Must use

Description: Reference information as defined for a particular Transaction Set or as specified by the

Reference Identification Qualifier

BIA04 373 Date M DT 8/8 Must use


Semantics: 1. BIA03 identifies the number of the inquiry/advice that is transferred.

2. BIA04 identifies the date of the inquiry/advice that is transferred.

3. BIA05 identifies the time of the inquiry/advice that is transferred.

Example: BIA*08*DD*3920394930203*20110106

X12V4030


9


Heading - Optional


User Option (Usage): Must use Purpose: To specify identifying information


REF01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification


Code Name


REF02 127 Reference Identification X AN 1/30 Must use



Example: REF*IA*0123456789

Note: This REF02 is the Pepboys Vendor Number that will be provided by Pepboys to the supplier prior to testing.

X12V4030


10

Loop Item Identification Pos: 010 Repeat: 10000

Mandatory

Loop: LIN Elements: N/A


Purpose: To specify basic item identification data

Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage



280 Loop SLN O 1000 Must use

320 Loop QTY O 99 Must use

X12V4030


11

LIN Item Identification Pos: 010 Max: 1

Detail - Mandatory

Loop: LIN Elements: 4




LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use

Code Name


LIN03 234 Product/Service ID M AN 1/48 Must use

Description: Mfg Part Number

LIN04 235 Product/Service ID Qualifier X ID 2/2 Used

Code Name


LIN05 234 Product/Service ID X AN 1/48 Used

Description: PBY Code

Example: LIN**VN*MFG Part Number*TP*ABC

Note: The LIN05 Represents the PBY Code which will be provided by Pepboys prior to testing

X12V4030


12


Detail - Optional



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


PID01 349 Item Description Type M ID 1/1 Must use

Description: Code indicating the format of a description


Code Name

F Free-form

PID05 352 Description X AN 1/80 Must use

Description: A free-form description to clarify the related data elements and their content

Example: PID*F****Part Description

X12V4030


13

Loop Subline Item Detail Pos: 280 Repeat: 1000

Optional

Loop: SLN Elements: N/A

User Option (Usage): Used

Purpose: To specify product subline detail item data



X12V4030


14

SLN Subline Item Detail Pos: 280 Max: 1

Detail - Optional

Loop: SLN Elements: 4




SLN01 350 Assigned Identification M AN 1/20 Must use


SLN03 662 Relationship Code M ID 1/1 Must use

Description: Code indicating the relationship between entities

Code Name

O Information Only

SLN04 380 Quantity X R 1/15 Must use

Description: Numeric value of quantity

SLN05 C001 Composite Unit of Measure X Comp Must use

Description: To identify a composite unit of measure(See Figures Appendix for examples of use)

SLN05-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use

Description: Code specifying the units in which a value is being expressed, or manner in which a

measurement has been taken

Code Name

PK Package This code is used to identify Pack Quantity

PH Package This code is used to identify Repack Quantity

Example: SLN*1**O*10*PK SLN*2**O*5*PH

Note:

There should be 2 SLN segments for each line item, one to report “Pack Qty” and one to report “Repack Qty”. If both quantities are not available, please send 1 and 1for the quantities in the SLN04 segments.

X12V4030


15

Loop Quantity Pos: 320 Repeat: 99

Optional

Loop: QTY Elements: N/A


Purpose: To specify quantity information



X12V4030


16

QTY Quantity Pos: 320 Max: 1

Detail - Optional

Loop: QTY Elements: 3

User Option (Usage): Must use Purpose: To specify quantity information


QTY01 673 Quantity Qualifier M ID 2/2 Must use

Description: Code specifying the type of quantity

Code Name

33 Quantity Available for Sale (stock quantity)

QTY02 380 Quantity X R 1/15 Must use


QTY03 C001 Composite Unit of Measure O Comp Must use


QTY03-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use



Code Name

EA Each

Example: QTY*33*123*EA

Note: The QOH must be in eaches

X12V4030


17


Summary - Optional



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


CTT01 354 Number of Line Items M N0 1/6 Must use


Example: CTT*10

X12V4030


18


Summary - Mandatory



Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning

(ST) and ending (SE) segments)


SE01 96 Number of Included Segments M N0 1/10 Must use


SE02 329 Transaction Set Control Number M AN 4/9 Must use



Example: SE*10*0001

X12V4030


19

SAMPLE 846

ST*846*1820

BIA*08*DD*PEP123456789*20101206

REF*IA*0123456789

LIN**VN*ABC1234*TP*ABC

PID*F****PART1DESCRIPTION

SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*24*EA

LIN**VN*234-5678*TP*ABC


SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*53*EA

LIN**VN*XYZ-789*TP*ABC


SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*15*EA

CTT*3

SE*20*1820

Ship Notice/Manifest - 856

1 Ver 1.7

856 Ship Notice/Manifest - v4030

X12/V4030/856

Version: 1.7

Author: GXS Publication: April 1, 2008 Modified: March 19, 2012


2 Ver 1.7

Revision History

Date Version Revision Approved By April 1, 2008 1.0 Initial Publication Diane Pizzarelli

October 20, 2008 1.1 Changed description of data associated with UK qualifier (LIN)

Diane Pizzarelli

May 15, 2009 1.2 Changed MAN02 min/max Paul Heidler

December 8, 2011 1.4 Modified User notes on the REF, TD3, and LIN segments

Diane Pizzarelli

December 19, 2011 1.5 Modified User notes on the N104 and LIN segments

Diane Pizzarelli

March 2, 2012 1.6 Modified User notes on the REF segment

Diane Pizzarelli

March 19, 2012 1.7

Corrected examples, added Special Order example, clarified user notes for the N1, and LIN segments.

Diane Pizzarelli


3 Ver 1.7

856 Ship Notice/Manifest Functional Group=SH

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/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 additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.


Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must use GS Functional Group Header M 1 Must use 010 ST Transaction Set Header M 1 Must use 020 BSN Beginning Segment for Ship

Notice M 1 Must use


LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 030 SN1 Item Detail (Shipment) O 1 Used 110 TD1 Carrier Details (Quantity and

Weight) O 20 Must use

120 TD5 Carrier Details (Routing Sequence/Transit Time)

O 12 Used

LOOP ID - TD3 12 1300 TD3 Carrier Details (Equipment) O 1 Used 150 REF Reference Identification O >1 Must use 200 DTM Date/Time Reference O 10 Must use


LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 050 PRF Purchase Order Reference M 1 Must use

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 190 MAN Marks and Numbers O >1 Must use

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 CN2/010 Must use 020 LIN Item Identification M 1 Must use


4 Ver 1.7

030 SN1 Item Detail (Shipment) M 1 Must use 060 PO4 Item Physical Details O 1 Must use 070 PID Product/Item Description O 200 Must use 110 TD1 Carrier Details (Quantity and


Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 CTT Transaction Totals O 1 Must use 020 SE Transaction Set Trailer M 1 Must use GE Functional Group Trailer M 1 Must use IEA Interchange Control Trailer M 1 Must use


5 Ver 1.7

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


User Option (Usage): Must use 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 ISA01 I01 Authorization Information Qualifier

Description: Code identifying the type of information in the Authorization Information

M ID 2/2 Must use



M AN 10/10 Must use

ISA03 I03 Security Information Qualifier Description: Code identifying the type of information in the Security Information

M ID 2/2 Must use



M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used.

M ID 2/2 Must use


M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use




6 Ver 1.7

Description: Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401


M DT 6/6 Must use


M TM 4/4 Must use


M 1/1 Must use


M ID 5/5 Must use

Code Name 00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1999 ISA13 I12 Interchange Control Number

Description: A control number assigned by the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code indicating sender's request for an interchange acknowledgment All valid standard codes are used.

M ID 1/1 Must use

ISA15 I14 Usage Indicator Description: Code indicating whether data enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use



M 1/1 Must use


7 Ver 1.7

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


User Option (Usage): Must use To indicate the beginning of a functional group and to provide control information

Semantics:


associated functional group trailer, GE02.

Comments:


Element Summary:

Ref Id Element Name Req Type Min/Max Usage GS01 479 Functional Identifier Code


M ID 2/2 Must use

Code Name SH Ship Notice/Manifest (856)


M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving transmission; codes agreed to by trading partners User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401

M AN 2/15 Must use

GS04 373 Date Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

M DT 8/8 Must use

GS05 337 Time Description: Time 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)

M TM 4/8 Must use

GS06 28 Group Control Number Description: Assigned number originated and maintained by the sender

M N0 1/9 Must use


8 Ver 1.7


M ID 1/2 Must use


GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

M AN 1/12 Must use


Board through October 1999


9 Ver 1.7

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


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

Semantics:

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).


Element Summary:



M ID 3/3 Must use

Code Name 856 Ship Notice/Manifest


M AN 4/9 Must use


10 Ver 1.7

BSN Beginning Segment for Ship Notice

Pos: 020 Max: 1 Heading - Mandatory


User Option (Usage): Must use To transmit identifying numbers, dates, and other basic data relating to the transaction set

Syntax Rules: 1. C0706 - If BSN07 is present, then BSN06 is required.

Semantics:

1. BSN03 is the date the shipment transaction set is created. 2. BSN04 is the time the shipment transaction set is created. 3. BSN06 is limited to shipment related codes.

Comments:

1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Example: BSN*00*1828458823*20080201*1454*0001~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage BSN01 353 Transaction Set Purpose Code


M ID 2/2 Must use


BSN02 396 Shipment Identification Description: A unique control number assigned by the original shipper to identify a specific shipment

M AN 2/30 Must use

BSN03 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8 Must use

BSN04 337 Time Description: Time 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)

M TM 4/4 Must use

BSN05 1005 Hierarchical Structure Code Description: Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

M ID 4/4 Must use

Code Name 0001 Shipment, Order, Packaging, Item


11 Ver 1.7

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

Loop: HL Elements: 2

User Option (Usage): Must use To identify dependencies among and the content of hierarchically related groups of data segments

Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure. 3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Example: HL*1**S~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage HL01 628 Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

M AN 1/12 Must use

HL03 735 Hierarchical Level Code Description: Code defining the characteristic of a level in a hierarchical structure

M ID 1/2 Must use

Code Name S Shipment


12 Ver 1.7

SN1 Item Detail (Shipment) Pos: 030 Max: 1 Detail - Optional


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

Syntax Rules: 1. P0506 - If either SN105 or SN106 is present, then the other is required.

Semantics:

1. SN101 is the ship notice line-item identification.

Comments:

1. SN103 defines the unit of measurement for both SN102 and SN104.

Example: SN1**9*EA~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage SN102 382 Number of Units Shipped

Description: Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set User Note: Must equal the sum of all SN102s at Item Level.

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

M ID 2/2 Must use

Code Name EA Each


13 Ver 1.7

TD1 Carrier Details (Quantity and Weight)

Pos: 110 Max: 20 Detail - Optional


User Option (Usage): Must use To specify the transportation details relative to commodity, weight, and quantity

Syntax Rules: 1. C0102 - If TD101 is present, then TD102 is required. 2. C0304 - If TD103 is present, then TD104 is required. 3. C0607 - If TD106 is present, then TD107 is required. 4. P0708 - If either TD107 or TD108 is present, then the other is required. 5. P0910 - If either TD109 or TD110 is present, then the other is required.

Example: TD1**1****G*30*LB~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TD102 80 Lading Quantity

Description: Number of units (pieces) of the lading commodity User Note: Must equal total number of MAN segments at the Pack Level

X N0 1/7 Must use

TD106 187 Weight Qualifier Description: Code defining the type of weight

O ID 1/2 Must use

Code Name G Gross Weight

TD107 81 Weight Description: Numeric value of weight

X R 1/10 Must use

TD108 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

X ID 2/2 Must use

Code Name LB Pound


14 Ver 1.7

TD5 Carrier Details (Routing Sequence/Transit Time)



User Option (Usage): Used To specify the carrier and sequence of routing and provide transit time information

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required. 2. C0203 - If TD502 is present, then TD503 is required. 3. C0708 - If TD507 is present, then TD508 is required. 4. C1011 - If TD510 is present, then TD511 is required. 5. C1312 - If TD513 is present, then TD512 is required. 6. C1413 - If TD514 is present, then TD513 is required. 7. C1512 - If TD515 is present, then TD512 is required.

Semantics:

1. TD515 is the country where the service is to be performed.

Comments:

1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.

Example: TD5**2*WATK~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TD502 66 Identification Code Qualifier

Description: Code designating the system/method of code structure used for Identification Code (67)

M ID 1/2 Must use

Code Name 2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code Description: Code identifying a party or other code

X AN 2/10 Must use


15 Ver 1.7

TD3 Carrier Details (Equipment) Pos: 1300 Max: 1 Detail - Optional

Loop: TD3 Elements: 2

User Option (Usage): Used To specify transportation details relating to the equipment used by the carrier

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present. 2. C0203 - If TD302 is present, then TD303 is required. 3. C0405 - If TD304 is present, then TD305 is required. 4. P0506 - If either TD305 or TD306 is present, then the other is required.

Example: TD3*TL**12345678~

User Note: This segment is not required for Special Order shipments.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TD301 40 Equipment Description Code

Description: Code identifying type of equipment used for shipment

X ID 2/2 Must use

Code Name TL Trailer (not otherwise specified)

TD303 207 Equipment Number Description: Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

X AN 1/10 Must use


16 Ver 1.7

REF Reference Identification Pos: 150 Max: >1 Detail - Optional


User Option (Usage): Must use To specify identifying information


Semantics:


Example: REF*BM*1234567890~ REF*CN*12345ABCDE6789ZZZ

User Note: Bill of Lading Number (BM) is required. Carrier's Ref Number (CN) is required for special orders only. It is the tracking # provided by the carrier. Packing List Number (PK) is optional.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage REF01 128 Reference Identification Qualifier


M ID 2/3 Must use

Code Name BM Bill of Lading Number CN Carrier's Reference Number (PRO/Invoice) PK Packing List Number

REF02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

X AN 1/30 Must use


17 Ver 1.7

DTM Date/Time Reference Pos: 200 Max: 10 Detail - Optional


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

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required. 2. C0403 - If DTM04 is present, then DTM03 is required. 3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Example: DTM*011*20080215~ DTM*371*20080220~

User Note: Shipped Date (011) is required. Current Schedule Delivery Date (067) is optional. Estimated Arrival Date (371) is required.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage DTM01 374 Date/Time Qualifier

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

M ID 3/3 Must use

Code Name 011 Shipped 067 Current Schedule Delivery 371 Estimated Arrival Date

DTM02 373 Date Description: Date expressed as CCYYMMDD

X DT 8/8 Must use


18 Ver 1.7

N1 Name Pos: 220 Max: 1 Detail - Optional

Loop: N1 Elements: 3

User Option (Usage): Must use To identify a party by type of organization, name, and code

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

Comments:



Example: N1*ST**92*14026~ 0r N1*ST**92*0766~

User Note:

For Regular Order ASNs, this will be the 5-digit Distribution Center location code sent on the Purchase Order. For Special Order ASNs, this will be the 4-digit store number location code sent on the Purchase Order.

Element Summary:



M ID 2/3 Must u

Code Name ST Ship To


X ID 1/2 Must use



X AN 4/5 Must use


19 Ver 1.7




Example: HL*2*1*O~

Element Summary:



M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

M AN 1/12 Must use


M ID 1/2 Must use

Code Name O Order


20 Ver 1.7

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


User Option (Usage): Must use To provide reference to a specific purchase order

Semantics:

1. PRF04 is the date assigned by the purchaser to purchase order.

Example: PRF*S3482451~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage PRF01 324 Purchase Order Number

Description: Identifying number for Purchase Order assigned by the orderer/purchaser

M AN 1/22 Must use


21 Ver 1.7




Example: HL*3*2*P~

Element Summary:



M AN 1/12 Must use


O AN 1/12 Must use


M ID 1/2 Must use

Code Name P Pack


22 Ver 1.7

MAN Marks and Numbers Pos: 190 Max: >1 Detail - Optional


User Option (Usage): Must use To indicate identifying marks and numbers for shipping containers

Syntax Rules: 1. C0605 - If MAN06 is present, then MAN05 is required. 2. P0405 - If either MAN04 or MAN05 is present, then the other is required.

Semantics:

1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.

2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.

3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.

Example: MAN*GM*00000079405300190343~ Or MAN*AA*000079405300190343~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage MAN01 88 Marks and Numbers Qualifier

Description: Code specifying the application or source of Marks and Numbers (87)

M ID 1/2 Must use

Code Name AA SSCC-18 GM SSCC-18 and Application Identifier

MAN02 87 Marks and Numbers Description: Marks and numbers used to identify a shipment or parts of a shipment

M AN 18/20 Must use


23 Ver 1.7




Element Summary:



M AN 1/12 Must use


O AN 1/12 Must use


M ID 1/2 Must use

Code Name I Item


24 Ver 1.7

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


User Option (Usage): Must use To specify basic item identification data

Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required. 2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

Example: LIN**UK*00794053018326*IN*8400211*MF*33968209~

User Note: The UPC and Buyers Item Number are not required for Special Order shipments The Manufacturer’s Number is required for Special Order shipments. (This will be the item number sent on the special order 850 with a ‘VP’ qualifier.)

Element Summary:

Ref Id Element Name Req Type Min/Max Usage LIN02 235 Product/Service ID Qualifier


M ID 2/2 Used

Code Name UK 14-digit UPC/EAN Code

Description: Pep Boys expects 12-digit UPC with 2 leading zeroes.

User Note: Not required for Special Order shipments.

LIN03 234 Product/Service ID Description: Identifying number for a product or service

M AN 14/14 Used

LIN04 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name IN Buyer's Item Number



X AN 8/8 Used


X ID 2/2 Used

Code Name MF Manufacturer

User Note: Manufacturers number required

for Special Order shipments.


X AN 1/15 Used


25 Ver 1.7

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


User Option (Usage): Must use To specify line-item detail relative to shipment


Semantics:


Example: SN1**9*EA~

Element Summary:


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

M R 1/10 Must use


M ID 2/2 Must use

Code Name EA Each


26 Ver 1.7

PO4 Item Physical Details Pos: 060 Max: 1 Detail - Optional


User Option (Usage): Must use To specify the physical qualities, packaging, weights, and dimensions relating to the item

Syntax Rules: 1. C0506 - If PO405 is present, then PO406 is required. 2. C1013 - If PO410 is present, then PO413 is required. 3. C1113 - If PO411 is present, then PO413 is required. 4. C1213 - If PO412 is present, then PO413 is required. 5. C1716 - If PO417 is present, then PO416 is required. 6. C1804 - If PO418 is present, then PO404 is required. 7. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required. 8. P0203 - If either PO402 or PO403 is present, then the other is required. 9. P0607 - If either PO406 or PO407 is present, then the other is required.


Semantics:

1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of packaging. Relative Position 1 (value R1) is the innermost package.

2. PO416 is the package identifier or the beginning package identifier in a range of identifiers. 3. PO417 is the ending package identifier in a range of identifiers. 4. PO418 is the number of packages in this layer.

Example: PO4*3~

User Note: Item level PO401 must equal item level SN102 divided by item level TD102. (Replenishment shipments only)

Element Summary:

Ref Id Element Name Req Type Min/Max Usage PO401 356 Pack

Description: The number of inner containers, or number of eaches if there are no inner containers, per outer container

O N0 1/6 Used


27 Ver 1.7

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


User Option (Usage): Must use To describe a product or process in coded or free-form format

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required. 2. C0703 - If PID07 is present, then PID03 is required. 3. C0804 - If PID08 is present, then PID04 is required. 4. C0905 - If PID09 is present, then PID05 is required. 5. R0405 - At least one of PID04 or PID05 is required.

Semantics:

1. Use PID03 to indicate the organization that publishes the code list being referred to. 2. PID04 should be used for industry-specific product description codes. 3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified

attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate. 4. PID09 is used to identify the language being used in PID05.


Element Summary:

Ref Id Element Name Req Type Min/Max Usage PID01 349 Item Description Type


M ID 1/1 Must use

Code Name F Free-form

PID05 352 Description Description: A free-form description to clarify the related data elements and their content

X AN 1/80 Must use


28 Ver 1.7







Element Summary:


Description: Number of units (pieces) of the lading commodity

X N0 1/7 Must use


O ID 1/2 Must use



X R 1/10 Must use


X ID 2/2 Must use

Code Name LB Pound


29 Ver 1.7

CTT Transaction Totals Pos: 010 Max: 1 Summary - Optional


User Option (Usage): Must use To transmit a hash total for a specific element in the transaction set

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required. 2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments:


Example: CTT*25~

Element Summary:



M N0 1/6 Must use


30 Ver 1.7

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


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

Comments:



Element Summary:



M N0 1/10 Must use


M AN 4/9 Must use


31 Ver 1.7

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


User Option (Usage): Must use To indicate the end of a functional group and to provide control information

Semantics:


Comments:


Element Summary:



M N0 1/6 Must use


M N0 1/9 Must use


32 Ver 1.7

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


User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary:



M N0 1/5 Must use


M N0 9/9 Must use


33 Ver 1.7

Sample 856 – Regular Order ISA*00* *00* *ZZ*YOURID *01*007914401 *080201*1454*^*00403*000000001*1*P*>~ GS*SH*YOURID*007914401*20080201*1454*000001*X*004030~ ST*856*0001~ BSN*00*1828458823*20080201*1454*0001~ HL*1**S~ SN1**18*EA~ TD1**1****G*60*LB~ TD5**2*WATK~ TD3*TL**12345678~ REF*BM*1234567890~ DTM*011*20080215~ DTM*371*20080220~ N1*ST**92*14011~ HL*2*1*O~ PRF*Y3482451~ HL*3*2*P~ MAN*GM*00000079405300190343~ HL*4*3*I LIN**UK*00794053018326*IN*84002115*MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART A~ TD1**3****G*10*LB~ HL*5*3*I~ LIN**UK*00794053018490*IN*84002146*MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART B~ TD1**3****G*10*LB~ CTT*2~ SE*29*0001~ GE*1*000001~ IEA*1*000000001~


34 Ver 1.7

Sample 856 – Special Order ISA*00* *00* *ZZ*YOURID *01*007914401 *080201*1454*^*00403*000000001*1*P*>~ GS*SH*YOURID*007914401*20080201*1454*000001*X*004030~ ST*856*0001~ BSN*00*1828458823*20080201*1454*0001~ HL*1**S~ SN1**18*EA~ TD1**1****G*20*LB~ TD5**2*WATK~ REF*BM*1234567890~ REF*CN*12345ABCDE6789ZZZ~ DTM*011*20080215~ DTM*371*20080220~ N1*ST**92*0766~ HL*2*1*O~ PRF*S3482451~ HL*3*2*P~ MAN*GM*00000079405300190343~ HL*4*3*I LIN******MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART A~ TD1**3****G*10*LB~ HL*5*3*I~ LIN******MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART B~ TD1**3****G*10*LB~ CTT*2~ SE*29*0001~ GE*1*000001~ IEA*1*000000001~

New Special Order QOH and ASN Mapping Guidelines for

Existing 4010 Version Vendors.

X12V4010 Inventory Inquiry/Advice - 846 Inventory Inquiry/Advice - 846

1


X12/V4010/846 : 846 Inventory Inquiry/Advice

2/6/2012

SPECIAL NOTE FOR PEPBOYS TRADING PARTNERS:

This transaction must be sent nightly, before 2am, 7 days a week.


2


Functional Group=IB

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice

Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be

used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser,

with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to

supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for

an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.





020 BIA Beginning Segment for


M 1 Must use



LOOP ID - LIN 10000



LOOP ID - SLN 1000


LOOP ID - QTY 99







Notes: 3/010 Number of line items (CTT01) is the accumulation of number of LIN segments.


3


Mandatory




ISA01 I01 Authorization Information Qualifier



M ID 2/2 Must use

Code Name


ISA02 I02 Authorization Information

Description: Information used for additional

identification or authorization of the

interchange sender or the data in the

interchange; the type of information is set by

the Authorization Information Qualifier (I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier



M ID 2/2 Must use

Code Name


ISA04 I04 Security Information

Description: This is used for identifying the

security information about the interchange

sender or the data in the interchange; the type

of information is set by the Security

Information Qualifier (I03)

M AN 10/10 Must use





being qualified

M ID 2/2 Must use

ISA06 I06 Interchange Sender ID


the sender for other parties to use as the

receiver ID to route data to them; the sender

always codes this value in the sender ID

element

M AN 15/15 Must use





being qualified

M ID 2/2 Must use


ISA08 I07 Interchange Receiver ID


the receiver of the data; When sending, it is

used by the sender as their sending ID, thus

other parties sending to them will use this as a

receiving ID to route data to them

M AN 15/15 Must use


4

User Note:




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 I10 Interchange Control Standards Identifier

Description: Code to identify the agency

responsible for the control standard used by the

message that is enclosed by the interchange

header and trailer

M ID 1/1 Must use

ISA12 I11 Interchange Control Version Number

Description: Code specifying the version


M ID 5/5 Must use

Code Name

00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1997

ISA13 I12 Interchange Control Number

Description: A control number assigned by the

interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested

Description: Code sent by the sender to

request an interchange acknowledgment (TA1)

M ID 1/1 Must use


ISA15 I14 Usage Indicator

Description: Code to indicate whether data

enclosed by this interchange envelope is test,

production or information

M ID 1/1 Must use

Code Name

P Production Data

T Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; the

component element separator is a delimiter and

not a data element; this field provides the

delimiter used to separate component data

elements within a composite data structure; this

value must be different than the data element

separator and the segment terminator

M 1/1 Must use


5


Mandatory




GS01 479 Functional Identifier Code

Description: Code identifying a group of


M ID 2/2 Must use

Code Name

IB Inventory Inquiry/Advice (846)

GS02 142 Application Sender's Code

Description: Code identifying party sending


partners

M AN 2/15 Must use

GS03 124 Application Receiver's Code

Description: Code identifying party receiving


partners

M AN 2/15 Must use

User Note:




GS04 373 Date


M DT 8/8 Must use

GS05 337 Time

Description: Time 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)

M TM 4/8 Must use

GS06 28 Group Control Number

Description: Assigned number originated and

maintained by the sender

M N0 1/9 Must use

GS07 455 Responsible Agency Code

Description: Code identifying the issuer of the

standard; this code is used in conjunction with

Data Element 480

M ID 1/2 Must use

Code Name


GS08 480 Version / Release / Industry Identifier Code

Description: Code indicating the version,

release, subrelease, and industry identifier of

the EDI standard being used, including the GS

and GE segments; if code in DE455 in GS

segment is X, then in DE 480 positions 1-3 are

the version number; positions 4-6 are the

M AN 1/12 Must use


6

release and subrelease, level of the version; and

positions 7-12 are the industry or trade

association identifiers (optionally assigned by

user); if code in DE455 in GS segment is T,

then other formats are allowed

Code Name

004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board

through October 1997

Semantics: 1. GS04 is the group date.


3. 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: 1. 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.


7


Heading - Mandatory



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


ST01 143 Transaction Set Identifier Code M ID 3/3 Must use



Code Name


ST02 329 Transaction Set Control Number M AN 4/9 Must use



Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate

transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Example: ST*846*0001


8

BIA Beginning Segment for


Pos: 020 Max: 1

Heading - Mandatory



Purpose: To indicate the beginning of an Inventory Inquiry/Advice Transaction Set


BIA01 353 Transaction Set Purpose Code M ID 2/2 Must use



Code Name

08 Status

BIA02 755 Report Type Code M ID 2/2 Must use

Description: Code indicating the title or contents of a document, report or supporting item


Code Name

DD Distributor Inventory Report

BIA03 127 Reference Identification M AN 1/30 Must use



BIA04 373 Date M DT 8/8 Must use


Semantics: 1. BIA03 identifies the number of the inquiry/advice that is transferred.

2. BIA04 identifies the date of the inquiry/advice that is transferred.

3. BIA05 identifies the time of the inquiry/advice that is transferred.

Example: BIA*08*DD*3920394930203*20110106


9


Heading - Optional


User Option (Usage): Must use Purpose: To specify identifying information


REF01 128 Reference Identification Qualifier M ID 2/3 Must use



Code Name


REF02 127 Reference Identification X AN 1/30 Must use



Example: REF*IA*0123456789

Note: This REF02 is the Pepboys Vendor Number that will be provided by Pepboys to the supplier prior to testing.


10

Loop Item Identification Pos: 010 Repeat: 10000

Mandatory

Loop: LIN Elements: N/A






280 Loop SLN O 1000 Must use

320 Loop QTY O 99 Must use


11

LIN Item Identification Pos: 010 Max: 1

Detail - Mandatory





LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use

Code Name


LIN03 234 Product/Service ID M AN 1/48 Must use

Description: Mfg Part Number

LIN04 235 Product/Service ID Qualifier X ID 2/2 Used

Code Name


LIN05 234 Product/Service ID X AN 1/48 Used

Description: PBY Code

Example: LIN**VN*MFG Part Number*TP*ABC

Note: The LIN05 Represents the PBY Code which will be provided by Pepboys prior to testing


12


Detail - Optional



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


PID01 349 Item Description Type M ID 1/1 Must use



Code Name

F Free-form

PID05 352 Description X AN 1/80 Must use

Description: A free-form description to clarify the related data elements and their content

Example: PID*F****Part Description


13

Loop Subline Item Detail Pos: 280 Repeat: 1000

Optional

Loop: SLN Elements: N/A

User Option (Usage): Used





14

SLN Subline Item Detail Pos: 280 Max: 1

Detail - Optional

Loop: SLN Elements: 4




SLN01 350 Assigned Identification M AN 1/20 Must use


SLN03 662 Relationship Code M ID 1/1 Must use

Description: Code indicating the relationship between entities

Code Name

O Information Only

SLN04 380 Quantity X R 1/15 Must use


SLN05 C001 Composite Unit of Measure X Comp Must use


SLN05-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use



Code Name

PK Package This code is used to identify Pack Quantity

PH Package This code is used to identify Repack Quantity

Example: SLN*1**O*10*PK SLN*2**O*5*PH

Note:

There should be 2 SLN segments for each line item, one to report “Pack Qty” and one to report “Repack Qty”. If both quantities are not available, please send 1 and 1 for the quantities in the SLN04 segments.


15

Loop Quantity Pos: 320 Repeat: 99

Optional

Loop: QTY Elements: N/A


Purpose: To specify quantity information




16

QTY Quantity Pos: 320 Max: 1

Detail - Optional

Loop: QTY Elements: 3

User Option (Usage): Must use Purpose: To specify quantity information


QTY01 673 Quantity Qualifier M ID 2/2 Must use

Description: Code specifying the type of quantity

Code Name

33 Quantity Available for Sale (stock quantity)

QTY02 380 Quantity X R 1/15 Must use


QTY03 C001 Composite Unit of Measure O Comp Must use


QTY03-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use



Code Name

EA Each

Example: QTY*33*123*EA

Note: The QOH must be in eaches


17


Summary - Optional



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


CTT01 354 Number of Line Items M N0 1/6 Must use


Example: CTT*10


18


Summary - Mandatory



Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning

(ST) and ending (SE) segments)


SE01 96 Number of Included Segments M N0 1/10 Must use


SE02 329 Transaction Set Control Number M AN 4/9 Must use



Example: SE*10*0001


19

SAMPLE 846

ST*846*1820

BIA*08*DD*PEP123456789*20101206

REF*IA*0123456789

LIN**VN*ABC1234*TP*ABC


SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*24*EA

LIN**VN*234-5678*TP*ABC


SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*53*EA

LIN**VN*XYZ-789*TP*ABC


SLN*1**O*1*PK

SLN*2**O*1*PH

QTY*33*15*EA

CTT*3

SE*20*1820


1 Ver 1.7

856 Ship Notice/Manifest - v4010

X12/V4010/856

Version: 1.7

Author: GXS Publication: April 1, 2008 Modified: March 19, 2012


2 Ver 1.7

856 Ship Notice/Manifest Functional Group=SH

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/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 additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must use GS Functional Group Header M 1 Must use 010 ST Transaction Set Header M 1 Must use 020 BSN Beginning Segment for Ship

Notice M 1 Must use


LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 030 SN1 Item Detail (Shipment) O 1 Used 110 TD1 Carrier Details (Quantity and

Weight) O 20

120 TD5 Carrier Details (Routing Sequence/Transit Time)

O 12 Must use

LOOP ID - TD3 12 1300 TD3 Carrier Details (Equipment) O 1 Used 150 REF Reference Identification O >1 Must use 200 DTM Date/Time Reference O 10 Must use


LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 050 PRF Purchase Order Reference M 1 Must use

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 C2/010 Must use 190 MAN Marks and Numbers O >1 Must use


3 Ver 1.7

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level M 1 CN2/010 Must use 020 LIN Item Identification M 1 Must use 030 SN1 Item Detail (Shipment) M 1 Must use 060 PO4 Item Physical Details O 1 Must use 070 PID Product/Item Description O 200 Must use 110 TD1 Carrier Details (Quantity and


Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 CTT Transaction Totals O 1 Must use 020 SE Transaction Set Trailer M 1 Must use GE Functional Group Trailer M 1 Must use IEA Interchange Control Trailer M 1 Must use


4 Ver 1.7

ISA Interchange Control Header Pos: Max: 1 Mandatory



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

Description: Code to identify the type of information in the Authorization Information

M ID 2/2 Must use



M AN 10/10 Must use

ISA03 I03 Security Information Qualifier Description: Code to identify the type of information in the Security Information

M ID 2/2 Must use



M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use


M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

M ID 2/2 Must use


ISA08 I07 Interchange Receiver ID Description: Identification code published by the receiver of the data; When sending,

M AN 15/15 Must use


5 Ver 1.7

it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401


M DT 6/6 Must use

ISA10 I09 Interchange TimeDescription: Time of the interchange

M TM 4/4 Must use

ISA11 I10 Interchange Control Standards IdentifierDescription: Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

M ID 1/1 Must use


M ID 5/5 Must use

Code Name 00401 Draft Standards for Trial Use Approved for Publication by ASC X12

Procedures Review Board through October 1997

ISA13 I12 Interchange Control Number Description: A control number assigned by the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code sent by the sender to request an interchange acknowledgment (TA1)

M ID 1/1 Must use


ISA15 I14 Usage Indicator Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use



M 1/1 Must use


6 Ver 1.7

GS Functional Group Header Pos: Max: 1 Mandatory



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


M ID 2/2 Must use

Code Name SH Ship Notice/Manifest (856)


M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving transmission; codes agreed to by trading partners

M AN 2/15 Must use

User Note: Inovis Test: CLPEPBOYS Pep Boys Test: 007914401T Production: 007914401

GS04 373 DateDescription: Date expressed as CCYYMMDD

M DT 8/8 Must use

GS05 337 TimeDescription: Time 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)

M TM 4/8 Must use

GS06 28 Group Control NumberDescription: Assigned number originated and maintained by the sender

M N0 1/9 Must use


M ID 1/2 Must use


GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in

M AN 1/12 Must use


7 Ver 1.7

DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed


Board through October 1997 Semantics:


associated functional group trailer, GE02.

Comments: 1. 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.


8 Ver 1.7

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


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

Semantics:

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).


Element Summary:



M ID 3/3 Must use

Code Name 856 Ship Notice/Manifest


M AN 4/9 Must use


9 Ver 1.7

BSN Beginning Segment for Ship Notice

Pos: 020 Max: 1 Heading - Mandatory


User Option (Usage): Must use To transmit identifying numbers, dates, and other basic data relating to the transaction set

Syntax Rules: 1. C0706 - If BSN07 is present, then BSN06 is required.

Semantics:

1. BSN03 is the date the shipment transaction set is created. 2. BSN04 is the time the shipment transaction set is created. 3. BSN06 is limited to shipment related codes.

Comments:

1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Example: BSN*00*1828458823*20080201*1454*0001~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage BSN01 353 Transaction Set Purpose Code


M ID 2/2 Must use


BSN02 396 Shipment Identification Description: A unique control number assigned by the original shipper to identify a specific shipment

M AN 2/30 Must use

BSN03 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8 Must use

BSN04 337 Time Description: Time 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)

M TM 4/4 Must use

BSN05 1005 Hierarchical Structure Code Description: Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

M ID 4/4 Must use

Code Name 0001 Shipment, Order, Packaging, Item


10 Ver 1.7




Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure. 3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Example: HL*1**S~

Element Summary:



M AN 1/12 Must use


M ID 1/2 Must use

Code Name S Shipment


11 Ver 1.7

SN1 Item Detail (Shipment) Pos: 030 Max: 1 Detail - Optional


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


Semantics:


Comments:

1. SN103 defines the unit of measurement for both SN102 and SN104.

Example: SN1**9*EA~

Element Summary:


Description: Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set User Note: Must equal the sum of all SN102s at Item Level.

M R 1/10 Used


M ID 2/2 Used

Code Name EA Each


12 Ver 1.7







Element Summary:


Description: Number of units (pieces) of the lading commodity User Note: Must equal total number of MAN segments at the Pack Level

X N0 1/7 Must use


O ID 1/2 Must use



X R 1/10 Must use


X ID 2/2 Must use

Code Name LB Pound


13 Ver 1.7

TD5 Carrier Details (Routing Sequence/Transit Time)



User Option (Usage): Used To specify the carrier and sequence of routing and provide transit time information

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required. 2. C0203 - If TD502 is present, then TD503 is required. 3. C0708 - If TD507 is present, then TD508 is required. 4. C1011 - If TD510 is present, then TD511 is required. 5. C1312 - If TD513 is present, then TD512 is required. 6. C1413 - If TD514 is present, then TD513 is required. 7. C1512 - If TD515 is present, then TD512 is required.

Semantics:

1. TD515 is the country where the service is to be performed.

Comments:

1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.

Example: TD5**2*WATK~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TD502 66 Identification Code Qualifier

Description: Code designating the system/method of code structure used for Identification Code (67)

M ID 1/2 Must use

Code Name 2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code Description: Code identifying a party or other code

X AN 2/10 Must use


14 Ver 1.7

TD3 Carrier Details (Equipment) Pos: 1300 Max: 1 Detail - Optional

Loop: TD3 Elements: 2

User Option (Usage): Used To specify transportation details relating to the equipment used by the carrier

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present. 2. C0203 - If TD302 is present, then TD303 is required. 3. C0405 - If TD304 is present, then TD305 is required. 4. P0506 - If either TD305 or TD306 is present, then the other is required.

Example: TD3*TL**12345678~

User Note: This segment is not required for Special Order shipments.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TD301 40 Equipment Description Code

Description: Code identifying type of equipment used for shipment

X ID 2/2 Used

Code Name TL Trailer (not otherwise specified)

TD303 207 Equipment Number Description: Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

X AN 1/10 Used


15 Ver 1.7

REF Reference Identification Pos: 150 Max: >1 Detail - Optional


User Option (Usage): Must use To specify identifying information


Semantics:


Example: REF*BM*1234567890~ REF*CN*12345ABCDE6789ZZZ

User Note: Bill of Lading Number (BM) is required. Carrier's Ref Number (CN) is required for special orders only. It is the tracking number provided by the carrier. Packing List Number (PK) is optional.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage REF01 128 Reference Identification Qualifier


M ID 2/3 Must use

Code Name BM Bill of Lading Number CN Carrier's Reference Number (PRO/Invoice) PK Packing List Number

REF02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

X AN 1/30 Must use


16 Ver 1.7

DTM Date/Time Reference Pos: 200 Max: 10 Detail - Optional


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

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required. 2. C0403 - If DTM04 is present, then DTM03 is required. 3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Example: DTM*011*20080215~ DTM*371*20080220~

User Note: Shipped Date (011) is required. Current Schedule Delivery Date (067) is optional. Estimated Arrival Date (371) is required.

Element Summary:

Ref Id Element Name Req Type Min/Max Usage DTM01 374 Date/Time Qualifier

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

M ID 3/3 Must use

Code Name 011 Shipped 067 Current Schedule Delivery 371 Estimated Arrival Date

DTM02 373 Date Description: Date expressed as CCYYMMDD

X DT 8/8 Must use


17 Ver 1.7

N1 Name Pos: 220 Max: 1 Detail - Optional

Loop: N1 Elements: 3

User Option (Usage): Must use To identify a party by type of organization, name, and code

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

Comments:



Example: N1*ST**92*14026~ 0r N1*ST**92*0766~

User Note:

For Regular Order ASNs, this will be the 5-digit Distribution Center location code sent on the Purchase Order. For Special Order ASNs, this will be the 4-digit store number location code sent on the Purchase Order.

Element Summary:



M ID 2/3 Must use

Code Name ST Ship To


X ID 1/2 Must use



X AN 4/5 Must use


18 Ver 1.7




Example: HL*2*1*O~

Element Summary:



M AN 1/12 Must use


M AN 1/12 Must use


M ID 1/2 Must use

Code Name O Order


19 Ver 1.7

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


User Option (Usage): Must use To provide reference to a specific purchase order

Semantics:

1. PRF04 is the date assigned by the purchaser to purchase order.

Example: PRF*S3482451~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage PRF01 324 Purchase Order Number

Description: Identifying number for Purchase Order assigned by the orderer/purchaser

M AN 1/22 Must use


20 Ver 1.7




Example: HL*3*2*P~

Element Summary:



M AN 1/12 Must use


O AN 1/12 Must use


M ID 1/2 Must use

Code Name P Pack


21 Ver 1.7

MAN Marks and Numbers Pos: 190 Max: >1 Detail - Optional


User Option (Usage): Must use To indicate identifying marks and numbers for shipping containers

Syntax Rules: 1. C0605 - If MAN06 is present, then MAN05 is required. 2. P0405 - If either MAN04 or MAN05 is present, then the other is required.

Semantics:

1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.

2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.

3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.

Example: MAN*GM*00000079405300190343~ Or MAN*AA*000079405300190343~

Element Summary:

Ref Id Element Name Req Type Min/Max Usage MAN01 88 Marks and Numbers Qualifier

Description: Code specifying the application or source of Marks and Numbers (87)

M ID 1/2 Must use

Code Name AA SSCC-18 GM SSCC-18 and Application Identifier

MAN02 87 Marks and Numbers Description: Marks and numbers used to identify a shipment or parts of a shipment

M AN 18/20 Must use


22 Ver 1.7




Element Summary:



M AN 1/12 Must use


O AN 1/12 Must use


M ID 1/2 Must use

Code Name I Item


23 Ver 1.7

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


User Option (Usage): Must use To specify basic item identification data

Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required. 2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

Semantics:

1. LIN01 is the line item identification

Example: LIN**UP*794053018326*IN*8400211*MF*33968209~

User Note: The UPC and Buyers Item Number are not required for Special Order shipments The Manufacturer’s Number is required for Special Order shipments. (This will be the item number sent on the special order 850 with a ‘VP’ qualifier.)

Element Summary:

Ref Id Element Name Req Type Min/Max Usage LIN02 235 Product/Service ID Qualifier


M ID 2/2 Used

Code Name UP 12-digit UPC Code

Description: Pep Boys expects 12-digit UPC



M AN 14/14 Used


X ID 2/2 Used

Code Name IN Buyer's Item Number



X AN 8/8 Used


X ID 2/2 Used

Code Name


24 Ver 1.7

MF Manufacturer User Note: Manufacturers number required

for Special Order shipments.


X AN 1/15 Used


25 Ver 1.7

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


User Option (Usage): Must use To specify line-item detail relative to shipment


Semantics:


Example: SN1**9*EA~

Element Summary:


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

M R 1/10 Must use


M ID 2/2 Must use

Code Name EA Each


26 Ver 1.7

PO4 Item Physical Details Pos: 060 Max: 1 Detail - Optional


User Option (Usage): Must use To specify the physical qualities, packaging, weights, and dimensions relating to the item

Syntax Rules: 1. C0506 - If PO405 is present, then PO406 is required. 2. C1013 - If PO410 is present, then PO413 is required. 3. C1113 - If PO411 is present, then PO413 is required. 4. C1213 - If PO412 is present, then PO413 is required. 5. C1716 - If PO417 is present, then PO416 is required. 6. C1804 - If PO418 is present, then PO404 is required. 7. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required. 8. P0203 - If either PO402 or PO403 is present, then the other is required. 9. P0607 - If either PO406 or PO407 is present, then the other is required.


Semantics:

1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of packaging. Relative Position 1 (value R1) is the innermost package.

2. PO416 is the package identifier or the beginning package identifier in a range of identifiers. 3. PO417 is the ending package identifier in a range of identifiers. 4. PO418 is the number of packages in this layer.

Example: PO4*3~

User Note: Item level PO401 must equal item level SN102 divided by item level TD102. (Replenishment shipments only)

Element Summary:

Ref Id Element Name Req Type Min/Max Usage PO401 356 Pack

Description: The number of inner containers, or number of eaches if there are no inner containers, per outer container

O N0 1/6 Must use


27 Ver 1.7

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


User Option (Usage): Must use To describe a product or process in coded or free-form format

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required. 2. C0703 - If PID07 is present, then PID03 is required. 3. C0804 - If PID08 is present, then PID04 is required. 4. C0905 - If PID09 is present, then PID05 is required. 5. R0405 - At least one of PID04 or PID05 is required.

Semantics:

1. Use PID03 to indicate the organization that publishes the code list being referred to. 2. PID04 should be used for industry-specific product description codes. 3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified

attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate. 4. PID09 is used to identify the language being used in PID05.


Element Summary:

Ref Id Element Name Req Type Min/Max Usage PID01 349 Item Description Type


M ID 1/1 Must use

Code Name F Free-form

PID05 352 Description Description: A free-form description to clarify the related data elements and their content

X AN 1/80 Must use


28 Ver 1.7







Element Summary:


Description: Number of units (pieces) of the lading commodity

X N0 1/7 Must use


O ID 1/2 Must use



X R 1/10 Must use


X ID 2/2 Must use

Code Name LB Pound


29 Ver 1.7

CTT Transaction Totals Pos: 010 Max: 1 Summary - Optional


User Option (Usage): Must use To transmit a hash total for a specific element in the transaction set

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required. 2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments:


Example: CTT*25~

Element Summary:



M N0 1/6 Must use


30 Ver 1.7

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


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

Comments:



Element Summary:



M N0 1/10 Must use


M AN 4/9 Must use


31 Ver 1.7

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


User Option (Usage): Must use To indicate the end of a functional group and to provide control information

Semantics:


Comments:


Element Summary:



M N0 1/6 Must use


M N0 1/9 Must use


32 Ver 1.7

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


User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary:



M N0 1/5 Must use


M N0 9/9 Must use


33 Ver 1.7

Sample 856 – Regular Order ISA*00* *00* *ZZ*YOURID *01*007914401 *080201*1454*U*00401*000000001*1*P*>~ GS*SH*YOURID*007914401*20080201*1454*000001*X*004010~ ST*856*0001~ BSN*00*1828458823*20080201*1454*0001~ HL*1**S~ SN1**18*EA~ TD1**1****G*20*LB~ TD5**2*WATK~ TD3*TL**12345678~ REF*BM*1234567890~ DTM*011*20080215~ DTM*371*20080220~ N1*ST**92*14011~ HL*2*1*O~ PRF*Y3482451~ HL*3*2*P~ MAN*GM*00000079405300190343~ HL*4*3*I LIN**UP*794053018326*IN*84002115*MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART A~ TD1**3****G*10*LB~ HL*5*3*I~ LIN**UP*794053018490*IN*84002146*MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART B~ TD1**3****G*10*LB~ CTT*2~ SE*29*0001~ GE*1*000001~ IEA*1*000000001~


34 Ver 1.7

Sample 856 – Special Order ISA*00* *00* *ZZ*YOURID *01*007914401 *080201*1454*U*00401*000000001*1*P*>~ GS*SH*YOURID*007914401*20080201*1454*000001*X*004010~ ST*856*0001~ BSN*00*1828458823*20080201*1454*0001~ HL*1**S~ SN1**18*EA~ TD1**1****G*20*LB~ TD5**2*WATK~ REF*BM*1234567890~ REF*CN*12345ABCDE6789ZZZ~ DTM*011*20080215~ DTM*371*20080220~ N1*ST**92*0766~ HL*2*1*O~ PRF*S3482451~ HL*3*2*P~ MAN*GM*00000079405300190343~ HL*4*3*I LIN******MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART A~ TD1**3****G*10*LB~ HL*5*3*I~ LIN******MF*33968209~ SN1**9*EA~ PO4*3~ PID*F****PART B~ TD1**3****G*10*LB~ CTT*2~ SE*29*0001~ GE*1*000001~ IEA*1*000000001~

time and cost savings - pep boysadded the method of delivery code in the po1 segment. in addition,...

Documents