Clickable Business Models eBusiness Education Acronyms Cross References
B2B Content Standards EC Technology Standards Glossary Implementation Guidelines
Implementation Options General Recommendations References Methodology/Legends
 Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search
 Product Identification | Partner/Location IDs | Doc/Reference IDs | Dates | Other Best Practices |
EIDX General Supporting Documentation
Status:  Provisional draft.  Adapted from previous published version (Balloted and Ratified by Membership, June 1997)

EIDX General Recommendations for Product Identifiers


Contents

See also Notes about EIDX Supporting Documentation


General Information About Product Identification


Product recommendations are general enough in this document that they should apply to all ASC X12 and UN EDIFACT transactions/messages in all versions/releases.

SEGMENTS USED IN PRODUCT IDENTIFICATION

ASC X12 uses a combination of generic and specific segments in its transactions. For example, REF Reference is generic and found throughout various transactions. PO1 is specific to the Purchase Order and PO Acknowledgment, while the POC is used in the Change Order and Change Order Acknowledgment with the exact same function as the PO1. Consequently, there are many segments where product identification data may be found. The most commonly used transactions and segments are listed below.

blank_space.gif (96 bytes) CORE TRANSACTIONS blank_space.gif (96 bytes) blank_space.gif (96 bytes)

CORE SEGMENTS (SEG)

810

Invoice blank_space.gif (96 bytes)

ACK

Line Item Acknowledgment

830

Forecast blank_space.gif (96 bytes)

IT1

Baseline Item Data (for 810 Invoice)

832

Price Catalog blank_space.gif (96 bytes)

IT8

Conditions of Sale

846

Inventory Inquiry/Advice blank_space.gif (96 bytes)

LIN

Item Identification Detail

850

Purchase Order blank_space.gif (96 bytes)

PO1

Purchase Order Baseline Item Data

855

PO Acknowledgment blank_space.gif (96 bytes)

POC

Line Item Change

856

Shipment Notice/Manifest (ASN) blank_space.gif (96 bytes)

REF

Reference

857

Shipment & Billing Notice blank_space.gif (96 bytes)

SLN

Sub-line Item Detail

860

PO Change blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

862

Ship Schedule blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

865

PO Change Acknowledgment blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

 

UN EDIFACT uses generic segments throughout its messages. For example, LIN, and only LIN, is used for line item data in all messages. Consequently, there are only a few segments used for product identification data.

blank_space.gif (96 bytes)

CORE MESSAGES

blank_space.gif (96 bytes) blank_space.gif (96 bytes)

CORE SEGMENTS (SEG)

INVOIC

Invoice

blank_space.gif (96 bytes)

LIN

Line Item

DELFOR

Delivery Forecasts

blank_space.gif (96 bytes)

PIA

Additional Product ID

PRICAT

Price Catalog

blank_space.gif (96 bytes)

RFF

Reference

INVRPT

Inventory Inquiry/Advice

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

ORDERS

Purchase Order

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

ORDRSP

PO Acknowledgment

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

DESADV

Despatch Advice (Shipment Notice)

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

ORDCHG

PO Change

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

DELJIT

Delivery Just-in-Time

blank_space.gif (96 bytes) blank_space.gif (96 bytes) blank_space.gif (96 bytes)

 

ELEMENTS USED IN PRODUCT IDENTIFICATION

ASC X12 segments use several pairs of the following data elements (DE) which are used in transactions:

Data Element

Code

235

PRODUCT/SERVICE IDENTIFICATION QUALIFIER

234

PRODUCT/SERVICE IDENTIFICATION

128

Reference Number qualifier

127

reference number

 

Similarly, UN EDIFACT segments provide for data elements which are used in many messages. These elements are components of compound elements. The following tables have examples of composites.

Composite

blank_space.gif (96 bytes) blank_space.gif (96 bytes)

C212

Item Number Identification

blank_space.gif (96 bytes)

Composite (Position)

Data Element

Description
blank_space.gif (96 bytes)

C212 (01)

7140

ITEM NUMBER
blank_space.gif (96 bytes)

C212 (02)

7143

ITEM NUMBER TYPE, CODED
blank_space.gif (96 bytes)

C212 (04)

3055

RESPONSIBLE AGENCY
(Identify an agency if appropriate)

C506

REFERENCE

blank_space.gif (96 bytes)
blank_space.gif (96 bytes)

Composite (Position)

Data Element

blank_space.gif (96 bytes)
blank_space.gif (96 bytes)

C506 (01)

1153

Reference Number Qualifier

blank_space.gif (96 bytes)

C506 (02)

1154

Reference Number

 


Line Item Numbers

Line Item Numbers in ASC X12 are specified in the PO101, LIN01, etc. This is not true in EDIFACT. In EDIFACT, the number in LIN01 indicates the occurrence of the LIN in the message. In EDIFACT, line item numbers are in RFF segments.

