Information about http://www.3m.com/US/about3M/ec/guidelines/855.pdf
3M Customer Purchase Order Acknowledgment Introduction This…
Pages: 26Language: english
Created: Mon Nov 22 08:51:18 1999
Display cached document
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8
Page 9
Page 10
Page 11
Page 12
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23
Page 24
Page 25
Page 26
3M Customer Purchase Order Acknowledgment
Introduction
This guideline provides a description and technical layout of the data segments sent in
3M' EDI purchase order acknowledgments (ASC X12 transaction set 855). 3M can
s
send many valid ASC X12 data segments and elements; however, this guideline includes
only those that are most commonly sent. If you have data requirements that are not
covered in this document, please consult your 3M EDI contact.
The ASC X12 version presented in this guideline is 004010. If you cannot receive
purchase order acknowledgments in 004010, please consult your 3M EDI contact for
information on other ASC X12 versions sent by 3M.
The format defined in this document is the 3M standard EDI purchase order
acknowledgment (POA). Some variations on this format are available which can be
discussed with your 3M EDI contact. Such variations include:
1. Timing of the return of the POA
2. POA optionally triggered by certain order changes
3. Type of status date returned Expected ship date or expected delivery date
4. Original acknowledgment type Detail (all line items) or exception detail (just line
items where change occurred)
5. Reacknowledgment type Detail, exception detail or no reacknowledgment
6. Optional return of product descriptions.
Some general comments are:
1. EDI purchase order acknowledgments will be sent for EDI purchase orders. On a
limited basis, POAs may be returned for orders received by mail, phone, or fax. If
you have such requirements, please discuss with your 3M EDI contact.
2. The purchase order acknowledgment will be returned after the purchase order is
entered on the 3M order processing system. The time for POA generation is flexible
based on your timing requirements.
3. The first POA will be sent back with a code of "00" (original) in BAK01 (transaction
set purpose). The standard original POA is a detail acknowledgment. This means
that the POA will contain all line items originally sent on the EDI order with a line
item status and a status date, if available. Optionally, a POA containing only
exception line items can be returned.
4. The line item status date returned is either an estimated ship or delivery date. It will
be sent back only if it has been established on the 3M order.
5. Subsequent purchase order acknowledgments or reacknowledgments are optionally
returned if certain data changes on the order after the original acknowledgment has
been returned. Changes which will result in a reacknowledgment are: quantity
change, status date change, product ID change, item deleted, order canceled. A
reacknowledgment can be identified from the BAK01 code of "04" (change). A
reacknowledgment can be returned in either detail or exception detail format.
6. Multiple ACK segments may be returned for a particular line item. This will happen
if product for a line item is scheduled to ship on different dates. This is usually due
to multiple ship or delivery schedules requested on the purchase order. It can also
happen in the case of partial backorder situations. For example, if ten units are
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
ordered and five units will ship and five are on backorder, two ACK segments will
be returned for this line item. One will show the five scheduled to ship and the other
will show the five on backorder. Status dates will also be sent, if available.
7. If prices are required on the POA, please discuss with your 3M EDI contact.
Examples of purchase order acknowledgments and their ASC X12 interpretation can be
found at the back of this guideline.
Note: For illustration purposes only, all examples use an asterisk (*) as the data
element separator a caret (^) as the segment terminator. In actual practice, values
must be chosen that do not conflict with the data.
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
855 Purchase Order Acknowledgment
Functional Group ID= PR
Introduction:
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.
Heading:
Page Pos. Seg. Req. Loop Notes and
No. No. ID Name Des. Max.Use Repeat Comments
3 010 ST Transaction Set Header M 1
4 020 BAK Beginning Segment for Purchase Order M 1
Acknowledgment
LOOP ID - N1 200
6 300 N1 Name O 1
7 310 N2 Additional Name Information O 2
8 320 N3 Address Information O 2
9 330 N4 Geographic Location O 1
Detail:
Page Pos. Seg. Req. Loop Notes and
No. No. ID Name Des. Max.Use Repeat Comments
LOOP ID - PO1 100000
10 010 PO1 Baseline Item Data O 1 n1
13 040 CTP Pricing Information O >1
LOOP ID - PID 1000
14 050 PID Product/Item Description O 1
LOOP ID - ACK 104
15 270 ACK Line Item Acknowledgment O 1
Summary:
Page Pos. Seg. Req. Loop Notes and
No. No. ID Name Des. Max.Use Repeat Comments
LOOP ID - CTT 1
18 010 CTT Transaction Totals O 1 n2
19 030 SE Transaction Set Trailer M 1
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
Transaction Set Notes
1. PO102 is required.
2. The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash
total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
855 Version 004010 2 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g.,
810 selects the Invoice Transaction Set).
Comments:
Notes: 3M Example(s): ST*855*000000027^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
855 Purchase Order Acknowledgment
Required ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Sender-assigned sequential control number to match control number on
SE segment.
855 Version 004010 3 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: BAK Beginning Segment for Purchase Order Acknowledgment
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set
and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BAK04 is the date assigned by the purchaser to purchase order.
2 BAK08 is the seller's order number.
3 BAK09 is the date assigned by the sender to the acknowledgment.
Comments:
Notes: 3M Example(s):
BAK*00*AC*12-22222-S*20000115****4BA1102ZZ*20000117^
BAK*04*AE*12-22222-S*20000115****4BA1102ZZ*20000118^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required BAK01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set
00 Original
Used on the original or first acknowledgment.
04 Change
Used on reacknowledgments. A reacknowledment
is optionally sent if a change occurs on the order
after the original acknowledgment has been sent
back.
Required BAK02 587 Acknowledgment Type M ID 2/2
Code specifying the type of acknowledgment
Defaults are:
AC or AD for original acknowledgments
(detail, with change or no change)
AE for reacknowledgments
RJ for order cancellations
AC Acknowledge - With Detail and Change
Used on the original acknowledgment if there was
any change made to the purchase order. All line
items are returned.
AD Acknowledge - With Detail, No Change
Used on the original acknowledgment if no change
was made to the purchase order. All line items are
required.
AE Acknowledge - With Exception Detail Only
855 Version 004010 4 November 22, 1999
3M Customer Purchase Order Acknowledgment
Used on the original acknowledgment and
reacknowledgments if exception detail only has been
requested. The acknowledgment contains only the
line item(s) where a change occurred.
AK Acknowledge - No Detail or Change
Used for the original acknowledgment if exception
detail only has been requested and no change was
made to the purchase order.
RJ Rejected - No Detail
Used if the order has been cancelled. No detail is
sent back.
Required BAK03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Required BAK04 373 Date M DT 8/8
Date expressed as CCYYMMDD
BAK05 328 Release Number O AN 1/30
Number identifying a release against a Purchase Order previously placed
by the parties involved in the transaction
Sent back if the release number was sent on the BEG segment of the
purchase order.
BAK07 367 Contract Number O AN 1/30
Contract number
Sent back if the contract number was sent on the BEG segment of the
purchase order.
Required BAK08 127 Reference Identification O AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
This is 3M's reference number for the customer purchase order (C.P.O.
number).
Required BAK09 373 Date O DT 8/8
Date expressed as CCYYMMDD
855 Version 004010 5 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: N1 Name
Position: 300
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104)
must provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
Notes: 3M Comments: The N1 loop is normally not sent.
3M Example(s): N1*ST*ABC WAREHOUSE^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical location, property or
an individual
BS Bill and Ship To
BT Bill-to-Party
ST Ship To
N102 93 Name X AN 1/60
Free-form name
N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for
Identification Code (67)
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
N104 67 Identification Code X AN 2/80
Code identifying a party or other code
855 Version 004010 6 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: N2 Additional Name Information
Position: 310
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify additional names or those longer than 35 characters in length
Syntax Notes:
Semantic Notes:
Comments:
Notes: 3M Comments: Use segments N2-N4 ONLY if address information cannot be
identified by a code in N104.
3M Example(s): N2*C/O ANDERSON CORP.^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required N201 93 Name M AN 1/60
Free-form name
N202 93 Name O AN 1/60
Free-form name
855 Version 004010 7 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: N3 Address Information
Position: 320
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes: 3M Comments: Use segments N2-N4 ONLY if address information cannot be
identified by a code in N104.
3M Example(s): N3*2222 MAIN STREET^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required N301 166 Address Information M AN 1/55
Address information
N302 166 Address Information O AN 1/55
Address information
855 Version 004010 8 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: N4 Geographic Location
Position: 330
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be
adequate to specify a location.
2 N402 is required only if city name (N401) is in the U.S. or Canada.
Notes: 3M Comments: Use segments N2-N4 ONLY if address information cannot be
identified by a code in N104.
3M Example(s): N4*ANYTOWN*NJ*66781234^
Data Element Summary
Ref. Data
Des. Element Name Attributes
N401 19 City Name O AN 2/30
Free-form text for city name
N402 156 State or Province Code O ID 2/2
Code (Standard State/Province) as defined by appropriate government
agency
N403 116 Postal Code O ID 3/15
Code defining international postal zone code excluding punctuation and
blanks (zip code for United States)
N404 26 Country Code O ID 2/3
Code identifying the country
855 Version 004010 9 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: PO1 Baseline Item Data
Position: 010
Loop: PO1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify basic and most frequently used line item data
Syntax Notes: 1 If PO103 is present, then PO102 is required.
2 If PO105 is present, then PO104 is required.
3 If either PO106 or PO107 is present, then the other is required.
4 If either PO108 or PO109 is present, then the other is required.
5 If either PO110 or PO111 is present, then the other is required.
6 If either PO112 or PO113 is present, then the other is required.
7 If either PO114 or PO115 is present, then the other is required.
8 If either PO116 or PO117 is present, then the other is required.
9 If either PO118 or PO119 is present, then the other is required.
10 If either PO120 or PO121 is present, then the other is required.
11 If either PO122 or PO123 is present, then the other is required.
12 If either PO124 or PO125 is present, then the other is required.
Semantic Notes:
Comments: 1 See the Data Element Dictionary for a complete list of IDs.
2 PO101 is the line item identification.
3 PO106 through PO125 provide for ten different product/service IDs per each
item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model
No., or SKU.
Notes: 3M Comments: The standard product IDs on the PO1 segment are the UPC
number and buyer's item number, if sent on the purchase order. If the PO1
segment must be returned exactly as it came in on the EDI purchase order, please
discuss with your 3M EDI contact.
3M Example(s): PO1*1*50*EA*3.2**UI*05632112344*IN*1629^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required PO101 350 Assigned Identification O AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
This is the purchase order line number as sent on the purchase order. It
is recommended that the line number be sent on the EDI purchase order.
Required PO102 330 Quantity Ordered X R 1/15
Quantity ordered
This is the original line item quantity as sent on the purchase order.
Required PO103 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner
in which a measurement has been taken
855 Version 004010 10 November 22, 1999
3M Customer Purchase Order Acknowledgment
This is the original unit of measure as sent on the purchase order.
BX Box
CA Case
CT Carton
EA Each
FT Foot
KT Kit
LB Pound
PK Package
RL Roll
See ASC X12 code list for additional codes.
PO104 212 Unit Price X R 1/17
Price per unit of product, service, commodity, etc.
If price is required, please discuss with your 3M EDI contact.
Required PO106 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
UPC number is sent in PO107 if available. If not, one of the following
will be returned:
Buyer's item number
3M item number
3M catalog number
If you have other product ID requirements, please discuss with your 3M
EDI contact.
IN Buyer's Item Number
UI U.P.C. Consumer Package Code (1-5-5)
VC Vendor's (Seller's) Catalog Number
VN Vendor's (Seller's) Item Number
Required PO107 234 Product/Service ID X AN 1/48
Identifying number for a product or service
PO108 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
The buyer's item number is returned in PO109, if it was sent on the
purchase order.
If the buyer's item number is not present, one of the following will be
returned, if available:
3M item number
3M catalog number
If you have other product ID requirements, please discuss with your 3M
EDI contact.
IN Buyer's Item Number
VC Vendor's (Seller's) Catalog Number
855 Version 004010 11 November 22, 1999
3M Customer Purchase Order Acknowledgment
VN Vendor's (Seller's) Item Number
PO109 234 Product/Service ID X AN 1/48
Identifying number for a product or service
855 Version 004010 12 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: CTP Pricing Information
Position: 040
Loop: PO1 Optional
Level: Detail
Usage: Optional
Max Use: >1
Purpose: To specify pricing information
Syntax Notes: 1 If either CTP04 or CTP05 is present, then the other is required.
2 If CTP06 is present, then CTP07 is required.
3 If CTP09 is present, then CTP02 is required.
4 If CTP10 is present, then CTP02 is required.
5 If CTP11 is present, then CTP03 is required.
Semantic Notes: 1 CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of
.90 would be the factor if a 10% discount is given.
2 CTP08 is the rebate amount.
Comments: 1 See Figures Appendix for an example detailing the use of CTP03 and CTP04.
See Figures Appendix for an example detailing the use of CTP03, CTP04 and
CTP07.
Notes: 3M Comments: The CTP is only returned if price change notification has been
requested. Price change notification will only be sent after the order hs been
entered on 3M's order management system.
3M Example(s): CTP**CHG*2.35^
Data Element Summary
Ref. Data
Des. Element Name Attributes
CTP02 236 Price Identifier Code X ID 3/3
Code identifying pricing specification
CHG Changed Price
CTP03 212 Unit Price X R 1/17
Price per unit of product, service, commodity, etc.
855 Version 004010 13 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: PID Product/Item Description
Position: 050
Loop: PID Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To describe a product or process in coded or free-form format
Syntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID04 is required.
5 If PID09 is present, then PID05 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred
to.
2 PID04 should be used for industry-specific product description codes.
3 PID08 describes the physical characteristics of the product identified in PID04.
A "Y" indicates that the specified attribute applies to this item; an "N" indicates it
does not apply. Any other value is indeterminate.
4 PID09 is used to identify the language being used in PID05.
Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is
used. If PID01 equals "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being
described in the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.
Notes: 3M Comments: The PID segment is optionally sent with the 3M product
description. It can always be sent or only sent if there has been a product change.
The default is to send the PID segment only if there is a product change.
3M Example(s): PID*F****471 PLSTC TP WHITE 1/2 X 36 YD BULK^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required PID01 349 Item Description Type M ID 1/1
Code indicating the format of a description
F Free-form
Required PID05 352 Description X AN 1/80
A free-form description to clarify the related data elements and their
content
855 Version 004010 14 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: ACK Line Item Acknowledgment
Position: 270
Loop: ACK Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To acknowledge the ordered quantities and specify the ready date for a specific line
item
Syntax Notes: 1 If either ACK02 or ACK03 is present, then the other is required.
2 If ACK04 is present, then ACK05 is required.
3 If either ACK07 or ACK08 is present, then the other is required.
4 If either ACK09 or ACK10 is present, then the other is required.
5 If either ACK11 or ACK12 is present, then the other is required.
6 If either ACK13 or ACK14 is present, then the other is required.
7 If either ACK15 or ACK16 is present, then the other is required.
8 If either ACK17 or ACK18 is present, then the other is required.
9 If either ACK19 or ACK20 is present, then the other is required.
10 If either ACK21 or ACK22 is present, then the other is required.
11 If either ACK23 or ACK24 is present, then the other is required.
12 If either ACK25 or ACK26 is present, then the other is required.
13 If either ACK27 or ACK28 is present, then the other is required.
14 If ACK28 is present, then both ACK27 and ACK29 are required.
Semantic Notes: 1 ACK29 Industry Reason Code may be used to identify the item status. In
addition, it may be used in conjunction with ACK01 to further clarify the status.
Comments:
Notes: 3M Example(s):
ACK*AR*50*EA*068*20000120**VO*AT25651^
ACK*IA*100*EA*002*20000530^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required ACK01 668 Line Item Status Code M ID 2/2
Code specifying the action taken by the seller on a line item requested by
the buyer
AC Item Accepted and Shipped
AR Item Accepted and Released for Shipment
Inventory has been allocated to fill this item, and it is
in some phase of the shipping process. Inventory
may have been: allocated, released to the warehouse
for shipment, in the process of being picked, picked
and on the dock, or picked and loaded on the trailer.
DR Item Accepted - Date Rescheduled
A date reschedule from what was originally
requested on the purchase order or from what was
previously acknowledged has occurred. The new
855 Version 004010 15 November 22, 1999
3M Customer Purchase Order Acknowledgment
date is sent in ACK05.
IA Item Accepted
This item has been accepted but inventory has not
yet been allocated.
IB Item Backordered
IC Item Accepted - Changes Made
This item has been accepted and is not on
backorder. This code is returned in the following
cases:
- the product has been changed from what was
originally ordered (e.g., item substitution or
customer-requested item change)
- multiple changes have occurred on this line item
(e.g., quantity change and date reschedule)
ID Item Deleted
IH Item on Hold
IQ Item Accepted - Quantity Changed
SP Item Accepted - Schedule Date Pending
ACK02 380 Quantity X R 1/15
Numeric value of quantity
The default is the quantity set up on the 3M order in 3M unit of measure.
This may differ from the order quantity in PO102. If your unit of
measure differs from 3M's and you require quantity returned in your unit,
please discuss with your 3M EDI contact.
ACK03 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the units in which a value is being expressed, or manner
in which a measurement has been taken
The default is the 3M unit of measure. If your unit of measure differs
from 3M's and you require your unit returned, please discuss with your
3M EDI contact.
BX Box
CA Case
CT Carton
EA Each
FT Foot
KT Kit
LB Pound
PK Package
RL Roll
See ASC X12 code list for additional codes.
ACK04 374 Date/Time Qualifier O ID 3/3
Code specifying type of date or time, or both date and time
If there is no date available for this item at the time of acknowledgment
generation, ACK04/ACK05 are not sent. If a date becomes available after
855 Version 004010 16 November 22, 1999
3M Customer Purchase Order Acknowledgment
the original acknowledgment was sent, a reacknowledgment is optionally
generated.
The status date is expressed in terms of either a ship OR a delivery date.
The default is ship date. Please indicate to your 3M EDI contact whether
you wish to receive delivery dates.
002 Delivery Requested
For delivery date customers.
This is the customer's requested delivery date.
010 Requested Ship
For ship date customers.
Used when an estimated ship date has not yet been
assigned, but there is a customer-requested ship date
entered on the system.
011 Shipped
For ship date customers.
Used when the line item has shipped and a ship date
is available on the system.
017 Estimated Delivery
For delivery date customers.
This is 3M's estimated delivery date. Used if this
date differs from the customer's requested delivery
date.
068 Current Schedule Ship
For ship date customers.
Used when the item has been assigned an estimated
ship date or "promise date". For locally stocked
items this date will be given as two days after the
order was entered on 3M's system. For factory
items, a promise date will be shown if available from
the factory.
ACK05 373 Date X DT 8/8
Date expressed as CCYYMMDD
ACK07 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
3M invoice number
VO Vendor's Order Number
ACK08 234 Product/Service ID X AN 1/48
Identifying number for a product or service
855 Version 004010 17 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: CTT Transaction Totals
Position: 010
Loop: CTT Optional
Level: Summary
Usage: Optional
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction
completeness and correctness.
Notes: 3M Example(s): CTT*5^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required CTT01 354 Number of Line Items M N0 1/6
Total number of line items in the transaction set
Total number of PO1 segments.
855 Version 004010 18 November 22, 1999
3M Customer Purchase Order Acknowledgment
Segment: SE Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.
Notes: 3M Example(s): SE*15*000000027^
Data Element Summary
Ref. Data
Des. Element Name Attributes
Required SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and
SE segments
Required SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
This will match the control number on the ST segment for this transaction
set.
855 Version 004010 19 November 22, 1999
3M Customer Purchase Order Acknowledgment
Purchase Order Acknowledgment Examples
Example 1
This example acknowledges the following:
· Line item 1 and 3 will ship as ordered on 1/20/2000.
· Line item 2 backordered and will ship on 1/27/2000.
· Line item 4 will ship on 1/20/2000. This item includes 3M' description as the item
s
was changed from what was originally ordered.
· Line item 5 had a quantity change.
The acknowledgment provides scheduled ship dates.
P.O. ACKNOWLEDGEMENT 01/17/2000
FROM: 3M Company P.O.: 12-22222-S
P.O. Date: 01/15/2000
BILL TO: Buying Company SHIP TO: ABC Warehouse
P.O. Box 500 2222 Main Street
Anytown, NJ 66678-1234 Anytown, NJ 66678-1234
ITEM QUANTITY UNIT ITEM AND DESCRIPTION SCHEDULED
SHIP DATE
1 50 Each 05632112344 01/20/2000
#22345 Connectors @$3.20
Cust Part No: 1629
2 100 Roll 05632134571 01/27/2000
#2312 Cable @$1.10
Cust Part No: 3456
****BACKORDERED*****
3 25 Each 05632199971 01/20/2000
#66667-1 Vinyl Insulated Rings @ $5.00
Cust Part No: 11123
4 110 Each 05632156789 01/20/2000
471 Plstc TP White ½ X 36 Yd Bulk @ $1.50
Cust Part No: 8203
5 60 Each 05632155555 01/20/2000
#225678 Connectors @$4.20
Cust Part No: 99235
****QUANTITY CHANGE*****
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
ASC X12 FORMAT INTERPRETATION
ST*855*000000027^ ASC X12 Transaction Set: 855
Transaction Set Control Number:
000000027
BAK*00*AC*12-22222-S Original acknowledgment with
*20000115****4BA1102ZZ detail and change
*20000117^ P.O. Number: 12-22222-S
P.O. Date: 01/15/2000
3M Reference Number: 4BA1102ZZ
P.O. Acknowledgment Date: 01/17/2000
PO1*1*50*EA*3.2**UI Buyer' Line Number: 1
s
*05632112344*IN*1629^ Quantity Ordered: 50
Buyer' Unit of Measure: EA=each
s
Price: $3.20
UPC Number: 05632112344
Buyer' Item Number: 1629
s
ACK*AR*50*EA*068*20000120 Line Item Status:
**VO*AT25651^ AR=item accepted and released for shipment
Quantity: 50
3M Unit of Measure: EA=each
Scheduled Ship Date: 01/20/2000
3M Invoice Number: AT25651
PO1*2*100*RL*1.1**UI Buyer' Line Number: 2
s
*05632134571*IN*3456^ Quantity Ordered: 100
Buyer' Unit of Measure: RL=roll
s
Price: $1.10
UPC Number: 05632134571
Buyer' Item Number: 3456
s
ACK*IB*100*RL*068*20000127 Line Item Status: IB=item backordered
**VO*AT25652^ Quantity: 100
3M Unit of Measure: RL=roll
Scheduled Ship Date: 01/27/2000
3M Invoice Number: AT25652
PO1*3*25*EA*5**UI Buyer' Line Number: 3
s
*05632199971*IN*11123^ Quantity Ordered: 25
Buyer' Unit of Measure: EA=each
s
Price: $5.00
UPC No: 05632199971
Buyer' Item Number: 11123
s
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
ACK*AR*25*EA*068*20000120 Line Item Status:
**VO*AT25651^ AR=item accepted and released for shipment
Quantity: 25
3M Unit of Measure: EA=each
Scheduled Ship Date: 01/20/2000
3M Invoice Number: AT25651
PO1*4*110*EA*1.5**UI Buyer' Line Number: 4
s
*05632156789*IN*8203^ Quantity Ordered: 110
Buyer' Unit of Measure: EA=each
s
Price: $1.50
UPC Number: 05632156789
Buyer' Item Number: 8203
s
PID*F****471 PLSTC TP 3M Item Description: 471 Plastic
WHITE ½ X 36 YD BULK^ Tape White ½ X 36 Yd Bulk
ACK*IC*110*EA*068 Line Item Status:
*20000120*VO*AT25651^ IC=item accepted, changes made
Quantity: 110
3M Unit of Measure: EA=each
Scheduled Ship Date: 01/20/2000
3M Invoice Number: AT25651
PO1*5*50*EA*4.2**UI Buyer' Line Number: 5
s
*05632155555*IN*99235^ Quantity Ordered: 50
Buyer' Unit of Measure: EA=each
s
Price: $4.20
UPC No: 05632155555
Buyer' Item Number: 99235
s
ACK*IQ*60*EA*068*20000120 Line Item Status:
**VO*AT25651^ IQ=item accepted, quantity changed
Quantity: 60
3M Unit of Measure: EA=each
Scheduled Ship Date: 01/20/2000
3M Invoice Number: AT25651
CTT*5^ Number of Line Items: 5
SE*15*000000027^ Number of Segments: 15
Transaction Set Control Number: 000000027
Note: Sample purchase order acknowledgment contains fictitious data.
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
Example 2
This example acknowledges multiple requested delivery dates for a line item.
P.O. ACKNOWLEDGMENT 05/03/2000
FROM: 3M Company P.O.: 6234X1
P.O. Date: 05/01/2000
BILL TO: ABC Distributor SHIP TO: XYZ Supply
P.O. Box 100 2345 1st Avenue
Anytown, E 22141-0200 New York, NY 01234-2345
ITEM QUANTITY UNIT ITEM AND DESCRIPTION REQUESTED DELIVERY DATE
1 300 Each 06123412341
#99999 Connectors @$1.10
100 Each 05/30/2000
100 Each 06/30/2000
100 Each 07/30/2000
855 Version 004010 November 22, 1999
3M Customer Purchase Order Acknowledgment
ASC X12 FORMAT INTERPRETATION
ST*855*00000028^ ASC X12 Transaction Set: 855
Transaction Set Control Number: 000000028
BAK*00*AD*6234X1*20000501 Original acknowledgment with detail,
****4BA9999ZZ*20000503^ no change
P.O. Number: 6234X1
P.O. Date: 05/01/2000
3M Reference Number: 4BA9999ZZ
P.O. Acknowledgment Date: 05/03/2000
PO1*1*300*EA*1.1**UI Buyer' Line Number: 1
s
*06123412341*IN*99999^ Quantity Ordered: 300
Buyer' Unit of Measure: EA=Each
s
Price: $1.10
UPC Number: 06123412341
Buyer' Item Number: 99999
s
ACK*IA*100*EA*002*20000530 Line Item Status: IA=item accepted
**VO*BK22345^ Quantity: 100
3M Unit of Measure: EA=Each
Requested Delivery Date: 05/30/2000
3M Invoice Number: BK22345
ACK*IA*100*EA*002*20000630 Line Item Status: IA=item accepted
**VO*BK22346^ Quantity: 100
3M Unit of Measure: EA=Each
Requested Delivery Date: 06/30/2000
3M Invoice Number: BK22346
ACK*IA*100*EA*002*20000730 Line Item Status: IA=item accepted
**VO*BK22347^ Quantity: 100
3M Unit of Measure: EA=Each
Requested Delivery Date: 07/30/2000
3M Invoice Number: BK22347
CTT*1^ Number of Line Items: 1
SE*8*00000028^ Number of Segements: 8
Transaction Set Control Number: 000000028
NOTE: Sample purchase order acknowledgment contains fictitious data.
855 Version 004010 November 22, 1999