inovis catalogue 832 (v4010) batch guide for vendors catalog...the inovis catalogue edi 832 batch...

Inovis Catalogue™

832 (v4010) Batch Guide for VendorsJuly 2007

ii Inovis Catalogue™ 832 (v4010) Batch Guide

Inovis11720 AmberPark DriveAlpharetta, Georgia 30004tel +1 877.446.6847www.inovis.com

Inovis Catalogue™ 832 (v4010) Batch Guide for VendorsDocument Release Date: 15 June 2007Software Release: 4.12.5Product Support: U.S.A—1.877.446.6847 (1.877.4INOVIS); EMEA—1+44 (0)1483 569388

Copyright © 2007 Inovis, Inc. All rights reserved.

InovisTM, the Inovis logo, Inovis CatalogueTM, Retail Web FormsTM, BizManagerTM, and InovisworksTM are all trademarks of Inovis, Inc.

TrustedLink®, TrustedLink® Enterprise, TrustedLink®iSeries, and TrustedLink® Windows are registered trademarks of Inovis, Inc.

All other trademarks and registered trademarks are the property of their respective owners.

The names of companies and individuals used in any sample database or as examples in the documentation are fictitious and illustrate the use of the software, only. Any resemblance to actual companies or individuals, whether past or present, is purely coincidental.

This document and the related software described in this manual are supplied under license or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. The information in this document is subject to change without notice and does not represent a commitment on the part of Inovis

This document may contain examples of data screens or reports or other descriptions or examples which use the names of individuals, companies, brands, categories, products and/or product codes. All of these names and codes are fictitious, and any similarity to the names and codes used by an actual person or entity is entirely coincidental.

U.S. Government Users: This documentation and any software it describes are "commercial items" as that term is defined in 48 C.F.R. 2.101 and successor regulations, consisting of "commercial computer software documentation", "documentation related to commercial computer software" or "commercial computer software" as such terms are used in 48 C.F.R. 12.212 and 48 C.F.R. 252.227-7014(a)(1) and their successor regulations. Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 252.227-7202-1 through 227.7202-4 and their successor regulations, all U.S. Government users, agencies and contractors acquire this documentation and the software to which it relates with only those rights described in this paragraph.

iii

Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Accessing Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Installing Acrobat Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Retailers and Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

1 OverviewStages of the Batch Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Batch Interface System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Inovis Catalogue Batch Interface Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6File Formats Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Customer Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Electronic Mailbox Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Production Mailbox Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Test Mailbox Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Catalogue Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7GTIN Type and Package Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Email Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Sample Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Online Correction of Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2 ValidationTransaction Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11EDI Standards Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Translation, Data Validation, and Data Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Data Validation and Data Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Types of Data Validations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12General Data Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Selection Code and Product Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12GTIN Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Compliance Checks2.0 Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

GTIN Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Prepack Code Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

GMA Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Color and Size Codes and Descriptions Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Prefix Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Product Description Uniqueness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Product Description Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

iv Inovis Catalogue™ 832 (v4010) Batch Guide

C O N T E N T S

4 Mapping to Inovis CatalogueAction Types Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Data Types for ANSI X12 (v4010) Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Notes About the Mapping Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Segment and Element Delimiters Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Mapping the ISA / IEA and GS / GE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ISA Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21IEA Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23GS Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23GE Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Inbound/Outbound MappingIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Heading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27BCT Beginning Segment for Price/Sales Catalogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35N1 Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52CTB Restrictions/Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

PID Segment Structure Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58TD4 Carrier Details (Special Handling and Hazardous Materials) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60LDT Lead Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62TC2 Commodity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63G55 Item Characteristics - Consumer Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69N1 Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70SLN Subline Item Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6 Samples

A GTIN Number Structures

B Check Digit CalculationsSample: Check digit calculation for the 13-digit EAN/UCC field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

C Attribute Locations

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

1

Introduction

novis Catalogue™ is the leading product information database for the electronic exchange of product information between retailers and vendors in the GM&A, grocery, hardlines, and other industries in the United States and worldwide. It contains more than

100 million Global Trade Item Numbers (GTINs) from more than 5,000 vendors and grows daily.

Inovis Catalogue enables vendors to focus on product catalogue content and sales instead of storing and communicating product information in different ways for different customers.

The chapter is organized in the following sections:

■ “Audience”

■ “Conventions Used in This Guide” on page 2

■ “Accessing Product Documentation” on page 2

■ “Retailers and Vendors” on page 3

■ “Contacting Technical Support” on page 3

Audience The expected users of this document are EDI technical personnel for North American vendor customers of Inovis Catalogue.

This guide is designed for vendors (and distributors) using 832 v4010 documents to maintain their catalogues in Inovis Catalogue and receive outbound data in 832 format (v4010) as ad hoc downloads.

Note: Inovis Catalogue supports v4010 and v4030 for inbound and outbound 832 documents. Customers need to use the applicable version number in their map and ensure with Inovis Technical Support that the Inovis translator is set up for the intended version for inbound and outbound documents.

This audience for this guide is technical personnel charged with the following:

■ Connecting to Inovis Catalogue via electronic mailboxing

■ Preparing inbound 832 documents to send to Inovis Catalogue

■ Receiving outbound 832 documents from Inovis Catalogue

This guide includes mapping guidelines for 832 documents.

I

2 Inovis Catalogue™ 832 (v4010) Batch Guide

Conventions Used in This Guide

Conventions Used in This GuideThis guide uses the following typographical conventions:

Accessing Product DocumentationYou can access all of the Inovis product documentation for Inovis Catalogue from within the Catalogue application. Most documentation is delivered in Adobe Acrobat PDF format. To read and print the documents, you will need Adobe Acrobat Reader, a free product from Adobe Systems. For information about downloading and installing Acrobat Reader, see the section, “Installing Acrobat Reader.”

To access the product documentation1 Log in to Inovis Catalogue.

2 From the Tools menu, select Product Documentation.

The Product Documentation window opens. A list of the documents is displayed.

3 Click on a document link. The File Download popup opens. You have the option to open the document or save it to your computer.

4 Do one of the following:

■ To open the document, click Open. The document opens in a separate window.

■ To save the document to your computer, click Save. The Save As window opens. Navigate to the location where you want to save the document, and click Save. The document is saved to your computer.

Related DocumentationRelevant documents for using Inovis Catalogue include the following:

■ Inovis Catalogue Attributes Guide — Use this guide to ensure that you use the correct product data attribute names and values.

■ Inovis Catalogue Browser Interface User Guide — Use this guide to understand how to use the browser interface to view, maintain, and download catalogue data. The guide also describes how to use Error Processing to view, correct, and either delete or resubmit error transactions.

■ For information about connectivity, contact your account representative.

■ For information about electronic mailboxing available through Inovis, go to the following URL:

http://www.inovis.com/solutions/van

This convention... Indicates... Example...

Bold text Mapping guideline column headers Attribute

ALL CAPS Attribute name in notes in mapping guidelines

BOOKING DATE

“Text in quotes” Cross-reference link to a section of the guide; click it to jump to that section

“Accessing Product Documentation” on page 2

Code text 832 sample or example DTM*092*20010917

http://www.inovis.com/solutions/van

Retailers and Vendors

Inovis Catalogue™ 832 (v4010) Batch Guide 3

Installing Acrobat ReaderSince most Inovis product documentation is delivered in Adobe Acrobat PDF format, you will need Adobe Acrobat Reader to read and print the documentation. Acrobat Reader is a free product from Adobe Systems.

To download and install Acrobat Reader1 Launch a Web browser and navigate to

http://www.adobe.com/products/acrobat/readstep.html

2 Download the Acrobat Reader installer.

3 Double-click the file you downloaded. The installer launches.

4 Follow the screens accepting the defaults.

You can now access Inovis product documentation by double-clicking the PDF file.

Retailers and Vendors In this guide the term “retailers” includes retailers, grocers, distribution centers, and third parties that extract data from Inovis Catalogue. An example of a third party is a company that makes tags attached to apparel.

The term “vendors” includes vendors, manufacturers, distributors, brokers, and wholesalers.

Contacting Technical SupportTo contact Technical Support for assistance:

■ Email [email protected]

■ Call 877.4INOVIS (877.446.6847)

To contact Technical Support for assistance in Europe, refer to the Inovis website at http://www.inovis.com or available phone numbers.


mailto:[email protected]

http://www.inovis.com


http://www.adobe.com/products/acrobat/readstep.htm

http://www.adobe.com/products/acrobat/readstep.htm


Contacting Technical Support

5

Overview 1his chapter provides an overview of using the batch interface to communicate with Inovis Catalogue using 832 documents. The batch interface enables vendors to maintain their catalogues (inbound data) and receive ad hoc downloads (outbound

data, requested through the browser interface).

Inovis Catalogue supports EDI ANSI X12 v4010 and v4030 specifications for inbound and outbound 832 documents. Customers need to use the applicable version number in their map and ensure with Inovis Technical Support that the Inovis translator is set up for the intended versions for inbound and outbound documents.

This guide is specifically designed for vendors (and distributors) using 832 v4010 documents. For version 4030, refer to the Inovis Catalogue 832 (v4030) Batch Guide for Vendors.

The chapter is organized in the following sections:

■ “Stages of the Batch Process” on page 5

■ “Batch Interface System Components” on page 6

■ “File Formats Supported” on page 6

■ “Customer Requirements” on page 7

■ “Electronic Mailbox Addresses” on page 7

■ “Catalogue Organization” on page 7

■ “GTIN Type and Package Characteristics ” on page 8

■ “Email Confirmation” on page 8

■ “Online Correction of Errors” on page 9

Stages of the Batch ProcessThe Inovis Catalogue EDI 832 batch process runs continuously, seven days a week, except between 8 pm and 12 am Pacific Standard Time (PDT).

An overview of the Inovis Catalogue inbound batch process is as follows:

1 Inovis picks up the inbound 832 document from the Inovis electronic mailbox.

2 Inovis checks file integrity against the EDI ANSI X12 (v4010) standards.

3 Inovis archives a copy of the 832.

4 The 832 is validated for ANSI X12 qualifiers, mandatory segments and elements, field lengths, and so on. A 997 (Functional Acknowledgement) is sent to the vendor.

T


O VE R V I E W

Batch Interface System Components

5 The files are queued and processed in FIFO order (first files in are the first files out).

Note: Control numbers must be unique. If a duplicate control number is found, the entire EDI document will be ignored. When resending a corrected document, it must be sent with a new control number.

6 Within the 832, Inovis Catalogue processes each valid ST/SE group as a separate transaction. As each ST/SE group is processed, one of the following occurs:

■ Translation Error — If a translation error occurs in the ST/SE group, the entire group is sent to Error Processing (EP). Subsequent ST/SE groups will continue to be processed. You can use EP (accessible through the browser interface) to locate the error in the 832 document. See “Online Correction of Errors” on page 9.

■ Valid ST/SE group — If the ST/SE group is valid, Catalogue loads the document and runs business rule validations, data validations, and compliance checks for each item. This process results in one of the following:

■ No errors — Successful data maintenance for that item.

■ Errors — The errors are sent to Error Processing (EP). No data maintenance takes place for that item. You can correct the errors (EP is accessible through the browser interface) and resubmit the error document. See“Online Correction of Errors” on page 9.

7 Inovis Catalogue sends you an email for each EDI document that contains errors. It includes a hyperlink to the browser interface where you can troubleshoot the errors. See “Email Confirmation” on page 8.

Batch Interface System ComponentsThe basic components of the Inovis Catalogue batch interface are as follows:

■ Client software to connect customer to the Inovis electronic mailbox

■ Inovis electronic mailbox

■ Inovis Catalogue product information database

Inovis Catalogue Batch Interface Diagram

File Formats SupportedInovis Catalogue supports EDI ANSI X12 v4010 and v4030 specifications for inbound and outbound 832 documents.

This guide is specifically designed for vendors (and distributors) using 832 v4010 documents. For version 4030, refer to the Inovis Catalogue 832 (v4030) Batch Guide for Vendors.

O VE R V I E W

Customer Requirements


1

Customer RequirementsBatch interface requirements include the following:

■ Maximum file size is 35MB.

■ Maximum number of LIN segments per ST is 30,000.

■ Customer must connect to Inovis’s electronic mailboxing service. This can accomplished by Internet, Intranet, or leased line. See mailbox addresses below.

For assistance with messaging and connectivity contact Technical Support. See “Contacting Technical Support” on page 3.

Electronic Mailbox Addresses Connect with Inovis Catalogue by sending documents to the following Inovis electronic mailboxes:

Production Mailbox AddressQualifier: 01

Receiver ID: 120812854 or 0120812854

Test Mailbox AddressQualifier: 12

Receiver ID: 5109654406

If you need information about how to obtain an Inovis electronic mailbox:

■ Call your Inovis Account Representative at 877.4INOVIS (877.446.6847)

■ Email [email protected] or [email protected]

If you are an existing Inovis customer and have questions about messaging and connectivity:

■ Call your Inovis Account Representative at 877.4INOVIS (877.446.6847)

■ Email Technical Support at [email protected]

Catalogue OrganizationInovis Catalogue organizes items in a two-level structure (EDI locations shown in parentheses):

■ Selection Codes (BCT03)

■ Products (LIN02/LIN03)

Selection Codes define broad categories of items. Each Selection Code is a three-digit number that can contain any number of Products. A Product is a grouping of items that have the same shape, material, function, vendor style or part number, or other characteristics except size or color. A Product identifier is up to 20 digits or upper-case characters. A Product can contain any number of items, which are identified by GTINs.

S A M P L E

Selection Code 108 and Product 123SHOEA appear in the 832 as follows:

BCT*RC*125103335555*108******01*00 …





O VE R V I E W

GTIN Type and Package Characteristics

LIN*A1*VN*123SHOEA*UP*555555011112*CM*234*SM*23456

GTIN Type and Package Characteristics Each GTIN is either consumer-sellable (scanned at POS and can also be vendor-sellable) or only vendor-sellable. This is defined by the GTIN Type (see “GTIN Number Structures” on page 77 for details):

■ Consumer-sellable or vendor-sellable: UP, EN

The GTIN Type is first specified in the LIN segment and indicates which of the following segments are used to define the GTIN’s package characteristics:

■ G55 - Consumer-sellable package

If the Inner Pack is marked with a GTIN, the GTIN is specified in the LIN.

The set of GTIN identifiers in G5501/G5502 must match the LIN GTIN data pair it belongs to.

Email ConfirmationWhen an 832 document is processed by Catalogue, there is a possibility that the document may have the following types of errors:

■ Translation errors

■ Errors resulting from business rule violations, data validations, and compliance checks.

Catalogue sends these errors to Error Processing (EP) and also sends you an email for each EDI document that contains errors. The email includes the number of errors that were found and a short description of each error. The email is sent to the primary contact email address for your account (Main > Account > Account Details). Be sure that this email address is valid.

The email also contains a hyperlink to the Inovis Catalogue login page. To view the errors, use Error Processing in the browser interface (Main > Error Processing). Some error transactions can be corrected and resubmitted using EP. See “Online Correction of Errors” on page 9 for more information about identifying and correcting errors.

Sample EmailThe email can be recognized by its subject line: "Inovis Catalogue error report (control number: DocumentControlNumber.)" as shown in the example.

E X A M P L E

Subject: Inovis Catalogue error report (control number: DocumentControlNumber)