EDIFICE description of LIN01 Line Item Number:
"It is required to assign a number to the line items within a message. The number is assigned by the sender of the message. The first line item within a message will be numbered ‘1’ and further line items will be incremented by ‘1’ for each new line."

EDIFICE description of Segment Group 25 RFF Line Item Number in ORDERS message:
"Within an order this must be a unique number which will be the key for identification of the line item. The number is assigned by the buyer, and it can only be assigned once during the lifetime of the order. It will be used, where needed, to refer to the original line item on any subsequent transactions relating to the order. Normally, the first line number on an order will be numbered ‘1’ and further line items will be incremented by ‘1’ for each new line. This DE must be used when DE1153 = ‘LI’."

At first this seems arbitrary, until configuring product options are examined. See the "PRODUCT OR COMPONENT OPTIONS" section. The examples illustrate the difference between ASC X12 and EDIFACT.

ASC X12 DE350 Assigned Identification

UN DE1153
Reference Qualifier/
(DE1154 Reference Number)


QUALIFIER MEANING


COMMENT

(Use for Line Item Number)

LI:(Line Item Number)

Line item reference number Reference number identifying a particular line in a document.

 

ASC X12 DE350 Assigned Identification


UN DE1082
Line Item Number



COMMENT

(Use for Line Item Number)

DO NOT USE FOR LINE ITEM NUMBER

Because of the structure of the Sub-line notation relative to the LIN segment, Line Item Number should not be used for the traditional Line Item Number.


Line item numbers should be sent by the buyer if it is important that they be received back on response documents (acknowledgments, ship notices, invoices, etc.) in order to match the responses correctly to the original purchase order.

Line Item Numbers Not Used

Some trading partners that manage Blanket Purchase Orders as part of the same forecasting application that generates Material Release or other types of planning schedules may not use line item numbers in their BPOs. Typically, these trading partners have applications that are designed to disallow the same part number to be on an order more than once. In which case, line item numbers may seem to be as irrelevant, and the line item number is not needed in response documents such as acknowledgments, ship notices and invoices.

Trading partners should be prepared to accommodate this type of situation. If the receiver’s application must have a customer line item number, dummy values might be calculated by the application interface program. Likewise, the buyer’s application might be coded to ignore the dummy line item numbers if they are sent in a response document. This is an example where the use of single-item BPOs are recommended, since in this case, line item number is always 1.

Line Item Numbers Used

It is very important that the line item number not be changed from the original line item number in the purchase order. Line item number is likely to be a key value used to match the change order line item of the purchase order in the buyer's system to the sales order in the supplier's system. If a purchasing system should renumber line items, because line items are deleted or closed, it may be difficult to match the line items in the seller's system. Also since part numbers are often repeated on line items within a given purchase order, the part number alone may not suffice for the line item matching. Never renumber line items. This practice should be corrected as soon as possible to avoid this serious problem.

Likewise, the integrity of the line item number in the purchase order should continue in the original acknowledgment transaction and the change acknowledgment returned to the buyer.

CROSSING APPLICATIONS and TRANSACTION/MESSAGES

The integrity of the line item number should be maintained across all applications and all transactions/messages. For example, if the line item number is five (5) characters long and the line item is used in a bar code, all five (5) characters should be used in the bar code. For example, the buyer should not expect that five (5) numbers of the bar code be transmitted in the purchase order, but that only four (4) of the numbers be used in the bar codes. This rule applies to all other data elements also.

Line Item Number Length

Earlier ASC X12 versions/releases limited ASSIGNED IDENTIFICATION to six digits. New versions/releases allow up to eleven (11) digits. The maximum allowable length is six digits in DE 1082 Line Item Number in EDIFACT.

The EDIFACT standard only allows 200000 occurrences of the SG25.LIN segment group on a purchase order, and ASC X12 allows only 100,000 line items on a purchase order. In reality, most legacy applications have only a two or three digit line item number field, and few applications allow for more than 100000 items per transaction. EIDX recommends the continued use of a maximum of six digits for line item number to accommodate the more realistic length of a line item number in the Electronics Industry and avoid system constraints. Check with the trading partner for their system constraints.

Actual Data Length

Although it is called "Assigned Identification" DE350 in ASC X12, it is common practice to have the "Line Item Number" placed in DE350. It is called "Number", but it is not defined as a numeric field. It is alphanumeric. Though the standards allow large numbers, some industries may be using the fields for unique identifiers other than a numeric counter; hence, the longer data fields.

The purchase order system could generate 1, 01, 001, 0001, 00001, or 000001. Unfortunately, systems do not equate 1, 01, 001, 0001, 00001, and 000001 without data manipulation because there is positional comparison.

The seller's system should maintain the integrity of the data without padding the number with leading zeros so the acknowledgments return the data exactly as sent by the seller. The data should be treated as an alphanumeric identifier, rather than as a number. The actual data length in all the purchase order related transactions should be consistent.

