ECTF EDIPro Standard
Provided for
Use by the Truck Parts Aftermarket
EDI 855 Purchase Order Acknowledgement (ASC X12 Version 4 Release 1)
This document contains an outline of common business issues for consideration when implementing the EDI 855 Purchase Order Acknowledgement for ASC X12 Version 4010. It is the intent of this document to act as an addendum to the ASC X12 EDI Standards documentation.
855 Purchase Order
Acknowledgement
Included in this document:
Page
Section 1: Business Issues......................................................... 2
Section 2: Purchase Order Process....................................... 6
Section 3: Segment Notes.................................................... 10
Section 4: Example Transaction......................................... 59
Section 1
855 Purchase Order
Acknowledgment
Business Issues
This section contains business discussions about the use of the 855 Purchase Order Acknowledgment. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
Acknowledging a Customer Purchase Order With Changes 3
Customer Quote/Contract Numbers.................................. 3
Use of Text Fields......................................................................... 3
Identification of Business Location........................................ 3
Service, Promotion, Allowance, or Charge Information 3
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 855 Purchase Order Acknowledgement transaction:
When an 855 order acknowledgment document is used to acknowledge a customer’s purchase order, quantity or price changes can be included in accordance with the following X12 guideline:
The PO1 segment should contain all of the item specific information received from the customer’s purchase order (850). The PO3 segment could be included within the PO1 loop to include any changed quantity and/or any changed price. The ACK segment should also be included to provide an outline of other changes.
Note: Individual trading partnerships may choose to use the PO1 segment to send the full line item data including changes from the original 850 document.
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 (see detailed REF discussion below).
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.
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 PO103 element.
Example:
PO102 PO103 PO106 PO107
Qty Qty U/M Product ID Qualifier Product ID (SCC-14) Comments
12 EA UK 30122222222228 Quantity ordered not
resolved
Is the order 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 PO103 element. Therefore, it is clear that the carton size from the SCC-14 pack identifier code is applied against the quantity ordered as specified in the PO102 element.
PO102 PO103 PO106 PO107
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
850 Purchase Order
Business Process
This section contains business discussions about the use of purchase order cycle documents. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
Business Case............................................................................... 7
Sample Business Cases.............................................................. 8
Suggested Guidelines............................................................... 8
Transaction Definition............................................................... 9
Electronic Commerce:
Automating the
Order/Order Change Process
Abstract: This section attempts to clarify the
order/order change process and to suggest a method of automation with the goal
of improving the timing and accuracy of order information .
The business processes to be discussed will start with the initial placing of an order and continue through the acknowledgment of any changes to the order. This process can be divided into four transactions.
|
Order Process |
Case 1 |
Case 2 |
Case 3 |
Case 4 |
Case 5 |
||||
|
B |
® |
850 Purchase Order |
® |
S |
4 |
4 |
|
|
|
|
U Y |
¬ |
855 Purchase Order Acknowledgment |
¬ |
E L |
|
4 |
|
4 |
|
|
E R |
® |
860 Purchase Order Change Request |
® |
L E |
|
|
4 |
|
4 |
|
|
¬ |
865 Purchase Order Change Acknowledgment / Request |
¬ |
R |
|
|
4 |
4 |
4 |
Refer to the definition of the example business cases on the next page.
Case 1 Purchase Order Only Processing
The 850 transaction could be implemented as a single transaction between the buyer and seller.
Case 2 Purchase Order and Acknowledgment Processing
To demonstrate how the order process could be implemented, the 850 would be used to transmit the initial purchase order. Then the 855 transaction would be used to acknowledge the order, as well as to communicate changes to the order such as substitutions, ship dates, and price.
Case 3 Buyer Initiated Change
To demonstrate how some partners may wish to process changes to purchase orders, the buyer initiated change request could be communicated using an 860 transaction. If a seller acknowledgment is required then an 865 transaction would be generated confirming, rejecting or stating changes to the 860 change request.
Case 4 Alternative Change Acknowledgments
It is the suggested guideline that the 855 be used to acknowledge an initial order.
However, if an acknowledgment transaction is required in response to a purchase order change request then the industry guideline allows for either an 855 Purchase Order Acknowledgment or an 865 Purchase Order Change Acknowledgment to be sent by the seller dependent on the buyers preference.
If a buyer is capable of receiving an 865 then the use of the 865 is preferred.
Case 5 Seller Initiate Changes
In some advanced partnerships the 865 can be used by the seller to notify the buyer of a seller initiated change to the order, such as substitutions, and ship date changes. In this case, if the partnership requires that the buyer acknowledge the change, then the 860 can be sent confirming or rejecting the seller initiated changes.
In the interest of furthering the cause of electronic commerce, this document is going to suggest a common usage of this group of transactions. It is acknowledged that variations from this suggested standard will exist, but should be treated as exceptions.
It is suggested that the:
· 855 be used by the seller to acknowledge the receipt of the initial purchase order. This transaction can be used to accept the order as received or to indicate acceptance with changes to the order.
· 855 be used by the seller to notify the buyer of a vendor generated order (VMI environment).
· 860 be used by the buyer to communicate any changes to the order.
· 855 or the 865 can alternatively be used by the seller to communicate a change to the purchase order. This transaction could be seller initiated, or in response to a buyer’s 860 Purchase Order Change Request. The choice of which transaction to use will be dependent on the specific partnership, however the use of the 865 is preferred.
850 Purchase Order
This buyer initiated transaction communicates the purchase order to the seller.
855 Purchase Order Acknowledgment
This seller initiated transaction permits the communication of the acknowledgment of the buyer’s initial purchase order.
Under the proposed guidelines, this transaction could also be used later in the order cycle for the seller to communicate another change to the purchase order, such as a delivery date change, or to acknowledge a change request from the buyer. (Refer to the Suggested Guidelines above for additional comments on when to use this transaction.)
860 Purchase Order Change Request
This buyer initiated transaction permits the communication of a requested change to the purchase order.
It is anticipated that this transaction would only be used when associated with orders that reside in the sellers system for a long duration. This is normally used to change blanket orders, orders with scheduled ship dates, or any order that might fall into the futures category.
It should be noted that the 860 can be used by the buyer to confirm a change associated with a seller initiated change to a purchase order. This could be a response to a 855 or to a 865 depending on the partnership and the timing of the transactions.
865 Purchase Order Change
Acknowledgment/Request
This seller initiated transaction permits the communication of the acknowledgment of change to a buyer purchase order. It also permits the seller to communicate additional changes to the accepted order.
Under the proposed guidelines, this transaction could also be used later in the order cycle for the seller to communicate another change to the purchase order, such as a delivery date change, or to acknowledge a change request from the buyer. (Refer to the Suggested Guidelines above for additional comments on when to use this transaction.)
The 865 is usually sent in response to 860 change request.
Section 3
855 Purchase Order
Acknowledgment
Segment Notes
This section contains business discussions about the segments used in the 855 Purchase Order Acknowledgment. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
855................................................................................................ 11
ST.................................................................................................. 13
BAK............................................................................................... 14
CUR.............................................................................................. 16
REF................................................................................................ 17
PER............................................................................................... 18
FOB............................................................................................... 19
CSH.............................................................................................. 20
SAC.............................................................................................. 21
DTM.............................................................................................. 22
TD5............................................................................................... 23
TD3............................................................................................... 25
MAN............................................................................................ 26
N1................................................................................................. 27
N3................................................................................................. 28
N4................................................................................................. 29
PO1.............................................................................................. 30
PO3.............................................................................................. 34
PID................................................................................................ 36
REF................................................................................................ 37
SAC.............................................................................................. 38
IT8................................................................................................. 39
DTM.............................................................................................. 40
ACK.............................................................................................. 41
MAN............................................................................................ 44
SCH.............................................................................................. 45
N1................................................................................................. 47
N3................................................................................................. 48
N4................................................................................................. 49
SLN................................................................................................ 50
PID................................................................................................ 54
CTT............................................................................................... 55
SE.................................................................................................. 56
|
|
||
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
030 |
ST |
Transaction Set Header |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
040 |
BAK |
Beginning Segment for Purchase Order Acknowledgment |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
050 |
CUR |
Currency |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
060 |
REF |
Reference Identification |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
070 |
PER |
Administrative Communications Contact |
O |
3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
090 |
FOB |
F.O.B. Related Instructions |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
120 |
CSH |
Sales Requirements |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SAC |
|
|
25 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
130 |
SAC |
Service, Promotion, Allowance, or Charge Information |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
180 |
DTM |
Date/Time Reference |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
270 |
TD5 |
Carrier Details (Routing Sequence/Transit Time) |
O |
12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
280 |
TD3 |
Carrier Details (Equipment) |
O |
12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
300 |
MAN |
Marks and Numbers |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - N1 |
|
|
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
360 |
N1 |
Name |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
380 |
N3 |
Address Information |
O |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
390 |
N4 |
Geographic Location |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - PO1 |
|
|
100000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
010 |
PO1 |
Baseline Item Data |
O |
1 |
|
N2/010 |
|
|
|
|
|
|
|
|
|
|
|
|
|
050 |
PO3 |
Additional Item Detail |
O |
25 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - PID |
|
|
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
090 |
PID |
Product/Item Description |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
130 |
REF |
Reference Identification |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SAC |
|
|
25 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
150 |
SAC |
Service, Promotion, Allowance, or Charge Information |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
170 |
IT8 |
Conditions of Sale |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
250 |
DTM |
Date/Time Reference |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - ACK |
|
|
104 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
310 |
ACK |
Line Item Acknowledgment |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
330 |
MAN |
Marks and Numbers |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SCH |
|
|
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
410 |
SCH |
Line Item Schedule |
O |
1 |
|
N2/410 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - N1 |
|
|
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
500 |
N1 |
Name |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
520 |
N3 |
Address Information |
O |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
530 |
N4 |
Geographic Location |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - SLN |
|
|
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
670 |
SLN |
Subline Item Detail |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
700 |
PID |
Product/Item Description |
O |
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - CTT |
|
|
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
010 |
CTT |
Transaction Totals |
O |
1 |
|
N3/010 |
|
|
|
|
|
|
|
|
|
|
|
|
|
030 |
SE |
Transaction Set Trailer |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Transaction Set Header |
Pos: 030 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*855*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
_ 855 Purchase Order Acknowledgment |
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 |
M |
AN |
4/9 |
|
|
|
Beginning Segment for Purchase Order Acknowledgment |
Pos: 040 Max: 1 Heading - Mandatory Loop: N/A Elements: 6 |
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates.
Example:
BAK*00*AC*092123456*20010331****0798765*20010331^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
BAK01 |
353 |
Transaction Set Purpose Code Description: Code identifying purpose of transaction set Code NAME
_ 00 Original 04 Change 42 Temporary Record Description: Preliminary data that will be
replaced with permanent information once verification of accuracy and
completeness has been performed |
M |
ID |
2/2 |
|
|
|
|
BAK02 |
587 |
Acknowledgment Type Description: Code specifying the type of acknowledgment ECTF Notes:
Code specifying the type of acknowledgment. Code AP supports a Vendor Managed Inventory (VMI) environment
in which the 855 is used by a buying party to setup a supplier generated
order on their business system. Code NAME
_ AC Acknowledge - With Detail and Change AD Acknowledge - With Detail, No Change AE Acknowledge - With Exception Detail Only AH Acknowledge - Hold Status AK Acknowledge - No Detail or Change AP Acknowledge - Product Replenishment |
M |
ID |
2/2 |
|
|
|
|
BAK03 |
324 |
Purchase Order Number Description: Identifying number for Purchase Order assigned
by the orderer/purchaser |
M |
AN |
1/22 |
|
|
|
|
BAK04 |
373 |
Date Description: Date expressed as CCYYMMDD |
M |
DT |
8/8 |
|
|
|
|
BAK08 |
127 |
Reference Identification Description: Reference information as defined for a
particular Transaction Set or as specified by the Reference Identification
Qualifier ECTF Notes:
Seller's order number. |
O |
AN |
1/30 |
|
|
|
|
BAK09 |
373 |
Date Description: Date expressed as CCYYMMDD |
O |
DT |
8/8 |
|
|
|
Currency |
Pos: 050 Max: 1 Heading - Optional Loop: N/A Elements: 2 |
To specify the currency (dollars, pounds, francs, etc.) used in a transaction.
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 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: 060 Max: >1 Heading - Optional Loop: N/A Elements: 2 |
To specify identifying information.
ECTF Notes:
This segment can optionally be used to communicate customer price, quote numbers, or other reference numbers. When included at this level, the quote number specified applies to all items on the order unless an override quote number exists at the detail line level.
Example:
REF*PR*ABC-12345-1^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
REF01 |
128 |
Reference Identification
Qualifier Description: Code qualifying the Reference Identification Code NAME
_ CO Customer Order Number DG Drawing Number PD Promotion/Deal Number PR Price Quote Number |
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 |
|
|
|
Administrative Communications Contact |
Pos: 070 Max: 3 Heading - Optional Loop: N/A Elements: 8 |
To identify a person or office to whom administrative communications should be directed.
Example:
PER*BD*JANE SMITH*TE*3121234567^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PER01 |
366 |
Contact Function Code Description: Code identifying the major duty or responsibility
of the person or group named Code NAME
_ BD Buyer Name or Department OC Order Contact |
M |
ID |
2/2 |
|
|
|
|
PER02 |
93 |
Name Description: Free-form name |
O |
AN |
1/60 |
|
|
|
|
PER03 |
365 |
Communication Number Qualifier Description: Code identifying the type of communication
number Code NAME
_ EM Electronic Mail FX Facsimile TE Telephone |
C |
ID |
2/2 |
|
|
|
|
PER04 |
364 |
Communication Number Description: Complete communications number including
country or area code when applicable |
C |
AN |
1/80 |
|
|
|
|
PER05 |
365 |
Communication Number Qualifier Description: Code identifying the type of communication
number |
C |
ID |
2/2 |
|
|
|
|
PER06 |
364 |
Communication Number Description: Complete communications number including
country or area code when applicable |
C |
AN |
1/80 |
|
|
|
|
PER07 |
365 |
Communication Number Qualifier Description: Code identifying the type of communication
number |
C |
ID |
2/2 |
|
|
|
|
PER08 |
364 |
Communication Number Description: Complete communications number including
country or area code when applicable |
C |
AN |
1/80 |
|
|
|
F.O.B. Related Instructions |
Pos: 090 Max: >1 Heading - Optional Loop: N/A Elements: 1 |
To specify transportation instructions relating to shipment.
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 |
|
|
|
Sales Requirements |
Pos: 120 Max: 1 Heading - Optional Loop: N/A Elements: 1 |
To specify general conditions or requirements of the sale.
Example:
CSH*BK^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
CSH01 |
563 |
Sales Requirement Code Description: Code to identify a specific requirement or
agreement of sale Code NAME _ N No Back Order BK Ship Partial - Balance Back Order SC Ship Complete SP Ship Partial,Balance Cancel |
O |
ID |
1/2 |
|
|
|
Service, Promotion, Allowance, or Charge Information |
Pos: 130 Max: 1 Heading - Optional Loop: SAC Elements: 5 |
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge.
ECTF Notes:
For all data elements within this segment, the decimal point is assumed and should not be included in the amount.
Example:
SAC*C*F050***1000*******06***MISC CHARGE DESCRIPTION^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
SAC01 |
248 |
Allowance or Charge Indicator Description: Code which indicates an allowance or charge for
the service specified Code NAME
_ A Allowance C Charge |
M |
ID |
1/1 |
|
|
|
|
SAC02 |
1300 |
Service, Promotion, Allowance, or
Charge Code Description: Code identifying the service, promotion,
allowance, or charge Code NAME
_ A010 Absolute Minimum Charge D240 Freight D500 Handling F050 Other (See related description) |
C |
ID |
4/4 |
|
|
|
|
SAC05 |
610 |
Amount Description: Monetary amount |
O |
N2 |
1/15 |
|
|
|
|
SAC12 |
331 |
Allowance or Charge Method of
Handling Code Description: Code indicating method of handling for an
allowance or charge Code NAME
_ 03 Vendor Check to Customer 04 Credit Customer Account 09 Allowance To Be Issued by Vendor Description: Code designating vendor as
the issuer of an allowance |
O |
ID |
2/2 |
|
|
|
|
SAC15 |
352 |
Description Description: A free-form description to clarify the related
data elements and their content |
C |
AN |
1/80 |
|
|
|
Date/Time Reference |
Pos: 180 Max: 10 Heading - Optional Loop: N/A Elements: 2 |
To specify pertinent dates and times.
Example:
DTM*037*20010413^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
DTM01 |
374 |
Date/Time Qualifier Description: Code specifying type of date. Code NAME
_ 001 Cancel After 002 Delivery Requested 010 Requested Ship 037 Ship Not Before 038 Ship No Later 039 Ship Week of 106 Required By 118 Requested Pick-up 372 Actual Arrival Date |
M |
ID |
3/3 |
|
|
|
|
DTM02 |
373 |
Date Description: Date expressed as CCYYMMDD |
C |
DT |
8/8 |
|
|
|
Carrier Details (Routing Sequence/Transit Time) |
Pos: 270 Max: 12 Heading - Optional Loop: N/A Elements: 5 |
To specify the carrier and sequence of routing and provide transit time information.
ECTF Notes:
Preferred Carrier
To specify a specific carrier preference a TD502 element should be included having a qualifier of "2", followed by a TD503 element containing a valid Standard Carrier Alpha Code (SCAC) describing the preferred carrier. The SCAC table is a certified list of four character codes associated with specific carriers. This list is published by the National Motor Freight Traffic Association. Examples of SCAC codes are listed below.
Code Description
CFWY Consolidated Freightways (Type - LTL)
FEPL Federal Express (Type - Air)
OVNT Overnight (Type - LTL)
Shipment Method
To specify a method of shipment a TD504 element should be included having a valid qualifier describing the method requested.
Service Level
To specify a service level a TD512 element should be included having a valid qualifier describing the service level requested.
Example:
TD5**2*AAAA*M*AAA FREIGHT CO.*******PS^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
TD502 |
66 |
Identification Code Qualifier Description: Code designating the system/method of code
structure used for Identification Code TD503 (67) Code NAME
_ 2 Standard Carrier Alpha Code (SCAC) 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer or Buyer's Agent |
C |
ID |
1/2 |
|
|
|
|
TD503 |
67 |
Identification Code Description: Code identifying a party or other code |
C |
AN |
2/80 |
|
|
|
|
TD504 |
91 |
Transportation Method/Type Code Description: Code specifying the method or type of
transportation for the shipment Code NAME
_ A Air H Customer Pickup M Motor (Common Carrier) T Best Way (Shippers Option) U Private Parcel Service AE Air Express LT Less Than Trailer Load (LTL) SR Supplier Truck |
C |
ID |
1/2 |
|
|
|
|
TD505 |
387 |
Routing Description: Free-form description of the routing or
requested routing for shipment, or the originating carrier's identity |
C |
AN |
1/35 |
|
|
|
|
TD512 |
284 |
Service Level Code Description: Code indicating the level of transportation
service or the billing service offered by the transportation carrier Code NAME
_ 09 Premium Surface Description: Indicates that alternate
routing instructions should be used instead of the regular ones given ND Next Day Air Description: Delivery during business day
hours of next business day ON Overnight SC Second Day Air Description: Delivery during business day
hours no later than second business day SD Saturday SE Second Day SG Standard Ground |
C |
ID |
2/2 |
|
|
|
Carrier Details (Equipment) |
Pos: 280 Max: 12 Heading - Optional Loop: N/A Elements: 1 |
To specify transportation details relating to the equipment used by the carrier.
Example:
TD3*LU^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
TD301 |
40 |
Equipment Description Code Description: Code identifying type of equipment used for
shipment Code NAME
_ LU Load/unload Device on Equipment TL Trailer (not otherwise specified) |
C |
ID |
2/2 |
|
|
|
Marks and Numbers |
Pos: 300 Max: 10 Heading - Optional Loop: N/A Elements: 2 |
To indicate identifying marks and numbers for shipping containers.
ECTF Notes:
Use of this segment to pass other data is discouraged.
Example:
MAN*PB*SP-654321-006^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
MAN01 |
88 |
Marks and Numbers Qualifier Description: Code specifying the application or source of
Marks and Numbers MAN02 (87) Code NAME
_ S Entire Shipment PB Premarked by Buyer |
M |
ID |
1/2 |
|
|
|
|
MAN02 |
87 |
Marks and Numbers Description: Marks and numbers used to identify a shipment
or parts of a shipment |
M |
AN |
1/48 |
|
|
|
Name |
Pos: 360 Max: 1 Heading - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code.
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 BY Buying Party (Purchaser) EN End User SE Selling Party ST Ship To |
M |
ID |
2/3 |
|
|
|
|
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 N104 (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: 380 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: 390 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 United States |
O |
ID |
2/3 |
|
|
|
Baseline Item Data |
Pos: 010 Max: 1 Detail - Optional Loop: PO1 Elements: 25 |
To specify basic and most frequently used line item data.
ECTF Notes:
PO101 is used to send back the item information obtained from the original purchase order. PO106 through PO125 provide for multiple product/service IDs for each item. If only one product/service ID is provided, PO106 and PO107 should be used. PO108 and PO109 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
PO1*0001*12900*EA*5.43*TP*VC*P-8750*UI*09999982010*BP*CC-14^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PO101 |
350 |
Assigned Identification Description: Alphanumeric characters assigned for
differentiation within a transaction set ECTF Notes:
Data element PO101 should reflect the buyer's unique line number. This
may not be possible in an 855 generated for a VMI order or non-EDI order. |
O |
AN |
1/20 |
|
|
|
|
PO102 |
330 |
Quantity Ordered Description: Quantity ordered |
C |
R |
1/15 |
|
|
|
|
PO103 |
355 |
Unit or Basis for Measurement
Code Description: Code specifying the units in which a value is
being expressed, or manner in which a measurement has been taken ECTF Notes:
One of the greatest difficulties in establishing trading partnerships
is the sharing of quantities with a possibility of interpretation problems
associated with quantity unit of measures.
Usually this only affects a small segment of products communicated,
therefore the problem does not always appear in the initial test transaction. For any
unit of measurement other than "each", both partners would be
advised to discuss their intent prior to implementing this transaction. Code NAME
_ BG Bag BK Book CA Case CG Card CT Carton EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
O |
ID |
2/2 |
|
|
|
|
PO104 |
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. |
C |
R |
1/17 |
|
|
|
|
PO105 |
639 |
Basis of Unit Price Code Description: Code identifying the type of unit price for an
item ECTF Notes:
Each time a price is used, this element should contain the appropriate
print 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 PR Promotion TF Per 1000 Feet TP Price per Thousand UM Price per Unit of Measure |
O |
ID |
2/2 |
|
|
|
|
PO106 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) ECTF Notes:
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 EN European Article Number (EAN) (2-5-5-1) RK Rack Number 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 |
|
|
|
|
PO107 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO108 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in PO106 |
C |
ID |
2/2 |
|
|
|
|
PO109 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO110 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in PO106. |
C |
ID |
2/2 |
|
|
|
|
PO111 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
Name |
Pos: 360 Max: 1 Heading - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code.
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 BY Buying Party (Purchaser) EN End User SE Selling Party ST Ship To |
M |
ID |
2/3 |
|
|
|
|
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 N104 (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: 380 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: 390 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 United States |
O |
ID |
2/3 |
|
|
|
Baseline Item Data |
Pos: 010 Max: 1 Detail - Optional Loop: PO1 Elements: 25 |
To specify basic and most frequently used line item data.
ECTF Notes:
PO101 is used to send back the item information obtained from the original purchase order. PO106 through PO125 provide for multiple product/service IDs for each item. If only one product/service ID is provided, PO106 and PO107 should be used. PO108 and PO109 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
PO1*0001*12900*EA*5.43*TP*VC*P-8750*UI*09999982010*BP*CC-14^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PO101 |
350 |
Assigned Identification Description: Alphanumeric characters assigned for
differentiation within a transaction set ECTF Notes:
Data element PO101 should reflect the buyer's unique line number. This
may not be possible in an 855 generated for a VMI order or non-EDI order. |
O |
AN |
1/20 |
|
|
|
|
PO102 |
330 |
Quantity Ordered Description: Quantity ordered |
C |
R |
1/15 |
|
|
|
|
PO103 |
355 |
Unit or Basis for Measurement
Code Description: Code specifying the units in which a value is
being expressed, or manner in which a measurement has been taken ECTF Notes:
One of the greatest difficulties in establishing trading partnerships
is the sharing of quantities with a possibility of interpretation problems
associated with quantity unit of measures.
Usually this only affects a small segment of products communicated,
therefore the problem does not always appear in the initial test transaction. For any
unit of measurement other than "each", both partners would be
advised to discuss their intent prior to implementing this transaction. Code NAME
_ BG Bag BK Book CA Case CG Card CT Carton EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
O |
ID |
2/2 |
|
|
|
|
PO104 |
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. |
C |
R |
1/17 |
|
|
|
|
PO105 |
639 |
Basis of Unit Price Code Description: Code identifying the type of unit price for an
item ECTF Notes:
Each time a price is used, this element should contain the appropriate
print 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 PR Promotion TF Per 1000 Feet TP Price per Thousand UM Price per Unit of Measure |
O |
ID |
2/2 |
|
|
|
|
PO106 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) ECTF Notes:
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 EN European Article Number (EAN) (2-5-5-1) RK Rack Number 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 |
|
|
|
|
PO107 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO108 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in PO106 |
C |
ID |
2/2 |
|
|
|
|
PO109 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO110 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in PO106. |
C |
ID |
2/2 |
|
|
|
|
PO111 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO112 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in PO106 |
C |
ID |
2/2 |
|
|
|
|
PO113 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO114 |
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 |
|
|
|
|
PO115 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO116 |
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 |
|
|
|
|
PO117 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO118 |
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 |
|
|
|
|
PO119 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO120 |
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 |
|
|
|
|
PO121 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO122 |
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 |
|
|
|
|
PO123 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
PO124 |
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 |
|
|
|
|
PO125 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
Additional Item Detail |
Pos: 050 Max: 25 Detail - Optional Loop: PO1 Elements: 5 |
To specify additional item-related data involving variations in normal price/quantity structure.
ECTF Notes:
This segment is used to send back the pricing and quantity changes from the original PO1 segment. If quantity and/or price changes on the 855 from that provided on the 850, the PO1 continues to reflect the 850 price and quantity and the PO3 reflects the changed price/quantity. Some examples of price/quantity variations are: price in different units from the PO1 segment, price changes by date, or price changes by quantity (break and level).
Example:
PO3*QP***5.33*TP*13000*EA^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PO301 |
371 |
Change Reason Code Description: Code specifying the reason for price or
quantity change Code NAME
_ AQ Alternate Quantity and Unit of Measure DC Date Change MP Minimum Order QO Quantity Ordered QP Quantity Based on Price Qualifier UP Unit Price |
M |
ID |
2/2 |
|
|
|
|
PO304 |
212 |
Unit Price Description: Price per unit of product, service, commodity,
etc. |
O |
R |
1/17 |
|
|
|
|
PO305 |
639 |
Basis of Unit Price Code Description: Code identifying the type of unit price for an
item 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 |
C |
ID |
2/2 |
|
|
|
|
PO306 |
380 |
Quantity Description: Numeric value of quantity |
M |
R |
1/15 |
|
|
|
|
PO307 |
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. PO307 defines the unit of measure for
PO306. Code NAME
_ BG Bag BK Book CA Case CG Card CT Carton EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
M |
ID |
2/2 |
|
|
|
Product/Item Description |
Pos: 090 Max: 1 Detail - Optional Loop: PID Elements: 2 |
To describe a product or process in coded or free-form format.
ECTF Notes:
This segment should only be used when specific agreements between trading partners have been discussed.
Example:
PID*F****WIRING ACCESSORY, SPECIAL RELEASE CONTROL ARM^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PID01 |
349 |
Item Description Type Description: Code indicating the format of a description Code NAME
_ F Free-form |
M |
ID |
1/1 |
|
|
|
|
PID05 |
352 |
Description Description: A free-form description to clarify the related
data elements and their content |
C |
AN |
1/80 |
|
|
|
Reference Identification |
Pos: 130 Max: >1 Detail - Optional Loop: PO1 Elements: 2 |
To specify identifying information.
Example:
REF*PR*ABC-12345-2^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
REF01 |
128 |
Reference Identification Qualifier Description: Code qualifying the Reference Identification Code NAME
_ DG Drawing Number PD Promotion/Deal Number PR Price Quote Number R1 Current Revision Number SE Serial Number |
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 |
|
|
|
Service, Promotion, Allowance, or Charge Information |
Pos: 150 Max: 1 Detail - Optional Loop: SAC Elements: 5 |
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge.
ECTF Notes:
For all data elements within this segment, the decimal point is assumed and should not be included in the amount.
Example:
SAC*C*F050***1000*******06***MISC CHARGE DESCRIPTION^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
SAC01 |
248 |
Allowance or Charge Indicator Description: Code which indicates an allowance or charge for
the service specified Code NAME
_ A Allowance C Charge |
M |
ID |
1/1 |
|
|
|
|
SAC02 |
1300 |
Service, Promotion, Allowance, or
Charge Code Description: Code identifying the service, promotion,
allowance, or charge Code NAME
_ A010 Absolute Minimum Charge D240 Freight D500 Handling F050 Other (See related description) |
C |
ID |
4/4 |
|
|
|
|
SAC05 |
610 |
Amount Description: Monetary amount |
O |
N2 |
1/15 |
|
|
|
|
SAC12 |
331 |
Allowance or Charge Method of
Handling Code Description: Code indicating method of handling for an allowance
or charge Code NAME
_ 04 Credit Customer Account 05 Charge to be Paid by Vendor 09 Allowance To Be Issued by Vendor Description: Code designating vendor as
the issuer of an allowance |
O |
ID |
2/2 |
|
|
|
|
SAC15 |
352 |
Description Description: A free-form description to clarify the related
data elements and their content |
C |
AN |
1/80 |
|
|
|
Conditions of Sale |
Pos: 170 Max: 1 Detail - Optional Loop: PO1 Elements: 1 |
To specify general conditions or requirements and to detail conditions for substitution of alternate products.
Example:
IT8*SC^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
IT801 |
563 |
Sales Requirement Code Description: Code to identify a specific requirement or
agreement of sale Code NAME _ N No Back Order BK Ship Partial - Balance Back Order SC Ship Complete SP Ship Partial,Balance Cancel |
C |
ID |
1/2 |
|
|
|
Date/Time Reference |
Pos: 250 Max: 10 Detail - Optional Loop: PO1 Elements: 2 |
To specify pertinent dates and times.
Example:
DTM*037*20010513^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
DTM01 |
374 |
Date/Time Qualifier Description: Code specifying type of date. Code NAME
_ 002 Delivery Requested 010 Requested Ship 037 Ship Not Before 038 Ship No Later 039 Ship Week of 106 Required By 118 Requested Pick-up 372 Actual Arrival Date |
M |
ID |
3/3 |
|
|
|
|
DTM02 |
373 |
Date Description: Date expressed as CCYYMMDD |
C |
DT |
8/8 |
|
|
|
Line Item Acknowledgment |
Pos: 310 Max: 1 Detail - Optional Loop: ACK Elements: 23 |
To acknowledge the ordered quantities and specify the ready date for a specific line item.
ECTF Notes:
ACK07 through ACK26 provide for multiple product/service IDs for each item. If only one product/service ID is provided, ACK07 and ACK08 should be used. ACK09 and ACK10 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
ACK*IC***068*20010413^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
ACK01 |
668 |
Line Item Status Code Description: Code specifying the action taken by the seller
on a line item requested by the buyer Code NAME
_ AC Item Accepted and Shipped AR Item Accepted and Released for Shipment DR Item Accepted - Date Rescheduled IA Item Accepted IB Item Backordered IC Item Accepted - Changes Made ID Item Deleted IH Item on Hold IQ Item Accepted - Quantity Changed IR Item Rejected IS Item Accepted - Substitution Made |
M |
ID |
2/2 |
|
|
|
|
ACK04 |
374 |
Date/Time Qualifier Description: Code specifying type of date or time, or both
date and time ECTF Notes:
Optionally, this segment can be used to specify the expected ship
date. Code NAME _ 068 Current Schedule Ship 080 Scheduled for Shipment (After and
Including) 083 Scheduled for Shipment (Prior to and
Including) |
O |
ID |
3/3 |
|
|
|
|
ACK05 |
373 |
Date Description: Date expressed as CCYYMMDD |
C |
DT |
8/8 |
|
|
|
|
ACK07 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) Code NAME _ RR Replacement Product Number Description: For use in the 855 this
qualifier is used to identify the catalog number that an item is being
"replaced by" (Replacement Catalog Number). SR Substitute Product Number UD U.P.C./EAN Consumer Package Code (2-5-5) Description: For use in the 855 this
qualifier is used to identify the U.P.C. number that an item is being
"replaced by" (Replacement U.P.C.). UE U.P.C./EAN Module Code (2-5-5) Description: For use in the 855 this
qualifier is used to identify the EAN that an item is being "replaced
by" (Replacement EAN). |
C |
ID |
2/2 |
|
|
|
|
ACK08 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK09 |
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 |
|
|
|
|
ACK10 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK11 |
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 |
|
|
|
|
ACK12 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK13 |
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 |
|
|
|
|
ACK14 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK15 |
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 |
|
|
|
|
ACK16 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK17 |
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 |
|
|
|
|
ACK18 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK19 |
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 |
|
|
|
|
ACK20 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK21 |
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 |
|
|
|
|
ACK22 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK23 |
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 |
|
|
|
|
ACK24 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
ACK25 |
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 |
|
|
|
|
ACK26 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
Marks and Numbers |
Pos: 330 Max: 10 Detail - Optional Loop: PO1 Elements: 2 |
To indicate identifying marks and numbers for shipping containers.
ECTF Notes:
At the detail level, the identifying marks and numbers would relate to specific line items. The use of this segment to pass additional information other than for the stated purpose is discouraged.
Example:
MAN*PB*SP-654321-007^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
MAN01 |
88 |
Marks and Numbers Qualifier Description: Code specifying the application or source of
Marks and Numbers MAN02 (87) Code NAME
_ L Line Item Only PB Premarked by Buyer |
M |
ID |
1/2 |
|
|
|
|
MAN02 |
87 |
Marks and Numbers Description: Marks and numbers used to identify a shipment
or parts of a shipment |
M |
AN |
1/48 |
|
|
|
Line Item Schedule |
Pos: 410 Max: 1 Detail - Optional Loop: SCH Elements: 4 |
To specify the data for scheduling a specific line-item.
Example:
SCH*10000*PC***037*20010413^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
SCH01 |
380 |
Quantity Description: Numeric value of quantity |
M |
R |
1/15 |
|
|
|
|
SCH02 |
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 KT Kit LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
M |
ID |
2/2 |
|
|
|
|
SCH05 |
374 |
Date/Time Qualifier Description: Code specifying type of date. Code NAME
_ 002 Delivery Requested 010 Requested Ship 037 Ship Not Before 038 Ship No Later 039 Ship Week of 106 Required By 118 Requested Pick-up 372 Actual Arrival Date |
M |
ID |
3/3 |
|
|
|
|
SCH06 |
373 |
Date Description: Date expressed as CCYYMMDD |
M |
DT |
8/8 |
|
|
|
Name |
Pos: 500 Max: 1 Detail - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code.
Example:
N1*EN*DYNAMICS INC.*9*1234567890000^
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
_ EN End User ST Ship To |
M |
ID |
2/3 |
|
|
|
|
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 N104 (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: 520 Max: 2 Detail - Optional Loop: N1 Elements: 2 |
To specify the location of the named party.
Example:
N3*123 INDUSTRY BLVD.*DOCK C^
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: 530 Max: 1 Detail - 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 (standard ISO) identifying the country Code NAME
_ CAN Canada MEX Mexico USA United States |
O |
ID |
2/3 |
|
|
|
Subline Item Detail |
Pos: 670 Max: 1 Detail - Optional Loop: SLN Elements: 27 |
To specify product subline detail item data.
ECTF Notes:
Segment SLN is to be used if the item is shipped in sub assemblies to identify the sub assemblies to the customer. SLN09 through SLN16 provide for multiple product/service IDs for each item. If only one product/service ID is provided, SLN09 and SLN10 should be used. SLN11 and SLN12 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
SLN*1.1**I*13000*EA*4.33*TP*I*VC*P-875B*UI*09999982005^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
SLN01 |
350 |
Assigned Identification Description: Alphanumeric characters assigned for
differentiation within a transaction set |
M |
AN |
1/20 |
|
|
|
|
SLN03 |
662 |
Relationship Code Description: Code indicating the relationship between
entities. This is the configuration code
indicating the relationship of the subline item to the baseline item. Code NAME
_ I Included |
M |
ID |
1/1 |
|
|
|
|
SLN04 |
380 |
Quantity Description: Numeric value of quantity |
C |
R |
1/15 |
|
|
|
|
SLN05 |
C001 |
Composite Unit of Measure Description: To identify a composite unit of measure(See
Figures Appendix for examples of use) |
C |
Comp |
|
|
|
|
|
|
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 KT Kit LB Pound MR Meter PC Piece PK Package RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
M |
ID |
2/2 |
|
|
|
|
SLN06 |
212 |
Unit Price Description: Price per unit of product, service, commodity,
etc. |
C |
R |
1/17 |
|
|
|
|
SLN07 |
639 |
Basis of Unit Price Code Description: Code identifying the type of unit price for an
item 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 |
|
|
|
|
SLN08 |
662 |
Relationship Code Description: Code indicating the relationship between
entities Code NAME
_ I Included |
O |
ID |
1/1 |
|
|
|
|
SLN09 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID SLN10 (234). Code NAME
_ BP Buyer's Part Number CB Buyer's Catalog Number RK Rack Number 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 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 |
C |
ID |
2/2 |
|
|
|
|
SLN10 |
234 |
Product/Service ID Description: Identifying number for a product or service. |
C |
AN |
1/48 |
|
|
|
|
SLN11 |
235 |
Product/Service ID Qualifier Description: See Product/Service ID Qualifier list in SLN09. |
C |
ID |
2/2 |
|
|
|
|
SLN12 |
234 |
Product/Service ID Description: Identifying number for a product or service. |
C |
AN |
1/48 |
|
|
|
|
SLN13 |
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 |
|
|
|
|
SLN14 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN15 |
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 |
|
|
|
|
SLN16 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN17 |
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 |
|
|
|
|
SLN18 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN19 |
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 |
|
|
|
|
SLN20 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN21 |
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 |
|
|
|
|
SLN22 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN23 |
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 |
|
|
|
|
SLN24 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN25 |
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 |
|
|
|
|
SLN26 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
|
SLN27 |
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 |
|
|
|
|
SLN28 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
Product/Item Description |
Pos: 700 Max: 1000 Detail - Optional Loop: SLN Elements: 2 |
To describe a product or process in coded or free-form format.
Example:
PID*F****CONTROL ARM BASE^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
PID01 |
349 |
Item Description Type Description: Code indicating the format of a description Code NAME
_ F Free-form |
M |
ID |
1/1 |
|
|
|
|
PID05 |
352 |
Description Description: A free-form description to clarify the related
data elements and their content. |
C |
AN |
1/80 |
|
|
|
Transaction Totals |
Pos: 010 Max: 1 Summary - Optional Loop: CTT Elements: 2 |
To transmit a hash total for a specific element in the transaction set.
Example:
CTT*3*28400^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
CTT01 |
354 |
Number of Line Items Description: Total number of line items (PO1 segments) in
the transaction set |
M |
N0 |
1/6 |
|
|
|
|
CTT02 |
347 |
Hash Total Description: Sum of values of the PO102 data element. |
O |
R |
1/10 |
|
|
|
Transaction Set Trailer |
Pos: 030 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 |
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).
Example:
SE*40*0001^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
|
SE01 |
96 |
Number of Included Segments Description: Total number of segments included in a
transaction set including ST and SE segments |
M |
N0 |
1/10 |
|
|
|
|
SE02 |
329 |
Transaction Set Control Number Description: Identifying control number that must be unique within
the transaction set functional group assigned by the originator for a
transaction set |
M |
AN |
4/9 |
|
|
Section 4
855 Purchase Order
Acknowledgment
Example Transaction
This
section contains an example transaction showing the use of the segments within
the 855 Purchase Order Acknowledgment.
Note: The example may not show
all segments or qualifier combinations.
ST*855*0001^
BAK*00*AC*092123456*20010331****0798765*20010331^
CUR*SE*USD^
REF*PR*ABC-12345-1^
REF*CO*554433^
PER*BD*JANE
SMITH*TE*3121234567^
FOB*PP^
CSH*BK^
SAC*C*F050***1000*******06***MISC
CHARGE DESCRIPTION^
DTM*037*20010413^
TD5**2*AAAA*M*AAA
FREIGHT CO.*******PS^
TD3*LU^
MAN*PB*SP-654321-006^
N1*BY*ABC
DISTRIBUTION*9*0012345670000^
N1*BT*ABC
FINANCIAL CENTER*9*0012345670001^
N3*100
S. LASALLE ST.*SUITE 410^
N4*CHICAGO*IL*60601*USA^
N1*ST*ABC
DISTRIBUTION W/H*9*0012345670000^
N3*8765
INDUSTRIAL DRIVE*DOCK #2^
N4*CHICAGO*IL*60601*USA^
N1*SE*XYZ
SUPPLIER*9*0076543210000^
PO1*0001*12900*EA*5.43*TP*VC*P-8750*UI*09999982010*BP*CC-14^
PO3*QP***5.33*TP*13000*EA^
PID*F****WIRING ACCESSORY, SPECIAL RELEASE CONTROL ARM^
REF*PR*ABC-12345-2^
SAC*C*F050***1000*******06***MISC CHARGE DESCRIPTION^
IT8*SC^
ACK*IC***068*20010413^
MAN*PB*SP-654321-007^
SCH*10000*PC***037*20010413^
SCH*3000*PC***037*20010513^
N1*EN*DYNAMICS INC.*9*1234567890000^
N3*123
INDUSTRY BLVD.*DOCK C^
N4*CHICAGO*IL*60601*USA^
SLN*1.1**I*13000*EA*4.33*TP*I*VC*P-875B*UI*09999982005^
PID*F****CONTROL
ARM BASE^
SLN*0001**I*13000*PC*1.00*TP*I*VC*P-8750S*UI*09999982001^
PID*F****CONTROL
ARM SUPPORT^
PO1*0002*500*EA*8.89*HP*VC*3252-IV^
DTM*037*20010418^
PO1*0003*15000*FT*400*TF*U1*78922512346^
ACK*IA^
CTT*3*28400^
SE*40*0001^