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
- 004010UCS
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Reporting Date/Action
To specify reporting date and action to be taken
Example: XQG20110512
Code designating the action to be taken by all parties
- G
- Plan Order(s) and Ship Product
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.
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).
Example: N1STC&S WHOLESALE GROCERS, INC.90018424670001
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- ZZ
- Mutually Defined
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.
C&S Ship-To D-U-N-S Number
Date/Time Reference
To specify pertinent dates and times
Example: DTM00920110511
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).
Example:
N1VNC&S WHOLESALE GROCERS, INC.ZZ0000996 (our internal buyer vendor number)
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor (internal buyer number)
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- ZZ
- Mutually Defined
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.
C&S Ship-To D-U-N-S Number
Date/Time Reference
To specify pertinent dates and times
Example: DTM00920110511
Detail
Item Identification
To specify basic item identification data
Example: LIN*UA001234567890
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.
- UA
- U.P.C./EAN Case Code (2-5-5)
Identifying number for a product or service
UPC Case Code (12 digits)
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Example: PO41224*OZ
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- CA
- Case
- FO
- Fluid Ounce
- LB
- Pound
- OZ
- Ounce
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.
Example:
ZAQA245CA~
ZAQS34CA~
ZAQT22CA~
ZAQD194CA01520110504ZZ5/15/2011~
ZAQD0CA01620110515ZZ5/15/2011~ To provide end date of promotion only
ZAQP250CA00420110518PO275193~
Code identifying activity details for the product being reported
- QA
- Current Inventory (Onhand)
- QD
- Additional Demand by Date
- QO
- Out of Stocks
- QP
- On Order by PO
- QS
- Turn or Combined Sales
- QT
- Promotional Sales
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
Code specifying type of date or time, or both date and time
- 004
- Purchase Order
- 015
- Promotion Start
- 016
- Promotion End
Date expressed as CCYYMMDD
Delivery requested date.
Code qualifying the Reference Identification
- PO
- Purchase Order Number
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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.
Example: CTT*15
Total number of line items in the transaction set
Contains the number of LIN segments present in the transaction set.
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
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.