The following tables illustrate the problem. Assume that the seller system must hold six positions to accommodate all their customers. They store the number exactly as the buyer sent the data. When the computer compares the entire field of six positions, it compares each position separately.

'1' is really ‘1, blank, blank, blank, blank, blank’ to fill all six positions.
'001' is really ‘0, 0, 1, blank, blank, blank’ to fill all six positions.

If a buyer sends, ‘1 ‘ and the seller stores it as ‘001’, a mismatch will occur, because '1 blank blank blank blank blank' does not equal '0 0 1 blank blank blank'.

blank_space.gif (96 bytes)

DATA POSITION

DATA

1

2

3

4

5

6

1

1

blank

blank

blank

blank

blank

01

0

1

blank

blank

blank

blank

001

0

0

1

blank

blank

blank

0001

0

0

0

1

blank

blank

00001

0

0

0

0

1

blank

000001

0

0

0

0

0

1

 


Product or Component Identification

Product numbers (a/k/a part numbers, items) are conveyed using the DE235/DE234 paired data elements in ASC X12 and the C212 composite element in UN EDIFACT. Multiple combinations may be used such as sending both the buyer part and the vendor part number. The preferred convention is to have a single product identification that means exactly the same interpretation to both trading partners. If this is not possible, then sufficient references to identify the product should be included. This may mean including both the buyer's product number and the seller's product number in paired fields within the segment, or including the buyer’s product number plus a key drawing reference, etc. Accompanying Engineering Changes (revisions) to the base product are often important for the trading partner to cross reference the product properly. Engineering Changes are discussed further in another section.

ASC X12 and UN codes are identical, unless otherwise noted.

ASC X12 (DE235) / UN C21202 (DE7143)




DESCRIPTION



NOTE

AB

Assembly Contract manufacturer (CM) may need to reference an assembly when ordering components from a Prime Contractor. It is also used when the part is being ordered from Contract Manufacturer by Prime Contractor.

BP

Buyer's Part Number The presence of a part qualifier by the ‘BP’ code supersedes the importance of any other part sent on the segment. This means that the buyer product is the most important part to cross reference to the seller’s internal part number if several part number qualifiers are sent.

EC

Engineering Change Level Used to identify revision level of a product or part.

EN

International Article Number (formerly called European Article Number) Number assigned to a manufacturer's product according to the International Article Numbering Association (EAN).

MG (X12)
MF (UN)

Manufacturer’s Part Number Use ‘MG’ only if the part must be clearly distinguished from the vendor part (VP).

PC (X12)
UA (UN)

Prime Contractor Part Number
Ultimate Customer’s Article Number
Use when appropriate.

UI (X12 only)

UPC Item Code (1-5-5) Use when appropriate.

UP

UPC Consumer Package Code (1-5-5-1) Use when appropriate. Note: The standards have other codes for other UPC formats.

VP

Vendor's (seller's) Part Number The ‘VP’ is preferred over the ‘MF’ and ‘MG’ qualifiers in most buyer-seller relationships.

New code needed

Contract Manufacturer’s Part Number Prime contractor may have to reference CM part number if placing an order with a supplier for drop Ship-To the CM.

 

Examples of product or component identification on any applicable segment:


TAG
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
1 (SEG) * ... * BP * B1234 * EC * 011 * VP * V2345 *
2 (SEG) * ... * BP * B1234 * VP * V2345 * MG * MX1A
3 (SEG) * ... * PC * 12-10 * VP * S121 * AB * AB923 * UP * 065783456
blank.gif (117 bytes)

TAG
DE
4347
DE
7140
DE
7143
DE
7140
DE
7143
DE
7140
DE
7143
DE
7140
DE
7143
1 LIN + ... + B1234 : BP
PIA + 1 + 011 : EC + V2345 : VP
2 LIN + ... + B1234 : BP
PIA + 1 + V2345 : VP + MX1A : MF
3 LIN + ... + 12-10 : PC
PIA + 1 + V2345 : VP + AB923 : AB + 011 : EC + 065783456 : UP

 


Rules for Product Identification

The following general rules apply:

1. Pairs of DE235 and DE234 (ASC X12) or occurrences of C212 (UN) should not be skipped within a segment.

For example: In ASC X12, a buyer part (BP), an engineering change (EC), and a vendor part (VP) usually occupy the first three pairs of DE235 and DE234 fields. In EDIFACT, the BP is generally sent on the LIN, then the EC and VP occupy the first two occurrences of C212 on the PIA segment. If engineering change (EC) is not available for a particular buyer part, the vendor part (VP) should be moved to the second pair of DE235 and DE234 or first occurrence of C212 within the appropriate segment.

NOTE: An engineering change or product revision may be alphanumeric, though it is often called ‘revision number’.


TAG
DE
235
DE
234
DE
235
DE
234
DE 235 DE
234
DE 235 DE 234
1.1 (SEG) * ... * BP * B1234 * EC * 011 * VP * V2345
1.2 (SEG) * ... * BP * B1234 * VP * V9876
blank.gif (117 bytes)                        

