Provided for Use by the Truck Parts
Aftermarket
852 Product Activity Data
(ASC X12 Version 4 Release 1)
This document contains an outline of common business issues
for consideration when implementing the EDI 852 Product Activity Data for ASC
X12 Version 4010. It is the intent of this
document to act as an addendum to the ASC X12 EDI Standards documentation.
852 Product Activity Data
Included in this document:
Page
Section 1: Business Issues.......................................................... 2
Section 2: Segment Notes....................................................... 3
Section 3: Sample Transaction............................................. 14
Section 1
852 Product Activity Data
Business Issues
This section contains business discussions about the
use of the 852 Product Activity Data.
These discussions will assist in determining application changes and
business process changes that may be necessary within a company.
Page
Business Issues.............................................................................. 2
VMI Relationships....................................................................... 2
Conversion Issues....................................................................... 2
Definition of Customer.............................................................. 2
Quantity Field Definitions......................................................... 2
Transaction Frequency............................................................ 2
The following business issues should be considered
when implementing the 852 Product Activity Data transaction.
The 852 Product Activity Data transaction is
primarily used in VMI (Vendor Managed Inventory) partnerships with
participating suppliers. The information contained within this transaction can
therefore be separated into two major concentrations: 1) current inventory
status information provided to the supplier for product replenishment purposes,
and 2) sales movement information provided to the supplier for use in the
supplier’s product planning process.
Due to the very specific nature of these VMI relationships it is critical that each of the fields contained within this transaction be clearly defined and understood by both the customer and the supplier.
With version 4010 of the ASC X12 EDI standards, many
data elements have changed positions and additional data elements are now
available to clearly define the data positioning. The definitions of the fields have NOT changed, only their
position in the transaction. Examples
of the new positions include:
|
Data Value |
Old Data Element |
New Data Element |
|
Order
Point |
ZA06 |
ZA02 |
|
Order
Quantity |
ZA06 |
ZA02 |
|
Order
Count |
ZA06 |
QTY02 |
Companies migrating from previous ASC X12 versions
of the EDI 852 transaction should carefully review this document to identify
the EDI translation mapping changes.
Throughout this document, the reference to the
Customer may be interpreted to be the initial receiver of goods from the
supplier/manufacturer. Depending on the specific channel, this could represent
a distributor, OEM, retail organization, etc.
The distributor’s customer (contractor, etc.) or a consumer of a retail
store is referenced in this document as the End Customer.
VMI partnerships offer many methods of addressing the inventory planning and replenishment process. This document intends to be universal in its support of the many fields that may be used in these partnerships. It is therefore advised that the final definition of these fields be determined between the VMI partners.
Quantity On Hand versus
Quantity Available
This transaction provides an opportunity to differentiate between two inventory quantities. The “quantity on hand” (defined in the QTY segment) is the total inventory of an item. The “quantity available” (defined in the ZA segment) is typically considered a portion of quantity on hand inventory that is available for sale and not committed to open customer orders.
Dependent on the suppliers planning/replenishment
algorithms, the frequency of these transactions may vary. The common frequencies are: daily, weekly,
or monthly transmissions as agreed between customer and supplier.
This is a high volume transaction. To reduce cost,
consideration should be given to scheduling transmissions during off-peak
hours.
Section 2
852 Product Activity Data
Segment Notes
This section contains business discussions about the
use of the segments within the 852 Product Activity. These discussions will assist in determining application changes
and business process changes that may be necessary within a company.
852.................................................................................................. 4
ST..................................................................................................... 5
XQ................................................................................................... 5
XPO................................................................................................. 6
N1................................................................................................... 7
LIN................................................................................................... 8
CTP................................................................................................. 9
QTY(Inventory)........................................................................ 10
ZA................................................................................................. 11
QTY(Transactions)................................................................... 13
CTT............................................................................................... 13
SE.................................................................................................. 14
Sample
Transaction................................................................................14
|
852 |
This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Activity Data Transaction Set (852) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a distributor, warehouse, or retailer to advise a trading partner of inventory, sales, and other product activity information. Product activity data enables a trading partner to plan and ship, or propose inventory replenishment quantities, for distribution centers, warehouses or retail outlets. The receiver of the transaction set will maintain some type of inventory/product movement records for its trading partners to enable replenishment calculations based on data provided by the distributor, warehouse or retailer.
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
010 |
ST |
Transaction Set Header |
M |
1 |
|
|
|
|
|
020 |
XQ |
Reporting Date/Action |
M |
1 |
|
|
|
|
|
030 |
XPO |
Pre-assigned Purchase Order Numbers |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - N1 |
|
|
200 |
|
|
|||
|
|
060 |
N1 |
Name |
O |
1 |
|
N1/060 |
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - LIN |
|
|
999999 |
|
|
|||
|
|
010 |
LIN |
Item Identification |
O |
1 |
|
|
|
|
|
020 |
CTP |
Pricing Information |
O |
25 |
|
|
|
|
|
070 |
QTY |
Quantity |
O |
1 |
|
|
|
|
LOOP ID - ZA |
|
|
>1 |
|
|
|||
|
|
080 |
ZA |
Product Activity Reporting |
M |
1 |
|
N2/080 |
|
|
|
090 |
QTY |
Quantity |
O |
1 |
|
N2/090 |
|
|
|
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
010 |
CTT |
Transaction Totals |
O |
1 |
|
N3/010 |
|
|
|
020 |
SE |
Transaction Set Trailer |
M |
1 |
|
|
|
ST |
Transaction Set Header |
Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 |
To indicate the start of a transaction set and to assign a control number.
Example:
ST*852*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
852 Product
Activity Data |
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 |
|
|
Reporting Date/Action |
Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 |
To specify reporting date and action to be taken.
Example:
XQ*G*20011201^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
|
XQ01 |
305 |
Transaction
Handling Code Description: Code designating
the action to be taken by all parties Code NAME
G Plan
Order(s) and Ship Product |
M |
ID |
1/2 |
|
|
|
XQ02 |
373 |
Date Description: Date expressed
as CCYYMMDD |
M |
DT |
8/8 |
|
|
Pre-assigned
Purchase Order Numbers |
Pos: 030 Max: >1 Heading - Optional Loop: N/A Elements: 2 |
To transmit pre-assigned purchase order numbers.
ECTF Notes:
This segment is used to designate a purchase order number or a range of purchase order numbers which the customer is authorizing to the supplier's planner.
Example:
XPO*092123456*092123556^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
|
XPO01 |
324 |
Purchase
Order Number Description: Identifying
number for Purchase Order assigned by the buyer/purchaser ECTF Notes: It is recommended
that the XPO01 (Purchase Order Number) element be used to transmit a single
purchase order number or the first purchase order number in a range. |
M |
AN |
1/22 |
|
|
|
XPO02 |
324 |
Purchase
Order Number Description: Identifying number
for Purchase Order assigned by the buyer/purchaser ECTF Notes: It is
recommended that the XPO02 (Purchase Order Number) element be used to
transmit the ending purchase order number in a range. |
O |
AN |
1/22 |
|
|
Name |
Pos: 060 Max: 1 Heading - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code.
ECTF Notes:
This segment is used to designate the customer/branch associated with the product activity information.
Although this is an optional segment in ASC X12, this is a required segment for VMI transactions.
DUNS+4 should be considered the primary and preferred method for identifying a location. ID Qualifiers 91 and 92 require prior trading partner agreement and should be avoided.
Example:
N1*RL*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 ECTF Notes: The RL
Qualifier is commonly used to designate the customer's branch location. Code NAME RL Reporting
Location |
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 (67) Code NAME
1 D-U-N-S Number 9 D-U-N-S+4,D-U-N-S
Number with Four Character Suffix 91 Assigned by Seller
or Seller's Agent (not recommended) |
C |
ID |
1/2 |
|
|
|
N104 |
67 |
Identification
Code Description: Code identifying
a party or other code |
C |
AN |
2/80 |
|
|
Item Identification |
Pos: 010 Max: 1 Detail - Optional Loop: LIN Elements: 11 |
To specify basic item identification data.
ECTF Notes:
LIN02 through LIN11 provide for 5 different Product/Service ID's for each item. If only one Product/Service ID is provided, LIN02 and LIN03 are used. LIN04 and LIN05 would be used for a second Product/Service ID. Multiple Product/Service ID's can be provided in any sequence.
Example:
LIN*1*VC*P-8750*UI*09999982010*BP*12345-6*RK*BZ0R6A12^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
LIN01 |
350 |
Assigned
Identification Description: Alphanumeric
characters assigned for differentiation within a transaction set |
O |
AN |
1/20 |
|
|
LIN02 |
235 |
Product/Service
ID Qualifier Description: Code identifying
the type/source of the descriptive number used in Product/Service ID (234) 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 |
M |
ID |
2/2 |
|
|
LIN03 |
234 |
Product/Service
ID Description: Identifying
number for a product or service |
M |
AN |
1/48 |
|
|
LIN10 |
235 |
Product/Service
ID Qualifier Description: Code identifying
the type/source of the descriptive number used in Product/Service ID (234) ECTF Notes: Refer
to LIN02 for recommended code list. |
C |
ID |
2/2 |
|
|
LIN11 |
234 |
Product/Service
ID Description: Identifying number
for a product or service |
C |
AN |
1/48 |
|
Pricing Information |
Pos: 020 Max: 25 Detail - Optional Loop: LIN Elements: 3 |
To specify pricing information
ECTF Notes:
This segment is used to communicate the customer's price information. It is typically used to confirm pricing information.
Example:
CTP**DIS*5.33******PE^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
|
CTP02 |
236 |
Price
Identifier Code Description: Code identifying
pricing specification Code NAME
DIS Distributor's
Price PRP Promotional
price |
C |
ID |
3/3 |
|
|
|
CTP03 |
212 |
Unit
Price Description: Price per unit
of product, service, commodity, etc. |
C |
R |
1/17 |
|
|
|
CTP09 |
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 NC No Charge PE Price per Each PF Price Per Foot PP Price per Pound TF Per 1000 Feet TP Price
per Thousand |
O |
ID |
2/2 |
|
|
Quantity of Inventory |
Pos: 070 Max: 1 Detail - Optional Loop: LIN Elements: 3 |
To specify quantity information.
ECTF Notes:
The quantity of the item on hand in the customer's inventory control system.
Example:
QTY*17*1000*EA^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
QTY01 |
673 |
Quantity
Qualifier Description: Code specifying the
type of quantity Code NAME
17 Quantity on Hand
Internal: The quantity of the catalog number on
hand in the customer's inventory control system. |
M |
ID |
2/2 |
|
|
QTY02 |
380 |
Quantity Description: Numeric value of
quantity |
C |
R |
1/15 |
|
|
QTY03 |
C001 |
Composite
Unit of Measure Description: To identify a
composite unit of measure(See Figures Appendix for examples of use) |
O |
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 RE Reel RL Roll SH Sheet SO Spool TH Thousand |
M |
ID |
2/2 |
|
Product Activity Reporting |
Pos: 080 Max: 1 Detail - Mandatory Loop: ZA Elements: 7 |
To provide activity details concerning product being reported.
Example:
ZA*QA*100*EA^
ZA*QA*100*EA*164*20011201*ACC*P^
ZA*QI*100*EA^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
|
ZA01 |
859 |
Activity
Code Description: Code identifying
activity details for the product being reported Code NAME
DG Quantity Damaged Description: Total
product listed as damaged goods Internal: The quantity
of inventory listed as damaged and therefore non-saleable. HL Quantity on Hold Internal: The
quantity of this catalog number on reserve. (The reserve is usually a
commitment by the customer to hold a specified amount of stock.) LS Lost Sales Internal:
Quantity requested by an end customer where sales were lost due to an
out of stock condition. OQ Planned Order
Quantity Description: The
quantity of the item suggested to order by the buying party. Internal: This
is the quantity of the material suggested to order by the customer. PO Calculated Reorder
Point Description: The
inventory level on the buying party's system at which an order quantity would
be suggested. Internal: This
is the inventory level on the customers system at which an order quantity
will be suggested. QA Current Inventory
Quantity Available for Shipment or Sale Description:
Indicates the quantity currently available to be sold or shipped. Internal: The
quantity of the catalog number available for sale. QC Quantity Committed Description:
Quantity reserved for orders not shipped Internal: The
quantity sold but not yet reduced from inventory. This is the quantity mortgaged against a sale that has not yet
been picked or shipped. QD Additional Demand
Quantity Description: The
quantity requested by the buying party in addition to normal order quantity
(i.e. promotions, etc.) Internal: The
quantity requested by the customer in addition to normal order quantity,
(e.g. promotions, etc.). This value should not be used in replenishment
calculations since it is an exception quantity. QI Quantity in
Transit Description:
Quantity of stock replenishment shipped but not received Internal: The
quantity in transit to the customer. QL Minimum Inventory
Quantity Description: The
minimum inventory quantity for replenishment purposes QM Maximum Inventory
Quantity Description: The maximum
inventory quantity for replenishment purposes QO Quantity Out of Stock Description: The
quantity of this item currently back ordered to the end customer. Internal: The
quantity of this catalog number currently back ordered to the end customer. QP Quantity On Order,
Not Yet Received Description: Total
quantity expected to be received from supplier for current reporting period,
but not yet received. Internal: The
quantity of this catalog number currently on order to the supplier. QR Quantity Received Description: The
quantity received into the buying party's system since the last 852 product
activity data update. Internal: The
quantity received into the customer's system since the last 852 product
activity data update. QS Quantity Sold Description: The
quantity sold to end customers since the last 852 product activity update. QT Adjustment to Inventory Quantity Internal: This value is used for
informational purposes only to communicate changes to inventory not defined
in this transaction. It should not be
used to calculate replenishment quantities. QU Quantity Returned By
Consumer Description: The
quantity returned by the buying party to the supplier since the last 852
product activity data update. Internal:
Quantity returned by customer to the supplier since the last 852
product activity data update. QZ Quantity
Transferred Internal: The
quantity transferred to a satellite branch.
Satellite branches are branches that are directly replenished from a
stocking branch.
For the purpose of calculating distributor forecast, Quantity
Transferred will be added by the supplier to the Quantity Sold to determine total demand on the
branch. (Demand = QZ + QS). |
M |
ID |
2/2 |
|
|
|
ZA02 |
380 |
Quantity Description: Numeric value of
quantity |
C |
R |
1/15 |
|
|
|
ZA03 |
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 RE Reel RL Roll SH Sheet SO Spool TH Thousand |
C |
ID |
2/2 |
|
|
|
ZA04 |
374 |
Date/Time
Qualifier Description: Code specifying type
of date or time, or both date and time Code NAME
036 Expiration Description: Date
coverage expires Internal: This
qualifier and associated date (ZA05) should be used to determine the ending
date of an Additional Demand Quantity.
Use of the qualifier allows for the additional quantity to be
maintained by the inventory management system for a period of time defined by
the buying party. 164 First Issue Internal: This
qualifier and associated date (ZA05) should be used to indicate a new item is
being added to the VMI routine and may indicate a future date to begin
planning. 171 Revision
Internal: This qualifier and associated date (ZA05)
should be used to indicate modification (e g; status, order point, etc.) to
an item within the VMI routine and may indicate a future date to begin using
the new data values. |
C |
ID |
3/3 |
|
|
|
ZA05 |
373 |
Date Description: Date expressed as
CCYYMMDD |
C |
DT |
8/8 |
|
|
|
ZA06 |
128 |
Reference
Identification Qualifier Description: Code qualifying
the Reference Identification Code NAME
ACC Status |
C |
ID |
2/3 |
|
|
|
ZA07 |
127 |
Reference
Identification Description: Reference
information as defined for a particular Transaction Set or as specified by
the Reference Identification Qualifier ECTF Notes: This field is used to designate the intended
disposition of the item. Code NAME
D Delete/Inactive Internal: This
item should be removed from the supplier's VMI system. N VMI Fill to
Customer Backorder Only Internal: This
item should not be planned by the supplier, but should the buying party's
system indicate a backorder, then the supplier should replenish to cover the
backorder. P VMI Planned Internal: This
item should be planned by the supplier. X Exclude from
Replenishment
Internal: The supplier should not replenish this
item. |
C |
AN |
1/30 |
|
|
Quantity of Transactions |
Pos: 090 Max: 1 Detail - Optional Loop: ZA Elements: 2 |
To specify quantity information.
ECTF Notes:
The use of this segment is to quantify the number of transactions associated to the quantity described in the ZA segment. Examples include the number of purchase transactions for the quantity sold (ZA01 = QS), the number of transfers for the quantity transferred (ZA01 = QZ), the number of returns for the quantity returned (ZA01 = QR), etc.
Example:
QTY*OC*5^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name |
Req |
Type |
Min/Max |
|
|
|
QTY01 |
673 |
Quantity
Qualifier Description: Code specifying
the type of quantity Code NAME
AG Number of End Users Description:
Number of participating users N4 Number of Times OC Order Count Description: The
number of orders processed associated with the QS (quantity sold). This order count could also be used with
QO (quantity out of stock/back orders) and lost sales. Internal: This
is the number of orders processed and associated with the QS (Quantity
Sold). Note: Additional uses of this "count"
field could be used with other qualifiers.
For example, with the QO (Quantity Out of Stock) (back orders). |
M |
ID |
2/2 |
|
|
|
QTY02 |
380 |
Quantity Description: Numeric value of
quantity |
C |
R |
1/15 |
|
|
Transaction Totals |
Pos: 010 Max: 1 Summary - Optional Loop: N/A Elements: 1 |
To transmit a hash total for a specific element in the transaction set
Example:
CTT*1^
Element Summary:
|
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
CTT01 |
354 |
Number
of Line Items Description: Total number of
line items in the transaction set ECTF Notes: Total
number of LIN segments. |
M |
N0 |
1/6 |
|
|
Transaction Set Trailer |
Pos: 020 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*26*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 3
852 Product Activity Data
Sample Transaction
This
section contains a sample transaction showing the use of the segments within
the 852 Product Activity Data.
Note: The sample may not show
all segments or qualifier combinations.
ST*852*0001^
XQ*G*19991205^
XPO*092123456*092123556^
N1*RL*ABC Distribution*9*1234567890001^
LIN*1*VC*P-8750*UI*09999982010*BP*12345-6*RK*BZ0R6A12^
CTP**DIS*5.33******PE^
QTY*17*1000*EA^
ZA*QA*1000*EA*164*20011201*ACC*P^
ZA*QP*100*EA^
LIN*2*VC*R-1224*UI*09999982512*BP*99345-6*RK*AR0R6A52^
CTP**DIS*4.99******PE^
QTY*17*503*EA^
ZA*QA*415*EA ^
ZA*QR*5*EA^
QTY*N4*1^
ZA*QS*88*EA^
QTY*OC*5^
CTT*2^
SE*19*0001^