X12 852 Product Activity Data
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.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PD
- Product Activity Data (852)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 852
- Product Activity Data
Reporting Date/Action
To specify reporting date and action to be taken
Code designating the action to be taken by all parties
- G
- Plan Order(s) and Ship Product
- H
- Notification Only
Date expressed as CCYYMMDD
- XQ02 is the reporting date. If reporting a date range, then XQ02 is the start date and XQ03 is the end date.
Date as YYYYMMDD for G and H.
Preassigned Purchase Order Numbers
To transmit preassigned purchase order numbers
Identifying number for Purchase Order assigned by the orderer/purchaser
- XPO01 is the preassigned purchase order number. If a range of purchase order numbers is to be transmitted, use XPO01 for the first number and XPO02 as the ending number.
Start position number.
Identifying number for Purchase Order assigned by the orderer/purchaser
End position number.
Code designating the system/method of code structure used for Identification Code (67)
- XPO03 and XPO04 specify the location to which the purchase order numbers apply.
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
Name
To identify a party by type of organization, name, and code
- The reporting location is required. The reporting location is specified explicitly in the N1 segment using the code RL in N101, or implicitly using the SDQ segment (Table 2) with the location data elements. They are mutually exclusive (the SDQ and the N1 with N101 containing RL).
Code identifying an organizational entity, a physical location, property or an individual
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
Code identifying a party or other code
- 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.
DUNS.
Detail
Item Identification
To specify basic item identification data
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- IN
- Buyer's Item Number
- UA
- U.P.C./EAN Case Code (2-5-5)
- UI
- U.P.C. Consumer Package Code (1-5-5)
- UN
- U.P.C. Case Code Number (1-1-5-5)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Costco's item number, vendor's model number, or designated UPC.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
- UA
- U.P.C./EAN Case Code (2-5-5)
- UI
- U.P.C. Consumer Package Code (1-5-5)
- UN
- U.P.C. Case Code Number (1-1-5-5)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Product Activity Reporting
To provide activity details concerning product being reported
- The quantity for the item identified in the LIN segment is required. Quantity is specified either in the ZA segment (ZA02) or in the SDQ segment.
Code identifying activity details for the product being reported
- QA
- Current Inventory Quantity Available for Shipment or Sale
- QP
- Quantity On Order, Not Yet Received
- QS
- Quantity Sold
Code specifying type of date or time, or both date and time
Blank.
- 007
- Effective
- 173
- Week Ending
Destination Quantity
To specify destination and quantity detail
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
Five digit location.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of LIN segments. Hash total (CTT02) is not used in this transaction set.
- When sending item and activity data in the LIN loop, the CTT segment is required.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.