TAG
DE 4347 DE 7140 DE 7143 DE
7140
DE
7143
DE 7140 DE 7143
1.1 LIN + ... + B1234 : BP
PIA + 1 + 011 : EC + V2345 : VP
1.2 LIN + ... + B1234 : BP
PIA + 1 + V2345 : VP

1.1 Product has an EC for the buyer’s Part Number and a VP (EDIFACT: BP is on the LIN preceding the PIA).

1.2 Product has a VP, but no EC for the buyer Part Number. Instead of skipping the position, the VP is moved into the first available position on the segment.


2. A particular qualifier may be required to follow another qualifier, for example, the 'EC' qualifier must follow the 'BP' or 'VP' qualifier to which it relates.

Engineering Changes (revision) levels for products immediately follow its related product identification. There should never be another product identification inserted between the engineering change level and its related product ID. Typically, the buyer part number or a third party part number might have an associated EC. It is unusual for a vendor part number to have an EC. ECs are not used with association assigned identifiers such as UPCs or EANs.


TAG
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
2.1 (SEG) * ... * BP * B1234 * EC * 011 * VP * V2345 EC* 3
blank.gif (117 bytes)                                  

TAG
DE 4347 DE 7140 DE
7143
DE 7140 DE 7143 DE 7140 DE
7143
2.1 LIN + ... + B1234 : BP
PIA + 1 + 011 : EC + V2345 : VP + 3 : EC

2.1 Both BP and VP have an EC; each EC follows the related product ID.

 

3. A primary qualifier such as ‘BP’ or ‘VP’ should not be required in a particular position among the several occurrences of the data elements.

For example, it is not appropriate to require that the ‘VP’ qualifier must be in the third occurrence of the pairs of data elements. Related qualifiers may be easier to interpret if they are serially grouped.


TAG
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
3.1 (SEG) * ... * BP * B1234 * EC * 011 * VP * V2345 EC* 3
3.2 (SEG) * ... * VP * V2345 EC* 3 * BP * B1234 * EC * 011
blank.gif (117 bytes)                                  

TAG
DE 4347 DE 7140 DE
7143
DE 7140 DE 7143 DE 7140 DE
7143
3.1 LIN + ... + B1234 : BP
PIA + 1 + 011 : EC + V2345 : VP + 3 : EC
3.2 LIN + ... + V2345 : VP
PIA + 1 + 3 : EC + B1234 : BP + 011 : EC

3.1 BP and its EC occurs first, and VP with its EC follows.

3.2 Order of BP and VP are reversed from above; this should make no difference when the recipient is mapping the data to the internal application.

 


Drawing References

Drawing data is conveyed using the DE235/DE234 paired data elements (ASC X12) or C212 composite elements with one of the codes listed below. Multiple combinations may be used, if needed.

ASC X12 and UN codes are identical, unless otherwise noted.

ASC X12
(DE235)

UN
C21202 (DE7143)


DESCRIPTION

DR

DR

Drawing Revision

GS

GS

General Specification

PK

PK

Packaging Drawing

PT (X12)

DW (UN)

Print or Drawing


Recommendations

The following recommendations are made for drawing data.

1. Any of the drawing qualifiers listed above may be in any order within a segment.
2. Drawing numbers should follow any Product ID and associated Engineering Change level (if applicable).

Examples on any applicable segment (SEG):


TAG
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
2.1 (SEG) *...* BP * B1234 * PT * T54 * GS * G122
2.2 (SEG) *...* BP * B1234 * EC * 011 * GS * G122 * PT * T54
2.3 (SEG) *...* BP * B1234 * EC * 011 * PK * 05 * GS * G122
blank.gif (117 bytes)                                  

TAG
DE
7140
DE
7143
DE
7140
DE 7143 DE
7140
DE
7143
DE
7140
DE
7143
2.1 LIN +...+ B1234 : BP
PIA +...+ T54 : DW + G122 : GS
2.2 LIN +...+ B1234 : BP
PIA +...+ 011 : EC + G122 : GS + T54 : DW
2.3 LIN +...+ B1234 : BP
PIA +...+ 011 : EC + 05 : PK + G122 : GS

3. When there is a drawing revision, the element(s) immediately following drawing data must contain the drawing revision qualifier ‘DR’ and the drawing revision data. If multiple drawings are used, each drawing revision must immediately follow its specific drawing before the next drawing is referenced. Examples on any applicable segment:


TAG
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
DE
235
DE
234
2.1 (SEG) *...* BP * B1234 * PT * T54 * DR * D1
2.2 (SEG) *...* BP * B1234 * GS * G122 * DR * N * PT * T54 * DR * P1
2.3 (SEG) *...* BP * B1234 * EC * 011 * PK * 05 * GS * G122 DR * N
blank.gif (117 bytes)                                        

