ECTF EDIPro Standard
Provided for Use by the Truck Parts
Aftermarket
EDI 810 Invoice (ASC X12 Version 4 Release 1.2-1)
This document contains an outline of common business issues for consideration when implementing the EDI 810 Invoice for ASC X12 Version 4010. It is the intent of this document to act as an addendum to the ASC X12 EDI Standards documentation.
810 Invoice
Included in this document:
Page
Section 1: Business Issues......................................................... 2
Section 2: Segment Notes...................................................... 5
Section 3: Example Transaction......................................... 40
Section 1
810 Invoice
Business Issues
This section contains business discussions about the use of the 810 Invoice. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
Debit and Credit Memos......................................................... 3
Customer Quote/Contract Numbers.................................. 3
Use of Text Fields......................................................................... 3
Identification of Business Location........................................ 3
Service, Promotion, Allowance, or Charge Information 3
Carrier Information.................................................................... 4
Units of Measure......................................................................... 4
Use of Shipping Container Code (SCC-14)........................ 4
Segment Usage.......................................................................... 5
Business Issues
The following business issues should be considered when implementing the 810 Invoice transaction:
ASC X12 has defined two approaches for handling credit and debit memos:
810 Invoice transaction set with the appropriate transaction type code (BIG07), or 812 Credit/Debit Adjustment transaction set, designed specifically for debits and credits. The 812 is not in general use, primarily because the business benefit of generating two separate transaction sets (810 for standard invoices and the 812 for debit and credit invoices) from the invoice process has not yet been demonstrated. It is recommended that the 810 transaction set be used for both.
To support special price considerations the EDI partnership may require that special customer quote numbers, specific contract numbers, or numbers associated with particular promotions be communicated on the purchase order document. It is suggested that the REF segment be used to identify this information
It should be noted that the REF segment may be included at the header portion of the transaction (thereby applying to the entire order), or at the line item level of the order (applying to the specified line).
Both the MAN and the MTX segments promote the inclusion of text data. When using these segments it is recommended that they be restricted to free form text and that any other use for specific data which could be mapped, be discouraged.
It should be noted that the use of text data in EDI transactions should be limited to those specific agreements between trading partners. Anytime text data is passed within a transaction, the receiving partner may have to queue the transaction into an exception process for review. In this case, the transaction cannot be automatically processed.
The DUNS + 4 number is composed of the DUNS number assigned by Dun & Bradstreet, plus (+) a 4 digit suffix number assigned by the buying organization to identify a unique location (store location, plant location, loading dock, department, etc.)
The DUNS + 4 should be used as the primary and preferred method of identifying business locations. Organizations not using the “+ 4” suffix of the DUNS number should insert four zeros in its place.
The Allowance/Charge Indicator (SAC01) rather than the sign of the amount field, should be used to identify a charge or an allowance.
The CAD segment is used to identify the specific carrier and level of service used for a shipment. When specifying a carrier, it is recommended that the Standard Carrier Alpha Code (SCAC) be used. CAD04 is used to identify the carrier and CAD09 is used to identify the “level of service” of the carrier.
As a best practice this standard encourages the use of the data element 355 to describe the quantity unit of measure and the use of data element 639 to describe price unit of measure. When using the SCC-14 to identify an item, the quantity unit of measure is not required (See “Use of Shipping Container Codes SCC-14”).
|
Examples of Unit of Measure Usage |
|||
|
Quantity |
Quantity Unit of Measure |
Price |
Price Unit of Measure |
|
Data element 330 |
Data element 355 |
Data element 212 |
Data element 639 |
|
100 |
EA (each) |
$5.00 |
PE (per each) |
|
500 |
EA (each) |
$6.00 |
HP (per hundred) |
|
10 |
BG (bag) |
$7.00 |
UM (per quantity unit of measure) |
As partnerships enter into the use of SCC-14 codes, considerations need to be outlined. This SCC-14 format includes the designation of the specific package size in the first position of the code. Depending on the item requested, a conflict could exist in the interpretation of the quantity designated in the SCC-14 code and the quantity unit of measure passed in the IT103 element.
Example:
IT102 IT103 IT106 IT107
Qty Qty U/M Product ID Qualifier Product ID (SCC-14) Comments
12 EA UK 30122222222228 Quantity ordered not
resolved
Is the invoice 1 carton of 12, or 12 cartons of 12?
Product ID
(SCC-14) Quantity (Per SCC-14) Description
00122222222227 1 Each
30122222222228 12 Inner Pack
50122222222222 96 Case
To avoid confusion, it is suggested that when using SCC-14 with pack identifier codes, do not include the IT103 element. Therefore, it is clear that the carton size from the SCC-14 pack identifier code is applied against the quantity invoiced as specified in the IT102 element.
IT102 IT103 IT106 IT107
Qty Qty U/M Product ID Qualifier Product ID (SCC-14) Comments
12 Not Used UK 00122222222227 Indicates 12 eaches
12 Not Used UK 30122222222228 Indicates 12 inner
packs of 12 each
If a specific segment appears in the “header” area of the transaction, then the information applies to the whole transaction. If the segment appears in the “detail” portion of the transaction, then the information applies to the detail line only. If both a “header” and a “detail” segment appear, then the “detail” will supersede on the specific line only.
Section 2
810 Invoice
Segment Notes
This section contains business discussions about the use of the segments within the 810 Invoice. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
810.................................................................................................. 7
ST..................................................................................................... 9
BIG............................................................................................... 10
CUR.............................................................................................. 11
REF................................................................................................ 12
N1................................................................................................. 13
N3................................................................................................. 14
N4................................................................................................. 15
ITD................................................................................................ 16
DTM.............................................................................................. 17
FOB............................................................................................... 18
IT1................................................................................................. 19
CTP............................................................................................... 23
PID................................................................................................ 24
REF................................................................................................ 25
SAC.............................................................................................. 26
SLN................................................................................................ 28
PID................................................................................................ 32
TDS............................................................................................... 33
TXI................................................................................................. 34
CAD............................................................................................. 35
SAC.............................................................................................. 37
CTT............................................................................................... 38
SE.................................................................................................. 39
|
|
||
This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
010 |
ST |
Transaction Set Header |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
020 |
BIG |
Beginning Segment for Invoice |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
040 |
CUR |
Currency |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
050 |
REF |
Reference Identification |
O |
12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - N1 |
|
|
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
080 |
N1 |
Name |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
100 |
N3 |
Address Information |
O |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
110 |
N4 |
Geographic Location |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
150 |
ITD |
Terms of Sale/Deferred Terms of Sale |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
160 |
DTM |
Date/Time Reference |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
170 |
FOB |
F.O.B. Related Instructions |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - IT1 |
|
|
200000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
010 |
IT1 |
Baseline Item Data (Invoice) |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
070 |
CTP |
Pricing Information |
O |
25 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - PID |
|
|
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
100 |
PID |
Product/Item Description |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
160 |
REF |
Reference Identification |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SAC |
|
|
25 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
240 |
SAC |
Service, Promotion, Allowance, or Charge Information |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SLN |
|
|
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
260 |
SLN |
Subline Item Detail |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
290 |
PID |
Product/Item Description |
O |
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Transaction Set Header |
Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 |
To indicate the start of a transaction set and to assign a control number.
Example:
ST*810*0001^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
ST01 |
143 |
Transaction Set Identifier Code Description: Code uniquely identifying a Transaction Set Code NAME
_ 810 Invoice |
M |
ID |
3/3 |
|
|
|
|
ST02 |
329 |
Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set ECTF Notes: Incremental counter that is assigned by the sender. It must match the control # in the SE
segment. |
M |
AN |
4/9 |
|
|
|
Beginning Segment for Invoice |
Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 5 |
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates.
Example:
BIG*20010520*0798765001*20010510*092123456***DR^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
BIG01 |
373 |
Date Description: Date expressed as CCYYMMDD |
M |
DT |
8/8 |
|
|
|
|
BIG02 |
76 |
Invoice Number Description: Identifying number assigned by issuer |
M |
AN |
1/22 |
Note: Karmak System Limit is 10. |
|
|
|
BIG03 |
373 |
Date Description: Date expressed as CCYYMMDD |
O |
DT |
8/8 |
|
|
|
|
BIG04 |
324 |
Purchase Order Number Description: Identifying number for Purchase Order assigned by the orderer/purchaser |
O |
AN |
1/22 |
|
|
|
|
BIG07 |
640 |
Transaction Type Code Description: Code specifying the type of transaction Code NAME
_ CR Credit Memo DR Debit Memo |
O |
ID |
2/2 |
|
|
|
Currency |
Pos: 040 Max: 1 Heading - Optional Loop: N/A Elements: 2 |
To specify the currency (dollars, pounds, francs, etc.) used in a transaction.
ECTF Notes:
Currency Code (CUR02) would typically be used when transacting business in multiple countries. Refer to ISO 4217 for standard currency codes.
Example:
CUR*SE*USD^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
CUR01 |
98 |
Entity Identifier Code Description: Code identifying an organizational entity, a physical location, property or an individual Code NAME
_ BY Buying Party (Purchaser) SE Selling Party |
M |
ID |
2/3 |
|
|
|
|
CUR02 |
100 |
Currency Code Description: Code (Standard ISO) for country in whose currency the charges are specified Code NAME _ CAD Canadian Dollar MXP Mexican Peso USD U.S. Dollar |
M |
ID |
3/3 |
|
|
|
Reference Identification |
Pos: 050 Max: 12 Heading - Optional Loop: N/A Elements: 2 |
To specify identifying information.
ECTF Notes:
This segment can optionally be used to communicate different reference numbers such as customer price reference numbers, quote numbers, or other reference numbers. When included at this level, the reference number specified applies to all items on the order unless an override reference number is encountered at the line item level.
Example:
REF*BM*0798765001^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
REF01 |
128 |
Reference Identification Qualifier Description: Code qualifying the Reference Identification Code NAME
_ BM Bill of Lading Number CO Customer Order Number DG Drawing Number LT Lot Number PK Packing List Number NT General Notes PD Promotion/Deal Number PR Price Quote Number SI Shipper's Identifying Number for
Shipment (SID) Description: A unique number (to the shipper) assigned
by the shipper to identify the shipment |
M |
ID |
2/3 |
|
|
|
|
REF02 |
127 |
Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier |
C |
AN |
1/30 |
|
|
|
Name |
Pos: 080 Max: 1 Heading - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code.
ECTF Notes:
DUNS+4 should be considered the primary and preferred method of identifying a location.
Example:
N1*BY*ABC DISTRIBUTION*9*0012345670000^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
||
|
|
N101 |
98 |
Entity Identifier Code Description: Code identifying an organizational entity, a physical location, property or an individual Code NAME
_ BS Bill and Ship To BT Bill-to-Party BF Bill From BY Buying Party (Purchaser) EN End User RE Party to receive commercial invoice
remittance SF Ship From SE Selling Party ST Ship To |
M |
ID |
2/3 |
|
Note: Karmak system requires two segments. One Buyer and one Seller (only two expected). Buyer
Seller |
|
|
|
N102 |
93 |
Name Description: Free-form name |
C |
AN |
1/60 |
|
||
|
|
N103 |
66 |
Identification Code Qualifier Description: Code designating the system/method of code structure used for Identification Code (67) Code NAME _ 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4,D-U-N-S Number with Four
Character Suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer or Buyer's Agent |
C |
ID |
1/2 |
|
||
|
|
N104 |
67 |
Identification Code Description: Code identifying a party or other code |
C |
AN |
2/80 |
|
||
|
Address Information |
Pos: 100 Max: 2 Heading - Optional Loop: N1 Elements: 2 |
To specify the location of the named party.
Example:
N3*100 S. LASALLE ST.*SUITE 410^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
N301 |
166 |
Address Information Description: Address information |
M |
AN |
1/55 |
|
|
|
|
N302 |
166 |
Address Information Description: Address information |
O |
AN |
1/55 |
|
|
|
Geographic Location |
Pos: 110 Max: 1 Heading - Optional Loop: N1 Elements: 4 |
To specify the geographic place of the named party.
ECTF Notes:
Country Code (N404) would typically be used when transacting business in multiple countries. Refer to ISO 3166 for standard country codes.
Example:
N4*CHICAGO*IL*60601*USA^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
N401 |
19 |
City Name Description: Free-form text for city name |
O |
AN |
2/30 |
|
|
|
|
N402 |
156 |
State or Province Code Description: Code (Standard State/Province) as defined by appropriate government agency |
O |
ID |
2/2 |
|
|
|
|
N403 |
116 |
Postal Code Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) |
O |
ID |
3/15 |
|
|
|
|
N404 |
26 |
Country Code Description: Code identifying the country Code NAME _ CAN Canada MEX Mexico USA U.S.A. |
O |
ID |
2/3 |
|
|
|
Terms of Sale/Deferred Terms of Sale |
Pos: 150 Max: >1 Heading - Optional Loop: N/A Elements: 7 |
To specify terms of sale.
Example:
ITD*15*3*2*20010520**20010525**12402****2% 10th PROX NET EOM^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
ITD01 |
336 |
Terms Type Code Description: Code identifying type of payment terms Code NAME
_ 01 Basic 09 Proximo 15 Special Proximo |
M |
ID |
2/2 |
|
|
|
|
ITD02 |
333 |
Terms Basis Date Code Description: Code identifying the beginning of the terms period Code NAME
_ 3 Invoice Date |
M |
ID |
1/2 |
|
|
|
|
ITD03 |
338 |
Terms Discount Percent Description: Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date. Include decimal point if not a whole number. (example: 2.5 is 2.5%) |
O |
R |
1/6 |
|
|
|
|
ITD04 |
370 |
Terms Discount Due Date Description: Date payment is due if discount is to be earned expressed in format CCYYMMDD |
C |
DT |
8/8 |
|
|
|
|
ITD06 |
446 |
Terms Net Due Date Description: Date when total invoice amount becomes due expressed in format CCYYMMDD |
M |
DT |
8/8 |
|
|
|
|
ITD08 |
362 |
Terms Discount Amount Description: Total amount of terms discount. The decimal point is assumed and should not be included in the amount. ECTF Notes: The amount in
this example is interpreted as $270.85. |
O |
N2 |
1/10 |
|
|
|
|
ITD12 |
352 |
Description Description: A free-form description to clarify the related data elements and their content |
O |
AN |
1/80 |
|
|
|
Date/Time Reference |
Pos: 160 Max: 10 Heading - Optional Loop: N/A Elements: 2 |
To specify pertinent dates and times.
Example:
DTM*011*20010520^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
DTM01 |
374 |
Date/Time Qualifier Description: Code specifying type of date or time, or both date and time Code NAME _ 011 Shipped |
M |
ID |
3/3 |
|
|
|
|
DTM02 |
373 |
Date Description: Date expressed as CCYYMMDD |
C |
DT |
8/8 |
|
|
|
F.O.B. Related Instructions |
Pos: 170 Max: 1 Heading - Optional Loop: N/A Elements: 1 |
To specify transportation instructions relating to shipment.
ECTF Notes:
This segment can optionally be used to communicate freight payment responsibility.
Example:
FOB*PP^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
FOB01 |
146 |
Shipment Method of Payment Description: Code identifying payment terms for transportation charges Code NAME
_ CC Collect PC Prepaid but Charged to Customer PP Prepaid (by Seller) PU Pickup |
M |
ID |
2/2 |
|
|
|
Baseline Item Data (Invoice) |
Pos: 010 Max: 1 Detail - Optional Loop: IT1 Elements: 25 |
To specify the basic and most frequently used line item data for the invoice and related transactions.
ECTF Notes:
IT106 through IT125 provide for multiple product/service IDs for each item. If only one product/service ID is provided, IT106 and IT107 are used. IT108 and IT109 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
In trading partnerships in which the order line # can be changed by the supplier, and both the original and "changed-to" line # are carried through the order/invoice cycle, a Product/Service ID qualifier of "PL" (buying party's order line #) may be used in conjunction with the Assigned Identifier on the transaction line segment (IT1).
Multiple product/service ID's can be presented in any sequence.
Example:
IT1*0001*10000*PC*5.33*TP*VC*P-8750*UI*09999982010*BP*CC-14*CH*USA^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
IT101 |
350 |
Assigned Identification Description: Alphanumeric characters assigned for differentiation within a transaction set ECTF Notes: Data element
IT101 should reflect the buyer's unique line number. This may not be possible
in an 810 generated for a VMI order or non-EDI order. |
O |
AN |
1/20 |
|
|
|
|
IT102 |
358 |
Quantity Invoiced Description: Number of units invoiced |
C |
R |
1/10 |
|
|
|
|
IT103 |
355 |
Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Code NAME _ BG Bag BK Book CA Case CG Card CT Carton EA Each FT Foot HU Hundred KG Kilogram LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
C |
ID |
2/2 |
|
|
|
|
IT104 |
212 |
Unit Price Description: Price per unit of product, service, commodity, etc. ECTF Notes: As a best
practice, this standard encourages the use of unit price to proactively identify
and resolve pricing discrepancies.
IT104 unit price is the net price for the line item on the
invoice. Trading partnerships using
list price and multipliers can use list price in the IT104 and the multiplier
in the CTP segment. |
C |
R |
1/17 |
|
|
|
|
IT105 |
639 |
Basis of Unit Price Code Description: Code identifying the type of unit price for an item ECTF Notes: This element
should contain the appropriate price unit of measure code associated with the
price. Code NAME _ HF Per 100 Feet HP Price per Hundred PE Price per Each PF Price Per Foot PP Price per Pound TF Per 1000 Feet TP Price per Thousand UM Price per Unit of Measure |
O |
ID |
2/2 |
|
|
|
|
IT106 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) ECTF Notes: The IT1 segment
allows for ten independent occurrences of the 235 Product/Service ID
Qualifier and 234 Product/Service ID data elements. Use qualifiers from the list as noted in the IT106 data element
for each occurrence of the 235 data element. It is recommended that the
U.P.C. number for an item be included when it exists. In addition, most partnerships recommend
that the vendor's part number or the customer's part number be included along
with the U.P.C. number. Code NAME
_ BP Buyer's Part Number CB Buyer's Catalog Number CH Country of Origin Code EN European Article Number (EAN) (2-5-5-1) HD International Harmonized Commodity Code Description: For customs authority purposes, the class
and description of a subject part or material item per harmonized agreements
on tariff commodity codes U2 U.P.C. Shipping Container Code (1-2-5-5) Description: A 13-digit code that uniquely identifies
the manufacturer's shipping unit, including the packaging indicator; the
first digit is the packaging indicator, the next two digits are the number
system characters, the next five digits are the manufacturer ID number, and
the remaining five digits are the item code UD U.P.C./EAN Consumer Package Code (2-5-5) UI U.P.C. Consumer Package Code (1-5-5) UK U.P.C./EAN Shipping Container Code
(1-2-5-5-1) Description: A 14-digit code that uniquely identifies
the manufacturer's shipping unit, including the packaging indicator and check
digit; the first digit is the packaging indicator, the next two digits are
the number system characters, the next five digits are the manufacturer ID
number, the second five digits are the item code, and the final digit is the
check digit VC Vendor's (Seller's) Catalog Number VP Vendor's (Seller's) Part Number |
C |
ID |
2/2 |
|
|
|
|
IT107 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
Note: This should your published
part number |
|
|
|
IT108 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT109 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT110 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT111 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT112 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT113 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT114 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT115 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT116 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT117 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT118 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT119 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT120 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT121 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT122 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT123 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
IT124 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
|
IT125 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
Pricing Information |
Pos: 070 Max: 25 Detail - Optional Loop: IT1 Elements: 2 |
To specify pricing information.
Example:
CTP******DIS*.90^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
CTP06 |
648 |
Price Multiplier Qualifier Description: Code indicating the type of price multiplier ECTF Notes: This element is
the Price Multiplier Qualifier. It is
used to provide a multiplier to the price listed in IT1 segment. Code NAME
_ DIS Discount Multiplier SEL Selling Multiplier |
O |
ID |
3/3 |
|
|
|
|
CTP07 |
649 |
Multiplier Description: Value to be used as a multiplier to obtain a new value |
C |
R |
1/10 |
|
|
|
Product/Item Description |
Pos: 100 Max: 1 Detail - Optional Loop: PID Elements: 2 |
To describe a product or process in coded or free-form format.
ECTF Notes:<