One or more errors occurred while processing your input file. Please login to the Inovis Catalogue User Interface to review and manage these errors.(http://catalogue.qrs.com)

Control number: DocumentControlNumberDate: May 6, 2005Time: 5:27:38 AMNumber of errors: 360

Error Count Description

http://catalogue.qrs.com

O VE R V I E W

Online Correction of Errors


1

-20505 23 Failed to get existing item attributes; error code=-20505-20505 15 Item Number not found-20511 3 Duplicate item number302 -90034 1 Item number already exists-20510 318 Specified Selection Code or Product not found. It may have been deleted by

another user.

Online Correction of ErrorsTwo types of errors are sent to Error Processing:

■ Translation errors

■ Errors resulting from business rule violations, data validations, and compliance checks.

You are notified by email (see “Email Confirmation” on page 8) of each EDI document (ST/SE group) that contains errors. You can use Error Processing (EP), accessible through the browser interface, to:

■ Locate a translation error in the 832 document.

Errors in the EDI document that cause processing to abort before translation occurs, cannot be fixed in Error Processing; however, you can view a fragment of the file surrounding the error which will help you identify the cause of the error. Once you review the error, delete the error document from EP and generate a new EDI file from your source system to resend to Inovis.

■ Correct and resubmit, or delete, errors due to business rule violations, data validations, or compliance checks. These types of errors can be edited in EP using Catalogue’s internal qXML format.

For more detailed information about identifying and correcting errors using the browser interface (Main > Error Processing), see the Inovis Catalogue Browser Interface User Guide for Vendors and the online help.


O VE R V I E W

Online Correction of Errors

11

Validation 2his chapter explains validation checks that are run on 832 documents sent to Inovis Catalogue. The chapter is organized in the following sections:

■ “Transaction Validation ” on page 11

■ “EDI Standards Validation” on page 11

■ “Translation, Data Validation, and Data Maintenance” on page 11

■ “Types of Data Validations” on page 12

Transaction Validation Transaction validation of inbound 832s occurs in two stages:

■ EDI validation

■ Translation, data validation and data maintenance

EDI Standards ValidationWhen an 832 document is sent to Inovis, it is compared to EDI ANSI X12 (v4010) standards and validated for ANSI X12 qualifiers, mandatory segment and elements, field lengths, and so on. If it passes EDI validation, you will receive a positive functional acknowledgement (FA) and the document proceeds to stage two: translation, data validation, and data maintenence. If it fails EDI validation, you will receive a negative FA, and you will not be able to view or process the document through Error Processing (EP).

Translation, Data Validation, and Data Maintenance

TranslationOnce the 832 document passes EDI standards validation, it is processed by Inovis Catalogue. Catalogue processes the document one ST/SE group at a time. If the ST/SE group contains valid X12 v4010 EDI that is currently not supported by Catalogue, a translation error results and you are notified by email. See “Email Confirmation” on page 8 for information about setting up a valid email address.

Note: If the ST/SE group contains a translation error, the entire ST/SE group will be rejected. Catalogue sends these errors to EP. See “Online Correction of Errors” on page 9 for more information about identifying and correcting errors.

If the document passes translation, processing continues with data validation, described in the next section.

T


VA L I D A T I O N

Types of Data Validations

Data Validation and Data MaintenanceOnce a document passes translation, Catalogue runs data validations for each item in the document. The following occurs:

■ Valid ST/SE groups are processed to update your catalogue (data maintenance).

■ ST/SE groups with errors are forwarded to EP, and you are notified by an email. See “Email Confirmation” on page 8 for information about setting up a valid email address.

Types of Data Validations Catalogue runs the following types of data validations.

General Data Validation

■ Data type validation fields (see “Data Types for ANSI X12 (v4010) Transactions” on page 19). All documents are validated to ANSI X12 (v4010) standards.

■ In addition, Catalogue validates all documents against another subset of validations. The following special characters are not allowed: > ^ ` [ ]

Note: < and " are allowed.

Selection Code and Product Validation

■ Each Selection Code and Product must have a unique identifier in a vendor's catalogue (Products are stored in upper case; they cannot be differentiated by varying case)

■ PRODUCT DESCRIPTION is required when adding a Product; we recommend that it be unique (that is, do not use the same description more than once)

■ The following characters must not appear in a Product (LIN data pair with VN qualifier): ! @ # $ % & * ( ) _ / |

GTIN ValidationGTIN (Global Trade Item Number) is an umbrella term for trade items. It is a 14-digit reference field used to uniquely identify a consumer unit, packaging level, or logistic unit (for example, prepack container, inner pack, case, module, or pallet) worldwide.

GTIN accommodates the four different numbering structures (formerly called Item Number Types) currently used to identify trade items:

■ EAN/UCC-8 (not supported by v4010)

■ UCC-12 (UPC)

■ EAN/UCC-13

■ EAN/UCC-14 (not supported by v4010)

GTIN identifier validation includes the following:

■ Validation of GS1 US Company Prefix (formerly UCC Manufacturer Block ID) when GTIN is type UP (applies to manufacturers but not distributors). This check is now part of the Prefix Validation compliance check. For more information about compliance checks, see Chapter 3 "Compliance Checks," on page 15, as well as the Inovis Catalogue Browser User Interface Guide.

VA L I D A T I O N



2

■ Each GTIN number/type identifier pair must be unique in the vendor’s catalogue and across all manufacturer catalogues in Inovis Catalogue (same number can be used with different GTIN types)

Note: A GTIN can exist in catalogues of a single manufacturer (“V” account type) and one or more distributors (“D” account type).

■ Check digit validation for UPC and EAN. See “Check Digit Calculations” on page 79.

■ GTIN number structure requirements. See “GTIN Number Structures” on page 77.

GTIN Attribute Validations and RulesWith the exception of SELECTION CODE DESCRIPTION and PRODUCT DESCRIPTION, catalogue data attributes are attached to GTINs, not Selection Codes or Products.

Note: For v4030, PRODUCT EXTENDED DESCRIPTION is an additional exception to this rule.

GTIN attribute validations include the following:

■ Field length, data type, and Unit of Measure (UOM), if any, as defined in the Inovis Catalogue Attributes Guide.

■ Attribute list values stored at Inovis must be sent in exact, case-sensitive format as they appear in the mapping guide below (for example, “Short sleeve,” not “short sleeve”)

■ Conformance to industry standards based on the compliance checks that are configured for your account

■ When updating a multiline attribute (an attribute that can contain more than one value, such as country of origin - see “Multiline Data Attributes” on page 14), send all of the values that are to appear in the updated list, not only the new values because the entire list will be replaced

GTIN Container and Component Validations and RulesContainers (formerly called prepacks or parent items) are GTINs that can contain other GTINS called components. GTIN container or component designation is stored in Inovis Catalogue in the data attribute PREPACK/CONTAINER CODE (“Pack” in the browser interface, and ITEM.PREPACK_CODE in qXML).

The following validations and guidelines apply to containers and components:

■ A container designation (MP, SP, PU, PC) is required for a GTIN to be a container, and the designation must be assigned at the time the GTIN is added to the catalogue

Note: For v4030, valid container designations are CA, DS, IP, MP, MX, SP, PL, PU, or PC.

■ A container designation can be changed to one of the other eight container designations but not eliminated (that is, you cannot change a container to a plain GTIN)

■ A component designation (PP) is not required for a GTIN to be a component, but if the GTIN is to be sold only as part of a container it should be designated PP (can be changed to blank later)

■ A GTIN initially without a container designation can later be designated PP but not a container

■ A component does not require the same Selection Code and/or Product as its container

■ A component must exist in Inovis Catalogue before it is assigned to a container


VA L I D A T I O N


■ To change a component's quantity or UOM, you must remove the component from the container, then add it to the container again with the corrected information

■ A component GTIN cannot be deleted until its container is deleted

Note: To delete a component GTIN but not its container, use the SLN segment or the browser interface to sever the container-component relationship, and then delete the GTIN.

■ Deleting a container does not delete its component GTINs, it deletes only the container GTIN and severs the container-component relationships

■ A container can have from 0 to 100 component GTINs

■ A container can contain other container GTINs, but the second level of containers cannot contain a third level of containers

■ A container is visible to retailers whether complete, incomplete, or empty

Multiline Data AttributesMost attributes can contain only one single value. Multiline attributes, however, support a list of values, such as a list of countries of origin for an item.

Values in a multiline attribute are returned in the order they appear in the load request.

To update a multiline attribute, you must send the entire revised list, not only the new values or deletions. The list you send does not modify the existing list, it replaces it. Similarly, to clear multiline values, send a new list, leaving out the values that should no longer appear in the list.

There are several groups of associated multiline attributes (that is, attributes that are logically related) in the Inovis Catalogue EDI interface. Chapter 4 "Mapping to Inovis Catalogue," on page 19 contains specific information regarding the number of allowed occurrences for each group. See the specific segment outlines for details.

15

Compliance Checks 3his chapter describes the compliance checks that are available in Inovis Catalogue and provides details about the validation rules that comprise each check. Compliance checks are a way to validate Catalogue data according to a set of pre-determined rules.

They can be used to enforce industry standards and may be mandated by your Trading Partners.

Note: The compliance checks are unrelated to which version of the ANSI X12 EDI standards you use (v4010 or v4030); they are applied after translation.

Inovis Catalogue can perform several different compliance checks. The compliance checks that are available to your account are determined by your Inovis administrator. Options are available if you want to be notified of non-compliant data. For more information about compliance check options and their configuration, see the Inovis Catalogue Browser User Interface Guide.

The following compliance checks are available:

■ 2.0 Compatibility — verifies that an item is compatible with Inovis Catalogue 2.0 and the allowed attributes will be visible to 2.0 Retailers.

■ GMA Compliance — verifies that an item is compliant with GM&A (General Merchandise and Apparel) industry standards.

■ Prefix Validation — verifies that an item’s GTIN begins with a prefix associated with your account. Not available to distributors.

■ Product Description Uniqueness — verifies that an item’s Product Description is unique across all products within your catalogue.

T


C O M P L I A N C E C H E C K S

2.0 Compatibility

2.0 CompatibilityInovis Catalogue vendors and distributors can use the 2.0 Compatibility compliance check to verify that an item is compatible with Inovis Catalogue 2.0 and the allowed attributes will be visible to 2.0 Retailers.

For this compliance check, Catalogue validates the item’s GTIN information (the qXML parameters ITEM_NUMBER_TYPE and ITEM_NUMBER) and the item’s prepack code (ITEM.PREPACK_CODE) according to the rules shown in the following tables. An item passes the compliance check only if it passes all GTIN rules and prepack code rules.

GTIN Rules

Prepack Code Rules

An item PASSES the compliance check if: An item FAILS the compliance check if:

■ The GTIN Type is UCC-12 (UP)

■ The GTIN Type is EAN-13 (EN)

■ The GTIN Type is GTIN-14 (UK) and the leading digit is zero

■ The GTIN Type is EAN-8 (EO)

■ The GTIN Type is GTIN-14 (UK) and the leading digit is not zero


■ ITEM.PREPACK_CODE is one of the following:

■ blank

■ MP

■ PC

■ PP

■ PU

■ SP

■ ITEM.PREPACK_CODE is one of the following:

■ CA

■ DS

■ IP

■ MX

■ PL


GMA Compliance


3

GMA ComplianceInovis Catalogue vendors and distributors can use the GMA Compliance check to verify that an item is compliant with GM&A industry standards.

For this compliance check, Catalogue validates the item’s NRF color and size codes (ITEM.NRF_COLOR_CODE and ITEM.NRF_SIZE_CODE) and descriptions (ITEM.NRF_COLOR_CODE_DESCRIPTION and ITEM.NRF_SIZE_CODE_DESCRIPTION) and the item’s prepack code (ITEM.PREPACK_CODE) according to the rules shown in the following table.

Color and Size Codes and Descriptions Rules


■ Both color code and color description are present

■ Color code is exactly 3 digits (no spaces)

■ For color code equal to 000, color description is NO COLOR

■ For color description equal to NO COLOR, color code is 000

■ For ITEM.PREPACK_CODE equal to PP or blank, size code starts with 1-8; exception is 00000 for NO SIZE

■ For ITEM.PREPACK_CODE equal to CA, DS, IP, MP, MX, PC, PL, PU, SP, size code starts with 9; exception is 00000 for NO SIZE

■ Both size code and size description are present

■ For size code equal to 00000, size description is NO SIZE

■ For size description equal to NO SIZE, size code is 00000

■ Different color codes under a single Product have the same color description

■ A single color code under a single Product has two different color descriptions

■ Once the value is set (populated), color code is changed

■ Different size codes under a single Product have the same size description

■ A single size code under a single Product has two different size descriptions

■ Once the value is set (populated), size code is changed

■ Two of the same type of GTIN exist under the same Product with the same color and size codes



Prefix Validation

Prefix ValidationInovis Catalogue vendors will be required to use the Prefix Validation compliance check that verifies that an item’s GTIN begins with a prefix associated with their account.

Note: This compliance check is not available to distributors.

This compliance check is applied to all UCC-12 (UP), EAN-13 (EN), and GTIN-14 (UK) items that are added using any of the Catalogue 4.x interfaces. It is not applied to EAN-8 (EO) items.

To verify your valid GS1 (UCC/EAN) company prefixes, go to Main > Account > Account Details and click the GS1 (UCC/EAN) Company Prefixes link at the top of the Account Details screen.

Product Description UniquenessInovis Catalogue vendors and distributors can use the Product Description Uniqueness compliance check to verify that an item’s description is unique across all products within their catalogue.

For this compliance check, Catalogue validates the item’s Product Description (HIERARCHY.PRODUCT_DESCRIPTION) according to the rules shown in the following table.

Product Description Rules


■ The item’s Product Description value is unique across all Products within your catalogue

■ The item’s Product Description value is not unique across all Products within your catalogue

19

Mapping to Inovis Catalogue 4his chapter explains some of the basics of mapping to Inovis Catalogue. Each element in an 832 document sent to Inovis Catalogue is translated into qXML format by Inovis before being forwarded to Inovis Catalogue. Use the mapping guide (see Chapter 5

"Inbound/Outbound Mapping," on page 25) and data validation guidelines (see Chapter 2 "Validation," on page 11 ) to ensure well-formed EDI that will translate successfully into qXML.

This chapter is organized in the following sections:

■ “Action Types Supported”

■ “Data Types for ANSI X12 (v4010) Transactions” on page 19

■ “Notes About the Mapping Guide” on page 20

■ “Mapping the ISA / IEA and GS / GE” on page 21

Action Types SupportedBefore information can be processed in or out of the batch system, the vendor must communicate the type of action required. Action Codes can be specified at the heading or detail level. Action Codes are processed in the order they appear in the EDI document. They can be applied to the entire ST or to individual Products and GTINs in the transaction.

Five EDI action types are accepted at the heading level:

■ Cancel (01)

■ Add (02)

■ Delete (03)

■ Change (04)

■ Replace (05)

If the user specifies any of the above Action Codes in the BCT10 segment at the header level, the Action Code applies to all LIN segments in the transaction set.

Data Types for ANSI X12 (v4010) TransactionsIn the tables below, the Attributes column shows the data type and minimum/maximum number of characters for the associated data element.

E X A M P L E :

AN 1/20

T


M A P P I N G T O I N OV I S C A T A L O G U E

Notes About the Mapping Guide

The data type codes are as follows:

■ AN—Alphanumeric, a sequence of any printable characters. Significant characters should be left-justified. Leading spaces, when they occur, are assumed significant. Trailing spaces should not be included.

■ DT—Date. CCYYMMDD format.

■ ID—Code values taken from a predefined X12 list.

■ N0—Numeric data that does not allow a decimal.

Note: A N0 note in the shaded area of the mapping guide indicates that no decimal is allowed, and displays the minimum/maximum number of digits allowed.

■ R—Numeric data that allows a decimal. The maximum number of digits to the right of the decimal appears after the comma (for example, R 1/8,4 indicates that four digits are allowed to the right of the decimal point). Note the following:

■ Use a decimal for fractional values.

■ Do not include the decimal for whole numbers. If the value is a whole number and does not require a decimal point, do not place a decimal point at the end, even if its character type is R.

■ Do not use leading zeros unless needed to satisfy a minimum length requirement.

■ Do not use commas (for example, use 1000 rather than 1,000).

■ Use a minus symbol (-) to indicate a negative value. Do not use plus symbols.

■ If the value includes a decimal, do not use trailing zeros unless required to show the level of precision.

■ Minus symbols and decimal points do not count toward field length limits.

■ Do not use special characters to indicate currency or measurements.

E X A M P L E :

Send one foot as “1”. Send one-and-one-eighth inches as “1.125”.

Send $15.95 as “15.95”.

Send $29.00 as “29”.

Notes About the Mapping GuideTake note of the following when working with the mapping guidelines below:

■ Required Segments and Data Elements. Codes indicate whether a segment or data element is mandatory, optional, or conditional on the presence of another data element. These codes appear in the Req. Des. column of the Mapping the STs section, and the Attributes column of the individual 832 segments in the mapping guide:

■ Mandatory (M)

■ Optional (O)

■ Conditional (C)

M A P P I N G T O I N OV I S C A T A L OG U E

Segment and Element Delimiters Supported


4

Note: A common use of C is a unit of measure (UOM) that is conditional on the presence of an optional (O) measurement.

■ Data Attributes. In the 832, a piece of information about a Product or GTIN is referred to as a data element. In the Inovis Catalogue, these pieces of information are referred to as attributes. For easy customer cross-reference, the shaded notes sections in the mapping guidelines provide the Inovis Catalogue attribute name in all capital letters (for example, SEASON) that is equivalent to the 832 data element.

Segment and Element Delimiters Supported The following delimiters are supported by the Inovis data translator.

Mapping the ISA / IEA and GS / GE

ISA HeaderThe ISA is fixed length (minimum and maximum are equal for each element), but data element separators are used between data elements to be consistent with the basic syntax of segment structure. Maximum lengths provided reference the minimum/maximum lengths read by the Inovis data translator.

Delimiter Symbol ASCII EBCDIC

Element Separator * HEX “2A” HEX “5C”

Component (Sub Element) Separator > HEX “3E” HEX “6E”

SegmentTerminator ~ HEX “7E” HEX “A1”

ISA Segment

Max Length

Data Type Value/Inovis Format Field

ISA01 2 N "00" - No authorization information present

ISA02 10 Spaces

ISA03 2 N "01" Password follows in ISA04

ISA04 10 AN Batch password (inbound only). Must be EXACTLY 10 characters, including spaces, if any.

ISA05 2 N Sender Interchange ID Qualifier:

"01" - DUNS Number

"08" - UCC Comm ID

"12" - Telephone Number

“ZZ” - Mutually defined

ISA06 15 N Sender Interchange ID (code defined by qualifier in ISA05).

When ISA05="01", ISA06 must be 9-digit DUNS Number

When ISA05="08", ISA06 must be 10-digit UCC Comm ID

When ISA05="12", ISA06 must be 10-digit telephone number

When ISA05="ZZ", ISA06 must be an alphanumeric sender ID with a maximum of 15 digits

(left justified, blank filled)

ISA07 2 N Receiver Interchange ID Qualifier (Inovis):

"01" - DUNS Number (PROD)

"12" - (TEST)




ISA08 15 N Receiver Interchange ID (Inovis)

The identification code defined by qualifier in ISA07:

"120812854" (PROD)

"5109654406" (TEST)

(left justified, blank filled)

ISA09 6 N Date interchange created in sender's system (YYMMDD)

ISA10 4 N Time interchange created in sender's system (HHMM)

ISA11 1 AN "U" - Interchange control standards identifier

ISA12 5 N Interchange Version ID

"00401" or "00200"

ISA13 9 N Interchange control number assigned by the sender. This number must match control number in IEA02.

ISA14 1 N "0" - Acknowledgment not requested

ISA15 1 AN "P" - Production mailbox data, "T" - Test mailbox data

ISA16 1 ">" - Sub-element separator

ISA Segment

Max Length


M A P P I N G T O I N OV I S C A T A L OG U E



4

IEA Trailer

GS Header

GE Trailer

IEA Segment

Max Length


IEA01 1 to 5 N Number of included groups:

use the count of GS segments within the transmission.

IEA02 9 N Interchange control number. Use value from ISA13

GS Segment

Max Length


GS01 2 AN Functional ID: must be "SC"

GS02 9 or 10 N Application Sender ID. Must match the ISA06, or the document will fail.

GS03 10 N Application Receiver's Code. Use value from ISA08:

"120812854" (PROD)

"5109654406" (TEST)

GS04 8 N Date in CCYYMMDD format

GS05 4 N Time in HHMM format

GS06 1 to 9 N Data interchange control number for this GS group. Assigned by the sender. Must be unique if more than one GS. Combined with ISA13 to identify GS in the 997 sent from Inovis.

GS07 1 AN Responsible agency code: for X12, use "X"

GS08 10 AN Version/release number (depends on the format version):

"004010" or "004010VICS"

GE Segment

Max Length


GE01 1 to 6 N Number of included transaction sets: use the count of ST segments within the Group.

GE02 1 to 9 N Data interchange control number. Use the value from GS06

25

Inbound/Outbound Mapping 5his chapter presents the mapping guidelines for each segment in an inbound or outbound 832 document. The guidelines detail 832 segments used by vendors sending data to Inovis Catalogue, and retailers and vendors receiving data.

Inovis Catalogue supports v4010 and v4030 for inbound and outbound 832 documents. Customers must use the applicable version number in their map and ensure with Inovis Technical Support that the Inovis translator is set up for the intended version of inbound and outbound documents.

Note: Inovis Catalogue v4010 mapping does not support the full suite attributes that are available in Catalogue 4.12.5. Version 4010 mapping supports only a subset of the attributes, those which are currently available in Catalogue 2.0. This availability makes it possible for customers who are upgrading from Catalogue 2.0 to 4.12.5 to do so without also upgrading thier maps from v4010 to v4030. To take full advantage of all of the attributes available in Catalogue 4.12.5, customers must upgrade their maps to v4030.

IntroductionThe Functional Group ID is SC.

This Draft Standard for Trial Use contains the format and establishes the data contents of the Price/Sales Catalogue Transaction Set (832) 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 furnishing or requesting the price of goods or services in the form of a catalogue.

Heading

Pos. No.

Seg. ID Name

Req. Des.

Max. Use

Loop Repeat Notes

M 010 ST Transaction Set Header M 1

M 020 BCT Beginning Segment for Price/Sales Catalogue

M 1

070 DTM Date/Time Reference O 11

090 CUR Currency O 1

LOOP ID - N1 >1

150 N1 Name O 1

T

26 Inovis Catalogue™ 832 (4010) Batch Guide

I N B O U N D / O U T B O U N D M A P P I N G

Detail

Detail

Summary

Notes1 Number of line items (CTT01) is the accumulation of the number of LIN segments.

2 Hash total (CTT02) is not used in this transaction.

Pos. No.

Seg. ID Name

Req. Des.

Max. Use

Loop Repeat Notes

LOOP ID - LIN >1

010 LIN Item Identification O 1 See Note 1.

030 DTM Date/Time Reference O 10

060 CTB Restrictions/Conditions O 3

070 PID Product/Item Description O 50

110 TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both)

O 10

140 LDT Lead Time O 1

165 TC2 Commodity O 2

168 G55 Item Characteristics - Consumer Unit O 1

LOOP ID - CTP 100

170 CTP Pricing Information O 1

LOOP ID - N1 >1

230 N1 Name O 1

LOOP ID - SLN 100

350 SLN Subline Item Detail O 1

Pos. No.

Seg. ID Name

Req. Des.

Max. Use

Loop Repeat Notes

010 CTT Transaction Totals M 1 See Notes 1 and 2.

M 020 SE Transaction Set Trailer M 1


ST Transaction Set Header

Inovis Catalogue™ 832 (4010) Batch Guide 27

5

ST Transaction Set HeaderPosition: 010

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1

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

Data Element Summary

Ref. Des.

Data Element Name Attributes

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

Code uniquely identifying a Transaction Set

832 Price/Sales Catalogue

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

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

The sender assigns the number in sequence. For each functional group, the first transaction set control number will be 0001, and each additional transaction in that group will be incremented by one (e.g., 0002, and so on).



BCT Beginning Segment for Price/Sales Catalogue

BCT Beginning Segment for Price/Sales CataloguePosition: 020

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of the Price/Sales Catalogue Transaction Set and specify catalogue purpose and number information

Syntax Notes:

Notes: INBOUND to Inovis:

Use BCT10 only to clarify to the receiver the sender's purpose of the transaction set. Use codes 01, 02, 03, 04, and 05 to maintain catalogue information owned by the vendor.

To add or update account attributes without sending catalogue data, use BCT10=04. Account maintenance will be ignored for BCT10=05.

To move a Product to a different Selection Code in your catalogue, see the description under BCT03.

OUTBOUND from Inovis:

If the Products or GTINs being sent are new or updated and part of an active subscription profile, no action code will be sent in the BCT10.


Ref. Des.


M BCT01 683 Catalogue Purpose Code M ID 2/2

Code indicating purpose of catalogue

RC Resale Catalogue

Vendor catalogue; Product and GTIN (UPC/EAN) setup and maintenance; outbound subscription data

M BCT02 684 Catalogue Number O AN 9/12

Identifying number for catalogue or superseded catalogue

VENDOR ID. Owner of the catalogue, generally the vendor (manufacturer, distributor, or agent).

Inovis Note: Vendor Inovis Catalogue Account Number

01 = Account Number is Duns Number. 9-digit Duns Number or full 12-digit Account Number must be sent.

08 = Account Number is GS1 US (formerly UCC) Comm ID. 10-digit GS1 US Comm ID or full 12-digit Account Number must be sent.

12 = Account Number is telephone number. Full 12-digit Account Number must be sent.




5

BCT03 685 Catalogue Version Number O AN 3/3

Identifying version number of catalogue or superseded catalogue

SELECTION CODE as detailed in the VICS EDI Trade Item Identification and Communication Guidelines

Inovis Note: Format (N0 3/3)

Each vendor should establish a logical catalogue hierarchy (see above). In Inovis Catalogue, this starts with the Selection Code and is followed by the Product and then the GTIN. Vendors may set up multiple Selection Codes, which serve as high-level groupings for Products. Each Product and its one or more GTINs must be assigned to a Selection Code.

In addition to grouping Products, Selection Codes enable a vendor to grant Trading Partners access to portions of the catalogue. Inovis allows vendors to grant access to their Trading Partners at the level of the entire catalogue, or at the level of one or more Selection Codes in that catalogue. It is important to assign Selection Codes not only with product groupings in mind, but also Trading Partner access if this feature is used.

MOVING A PRODUCT TO A DIFFERENT SELECTION CODE

To move the Product referenced in LIN02/03 to a different Selection Code in your catalogue, do the following:

1. Create a new Selection Code, if needed.

2. Make sure that retailers you want to receive an Inovis Catalogue export that notifies them of the change have access to the Selection Code where the Product will be moved. Do this before moving the Product. Note that retailers who lose access to GTINs as a result of the Product move will not be notified by Inovis Catalogue.

3. In BCT03 enter the Selection Code where you want to move the Product.

4. In BCT10, use either the change (04) or replace (05) action.

Inovis Catalogue will move the Product and all of its GTINs and associated attributes to the specified Selection Code. It will not change attribute data other than Selection Code data.

Moving a Product in this way does not impact 1SYNC (formerly UCCnet) registration of the Product.

Important: If you do not want to move the Product, make sure that the specified Selection Code is the one where the Product currently resides. If it is different, Inovis Catalogue will move the Product.

BCT09 352 Description O AN 1/25

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

Inovis Note: Description of Selection Code specified in BCT03.

BCT10 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set

Data Element Summary (Continued)

Ref. Des.





01 Cancellation

Restricted use. See VICS EDI Trade Item Identification and Communication Guidelines.

Inovis Attribute: CANCEL DATE. Only GTINs may be canceled.

For a GTIN to qualify for cancellation, it must never have been introduced into the supply chain, produced or shipped. If a GTIN does not meet these criteria, it must be discontinued (DTM01=036) rather than canceled.

To cancel a GTIN, one of the LIN Pairs EN or UP (GTIN) is required. In addition, a CANCEL DATE may be sent in the DTM segment (DTM01=177). This date may not be more than one month prior to the processing date or it will result in an error. If no CANCEL DATE is sent, Inovis will use the processing date.

Canceled GTINs may not be reused until 12 months after cancellation. Inovis recommends that canceled GTINs remain on the catalogue until this 12-month period has passed.

02 Add

Inovis Note:

To add a Selection Code, BCT03 (Selection Code) is required. If the Selection Code already exists in your catalogue, the action will be ignored and no error message will be returned.

To add a Product, BCT03 (Selection Code), LIN Pair/VN (Product), and PID Pair/08 (Product Description) are required. See PID segment for additional instructions regarding Product Description.

To add a GTIN, BCT03 (Selection Code), LIN Pair/VN (Product), and one of the LIN Pairs EN or UP (GTIN) is required.

When adding a Product or GTIN, if the parent Selection Code and/or Product referenced does not exist, it, too, will be added to the catalogue.


Ref. Des.





5

03 Delete

Inovis Note:

Deleting a Selection Code deletes all Products and GTINs under the Selection Code. To delete a Selection Code, do not include any LIN segments. If LIN segments are included, only Products or GTINs will be deleted.

Deleting a Product deletes all GTINs under the Product, as well as the Product and all of its attributes. To delete a Product, do not include a GTIN in the LIN segment. Including a GTIN in the LIN will delete only the GTIN.

To delete a Product, BCT03 (Selection Code) and LIN Pair/VN (Product) are required.

To delete a GTIN, only one of the LIN Pairs EN or UP (GTIN) is required.

Deleting a GTIN from the catalogue does not alter the minimum retention period (30 months for apparel and 48 months for all other items) as defined in the VICS EDI Trade Item Identification and Communication Guidelines.

When the last GTIN is deleted from a Product, the Product is automatically deleted from Inovis Catalogue.

04 Change

Inovis Note:

Change means changing the value in a specific field within a record to something different than what currently exists on the Catalogue. A Change action code will not blank out fields. Change requires sending only fields that are changing.

To change account information but not provide product data, do not send Selection Code or LIN loop.

To change Selection Code Description, BCT03 (Selection Code) and BCT09 (Selection Code Description) are required.

To change Product attributes, BCT03 (Selection Code) and LIN Pair/VN (Product) are required.

To change a GTIN, BCT03 (Selection Code), LIN Pair/VN (Product), and one of the LIN Pairs EN or UP (GTIN) are required.

Product name and GTIN identifier/qualifier cannot be changed in the existing record. To change them, delete the record, then re-add it with the new value(s). Additional constraints may be imposed by your configured compliance checks.


Ref. Des.





05 Replace

Inovis Note:

If you specify replace for an existing item, the item is updated only with the attributes specified in that data record. A Replace action code will blank out fields.

Account maintenance will be ignored for BCT10=05.

To replace Selection Code Description, BCT03 (Selection Code) and BCT09 (Selection Code Description) are required.

To replace Product attributes, BCT03 (Selection Code) and LIN Pair/VN (Product) are required.

To replace a GTIN, BCT03 (Selection Code), LIN Pair/VN (Product), and one of the LIN Pairs EN or UP (GTIN) are required.

Product name and GTIN identifier/qualifier cannot be changed in the existing record. To change them, delete the record, then re-add it with the new value(s). Additional constraints may be imposed by your configured compliance checks.


Ref. Des.



DTM Date/Time Reference


5

DTM Date/Time Reference Position: 070

Loop:

Level: Heading

Usage: Optional

Max Use: 11

Purpose: To specify pertinent dates and times

Syntax Notes:

Notes: One segment for each date. This Header-level segment will be used to specify the dates for all GTINs identified in the transaction. If a GTIN has a different date, the DTM segment at the Detail level will override the date for that GTIN only.

Inovis Note: OUTBOUND, all dates will be sent at the Detail level.

Validation Notes: 1. If provided, BOOKING DATE must precede AVAILABILITY DATE, which must precede DISCONTINUE DATE.

2. Date format must be CCYYMMDD.


Ref. Des.


M DTM01 374 Date/Time Qualifier M ID 3/3

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

018 Available

Inovis Attribute: AVAILABLE DATE. First available ship date. Implies nothing about current availability.

036 Expiration

Date coverage expires

Inovis Attribute: DISCONTINUE DATE

Caution must be exercised when deleting a GTIN from the catalogue. Due to ordering and shipping cycle times, a GTIN should reside on the catalogue as discontinued for at least one year after the last of the product has been shipped.


043 Publication (Outbound only)

DATE OF CHANGE. Date on which the data changed in Catalogue.

092 Contract Effective

Inovis Attribute: BOOKING DATE. Date the item is available for ordering, or first order date.




177 Cancellation

Date on which the coverage or service is no longer in force

Inovis Attribute: CANCEL DATE. Date the GTIN is canceled. For a GTIN to qualify for cancellation, it must never have been introduced into the supply chain, produced or shipped. If a GTIN does not meet these criteria, it must be discontinued (DTM01=036) rather than canceled.


M DTM02 373 Date M DT 8/8

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year


Ref. Des.



CUR Currency


5

CUR CurrencyPosition: 090

Loop:

Level: Heading

Usage: Optional

Max Use: 1

Purpose: To specify the currency (dollars, pounds, euros, etc.) used in a transaction

Syntax Notes:

Notes: Inovis Note: All prices are assumed to be in U.S. Dollars, unless otherwise specified in this segment. The use of this segment at the Header level indicates the currency for all prices in the transaction set.

This Header-level segment is also used to convey the attribute COMPANY CURRENCY, which is the company’s Account-level currency preference. A blank value can be sent for this attribute. To add or update COMPANY CURRENCY without sending catalogue data, use BCT10=04.

If no CUR segment is sent at the Header level, USD will be inserted by the system as the customer's currency unit of measure (UOM) for all prices in the transaction.


Ref. Des.


M CUR01 98 Entity Identifier Code M ID 2/3

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

SE Selling Party

M CUR02 100 Currency Code M ID 3/3

Code (Standard ISO) for country in whose currency the charges are specified

Inovis Attributes:

COMPANY CURRENCY

Inovis Note: Inovis Catalogue 2.0 vendors are restricted to the following COMPANY CURRENCY values: USD, CAD, EUR, GBP, MXN and blank/none.

Unit of Measure for UNIT COST and MANUFACTURER'S SUGGESTED RETAIL PRICE

ISO 4217 3-character Currency Codes:

USD U.S. Dollar (Default if no CUR is sent)

AED United Arab Emirates Dirham

AFA Afghani

ALL Albanian Lek

AMD Armenian Dram

ANG Netherlands Antillian Guilder

AOA Angolan Kwanza



CUR Currency

ARS Argentine Peso

AUD Australian Dollar

AWG Aruban Guilder

AZM Azerbaijanian Manat

BAM Bosnia and Herzegowina Convertible Marks

BBD Barbados Dollar

BDT Bangladesh Taka

BGL Bulgarian Lev

BHD Bahraini Dinar

BIF Burundi Franc

BMD Bermuda Dollar

BND Brunei Dollar

BOB Boliviano

BRL Brazilian Real

BSD Bahamian Dollar

BTN Bhutan Ngultrum

BWP Botswana Pula

BYR Belarussian Ruble

BZD Belize Dollar

CAD Canadian Dollar

CDF Franc Congolais

CHF Swiss Franc

CLP Chilean Peso

CNY Chinese Yuan Renminbi

COP Colombian Peso

CRC Costa Rican Colon

CUP Cuban Peso

CVE Cape Verde Escudo

CYP Cyprus Pound

CZK Czech Koruna

DJF Djibouti Franc

DKK Danish Krone

DOP Dominican Peso

DZD Algerian Dinar

EEK Estonian Kroon

EGP Egyptian Pound

ERN Eritrean Nakfa

ETB Ethiopian Birr

EUR Euro


Ref. Des.



CUR Currency


5

FJD Fiji Dollar

FKP Falkland Islands Pound

GBP British Pound Sterling

GEL Georgia Lari

GHC Ghanaian Cedi

GIP Gibraltar Pound

GMD Gambian Dalasi

GNF Guinea Franc

GTQ Guatemalan Quetzal

GWP Guinea-Bissau Peso

GYD Guyana Dollar

HKD Hong Kong Dollar

HNL Honduran Lempira

HRK Croatian Kuna

HTG Haitian Gourde

HUF Hungarian Forint

IDR Indonesian Rupiah

ILS Israeli New Shekel

INR Indian Rupee

IQD Iraqi Dinar

IRR Iranian Rial

ISK Iceland Krona

JMD Jamaican Dollar

JOD Jordanian Dinar

JPY Japanese Yen

KES Kenyan Shilling

KGS Kyrgyzstan Som

KHR Cambodian Riel

KMF Comoro Franc

KPW North Korean Won

KRW Korean Won

KWD Kuwaiti Dinar

KYD Cayman Islands Dollar

KZT Kazakhstan Tenge

LAK Lao Kip

LBP Lebanese Pound

LKR Sri Lanka Rupee

LRD Liberian Dollar

LSL Lesotho Loti


Ref. Des.




CUR Currency

LTL Lithuanian Litus

LVL Latvian Lats

LYD Libyan Dinar

MAD Moroccan Dirham

MDL Moldovan Leu

MGF Malagasy Franc

MKD Macedonian Denar

MMK Myanmar Kyat

MNT Mongolian Tugrik

MOP Macau Pataca

MRO Mauritanian Ouguiya

MTL Maltese Lira

MUR Mauritius Rupee

MVR Maldive Rufiyaa

MWK Malawi Kwacha

MXN Mexican Peso

MYR Malaysian Ringgit

MZM Mozambique Metical

NAD Namibian Dollar

NGN Nigerian Naira

NIO Nicaraguan Cordoba Oro

NOK Norwegian Krone

NPR Nepalese Rupee

NZD New Zealand Dollar

OMR Omani Rial

PAB Panamanian Balboa

PEN Peruvian Nuevo Sol

PGK Papua New Guinea Kina

PHP Philippine Peso

PKR Pakistan Rupee

PLN Polish Zloty

PYG Paraguay Guarani

QAR Qatari Rial

ROL Romanian Leu

RUR Russian Ruble

RWF Rwanda Franc

SAR Saudi Riyal

SBD Solomon Islands Dollar

SCR Seychelles Rupee


Ref. Des.



CUR Currency


5

SDD Sudanese Dinar

SEK Swedish Krona

SGD Singapore Dollar

SHP Saint Helena Pound

SIT Slovenian Tolar

SKK Slovak Koruna

SLL Sierra Leone

SOS Somali Shilling

SRG Suriname Guilder

STD Sao Tome and Principe Dobra

SVC El Salvador Colon

SYP Syrian Pound

SZL Swaziland Lilangeni

THB Thai Baht

TJS Tajikistan Somoni

TMM Turkmenistan Manat

TND Tunisian Dinar

TOP Tongan Pa'anga

TPE Timor Escudo

TRL Turkish Lira

TTD Trinidad and Tobago Dollar

TWD New Taiwan Dollar

TZS Tanzanian Shilling

UAH Ukraine Hryvnia

UGX Uganda Shilling

UYU Peso Uruguayo

UZS Uzbekistan Sum

VEB Venezuelan Bolivar

VND Vietnamese Dong

VUV Vanuatu Vatu

WST Samoan Tala

XAF CFA Franc BEAC

XCD East Caribbean Dollar

XDR SDR

XOF CFA Franc BCEAO

XPF CFP Franc

YER Yemeni Rial

YUM Yugoslavian Dinar

ZAR South African Rand


Ref. Des.




CUR Currency

ZMK Zambian Kwacha

ZWD Zimbabwe Dollar


Ref. Des.



N1 Name


5

N1 NamePosition: 150

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: 1

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

Syntax Notes: 1 At least one of N102 or N103 is required.

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

Notes: Inovis Note: When supported, values in the N1 loop at the Detail level override values provided at the Header level.

For COUNTRY OF ORIGIN (when N101=CT), you must use a 3-character ISO 3166-1 Country Code.

See also “Multiline Data Attributes” on page 14.

OUTBOUND: All values will be sent at the Detail level, except where N101=VN (general company information). In the case of N101= VN, values will be sent ONLY at the Header level.


Ref. Des.


M N101 98 Entity Identifier Code M ID 2/3


CT Country of Origin

Inovis Attribute: COUNTRY OF ORIGIN. Country where the product is manufactured.

Supported at both the Header and Detail levels.

N103=38 required. N104 will contain the country code.

Repeat the N1 segment up to three times, once for each country.

SF Ship From

Inovis Note: Supported at both the Header and Detail levels.

Use with N102 and the N104 segment to designate point of origin or shipping locations for GTINs.

At least one of SHIP FROM LOCATION NAME (N102) or SHIP FROM LOCATION CODE (N104) is required. If sending Name but not Code, do not include N103=91. "91" should only be included in N103 when sending a Ship From Location Code.

Repeat the N1 loop up to 15 times, once for each shipping location. Each set must be unique, and Ship From Location Code cannot be duplicated.



N1 Name

VN Vendor

Inovis Note: Supported at the Header level only. To add or update account attributes without sending catalogue data, use BCT10=04.

Include Company Name in N102. The value will not be stored in Inovis Catalogue, but it must be sent to meet the syntax requirement for the N1 segment.

Do not use N103 or N104 with this value.

Only one occurrence of the N1 loop is required to specify all of the company information attributes.

N102 93 Name O AN 1/40

Free-form name

Inovis Attributes:

When N101=SF, SHIP FROM LOCATION NAME (AN 1/40)

When N101= VN, include Company Name to satisfy syntax requirement for the N1 segment.

N103 66 Identification Code Qualifier O ID 1/2

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

Inovis Note: Not used when N101=L5 or VN.

38 Country Code

Inovis Note: Use when N101= CT.

91 Assigned by Seller or Seller's Agent

Inovis Note: Use when N101=SF, only when including a SHIP FROM LOCATION CODE in N104. Otherwise, this value should not be sent.

N104 67 Identification Code C AN 1/40

Code identifying a party or other code

Inovis Note: Not used when N101=VN.

N101=CT. Inovis Attribute: COUNTRY OF ORIGIN (AN 3/3). ISO 3166-1 Country Code List (see table that follows).

N101=SF. Inovis Attribute: SHIP FROM LOCATION CODE (AN 2/40). Vendor’s unique code for shipping location.


Ref. Des.



N1 Name


5

3-character ISO 3166-1 Country Codes

Code Country

AFG

ALB

DZA

ASM

AND

AGO

AIA

ATA

ATG

ARG

ARM

ABW

AUS

AUT

AZE

BHS

BHR

BGD

BRB

BLR

BEL

BLZ

BEN

BMU

BTN

BOL

BIH

BWA

BVT

BRA

IOT

BRN

BGR

BFA

BDI

KHM

CMR

CAN

CPV

CYM

CAF

TCD

CHL

CHN

AFGHANISTAN

ALBANIA

ALGERIA

AMERICAN SAMOA

ANDORRA

ANGOLA

ANGUILLA

ANTARCTICA

ANTIGUA AND BARBUDA

ARGENTINA

ARMENIA

ARUBA

AUSTRALIA

AUSTRIA

AZERBAIJAN

BAHAMAS

BAHRAIN

BANGLADESH

BARBADOS

BELARUS

BELGIUM

BELIZE

BENIN

BERMUDA

BHUTAN

BOLIVIA

BOSNIA AND HERZEGOWINA

BOTSWANA

BOUVET ISLAND

BRAZIL

BRITISH INDIAN OCEAN TERRITORY

BRUNEI DARUSSALAM

BULGARIA

BURKINA FASO

BURUNDI

CAMBODIA

CAMEROON

CANADA

CAPE VERDE

CAYMAN ISLANDS

CENTRAL AFRICAN REPUBLIC

CHAD

CHILE

CHINA



N1 Name

CXR

CCK

COL

COM

COG

COD

COK

CRI

CIV

HRV

CUB

CYP

CZE

DNK

DJI

DMA

DOM

TMP

ECU

EGY

SLV

GNQ

ERI

EST

ETH

FLK

FRO

FJI

FIN

FRA

GUF

PYF

ATF

GAB

GMB

GEO

DEU

GHA

GIB

GRC

GRL

GRD

GLP

GUM

CHRISTMAS ISLAND

COCOS (KEELING) ISLANDS

COLOMBIA

COMOROS

CONGO

CONGO, DEMOCRATIC REPUBLIC OF (ZAIRE)

COOK ISLANDS

COSTA RICA

COTE D'IVOIRE

CROATIA (LOCAL NAME: HRVATSKA)

CUBA

CYPRUS

CZECH REPUBLIC

DENMARK

DJIBOUTI

DOMINICA

DOMINICAN REPUBLIC

EAST TIMOR

ECUADOR

EGYPT

EL SALVADOR

EQUATORIAL GUINEA

ERITREA

ESTONIA

ETHIOPIA

FALKLAND ISLANDS (MALVINAS)

FAROE ISLANDS

FIJI

FINLAND

FRANCE

FRENCH GUIANA

FRENCH POLYNESIA

FRENCH SOUTHERN TERRITORIES

GABON

GAMBIA

GEORGIA

GERMANY

GHANA

GIBRALTAR

GREECE

GREENLAND

GRENADA

GUADELOUPE

GUAM


Code Country


N1 Name


5

GTM

GIN

GNB

GUY

HTI

HMD

HND

HKG

HUN

ISL

IND

IDN

IRN

IRQ

IRL

ISR

ITA

JAM

JPN

JOR

KAZ

KEN

KIR

PRK

KOR

KWT

KGZ

LAO

LVA

LBN

LSO

LBR

LBY

LIE

LTU

LUX

MAC

MKD

MDG

MWI

MYS

MDV

MLI

MLT

GUATEMALA

GUINEA

GUINEA-BISSAU

GUYANA

HAITI

HEARD AND MCDONALD ISLANDS

HONDURAS

HONG KONG

HUNGARY

ICELAND

INDIA

INDONESIA

IRAN (ISLAMIC REPUBLIC OF)

IRAQ

IRELAND

ISRAEL

ITALY

JAMAICA

JAPAN

JORDAN

KAZAKHSTAN

KENYA

KIRIBATI

KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF

KOREA, REPUBLIC OF

KUWAIT

KYRGYZSTAN

LAO PEOPLE'S DEMOCRATIC REPUBLIC

LATVIA

LEBANON

LESOTHO

LIBERIA

LIBYAN ARAB JAMAHIRIYA

LIECHTENSTEIN

LITHUANIA

LUXEMBOURG

MACAU

MACEDONIA, FORMER YUGOSLAV REPUBLIC OF

MADAGASCAR

MALAWI

MALAYSIA

MALDIVES

MALI

MALTA


Code Country



N1 Name

MHL

MTQ

MRT

MUS

MYT

MEX

FSM

MDA

MCO

MNG

MSR

MAR

MOZ

MMR

NAM

NRU

NPL

NLD

ANT

NCL

NZL

NIC

NER

NGA

NIU

NFK

MNP

NOR

OMN

PAK

PLW

PSE

PAN

PNG

PRY

PER

PHL

PCN

POL

PRT

PRI

QAT

REU

ROU

MARSHALL ISLANDS

MARTINIQUE

MAURITANIA

MAURITIUS

MAYOTTE

MEXICO

MICRONESIA, FEDERATED STATES OF

MOLDOVA, REPUBLIC OF

MONACO

MONGOLIA

MONTSERRAT

MOROCCO

MOZAMBIQUE

MYANMAR

NAMIBIA

NAURU

NEPAL

NETHERLANDS

NETHERLANDS ANTILLES

NEW CALEDONIA

NEW ZEALAND

NICARAGUA

NIGER

NIGERIA

NIUE

NORFOLK ISLAND

NORTHERN MARIANA ISLANDS

NORWAY

OMAN

PAKISTAN

PALAU

PALESTINIAN TERRITORY, OCCUPIED

PANAMA

PAPUA NEW GUINEA

PARAGUAY

PERU

PHILIPPINES

PITCAIRN

POLAND

PORTUGAL

PUERTO RICO

QATAR

REUNION

ROMANIA


Code Country


N1 Name


5

RUS

RWA

SHN

KNA

LCA

SPM

VCT

WSM

SMR

STP

SAU

SEN

SYC

SLE

SGP

SVK

SVN

SLB

SOM

ZAF

SGS

ESP

LKA

SDN

SUR

SJM

SWZ

SWE

CHE

SYR

TWN

TJK

TZA

THA

TGO

TKL

TON

TTO

TUN

TUR

TKM

TCA

TUV

UGA

RUSSIAN FEDERATION

RWANDA

SAINT HELENA

SAINT KITTS AND NEVIS

SAINT LUCIA

SAINT PIERRE AND MIQUELON

SAINT VINCENT AND THE GRENADINES

SAMOA

SAN MARINO

SAO TOME AND PRINCIPE

SAUDI ARABIA

SENEGAL

SEYCHELLES

SIERRA LEONE

SINGAPORE

SLOVAKIA (SLOVAK REPUBLIC)

SLOVENIA

SOLOMON ISLANDS

SOMALIA

SOUTH AFRICA

SOUTH GEORGIA AND SOUTH SANDWICH ISLANDS

SPAIN

SRI LANKA

SUDAN

SURINAME

SVALBARD AND JAN MAYEN ISLANDS

SWAZILAND

SWEDEN

SWITZERLAND

SYRIAN ARAB REPUBLIC

TAIWAN, PROVINCE OF CHINA

TAJIKISTAN

TANZANIA, UNITED REPUBLIC OF

THAILAND

TOGO

TOKELAU

TONGA

TRINIDAD AND TOBAGO

UNISIA

TURKEY

TURKMENISTAN

TURKS AND CAICOS ISLANDS

TUVALU

UGANDA


Code Country



N1 Name

UKR

ARE

GBR

USA

UMI

URY

UZB

VUT

VAT

VEN

VNM

VGB

VIR

WLF

ESH

YEM

YUG

ZMB

ZWE

UKRAINE

UNITED ARAB EMIRATES

UNITED KINGDOM

UNITED STATES

UNITED STATES MINOR OUTLYING ISLANDS

URUGUAY

UZBEKISTAN

VANUATU

VATICAN CITY STATE (HOLY SEE)

VENEZUELA

VIET NAM

VIRGIN ISLANDS (BRITISH)

VIRGIN ISLANDS (U.S.)

WALLIS AND FUTUNA ISLANDS

WESTERN SAHARA

YEMEN

YUGOSLAVIA

ZAMBIA

ZIMBABWE


Code Country


LIN Item Identification


5

LIN Item IdentificationPosition: 010

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To specify basic item identification data

Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required.

2 If either LIN06 or LIN07 is present, then the other is required.

3 If either LIN08 or LIN09 is present, then the other is required.

Notes: Inovis Note: Information pairs may be sent in any order, as long as the correct qualifier precedes the corresponding information in the next data element. LIN02 and LIN03 are always required, regardless of which qualifier is specified.

Up to 7 qualifier/data pairs may be sent for each LIN, but only one GTIN Type qualifier will be supported per item. Use only one of EN or UP with any combination of the other supported qualifiers: Product (VN), NRF (National Retail Federation) COLOR CODE (CM), NRF SIZE CODE (SM), Attempting to load multiple GTIN types for a single item will produce an error. See Appendix A, "GTIN Number Structures," on page 77 for GTIN qualifier structures.

OUTBOUND, data pairs will be sent in the order they appear in the guide below; empty delimiters may be sent if all attributes are not populated.

Validation Notes: If COLOR CODE or SIZE CODE is provided, COLOR DESCRIPTION or SIZE DESCRIPTION is required.


Ref. Des.


LIN01 350 Assigned Identification O AN 1/6

Alphanumeric characters assigned for differentiation within a transaction set

A sequential number assigned to each line item within the transaction starting with one.

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

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

VC Vendor's (Seller's) Catalogue Number

VN Vendor's (Seller's) Item Number

VENDOR PRODUCT IDENTIFIER as defined by the VICS EDI Trade Item Identification and Communication Guidelines. When adding a Product, do not use leading spaces.

Inovis Note: Format (AN 1/20)




M LIN03 234 Product/Service ID M AN 1/20

Identifying number for a product or service

Compliance Check: Restrictions may be applied by the following compliance checks:

■ 2.0 Compatibility

■ Prefix Validation (mandatory for vendors)

See “Compliance Checks” on page 15.

LIN04 235 Product/Service ID Qualifier O ID 2/2


Compliance Check: Restrictions may be applied by the following compliance checks:

■ 2.0 Compatibility

■ Prefix Validation (mandatory for vendors)

See “Compliance Checks” on page 15.

EN EAN/UCC - 13

Data structure for the 13 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN)

UP UCC - 12

Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN). Also known as the Universal Product Code (UPC)

Inovis Note: OUTBOUND, there is no restriction on a value that is not EN or UP. All 2-character values are sent.

LIN05 234 Product/Service ID C AN 12/13




CM National Retail Federation Color Code

Inovis Attribute: NRF COLOR CODE (N0 3/3)

Compliance Check: Restrictions may be applied by the GMA compliance check. See “Compliance Checks” on page 15.

LIN07 234 Product/Service ID C N0 3/3



Ref. Des.





5



SM National Retail Federation Size Code

Inovis Attribute: NRF SIZE CODE (N0 5/5)


LIN09 234 Product/Service ID C N0 5/5



Ref. Des.





DTM Date/Time ReferencePosition: 030

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 10

Purpose: To specify pertinent dates and times

Syntax Notes:

Notes: This segment is used to override the corresponding date at the Header level. These dates are only applicable to the GTIN identified in the preceding LIN segment.

Inovis Note: OUTBOUND, this segment (at the Detail level) will be used to communicate all dates.

Validation Notes: 1. If provided, BOOKING DATE must precede AVAILABILITY DATE, which must precede DISCONTINUE DATE.

2. Date format must be CCYYMMDD.


Ref. Des.Data Element Name Attributes

M DTM01 374 Date/Time Qualifier M ID 3/3

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

018 Available

Inovis Attribute: AVAILABLE DATE. First available ship date. Implies nothing about current availability.

036 Expiration

Date coverage expires

Inovis Attribute: DISCONTINUE DATE

Caution must be exercised when deleting a GTIN from the catalogue. Due to ordering and shipping cycle times, a GTIN should reside on the catalogue as discontinued for at least one year after the last of the product has been shipped.


043 Publication

DATE OF CHANGE. Date on which the data changed in Catalogue.

Inovis Note: OUTBOUND only. System-generated date specifying when Product or GTIN was last changed in Catalogue.

NOT SUPPORTED INBOUND FROM VENDORS.




5

092 Contract Effective

Inovis Attribute: BOOKING DATE. Date the item is available for ordering, or first order date.

177 Cancellation

Date on which the coverage or service is no longer in force

Inovis Attribute: CANCEL DATE. Date that GTIN is canceled. For a GTIN to qualify for cancellation, it must have never been introduced into the supply chain; it must not have been produced or shipped. If a GTIN does not meet these criteria, it must be discontinued (DTM01=036) rather than canceled.


M DTM02 373 Date M DT 8/8

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year


Ref. Des.Data Element Name Attributes



CTB Restrictions/Conditions

CTB Restrictions/ConditionsPosition: 060

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 3

Purpose: To specify restrictions/conditions (such as shipping, ordering)

Syntax Notes: 1 At least one of CTB02, CTB04, or CTB06 is required.

2 If either CTB03 or CTB04 is present, then the other is required.

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

Notes: Inovis Note: OUTBOUND, this segment (at the Detail level) will be used to communicate all ordering restrictions/conditions.


Ref. Des.


M CTB01 688 Restrictions/Conditions Qualifier M ID 2/2

Code identifying the type of restriction/condition

OR Ordering

M CTB03 673 Quantity Qualifier M ID 2/2

Code specifying the type of quantity

57 Minimum Order Quantity

Inovis Attribute: MINIMUM ORDER QUANTITY. Manufacturer imposed minimum order for item. Quantity will be provided in CTB04.

Inovis Format: N0 1/9

70 Maximum Order Quantity

Inovis Attribute: MAXIMUM ORDER QUANTITY. Manufacturer imposed maximum order for item. Quantity will be provided in CTB04.


M CTB04 380 Quantity M R 1/9

Numeric value of quantity


PID Product/Item Description


5

PID Product/Item DescriptionPosition: 070

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 50

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

Syntax Notes: 1 If PID04 is present, then PID03 is required.

2 At least one of PID04 or PID05 is required.

Notes: If PID01=F, then use PID05. If PID01=S, then use PID04.

Inovis Note: All attributes in this segment will be associated with the GTIN specified in the preceding LIN except for the following (when PID02=08):

PRODUCT DESCRIPTION

Only this attribute will be associated with the Product specified in the preceding LIN.

Validation Notes: COLOR DESCRIPTION or SIZE DESCRIPTION can be provided without COLOR CODE or SIZE CODE.


Ref. Des.


M PID01 349 Item Description Type M ID 1/1

Code indicating the format of a description

F Free-form

The description will be found in PID05.

Inovis Note: Use with PID02/05.

S Structured (From Industry Code List)

The description will be found in PID04.

Inovis Note: Use with PID03/04.

PID02 750 Product/Process Characteristic Code O ID 2/3

Code identifying the general class of a product or process characteristic

08 Product

Inovis Attribute:

PRODUCT DESCRIPTION. A meaningful description of the product represented in the preceding LIN. Use with PID05.

Compliance Check: Restrictions may be applied by the Product Description Uniqueness compliance check. See “Compliance Checks” on page 15.




73 Vendor color description

. Inovis Attribute:

COLOR DESCRIPTION. Text expression of GTIN color. Use with PID05.

Compliance Check: Restrictions may be applied by the GMA compliance check. See “Compliance Checks” on page 15

74 Vendor size description

Inovis Attribute:

SIZE DESCRIPTION. Text expression of GTIN size. Use with PID05.


92 Fabric Description

Inovis Attribute: FABRIC DESCRIPTION. Fabric content or description. Use with PID05.

TRN Trade Name

Inovis Attribute: TRADE NAME. Brand or label name for GTIN. Use with PID05.

WD Warranty Description

The warranty description for the final consumer, which the retailer needs to keep on file, in case the consumer has a claim against the warranty

Inovis Attribute: WARRANTY DESCRIPTION. Text description of warranty coverage and terms. Use with PID05.

PID03 559 Agency Qualifier Code O ID 2/2

Code identifying the agency assigning the code values

VI Voluntary Inter-Industry Commerce Standard (VICS) EDI

Inovis Note: Refer to PID04 for list of relevant attributes and supported codes for each.


Ref. Des.





5

PID04 751 Product Description Code C AN 2/10

A code from an industry code list which provides specific data about a product characteristic

PID03=VI.

For attribute SPECIAL ITEM CODE, acceptable values:

CL: Collateral as defined by the VICS EDI Trade Item Identification and Communication Guidelines

GW: Gift with purchase as defined by the VICS EDI Trade Item Identification and Communication Guidelines

PW: Purchase with purchase as defined by the VICS EDI Trade Item Identification and Communication Guidelines

Inovis Note: When using a SPECIAL ITEM CODE, you must include the code in all updates to the GTIN or the code will be cleared.

For attribute PREPACK/CONTAINER CODE, acceptable values:

MP: GTIN multipack as defined by the VICS EDI Trade Item Identification and Communication Guidelines

PC: Prepack subject to change (quantity of component items may vary)

PP: GTIN is sold only as a component of a prepack

PU: GTIN prepack as defined by the VICS EDI Trade Item Identification and Communication Guidelines

SP: GTIN setpack as defined by the VICS EDI Trade Item Identification and Communication Guidelines

If a GTIN is going to have component relationships assigned to it (see the SLN segment for additional instructions), it must have a prepack/container code of PC, PU, MP, or SP. Prepack/container designation must be indicated at the time the GTIN is first added to the Catalogue. Although the prepack/container designation may be changed from one of the prepack/container codes noted above (PP is not a container) to one of the others, assignment of a prepack/container code can not be added at a later time.

Any GTIN in the catalogue can be a component and requires no special indicator. However, if a GTIN is to be sold ONLY as part of a prepack, setpack, or packaging container, it should be designated with the code PP. This code should be provided in the PID04 when the GTIN is first added to the catalogue.

Compliance Check: Restrictions may be applied by the 2.0 Compatibility compliance check. See “Compliance Checks” on page 15.


Ref. Des.





PID Segment Structure TableThe table below indicates the correct structure for the PID segment based upon the attribute being sent. Each attribute requires a separate occurrence of the PID. “Value” indicates the element within the PID segment that will contain the actual attribute value. Refer to the PID segment detail above for attribute format requirements and lists of acceptable values, where appropriate.

For attribute ODD SIZE INDICATOR, acceptable value:

OS: Size not within normal size range (Odd Size). May be at a different price point than other GTINs with the same product identifier.

For attribute REORDERABLE PRODUCT, acceptable values:

RN: GTIN cannot be reordered - does not imply any information on current availability.

RY: GTIN can be reordered - does not imply any information on current availability.

For attribute SEASONAL AVAILABLITY, acceptable values:

SN: Seasonal GTIN currently not available

SY: Seasonal GTIN currently available

PID05 352 Description C AN 1/80


Inovis Note: When using PID05, PID01 and PID02 must also be present.

PID02=08, PRODUCT DESCRIPTION (AN 1/25)

PID02=73, COLOR DESCRIPTION (AN 1/10)

PID02=74, SIZE DESCRIPTION (AN 1/10)

PID02=92, FABRIC DESCRIPTION (AN 1/40)

PID02=TRN, TRADE NAME, (AN 1/25)

PID02=WD, WARRANTY DESCRIPTION (AN 1/80)

Attribute PID01 PID02 PID03 PID04 PID05

Product Description F 08 Value

Color Description F 73 Value

Size Description F 74 Value

Fabric Description F 92 Value

Trade Name F TRN Value


Ref. Des.





5

Warranty Description F WD Value

Prepack Item Code S VI Value

Special Item Code S VI Value

Reorderable Product S VI Value

Seasonal Availability S VI Value

Odd Size Indicator S VI Value

Attribute (Continued) PID01 PID02 PID03 PID04 PID05



TD4 Carrier Details (Special Handling and Hazardous Materials)

TD4 Carrier Details (Special Handling and Hazardous Materials)Position: 110

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 10

Purpose: To specify transportation special handling requirements, or hazardous materials information, or both

Syntax Notes: 1 At least one of TD402 or TD404 is required.

2 If TD402 is present, then TD403 is required.

Notes: Inovis Note: One SPECIAL HANDLING CODE and a single occurrence of HAZARDOUS MATERIALS CLASS CODE and HAZARDOUS MATERIAL DESCRIPTION can be provided in each occurrence of the TD4.

Validation Notes: If one of HAZARDOUS MATERIALS CLASS CODE or HAZARDOUS MATERIALS DESCRIPTION is provided, the other is required.

When specifying International Fire Code Institute class code designations, TD402 and TD403 will not be used, and TD404 will contain the text class code designation. Contact the International Fire Code Institute for a list of class code designations: Internal Fire Code Institute 5360 Workman Mill Road Whittier, CA 90601-2298.

This segment may also be used to specify the Department of Transportation coed and description for hazardous materials.

Inovis Note: Maximum use is 1 per LIN for the Inovis Catalogue.


Ref. Des.

Data Element Name Attribute

TD402 208 Hazardous Material Code Qualifier O ID 1/1

Code which qualifies the Hazardous Materials Class Code (209)

Inovis Note: Use when TD403 specifies the HAZARDOUS MATERIALS CLASS CODE and TD404 the HAZARDOUS MATERIAL DESCRIPTION.

If one of Hazardous Materials Class Code or Description is provided, both are required. Up to five occurrences of Code and Description are allowed. Repeat the TD4 segment up to five times, once for each occurrence.

D Hazardous Materials ID, DOT

TD403 209 Hazardous Material Class Code C AN 1/4

Code specifying the kind of hazard for a material

Inovis Attribute: HAZARDOUS MATERIALS CLASS CODE. Hazardous materials identification code per the U.S. Department of Transportation (DOT). Denotes that contents are hazardous materials and what type.


TD4 Carrier Details (Special Handling and Hazardous Materials)


5

TD404 352 Description C AN 1/40


Inovis Attribute: HAZARDOUS MATERIAL DESCRIPTION. Text expression of U.S. DOT Hazardous Materials Code.


Ref. Des.




LDT Lead Time

LDT Lead TimePosition: 140

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To specify lead time for availability of products and services


Ref. Des.Data Element Name Attribute

M LDT01 345 Lead Time Code M ID 2/2

Code indicating the time range

AE From date of PO receipt to shipment

M LDT02 380 Quantity M R 1/3

Numeric value of quantity of “unit of time periods”

Inovis Attribute: LEAD TIME. Estimated time from receipt of purchase order to shipment.


M LDT03 344 Unit of Time Period or Interval M ID 2/2

Code indicating the time period or interval

DA Calendar Days

DW Work Days

Inovis Note: OUTBOUND, there is no restriction on a value that is not DA or DW. All 2-character values are sent.


TC2 Commodity


5

TC2 CommodityPosition: 165

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 2

Purpose: To identify a commodity or a group of commodities or a tariff page commodity

Syntax Notes:

Notes: Inovis Note: Due to restrictions within the 832, only two occurrences of the TC2 segment may be sent. Inovis can only store two of the four attributes supported in the TC2 segment for each GTIN.


Ref. Des.


M TC201 23 Commodity Code Qualifier M ID 1/1

Code identifying the commodity coding system used for Commodity Code

J Harmonized System-Based Schedule B

Classification of exported merchandise

N National Motor Freight Classification (NMFC)

Q Quota Category

M TC202 22 Commodity Code M AN 1/10

Code describing a commodity or group of commodities

Inovis Attributes:

When TC201=J, HARMONIZED SYSTEM BASED SCHEDULE B (N0 6/10)

When TC201=N, NATIONAL MOTOR FREIGHT CLASSIFICATION (NMFC) (N0 8/8)

When TC201=Q, QUOTA CATEGORY (N0 6/6)



G55 Item Characteristics - Consumer Unit

G55 Item Characteristics - Consumer UnitPosition: 168

Loop: LIN Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To provide physical characteristics relative to a consumer unit

Syntax Notes: 1 If either G5503 or G5504 is present, then the other is required.

2 If either G5505 or G5506 is present, then the other is required.





7 If any of G5523, G5524, or G5525 is present, then all are required.

Notes: Use this segment to provide physical characteristics relative to a consumer selling unit.

Specify the dimensions of the consumer unit by using G5505 through G5510. Linear dimensions must be in the same unit of measure.

Specify the weight of the consumer unit using G5523/24/25.

Specify the volume (cube) of the consumer unit using G5511 and G5512.

Inovis Note: The qualifier/data pair in G5501/02 must match the GTIN specified in the preceding LIN segment.


Ref. Des.


M G5501 235 Product/Service ID Qualifier M ID 2/2


EN EAN/UCC - 13


UP UCC - 12


Inovis Note: OUTBOUND, there is no restriction on a value that is not EN or UP. All 2-character values are sent.

M G5502 234 Product/Service ID M AN 1/14





5

Inovis Note: Must be the same as GTIN specified in the preceding LIN segment.

G5505 65 Height O R 1/8

Vertical dimension of an object measured when the object is in the upright position

Inovis Attribute: CONSUMER PACKAGE HEIGHT (R 1/8,3)

G5506 355 Unit or Basis for Measurement Code C ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

FT Foot

IN Inch

MM Millimeter

MR Meter

YD Yard

G5507 189 Width O R 1/8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

Inovis Attribute: CONSUMER PACKAGE WIDTH (R 1/8,3)



Inovis Note: Refer to G5506 for list of acceptable values.

G5509 82 Length O R 1/8

Largest horizontal dimension of an object measured when the object is in the upright position

Inovis Attribute: CONSUMER PACKAGE LENGTH (R 1/8,3)



Inovis Note: Refer to G5506 for list of acceptable values.

G5511 183 Volume O R 1/8

Value of volumetric measure

Inovis Attribute: CONSUMER PACKAGE VOLUME (cube) (R 1/8,3)



CC Cubic Centimeter

CF Cubic Feet

CI Cubic Inches

CR Cubic Meter

CY Cubic Yard

GA Gallon


Ref. Des.





LT Liter

ML Milliliter

PT Pint

QT Quart

G5514 357 Size O R 1/8

Size of supplier units in pack

Inovis Attribute: CONSUMER PACKAGE SIZE. Identifies the size of a consumer package by its most common measure (usually a measure of weight, volume, or the number of items in the package). Should be specified as G5514=1 and G5515=EA for all trade items packaged as singles. (R 1/8,3)



12 Packet

15 Stick

AF Centigram

A unit of metric weight equal to 0.01 gram or 0.000035 ounce

AS Assortment

AV Capsule

A compact metallic or plastic container for liquids or solids

BG Bag

BI Bar

A centimeter-gram-second unit of pressure, equal to one million dynes per square centimeter

BO Bottle

BR Barrel

BU Bushel

32 dry quarts

BX Box

C3 Centiliter

CA Case

CC Cubic Centimeter

CF Cubic Feet

CH Container

CI Cubic Inches

CM Centimeter

CN Can

CR Cubic Meter


Ref. Des.





5

CT Carton

CU Cup

CY Cubic Yard

DG Decigram

DL Deciliter

DM Decimeter

DS Display

DZ Dozen

EA Each

EP Eleven pack

FO Fluid Ounce

FT Foot

GA Gallon

GR Gram

GS Gross

HC Hundred Count

HD Half Dozen

HL Hundred Feet - Linear

IN Inch

JR Jar

KE Keg

A unit of weight equal to 100 pounds, used for nails

KG Kilogram

LB Pound

LT Liter

ME Milligram

ML Milliliter

MM Millimeter

MR Meter

OP Two pack

OZ Ounce - Av

P3 Three pack

P4 Four-pack

P5 Five-pack

P6 Six pack

P7 Seven pack

P8 Eight-pack

P9 Nine pack

PC Piece


Ref. Des.





PK Package

PL Pallet/Unit Load

PR Pair

PT Pint

PY Peck, Dry U.S.

QT Quart

RL Roll

ST Set

TH Thousand

TP Ten-pack

U2 Tablet

A compressed or molded block of solid material; a collection of sheet paper glued together at one edge

YD Yard

G5523 395 Unit Weight O R 1/8

Numeric value of weight per unit

Inovis Attribute: CONSUMER PACKAGE WEIGHT. Gross weight of the consumer package. (R 1/8,3)

G5524 187 Weight Qualifier C ID 1/2

Code defining the type of weight

G Gross Weight

G5525 188 Weight Unit Code C ID 1/1

Code specifying the weight unit

L Pounds

O Ounces


Ref. Des.



CTP Pricing Information


5

CTP Pricing InformationPosition: 170

Loop: CTP Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To specify pricing information

Syntax Notes:


Ref. Des.Data Element Name Attribute

M CTP02 236 Price Identifier Code O ID 3/3

Code identifying pricing specification

CAT Catalogue Price

Inovis Attribute: UNIT COST. Standard wholesale cost of an item. Used for Inbound.

MSR Manufacturer's Suggested Retail

Inovis Attribute: MANUFACTURER’S SUGGESTED RETAIL PRICE. Price that is printed on ticket identified as suggested retail.

UCP Unit cost price

Inovis Attribute: UNIT COST. Standard wholesale cost of an item. Used for Inbound and Outbound.

M CTP03 212 Unit Price O R 1/17

Price per unit of product, service, commodity, etc.

The price is sent with a decimal point only when need, for example, $15.95 would be sent as "15.95", and $29.00 would be sent as "29".

Inovis Attributes:

When CTP02=CAT, UNIT COST

When CTP02=UCP, UNIT COST

When CTP02=MSR, MANUFACTURER'S SUGGESTED RETAIL PRICE

Inovis Format: R 1/17,4



N1 Name

N1 NamePosition: 230

Loop: N1 Optional

Level: Detail

Usage: Optional

Max Use: 1

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

Syntax Notes: 1 At least one of N102 or N103 is required.

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

Notes: Inovis Note: Values in the N1 loop at the Detail Level override values provided at the Header Level.

See “Multiline Data Attributes” on page 14.

OUTBOUND, this segment (at the Detail Level) will be used to communicate the country of origin attribute.


Ref. Des.


M N101 98 Entity Identifier Code M ID 2/3


CT Country of Origin

Inovis Attribute: COUNTRY OF ORIGIN. Country where the product is manufactured.

N103=38 required. N104 will contain the country code.

Repeat the N1 segment up to three times, once for each country.

N102 93 Name O AN 1/40

Free-form name

N103 66 Identification Code Qualifier C ID 1/2

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

38 Country Code

Inovis Note: Use when N101=CT.

N104 67 Identification Code C AN 1/40

Code identifying a party or other code

N101=CT – Inovis Attribute: COUNTRY OF ORIGIN (AN 3/3). ISO 3166-1 3-character Country Code List. Refer to Header Level N104 for list of acceptable country codes


SLN Subline Item Detail


5

SLN Subline Item DetailPosition: 350

Loop: SLN Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To specify product subline detail item data

Syntax Notes: 1 If either SLN04 or SLN05 is present, then the other is required.

2 If either SLN09 or SLN10 is present, then the other is required.

Notes: IMPORTANT: The SLN segment is supported INBOUND ONLY for this release. Use qXML request/response to extract component data from Inovis Catalogue.

To add a component to a container already containing components, send only the new components. Existing components are not omitted by this action, so do not send them again.

To change a component’s quantity or UOM you must remove the component from the container, then add it to the container again with the corrected information.

To delete a component, the GTIN container must already exist in the catalogue. Do not send a delete component request (SLN03=D) if you are adding the container GTIN in the LIN.

Prepacks, setpacks, and packaging containers are identified in the LIN segment. To specify the contents of a packaging container, use the SLN segment with code I in SLN03. When changing the contents of an existing packaging container, use SLN03=D or I to delete an existing GTIN from or include a new GTIN in the packaging container, respectively.

The SLN segment cannot be used to add GTINs to the catalogue. GTINs to be included as part of a prepack, setpack or other packaging container must have already been added to the catalogue, either in a previous LIN or a previous transaction.

Up to 100 component GTINs are supported per container.

For a GTIN to accept component relationship assignments, it must have a prepack/container code of MP, PC, PU, or SP. This includes master and inner packs. Prepack designation must be indicated at the time the GTIN is first added to the Catalogue. Refer to the PID segment, specifically the PID04, for further instructions.

No more than three total levels of packaging containment may exist in the Catalogue. This means that a container may have another container as a component, but that container may not have other containers as components. In other words, the GTINs at the lowest level of a three-level packaging hierarchy may not have a prepack/container code of MP, PC, PU, or SP.



SLN Subline Item Detail


Ref. Des.


M SLN01 350 Assigned Identification M AN 1/20

Alphanumeric characters assigned for differentiation within a transaction set

M SLN03 662 Relationship Code M ID 1/1

Code indicating the relationship between entities

D Delete

I Included

PREPACK/SETPACK/CONTAINER Breakdown. Each component GTIN is represented by: (1) its GTIN; (2) the quantity of this GTIN in the prepack/setpack/container.

SLN04 380 Quantity O R 1/5

Numeric value of quantity

The quantity of the GTIN identified in SLN09/10 that is contained in the prepack/setpack (assortment) identified in the LIN segment.

Do not use when SNL03=D. Format: N0 1/5.

SLN05 355 Unit or Basis for Measurement Code M ID 2/2


EA Each

M SLN09 235 Product/Service ID Qualifier M ID 2/2


EN EAN/UCC - 13


UP UCC - 12


M SLN10 234 Product/Service ID M AN 1/48

IIdentifying number for a product or service


CTT Transaction Totals


5

CTT Transaction TotalsPosition: 010

Loop:

Level: Summary

Usage: Mandatory

Max Use: 1

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


Ref. Des.


M CTT01 354 Number of Line Items M R 1/6

Total number of line items in the transaction set

The number of LIN segments present in the transaction set.

Format: N0 1/6.



SE Transaction Set Trailer

SE Transaction Set TrailerPosition: 020

Loop:

Level: Summary

Usage: Mandatory

Max Use: 1

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


Ref. Des.


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

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

Format: N0 1/10.

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

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

This must be the same number as is in the ST segment (ST02) for the transaction set.

75

Samples 6his chapter presents a Inovis Catalogue 832 sample document.

This sample is provided solely for assistance with formatting the EDI document, including segments and data elements. This sample includes some of the supported

EDI attributes, at both the header and detail levels. For this reason, the following sample would not necessarily pass EDI translation or Inovis Catalogue validation rules.

ISA*00* *00* *12*5102155000 *12*8008728255 *040201*1459*U*00401*000000001*0*T*>-GS*SC*5102155500*8008728255*20040201*1615*1*X*004010-ST*832*0001-BCT*RC*125102155000*100******MISSES COLLECTION*02-DTM*018*20040315-DTM*036*20201231-DTM*092*20040301-DTM*043*20040215-CUR*SE*USD-N1*CT**38*GBR-N1*CT**38*USA-N1*CT**38*CAN-N1*SF*NORTHERN CA DC*91*1001-N1*VN*SAMPLE VENDOR-LIN*01*VN*PROD12345*UP*444444000019*CM*100*SM*10985-DTM*018*20040315-DTM*036*20201231-DTM*092*20040301-CTB*OR**57*100-CTB*OR**70*2000-PID*F*08***SILK DRESS-PID*F*73***HEATHER GR-PID*F*74***SIZE 8-PID*F*92***100% COTTON-PID*F*TRN***ELEGANT MISS-PID*F*WD***WARRANTIED AGAINST MFG DEFECTS FOR 1 YEAR-PID*S**VI*MP-PID*S**VI*PW-PID*S**VI*RN-PID*S**VI*SY-PID*S**VI*OS-TD4**D*1004*HAZ MATERIAL DESC 1-LDT*AE*5*DA-TC2*J*8760954321-TC2*N*12345678-G55*UP*444444000019***40*IN*10*IN*1.5*IN*600*CI**1*EA********3*G*L-CTP**MSR*100000-CTP**UCP*12-

T


S A M P L E S

N1*CT**38*SGP-SLN*1**I*10*EA****UP*44444000033-CTT*1-SE*41*0001-GE*1*1-IEA*1*000000001-

77

GTIN Number Structures A

he following are the required number structures for GTIN types supported by Inovis Catalogue 4.x. The GS1 (formerly EAN.UCC) Company Prefix and Item or Case Reference identifiers can be of varying length, which is indicated in the diagrams

below by arrows.

Note: GTIN Type must be upper case.

The following are the number structures for GTIN types supported by Inovis Catalogue.

UP: UCC-12 (UPC Consumer Package Code)

Primary GTIN type used in North America. Typically used for a consumer unit. A UPC is a 12-digit Universal Product Code that uniquely identifies a consumer unit. It uses Modulo-10 calculation.

EN: EAN/UCC-13 (European Article Number)

Primary GTIN type used outside of North America. Typically used for a consumer unit. This EAN is a 13-digit code that uniquely identifies a consumer unit. It uses Modulo-10 calculation.

Code Description

UP UCC-12 (12-digit UPC Consumer Package Code)

EN EAN/UCC-13 (13-digit European Article Number)

EO EAN/UCC-8 (8-digit European Article Number) (not supported by v4010)

UK EAN/UCC-14 (14-digit Shipping Container Code) (not supported by v4010)

Number System Character

UCC Company Prefix Item Reference Check Digit

N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12

Country Code Prefix

EAN.UCC Prefix Item Reference Check Digit

N1 N2 N3 N4 N5 N6 N7 N8 N9N10 N11 N12 N13

T


G T I N N U M B E R S T R U C T U RE S

EO: EAN/UCC-8 (European Article Number)

Note: Not supported by v4010 of the ANSI X12 EDI standards.

Used outside of North America. Can be either a vendor- or consumer-sellable unit. This EAN is an 8-digit code used to identify a consumer unit. Assigned directly by the EAN Member Organization of that country for products that have limited barcode space. It uses Modulo-10 calculation.

UK: EAN/UCC-14 (Shipping Container Code)

Note: Not supported by v4010 of the ANSI X12 EDI standards.

Vendor sellable only. A EAN/UCC Shipping Container Code is a 14-digit code that uniquely identifies the manufacturer’s shipping unit (case, module, or pallet), i.e., the product and package quantity. Previously also known as SCC-14. It uses Modulo-10 calculation.

For more information, visit the Uniform Code Council website at www.uc-council.org

Country Code Prefix EAN.UCC-8 Prefix and Item Reference

Check Digit

N1 N2 N3 N4 N5 N6 N7 N8

Packaging Indicator

Number System Character

EAN.UCC Prefix Case Reference Check Digit

N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11N12 N13 N14

http://www.uc-council.org

79

Check Digit Calculations B

novis Catalogue uses the following formula to calculate the check digit (for example, the last digit) of a GTIN. It is the formula used by GS1 US (formerly, the Uniform Code Council (UCC)). To use this formula, all digits except the check digit must already be

known.

Note: Use the GS1 US Web-based Check Digit Calculator to quickly find a check digit. Click the following link:

http://www.uc-council.org/checkdig.htm

Sample: Check digit calculation for the 13-digit EAN/UCC field

In the sample, the check digit is 3. The full GTIN is thus 6291041500213.

GTIN Type Digit Positions

EAN/UCC-8 (not supported by v4010)

N1 N2 N3 N4 N5 N6 N7 N8

UCC-12 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12

EAN/UCC-13 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13

EAN/UCC-14 (not supported by v4010)

N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14

Step 1: Multiply value of each position by:

x3 x1 x3 x1 x3 x1 x3 x1 x3 x1 x3 x1 x3

Step 2: Add the results to determine the sum

Step 3: Subtract sum from the next highest multiple of ten to determine the check digit

Digit Positions N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13

GTIN without check digit 6 2 9 1 0 4 1 5 0 0 2 1

Step 1: Multiply x1 x3 x1 x3 x1 x3 x1 x3 x1 x3 x1 x3

Step 2: Add results 6 6 9 3 0 12 1 15 0 0 2 3 = 57

Step 3: Subtract sum from next highest multiple of ten (60) to determine the check digit (3): 60-57=3

GTIN with check digit 6 2 9 1 0 4 1 5 0 0 2 1 3

I

http://www.uc-council.org/checkdig.htm


C H E C K D I G I T C A L C U L A T I O N S

Sample: Check digit calculation for the 13-digit EAN/UCC field

81

Attribute Locations C

he following table lists all supported data attributes in Inovis Catalogue and their EDI 832 element locations. More information about data attributes is available in the Inovis Catalogue Attributes Guide.

In the table below, columns from left indicate:

■ UI Display Name—Attribute name as it appears in the browser interface

■ Format and Validation:

■ CHAR—Alphanumeric value; number indicates maximum number of characters (if applicable, a list of acceptable values for the attribute appears in mapping guidelines)

■ NUMBER—Numeric value; one number indicates maximum number of digits, no decimal allowed; second number, if any, indicates maximum number of digits to right of decimal

■ DATE—CCYYMMDD is only allowable date format

■ UOM – “0” = no UOM for the attribute; “EA” = Each; “LIST” = attribute requires UOM value from list of acceptable values in mapping guidelines.

■ Multiline – “0” = attribute is not multiline; number = attribute is multiline (where number indicates maximum number of iterations allowed); * = the UNIT COST and MSRP attributes are sent in the CTP segment. The CTP loop allows up to 100 occurrences, so the maximum number of UNIT COST and MSRP occurrences combined in an 832 is 100 (for example, 95 UNIT COSTs and 5 MSRPs).

■ 832 Locations – EDI 832 element locations of the attribute and its dependencies

■ 4010 – Catalogue attributes supported by EDI 832 v4010. Catalogue supports v4010 for inbound and outbound.

■ 4030 – Catalogue attributes supported by EDI 832 v4030. Catalogue supports v4030 for inbound and outbound.

UI Display Name Format and Validation UOM

Multi Line 832 Locations 4010 4030

Vendor Name CHAR(25) 0 0 N101(VN) N102 x x

Vendor Account ID CHAR(13) 0 0 ISA05/06 GS02 BCT02 x x

Company Currency CHAR(3) 0 0 Header - CUR01(SE) CUR02 x x

Company Address CHAR(55) 0 0 N101(VN) N301 x

T


A T T R I B U T E L O C A T I O N S

Company Address Line 2 CHAR(55) 0 0 N101(VN) N302 x

Company City CHAR(30) 0 0 N101(VN) N401 x

Company State or Province CHAR(2) 0 0 N101(VN) N402 x

Company ZIP or Postal Code CHAR(15) 0 0 N101(VN) N403 x

Company Country CHAR(3) 0 0 N101(VN) N404 x

Company Telephone Number NUMBER(20) 0 0 N101(VN) PER01(OS) PER(TE) Pair x

Company Facsimile Number NUMBER(20) 0 0 N101(VN) PER01(OS) PER(FX) Pair x

Company E-Mail Address CHAR(40) 0 0 N101(VN) PER01(OS) PER(EM) Pair x

Company Internet URL CHAR(80) 0 0 N101(VN) REF01(URL) REF03 x

Primary Contact Name CHAR(60) 0 0 N101(L5) PER01(IC) PER02 x

Primary Contact Telephone Number

NUMBER(20) 0 0 N101(L5) PER01(IC) PER(TE) Pair x

Primary Contact Facsimile Number

NUMBER(20) 0 0 N101(L5) PER01(IC) PER(FX) Pair x

Primary Contact E-Mail Address

CHAR(40) 0 0 N101(L5) PER01(IC) PER(EM) Pair x

Secondary Contact Name CHAR(60) 0 0 N101(L5) PER01(AL) PER02 x

Secondary Contact Telephone Number

NUMBER(20) 0 0 N101(L5) PER01(AL) PER(TE) Pair x

Secondary Contact Facsimile Number

NUMBER(20) 0 0 N101(L5) PER01(AL) PER(FX) Pair x

Secondary Contact E-Mail Address

CHAR(40) 0 0 N101(L5) PER01(AL) PER(EM) Pair x

Backup Contact Name CHAR(60) 0 0 N101(L5) PER01(CN) PER02 x

Backup Contact Telephone Number

NUMBER(20) 0 0 N101(L5) PER01(CN) PER (TE) Pair x

Backup Contact Facsimile Number

NUMBER(20) 0 0 N101(L5) PER01(CN) PER (FX) Pair x

Backup Contact E-Mail Address CHAR(40) 0 0 N101(L5) PER01(CN) PER (EM) Pair x

Global Location Number NUMBER(13) 0 0 Header - N101(VN) N103(UL) N104 x

Selection Code NUMBER(3) 0 0 BCT03 x x

Selection Code Description CHAR(25) 0 0 BCT09 x x

Product CHAR(20) 0 0 LIN(VC) Pair x

Product CHAR(20) 0 0 LIN(VN) Pair x x

Product Description CHAR(25) 0 0 PID01(F) PID02(08) PID05 x x

Product Extended Description CHAR(40) 0 0 PID01(X) PID02(08) PID03(VI) PID04(ED) PID05

x

UI Display Name (Continued)Format and Validation UOM




C

GTIN NUMBER(14) 0 0 LIN (EN/EO/UK//UP) (Pair x

GTIN NUMBER(14) 0 0 LIN (EN/UP/)Pair x x

Trading Partner Allowed for Private Item

NUMBER(13) 0 10 Detail - REF01(RAN) REF02 x

Discontinue Date DATE 0 0 DTM01(036) DTM02 x x

Cancel Date DATE 0 0 DTM01(177) DTM02 x x

Effective Date of Change DATE 0 0 Header and Detail

DTM01(152) DTM02

x

Publication Date DATE 0 0 Header and Detail

DTM01(440) DTM02

x

Booking Date (Item Effective Date)

DATE 0 0 DTM01(092) DTM02 x x

Available Date DATE 0 0 DTM01(018) DTM02 x x

End Availability Date DATE 0 0 Header and Detail

DTM01(604) DTM02

x

Consumer Availability Date DATE 0 0 Header and Detail

DTM01(614) DTM02

x

Shelf Life Expiration Date DATE 0 0 DTM01(511) DTM02 x

Item Marked with Expiration Date, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(MARKEXPDATE) x

Shelf Life (Days) NUMBER(4) LIST 0 MEA01(TI) MEA02(SHA) MEA03 x

Unit Cost NUMBER(17,4) LIST * CTP02(CAT) CTP03 - CTP02 (UCP) Loop

x

Unit Cost NUMBER(17,4) LIST * CTP02(UCP) CTP03 - CTP02 (UCP) Loop

x x

Unit Cost Effective Date DATE 0 * DTM01(196) DTM02 - CTP Loop x

Unit Cost Expiration Date DATE 0 * DTM01(197) DTM02 - CTP Loop x

Manufacturer's Suggested Retail Price

NUMBER(17,4) LIST * CTP02(MSR) CTP03 - CTP02 (MSR) Loop

x x

Suggested Retail Price Effective Date

DATE 0 * DTM01(196) DTM02 - CTP Loop x

Suggested Retail Price Expiration Date

DATE 0 * DTM01(197) DTM02 - CTP Loop x

Retail Price on Trade Item NUMBER(17,4) LIST 5 Detail - CTP02(RTL) CTP03 x

GTIN Description CHAR(30) 0 0 PID01(F) PID02(GEN) PID05 x

GTIN Extended Description CHAR(80) 0 0 PID01(X) PID02(GEN) PID03(VI) PID04(ED) PID05

x





Cash Register Description CHAR(20) 0 0 G5516 x

Set Pieces NUMBER(20) 0 0 REF01(SJ) REF02 x

Prepack/Container Code CHAR(2) 0 0 PID01(S) PID03 (VI) PID04 (PP, PU, PC, SP, MP)

x x

Prepack/Container Code CHAR(2) 0 0 PID01(S) PID03 (VI) PID04 (CA, DS, IP, MP, MX, PC, PL, PP, PU, SP)

x

Special Item Code CHAR(2) 0 0 PID01(S) PID03 (VI) PID04 (CL, GW, PW)

x x

Item Not for Resale, Y/N CHAR(1) 0 0 YNQ02 YNQ10(NORESALE) x

Base Unit, Y/N CHAR(1) 0 0 YNQ02 YNQ10(BU) x

Consumer Unit, Y/N CHAR(1) 0 0 YNQ02 YNQ10(CU) x

Despatch/Shipping Unit Y/N CHAR(1) 0 0 YNQ02 YNQ10(DU) x

Invoice Unit, Y/N CHAR(1) 0 0 YNQ02 YNQ10(IU) x

Orderable Unit, Y/N CHAR(1) 0 0 YNQ02 YNQ10(OU) x

Variable Unit Y/N CHAR(1) 0 0 YNQ02 YNQ10(VU) x

Sub Brand CHAR(35) 0 0 PID01(F) PID02(09) PID05 x

NRF Color Code NUMBER(3) 0 0 LIN(CM) Pair x x

Color Description CHAR(10) 0 0 PID01(F) PID02(73) PID05 x x

Color Extended Description CHAR(25) 0 0 PID01(X) PID02(73) PID03(VI) PID04(ED) PID05

x

Primary Pantone Color Code NUMBER(6) 0 0 LIN(VE) Pair x

Pantone Accent Color Code 1 NUMBER(6) 0 0 PID01(X) PID03(94) PID04(PA1) PID05 x




NRF Size Code NUMBER(5) 0 0 LIN(SM) Pair x x

Size Description CHAR(10) 0 0 PID01(F) PID02(74) PID05 x x

Size Extended Description CHAR(25) 0 0 PID01(X) PID02(74) PID03(VI) PID04(ED) PID05

x

Trade Name CHAR(25) 0 0 PID01(F) PID02(TRN) PID05 x x

Model Name/Number CHAR(25) 0 0 LIN(MN) Pair x

Replaced Item Number NUMBER(14) LIST 0 SLN03(S) SLN10 x x

Replaced Item Number NUMBER(14) LIST 0 G5530 or

G3924 or

SLN03(S) SLN10

x





C

Fast Moving Consumer Goods Item Number

NUMBER(35) LIST 0 LIN(IS) Pair or LIN(IB) Pair x

Marked with Batch Number, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(BATCHNUM) x

Manufacturer of Goods CHAR(25) 0 0 N101(MF) N102 x

Manufacturer’s GLN NUMBER(13) 0 0 Header and Detail

N101(MF) N103(UL) N104

x

Manufacturer Internet URL CHAR(80) 0 0 N101(MF) REF01(URL) REF03 x

Information Provider’s GLN NUMBER(13) 0 0 Detail - N101(HQ) N103(UL) N104 x

Information Provider’s Name CHAR(13) 0 0 Detail - N101(HQ) N102 x

Brand Owner’s GLN NUMBER(13) 0 0 Detail - N101(BRN) N103(UL) N104 x

Brand Owner’s Name CHAR(13) 0 0 Detail - N101(BRN) N102 x

Brand Type CHAR(25) 0 0 PID01(F) PID02(BND) PID05 x

Vendor Purchase Method CHAR(25) 0 0 REF01(K6) REF02 x

Feature/Benefit CHAR(80) 0 5 PID01(F) PID02(SF) PID05 x

Gender By Age CHAR(25) 0 0 REF01(5E) REF02 x

Product Style CHAR(25) 0 0 REF01(87) REF02 x

Packaging Marked with Green Dot, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(GREENDOT) x

Recyclable Trade Item, Y/N CHAR(1) 0 0 YNQ02 YNQ10(RECYCLEITEM) x

Recycle Type NUMBER(1) 0 0 PKG02(02) PKG03(ZZ) PKG04 x

Recycle Description CHAR(40) 0 0 PID01(F) PID02(AJ) PID05 x

Right to Return Items not Sold, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(RTNUNSOLD) x

Return Goods Policy CHAR(20) 0 0 PID01(F) PID02(DAC) PID05 x

Component GTIN NUMBER(14) 0 100 SLN10 x x

Component GTIN Quantity NUMBER(5) EA 100 SLN04 x x

Colorization CHAR(25) 0 0 PID01(F) PID02(35) PID05 x

Finish Description CHAR(40) 0 0 PID01(F) PID02(77) PID05 x

Fabric Description CHAR(40) 0 0 PID01(F) PID02(92) PID05 x x

Gold Karat CHAR(3) 0 0 MEA01(PS) MEA02(GD) MEA03 x

Vendor Collection Name CHAR (60) 0 0 PID01(F) PID02 (LO), PID05 x

Product Shape CHAR(25) 0 0 PID01(F) PID02(PFA) PID05 x

Sleeve Length CHAR(25) 0 0 PID01(X) PID02(84) PID03(94) PID04(SLEEVE) PID05

x

Collar Type CHAR(25) 0 0 PID01(X) PID02(84) PID03(94) PID04(COLLAR) PID05

x

Stone CHAR(25) 0 0 PID01(F) PID05 PID06(SN) x





Product Type or Function CHAR(20) 0 0 REF01(PG) REF02 x

Season CHAR(12) 0 0 PID01(F) PID02(63) PID05 x

Scents/Flavors/Variant CHAR(25) 0 0 PID01(F) PID02(AE) PID05 x

Sport CHAR(15) 0 0 PID01(X) PID02(84) PID03(94) PID04(SPORT) PID05

x

Team CHAR(25) 0 0 N101(U4) N102 x

Item Deposit Value NUMBER(8,8) 0 0 G5520 x

Coupon Family Code NUMBER(3) 0 0 G5518 x

Item Usage Description CHAR(80) 0 0 PID01(F) PID02(AC) PID05 x

Alcohol Percent NUMBER(4,2) LIST 0 PID01(F) PID02(P6) PID05 x

Radiation Applied to Item, Y/N CHAR(1) 0 0 YNQ02 YNQ10(IRRADIATEDITEM) x

Radiation Applied to Raw Material, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(IRRADIATEDMTL) x

Radiation Applied to ingredient, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(IRRADIATEDING) x

Genetically Modified Item, Y/N CHAR(1) 0 0 YNQ01(G4) YNQ02 x

Alternate Unit of Measure CHAR(2) 0 0 MEA01(BD) MEA02(OTE)

MEA03(1) MEA04

x

Horsepower Rating NUMBER(8,2) 0 0 REF01(HR) REF02 x

Minimum Order Quantity NUMBER(9) 0 0 CTB01(OR) CTB03(57) CTB04 x x

Maximum Order Quantity NUMBER(9) 0 0 CTB01(OR) CTB03(70) CTB04 x x

Order Quantity Multiple NUMBER(9) 0 0 CTB01(OR) CTB03(AP) CTB04 x

Order Sizing Factor NUMBER(9,4) LIST 0 G3921 x

Invoiced Unit of Measure CHAR(2) 0 0 MEA01(BD) MEA02(ZZZ)

MEA03(1) MEA04

x

Lead Time NUMBER(3,0) LIST 0 LDT01(AE) LDT02 x x

Reorderable Product CHAR(2) 0 0 PID01(S) PID03(VI) PID04(RY, RN) x x

Seasonal Availability CHAR(2) 0 0 PID01(S) PID03(VI) PID04(SN, SY) x x

Odd Size Indicator CHAR(2) 0 0 PID01(S) PID03(VI) PID04(OS) x x

Ship From Location Name CHAR(40) 0 15 N101(SF) N102 x x

Ship From Location Code CHAR(40) 0 15 N101(SF) N103(91) N104 x x

Ship From City CHAR(30) 0 15 N101(SF) N401 x

Ship From State or Province CHAR(2) 0 15 N101(SF) N402 x

Ship From Zip or Postal Code CHAR(15) 0 15 N101(SF) N403 x

Ship From Country CHAR(3) 0 15 N101(SF) N404 x





C

Country of Origin CHAR(3) 0 3 N101(CT) N103(38) N104 x x

Target Market Country Code CHAR(35) 0 15 Header and Detail N101(9C) N103(38) N104

x

Target Market Subdivision Code

CHAR(7) 0 15 Header and Detail N101(9C) N103(38) N104-N407

x

Transportation Method CHAR(2) 0 0 TD504 x

Special Handling Code CHAR(3) 0 5 TD401 x

Flash Point Temperature NUMBER(8,8) LIST 2 Detail - MEA01(TE) MEA02(FP) MEA03 x

Minimum Storage Temperature NUMBER(8,8) LIST 0 Detail - MEA01(TE) MEA02(TES) MEA05 x

Maximum Storage Temperature NUMBER(8,8) LIST 0 Detail - MEA01(TE) MEA02(TES) MEA06 x

Aerosol, Y/N CHAR(1) 0 0 PID01(F) PID02(PFK) PID05 x

Hazardous Material Class Code CHAR(4) 0 5 TD402(D) TD403 x x

Hazardous Material Description

CHAR(40) 0 5 TD402(D) TD404 x x

North American Workplace Hazardous Materials Information System (HMIS) Code

CHAR(5) 0 0 Detail - PID01(S) PID03(OS) PID04 x x

National Motor Freight Classification Code

NUMBER(7) 0 0 TC201(N) TC202 x x

Material Safety Data Sheet (MSDS) Number

CHAR(20) 0 0 REF01(MS) REF02 x

Item has been Recalled, Y/N CHAR(1) 0 0 YNQ02 YNQ10(RECALL) x

Harmonized Tariff Schedule NUMBER(10) 0 0 TC201(A) TC202 x

Harmonized System Based Schedule B

NUMBER(10) 0 0 TC201(J) TC202 x x

Quota Category NUMBER(6) 0 0 TC201(Q) TC202 x x

UN/SPSC Classification Code NUMBER(10) 0 0 PID01(S) PID03(UN) PID04 x

Classification Agency CHAR(13) 0 3 N101(AG) N103(97) N104 x

Classification Level 1 Value CHAR(45) 0 3 N1 Loop - REF01(19) REF02 x

Classification Level 2 Value CHAR(45) 0 3 N1 Loop - REF01(2P) REF02 x

Warranty Description CHAR(80) 0 0 PID01(F) PID02(WD) PID05 x x

Warranty Period (Time Frame) NUMBER(8,8) LIST 0 MEA01(WR) MEA02(TT) MEA03 x

Tire Segment CHAR(25) 0 0 PID01(X) PID02(TIR) PID03(94) PID04(SEGMENT) PID05

x

Tire Speed Rating CHAR(9) 0 0 PID01(X) PID02(TIR) PID03(94) PID04(RATING) PID05

x

Item Barcode Type CHAR(35) 0 5 PKG01(F) PKG02(34) PKG05 x

Consumer Item Length NUMBER(8,3) LIST 0 MEA01(PD) MEA02(LN) MEA03 x

Item Length Description CHAR(40) 0 0 PID01(F) PID02(DM) PID05 x





Consumer Item Width NUMBER(8,3) LIST 0 MEA01(PD) MEA02(WD) MEA03 x

Consumer Item Height NUMBER(8,3) LIST 0 MEA01(PD) MEA02(HT) MEA03 x

Consumer Item Diameter NUMBER(8,3) LIST 0 MEA01(PD) MEA02(DI) MEA03 x

Consumer Item Net Weight NUMBER(8,3) LIST 0 MEA01(PD) MEA02(WT) MEA03 x

Consumer Item Drained Weight

NUMBER(8,3) LIST 0 MEA01(PD) MEA02(NNW) MEA03 x

Consumer Item Volume (Cube) NUMBER(8,3) LIST 0 MEA01(PD) MEA02(VOL) MEA03 x

Capacity/Volume Description CHAR(40) 0 0 PID01(F) PID02(SIZ) PID05 x

Installation Length NUMBER(8,8) LIST 0 MEA01(DT) MEA02(LN) MEA03 x

Installation Width NUMBER(8,8) LIST 0 MEA01(DT) MEA02(WD) MEA03 x

Installation Height NUMBER(8,8) LIST 0 MEA01(DT) MEA02(HT) MEA03 x

Size of Units in Consumer Package (Net Content)

NUMBER(8,4) LIST 0 G5514 x x

Net Content Declaration Required, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(DECLARATION) x

Consumer Package Length NUMBER(8,3) LIST 0 G5509 x x

Consumer Package Width NUMBER(8,3) LIST 0 G5507 x x

Consumer Package Height NUMBER(8,3) LIST 0 G5505 x x

Consumer Package Gross Weight

NUMBER(8,3) LIST 0 G5523 G5524(G) x x

Consumer Package Volume (Cube)

NUMBER(8,3) LIST 0 G5511 x x

Consumer Packaging Type CHAR(3) 0 0 G5533 Part 1 x

Consumer Packaging Material CHAR(2) 0 0 G5533 Part 2 x

Peg Horizontal NUMBER(7,4) LIST 0 MEA01(PS) MEA02(D6) MEA03 x

Peg Vertical NUMBER(7,4) LIST 0 MEA01(PS) MEA02(D8) MEA03 x

Anti-Theft Device Location CHAR(1) 0 0 PKG01(X) PKG02(34) PKG03(VI)

PKG04(MES) PKG05

x

Tamper Resistant Packaging, Y/N

CHAR(1) 0 0 YNQ02 YNQ10(PKGTAMPER) x

A Special Opening Package Type

CHAR(15) 0 0 PKG01(F) PKG02(35) PKG05 x

Inner Pack Qty NUMBER(3) 0 0 G3927 or PKL04 x

Inner Pack Length NUMBER(8,3) LIST 0 PKL07 x





C

Inner Pack Width NUMBER(8,3) LIST 0 PKL06 x

Inner Pack Height NUMBER(8,3) LIST 0 PKL05 x

Inner Pack Gross Weight NUMBER(8,3) LIST 0 PKL09 x

Inner Pack Volume (Cube) NUMBER(8,3) LIST 0 PKL11 x

Inner Pack Packaging Type CHAR(3) 0 0 PKG02(IP) PKG05 Part 1 x

Inner Pack Packaging Material CHAR(2) 0 0 PKG02(IP) PKG05 Part 2 x

Master Pack/Case Qty NUMBER(6) 0 0 G3917 x

Master Pack/Case Length NUMBER(8,3) LIST 0 G3912 x

Master Pack/Case Width NUMBER(8,3) LIST 0 G3910 x

Master Pack/Case Height NUMBER(8,3) LIST 0 G3908 x

Master Pack/Case Gross Weight

NUMBER(8,3) LIST 0 G3906(G) G3905 x

Master Pack/Case Net Weight NUMBER(8,3) LIST 0 G3925(N) G3926 x

Master Pack/Case Volume (Cube)

NUMBER(8,3) LIST 0 G3914 x

Master Pack/Case Packaging Type

CHAR(3) 0 0 G3928 Part 1 x

Master Pack/Case Packaging Material

CHAR(2) 0 0 G3928 Part 2 x

Master Pack/Case Container or Equipment Type

CHAR(1) 0 0 PKG02(36) PKG03(VI) PKG04 Part 1 x

Master Pack/Case Packaging Configuration

CHAR(2) 0 0 PKG02(36) PKG03(VI) PKG04 Part 2 x

Returnable Packaging, Y/N CHAR(1) 0 0 YNQ02 YNQ10(RTNPKG) x

Packaging Terms and Conditions

CHAR(3) 0 0 PKG01(F) PKG02(CC) PKG05 x

Nesting Increment NUMBER(8,3) LIST 0 MEA01(PS) MEA02(NK) MEA03 x

Nesting or Stacking Quantity NUMBER(4) 0 0 MEA01(PS) MEA02(NK) MEA06 x

Maximum Stacking Weight NUMBER(7,4) LIST 0 MEA01(PS) MEA02(MX) MEA03 x

Pallet Blocks NUMBER(3) 0 0 G3916 Part 1 x

Pallet Tiers NUMBER(3) 0 0 G3916 Part 2 x

Pallet Length NUMBER(8,3) LIST 0 MEA01(PA) MEA02(LN) MEA03 x

Pallet Width NUMBER(8,3) LIST 0 MEA01(PA) MEA02(WD) MEA03 x





Pallet Height NUMBER(8,3) LIST 0 MEA01(PA) MEA02(HT) MEA03 x

Pallet Gross Weight NUMBER(8,3) LIST 0 MEA01(PA) MEA02(WT) MEA03 x

Pallet Net Weight NUMBER(8,3) LIST 0 When PID04(PL) G3925(N) G3926,

else MEA01(PA) MEA02(N) MEA03

x

Pallet Volume (Cube) NUMBER(8,3) LIST 0 MEA01(PA) MEA02(VOL) MEA03 x

Pallet Alternate Tiers NUMBER(3) 0 0 G3922 x

Pallet Type CHAR(3) 0 0 Detail - N101(SUS) PAL01 x

Pallet Terms and Conditions CHAR(2) 0 0 Detail - N101(SUS) PAL15 x

Marked with Ingredients, Y/N CHAR(1) 0 0 YNQ02 YNQ10(INGMARK) x

List of Ingredients CHAR(4000) 0 0 PID01(F) PID02(ING) PID05 x

Organic Item Code CHAR(35) 0 0 PID01(X) PID02(84) PID03(94)

PID04(ORGANIC) PID05

x

Sears RIM Hardlines Filter CHAR(2) 0 0 REF01(8N) REF02(RH) YES x

Sears RIM Softlines Filter CHAR(2) 0 0 REF01(8N) REF02(RS) YES x

Sears SAMS Minimum Filter CHAR(2) 0 0 REF01(8N) REF02(S) YES x

Sears Tires Automotive Filter CHAR(2) 0 0 REF01(8N) REF02(T) YES x

Hanger Type CHAR(6) LIST 3 PKG01(F) PKG02(36) PKG05 x



91

Index Numerics2.0 Compatibility compliance check, 16

Aaccessing documentation, 2action types, 19actions

change, 31replace, 32

addresses, electronic mailboxes, 7ANSI X12 standards, 5–6

Bbatch interface

diagram, 6overview, 5

BCT, 28

Cchange, 31check digit calculations, 79Color code, GMA compliance rules, 17compliance checks

2.0 Compatibility, 16about, 15email notification options, 15GMA Compliance, 17Prefix Validation, 18Product Description Uniqueness, 18rejecting non-compliant data, 15types, 15

confirmation by email, 8connecting to QRS, 7CTB

LIN, 54CTP, 69CTT, 73CUR

heading, 35customer requirements, 7customer support, 3

Ddata types, 19documentation

accessing, 2related, 2

DTMheading, 33LIN, 52

Eelectronic mailbox addresses, 7email confirmation, 8email notification

compliance check options, 15errors

correcting, 9EDI validation, 11

Ffile formats, 6file size, maximum, 7flipping Sel Codes, 28

GG55, 64GE, 23GMA compliance check, 17GS, 23GS1 (UCC/EAN) prefix validation, 18GTIN, 2.0 compatibility rules, 15–16GTINs, 1, 7

IIEA, 23interface, batch, 5ISA, 21

LLDT, 62LIN, 49LIN segments per ST, maximum number, 7

Mmailbox addresses, 7maximum file size, 7maximum number of LIN segments per ST, 7moving Products, 28

NN1

detail, 70heading, 41

non-compliant data, rejecting, 15

Oorganization of products, 7

PPID, 55

I N D E X


Prefix Validation compliance check, 18prepack code, 2.0 compatibility rules, 16Product Description rules, 18Product Description Uniqueness compliance check, 18product organization, 7Products, 7

QQRS, connecting to, 7

Rrelated documentation, 2requirements of customer, 7

SSE, 74segments

BCT, 28CTB, LIN, 54CTP, 69CTT, 73CUR, heading, 35DTM, heading, 33DTM, LIN, 52G55, 64LDT, 62LIN, 49

N1, detail, 70N1, heading, 41PID, 55SE, 74SLN, 71ST, 27TC2, 63TD4, 60

Sel Code flipping, 28Selection Codes, 7Size code, GMA compliance rules, 17SLN, 71ST, 27

TTC2, 63TD4, 60technical support, 3typographical conventions, 2

UUCC/EAN prefix validation, 18

Vvalidation

EDI, 11

inovis catalogue 832 (v4010) batch guide for vendors catalog...the inovis catalogue edi 832 batch...

Documents