TAG
DE
7140
DE
7143
DE
7140
DE 7143 DE
7140
DE
7143
DE
7140
DE
7143
2.1 LIN +...+ B1234 : BP
PIA +...+ T54 : DW + D1 : DR
2.2 LIN +...+ B1234 : BP
PIA +...+ G122 : GS + N : DR + T54 : DW + P1 : DR
2.3 LIN +...+ B1234 : BP
PIA +...+ 011 : EC + 05 : PK + G122 : GS + N : DR

 


Product or Component Options

SUBLINE CONFIGURATION IN ASC X12

Products with options should be identified in ASC X12 by the use of the base line item segment (such as PO1 or IT1) with Subline Item (SLN) segments. SLN segments are used to identify ‘added’ or ‘deleted’ product data to the base line item, as well as included products in the configuration. Multiple SLN segments are allowed for each line item. Options may be added, deleted, or included as long as the relationship to the base item is clear. Sub-line data is illustrated in depth in the following pages.

Base Product

for

First line item:

PO1*1*20 *EA*15.25*CT*BP*B1234

Subline

for

first option:

SLN*1.1**A*20*EA*2.50*QT*A*BP*300A

Subline

for

second option:

SLN*1.1**D*15*EA*1.50*QT*S*BP*ZZ123

Base Product

for

Second line item:

PO1*2*50 *EA*5500.00*QT*BP*C600A

Subline

for

first option:

SLN*1.1**D*50*EA*100.00*QT*A*BP*A10

Subline

for

second option:

SLN*1.1**A*50*EA*200.00*QT*S*BP*A01

In a case where multiple combinations of sub-line items would cause confusion in relation to the base item, the base item should be split into multiple line items, each with relevant sub-line items. Each split base item would have relevant sub-line items. For example, if a system is being ordered that consists of a computer and peripherals, the peripherals might be considered to be options for the computer system. However, the peripherals themselves might have options. The base item might have to be split, so that a particular peripheral, such as a printer, can be ordered with options. The peripheral would be its own line item, with options relevant to that computer specified under that line item.

SUBLINE CONFIGURATION IN UN EDIFACT

EDIFACT is more complex on the Sub-line Item than ASC X12. Instead of one PO1/LIN with the appropriate SLN segments within the loop, multiple LIN segments are sent in EDIFACT. In effect, multiple line items are sent. This is the only way product options can be configured and identified in EDIFACT. A further complication in EDIFACT is the usage of line item number. The LIN01 value is incremented by 1 for each LIN sent. Instead of representing line item number, it represents occurrence of the LIN segment. Line Item number is specified on a subsequent RFF segment within the LIN segment group, and the RFF comes after several other segments. If there are two parts on an order, with two options each, there will be six LIN segments, with LIN01 numbered 1 through 6 as traditionally defined, for two line item numbers. LIN04 is set to ‘1’ to indicate that it is a sub-line, and the configuration code is sent in LIN06.

First LIN:

BASE product for FIRST line item ................................................................ LIN+1++B1234:BP+0’
Qty of base product, first line item QTY+21:20:PCE’
Base product price, first line item PRI+INF:15.25:CT’
Line item number RFF+LI::1’

Second LIN:

Sub-line for first item, first option ................................................................ LIN+2++300A:BP+1++A
Qty of first item, first option QTY+21:20:PCE’
Price change for first item, first option PRI+INF:2.50:QT+A’
Line item number that this sub-line applies RFF+LI::1’

Third LIN:

Sub-line for first item, second option ................................................................ LIN+3++ZZ123:BP+1++D
Qty of first item, second option QTY+21:15:PCE’
Price change for first item, second option PRI+INF:1.50:QT+S’
Line item number that this sub-line applies REF+LI::1’

Fourth LIN:

BASE product for SECOND line item ................................................................ LIN+4++C600A:BP+0’
Qty of base product, second line item QTY+21:50:PCE’
Base product price, second line item PRI+INF:5500.00:CT’
Line item number RFF:LI::2’

Fifth LIN:

Subline for the first option ................................................................ LIN+5++A01:BP+1++D’
Qty of second item, first option QTY+21:50:PCE’
Price change for second item, first option PRI+INF:100.00:QT+A’
Line item number that this sub-line applies RFF:LI::2’

Sixth LIN:

Subline for the second option ................................................................ LIN+6++A10:BP+1++A’
Qty of second item, second option QTY+21:50:PCE’
Price change for second item, second option PRI+INF:200.00:QT+S’
Line item number that this sub-line applies RFF:LI::2’

There are two important factors for correctly configuring options in EDI:

1. A Configuration Code indicates the action or status of the sub-line item in the configuration.

2. The Sub-line Price Change Code indicates the cost effect of the sub-line.

CONFIGURATION CODE

The Configuration Code indicates if the sub-line option is to be added (A), deleted (D), included (I), or substituted (S) from the total assembly or system. Use the Configuration Code (DE661) set to ‘D’ to interpret a removal of the component. If the option is deleted, do not sign the quantity field as negative (-).

