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.