Codes are identical in ASC X12 and UN EDIFACT unless otherwise noted.

ASC X12
(DE 661)

UN
(DE 7083)


DESCRIPTION

A

A

Add (an option)

D

D

Delete (an option)

I

I

Include (an option)

S

??

Substitute (an option)


SUBLINE PRICE CHANGE CODE

The Sub-line Price Change Code indicates whether the costs should be added (A), subtracted (S) or included (I) (neither added nor subtracted). There is no implication that a Configuration Code has to match the direction of the Sub-line Price Change Code ID, i.e., an added option does not imply additional costs. Adding an option may result in an increase, decrease, or no change in costs.

Codes are identical in ASC X12 and UN EDIFACT unless otherwise noted.

X12 (DE 662)

UN (DE 5213)

DESCRIPTION

A

A

Add (costs)

I

I

Include (costs)

S

S

Subtract (costs)

 

NOTE: Purchase Order segments are used for the examples.

EXAMPLE 1: Illustrate "Add Option/Add Option Price"

X12

01

02

03

04

05

06

07

08

09

10

(1) PO1 *1 *20 *EA *15.25 *CT *BP *B1234’
(2) SLN *1.1 * *A *20 *EA *2.50 *QT *A *BP *300B’
UN
(1) LIN +1 + +B1234 :BP +0’
QTY +21 :20 :PCE’
PRI +INF :15.25 :CT’
RFF +LI : :1’

 

blank_space.gif (96 bytes) ASC X12/UN Element Value Meaning
(1) Base Item: PO101/ RFF01.C50602 1 Line Item Number
PO102/ QTY01.C18602 20 Number of units of the base item
PO104/ PRI01.C50902 15.25 Price per base item unit
PO107/ LIN003.C21202 B1234 Product ID for the base part
(2) First Option "Add Option" to Base Item / Add Option Price to Base Price
SLN03/LIN06 A Add the option to the base item
SLN10/LIN003.C21202 300B Product ID for the option
SLN04/QTY01.C18602 20 Number of units of the option to be added
SLN06/PRI01.C50902 2.50 Price per option
SLN08/PRI02 A Price per option is to be added

 

EXAMPLE 2: Illustrate "Delete Option/Subtract Option Price"

X12

01

02

03

04

05

06

07

08

09

10

(1) PO1 *1 *20 *EA *15.25 *CT *BP *B1234’
(3) SLN *1.2 * *D *20 *EA *1.50 *QT *S *BP *300A’
UN
(1) LIN +1 + +B1234 :BP +0’
QTY +21 :20 :PCE’
PRI +INF :15.25 :CT’
RFF +LI : :1’
(3) LIN +3 + +300A :BP +1 + +D’
QTY +21 :20 :PCE’
PRI +INF :1.50 :QT +S’
RFF +LI : :1’

 

blank_space.gif (96 bytes) ASC X12/UN Element Value Meaning
(1) Base Item: PO101/RFF01.C50602 1 Line Item Number
PO102/QTY01.C18602 20 Number of units of the base item
PO104/PRI01.C50902 15.25 Price per base item unit
PO107/LIN003.C21202 B1234 Product ID for the base part
(3)Second Option: "Delete Option" from Base Item / Subtract Option Price from Base Price
  SLN03/ LIN06 D Delete the option from the base item
SLN10/LIN003.C21202 300A Product ID for the option
SLN04/QTY01.C18602 20 Number of units of the option to be deleted
SLN06/PRI01.C50902 1.50 Price per option
SLN08/PRI02 S Price per option is to be subtracted

 

EXAMPLE 3: Illustrate "Delete Option/Add Charge"

X12

01

02

03

04

05

06

07

08

09

10

(1) PO1 *1 *20 *EA *15.25 *CT *BP *B1234’
(4) SLN *1.3 * *D *15 *EA *1.00 *QT *A *BP *ZZ123’
UN
(1) LIN +1 + +B1234 :BP +0’
QTY +21 :20 :PCE’
PRI +INF :15.25 :CT’
RFF +LI : :1’
(4) LIN +4 + +ZZ123 :BP +1 + +D’
QTY +21 :15 :PCE’
PRI +INF :1.00 :QT +A’
RFF +LI : :1’

 

blank_space.gif (96 bytes) ASC X12/UN Element Value Meaning
(1) Base Item: PO101/ RFF01.C50602 1 Line Item Number
PO102/QTY01.C18602 20 Number of units of the base item
PO104/PRI01.C50902 15.25 Price per base item unit
PO107/LIN003.C21202 B1234 Product ID for the base part
(4) Third Option: "Delete Option" from Base Item / Add Charge for to Base Price
SLN03/LIN06 D Delete the option from the base item
SLN10/LIN003.C21202 ZZ123 Product ID for the option
SLN04/QTY01.C18602 15 Number of units of the option to be deleted
SLN06/PRI01.C50902 1.00 Price per option
SLN08/PRI02 A Price per option is to be added

 

EXAMPLE 4: Illustrate "Include Option at No Charge"

X12

01

02

03

04

05

06

07

08

09

10

(1) PO1 *1 *20 *EA *15.25 *CT *BP *B1234’
(5) SLN *1.4 * *I *20 *EA * * * *BP *AB123’
UN
(1) LIN +1 + +B1234 :BP +0’
QTY +21 :20 :PCE’
PRI +INF :15.25 :CT’
RFF +LI : :1’
(5) LIN +5 + +AB123 :BP +1 + +I’
QTY +21 :20 :PCE’
RFF +LI : :1’

 

blank_space.gif (96 bytes) ASC X12/UN Element Value Meaning
(1) Base Item: PO101/RFF01.C50602 1 Line Item Number
PO102/QTY01.C18602 20 Number of units of the base item
PO104/PRI01.C50902 15.25 Price per base item unit
PO107/LIN003.C21202 B1234 Product ID for the base part
(5)Fourth Option: "Include Option" with Base Item at No Charge
SLN03/LIN06 I Include the option with the base item
SLN10/LIN003.C21202 AB123 Product ID for the option
SLN04/QTY01.C18602 20 Number of units of the option to be included
SLN06/PRI01.C50902 Not sent Price per option not sent = no charge
SLN08/PRI02 Not sent N/A

 

 


Secondary Packaging

‘Package’ and ‘packaging’ have different meanings.

Shipping packaging refers to external packaging which relates to shipping. Shipping packaging is conveyed in the TD1 Carrier Detail segment in ASC X12.

A product's package (or component packaging) is an integral part of the product, e.g., die package in surface mount diodes. Product packages are considered to be part specifications.

Secondary packaging (or ‘presentation’) is a packaging form which is external of the product. However, it may not be external to the manufacturing process, e.g., auto-insertion, and it may require a unique manufacturer’s or seller’s product number. Trays, tubes, and reels are examples of secondary packaging.

This section discusses only secondary packaging. Secondary packaging data is conveyed using the following:

In ASC X12: Packaging Code (DE103) in the PO404 element in the PO4 Item Physical Details segment
In EDIFACT: Type of Packages Identification (DE7065) in the PAC03.C20201 element in the PAC Package segment.


EIDX is using ASC X12 Packaging Codes in EDIFACT messages, since it can reference US, ANSI ASC X12 as the Code List Responsible Agency in PAC03.C20203 as the code source.

The ASC X12 Packaging Code is a two-part data element:

The following Product/Service Identification qualifiers for ASC X12 secondary packaging codes are recommended for DE103 PACKAGING CODE.

DE103 Part 1

DE103 Part 2

Description
Part 1

Description
Part 2

AMM

90

Ammo Pack

Standard

BLK

90

Bulk

Standard

PKG

  Package - not otherwise specified
(Use for waffle pack or other secondary packaging types that do not have a code assigned yet)

Standard

RAL

90

Rail (semiconductor)

Standard

REL

90

Reel (tape and reel)

Standard

TBE

90

Tube

Standard

TRY

90

Tray

Standard

 

Example:

X12

01

02

03

04

05

06

07

08

09

10

(1) PO1 *1 *20 *EA *15.25 *CT *BP *B1234’
(2) PO4 * * * *REL90
UN
(1) LIN +1 + +B1234 :BP +0’
(2) REF
(3) QTY
(4) PRI
(5) PAC + + +REL90 : :116

 

blank_space.gif (96 bytes) ASC X12/UN Element Value Meaning
(1) Base Item: PO101/RFF01.C50602 1 Line Item Number
PO102/QTY01.C18602 20 Number of units of the base item
PO104/PRI01.C50902 15.25 Price per base item unit
PO107/LIN003.C21202 B1234 Product ID for the base part
(2) Package Secondary Packaging
PO404/ PAC03.C20201 REL90 Tape and Reel, Standard
PAC03.C20203 (UN) 116 Responsible Agency is US, ANSI ASC X12

 

 


Concatenated Data


It is recommended not to concatenate two business data items into one data element in a segment. An example of this method is the concatenation of the revision number to its related base product identification number.

If two business data elements are found within one data element in a segment, the receiving trading partner may need to review the single data element to split the components for their internal processing. The receiving party may need to accurately re-concatenate the two data elements into one data element before returning response transactions such as a PO acknowledgment in response to a purchase order.

The receiver of the data would need to know the position where the concatenated data begins. A unique splitting rule may need to be applied per trading partner if several trading partners have this practice.

It is the buyer’s responsibility to separate the two parts of data before sending the data, if their application concatenates data.

In lieu of concatenating data, it is recommended to select a qualifier from the standards data dictionary for Reference Number Qualifier in an REF/RFF segment or Product ID Qualifier in other segments even if the qualifier selected does not have the exact definition. The trading partner arrangement will recognize the codes properly.

SAMPLES OF CONCATENATED PRODUCT AND ENGINEERING CHANGE DATA:

    CONCATENATED into one data element

BASE ID

REVISION

(not recommended in one data element)

1C345654

9

1C345654 9

1C345654

9

1C345654 9

1C345654

9

1C345654 9

1C345654

9

1C345654 9

RECOMMENDED METHODS using ASC X12 as example:

TAG

DE 235 DE 234 DE 235 DE 234

(SEG)

*...* *BP *1C345654 *EC *9
blank.gif (117 bytes)          

TAG

DE 128 DE 127 DE 128 DE 127 DE 128

REF

*DG *DWGA1

REF

*DR *A

 

 


Product Identification Reference and Drawings Overflow


In ASC X12, there are times when all pairs of the Product/Service Identification Qualifier (DE235) and Product/ Service Identification (DE234) in a segment contain data. For example, the ASC X12 LIN segment allows for thirteen DE 235/234 pairs, and the ASC X12 PO1 allows for ten pairs. One drawing reference can use up two pairs (one for the drawing, one for its revision). Some types of products (often custom assemblies) have several drawings which need to be conveyed in a transaction/message.

In UN EDIFACT, this problem rarely occurs, since the standard allows for 60 Product ID references on the PIA segment. The remainder of this section will address only ASC X12, since EDIFACT seems to accommodate the additional codes well.

If there is a need to convey additional product information within the product loop such as the PO1 segment, use REF or N9 segments with appropriate qualifiers. The number of references to send is limited by the standards and reasonable business practices.

Example:



TAG
01/
10/
19
02/
11/
20
03/
12/
21
04/
13/
22
05/
14/
23
06/
15/
24
07/
16/
25

08/
17

09/
18
(1) PO1* 1 * 20 * EA * 15.25 * CT * BP * B1234 * EC * 2
* VP * PT345 * EC * 3 * PT * 1C4 * DR * A #
(2) REF* DG * X234
(3) REF* DR * 1
(4) REF* DG * Y875
(5) REF* DR * 9

 

Segment 1 (Assuming transactions with PO1 segment such as a purchase order)

Line item number

1

Quantity

20

Unit of Measure

Each

Unit Price

15.25

Price Basis

Contract

Buyer part

B1234

BP Engineering Change

2

Vendor part

PT345

VP Engineering Change

3

VP Print or Drawing

1C4

VP Drawing Revision

A
The REF segments contain overflow attributes since only ten attributes were found in the PO1 segment:
Segment 2: The Vendor product has a Drawing Number of X244.
Segment 3: The preceding Drawing Number of X234 has a Drawing Revision value of 1.
Segment 4: The Vendor product has a Drawing Number of Y875.
Segment 5: The preceding Drawing Number of Y875 has a Drawing Revision value of 9.

 


Serial Numbers

In ASC X12 Serial Numbers are conveyed using Reference Number Qualifier (DE128) and Reference Number (DE127) paired data elements, specifically in the REF Reference segment. Multiple occurrences of REF are allowed per base line item.

In UN EDIFACT, Serial Numbers are conveyed using the GIN Goods Identity Number segment. This segment includes the Identity Number Qualifier (DE7405) and several occurrences of the compound element C208 Identity Number Range. Multiple occurrences of Serial Numbers or Serial Number ranges may be sent on one GIN segment and multiple occurrences of GIN are allowed per item.

X12 DE128 Reference Number Qualifier

UN DE7405
Identity Number Qualifier



QUALIFIER MEANING

SE

BN

Serial Number

 

Discrete Serial Numbers vs. Ranges

In ASC X12, back-to-back REF segments with the Serial Number Qualifier ‘SE’ for the Reference Number Qualifier (DE128) can be interpreted as two discrete serial numbers or the beginning and ending serial number for a range of serial numbers. The interpretation is determined by the trading partner arrangement. If there are more than two REF segments for serial numbers, trading partners need to agree on the interpretation.

In EDIFACT, the C208 Identity Qualifier Range in the GIN segment can have either one or two values in the C20801 and C20802 elements (both DE7402). If one value is sent in each C208, the serial number is a discrete serial number. If two values are sent, the two values represent the beginning and end of a range.

EXAMPLES:

TAG DE 128 DE 127
(1) REF * SE * 12234
REF * SE * 12250
REF * SE * 12266
(2) REF * SE * 12234
REF * SE * 12250
blank.gif (117 bytes)          

TAG

DE 7143
C20801 DE 7402 C20802 DE 7402 C20801 DE 7402 C20802 DE 7402 C20801 DE 7402 C20802 DE 7402
Etc.
(1) GIN + BN + 12234 + 12250 + 12266 ...
(2) GIN + BN + 12234 : 12250


Case (1) Serial numbers are discrete serial numbers.

Case (2) Serial numbers are ranges.

In ASC X12, this interpretation of the two REF segments is by trading partner agreement.

Last updated 06 February 2003