X12 852 Scan Base Trading 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
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
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
Use of code F or G in XQ01 requires the supplier to advise the distributor/warehouse of replenishment quantity usually via Transaction Set 855 (Purchase Order Acknowledgment).
Code designating the action to be taken by all parties
- F
- Plan and Submit Suggested Purchase Order(s)
- 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.
Current 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).
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
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
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.
D-U-N-S Number + 4 Character Suffix.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- DP
- Department Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
For WINS, reference numbers pertaining to the entire order as a whole should be put in the header level of the transaction set. Reference numbers pertaining to individual line items should appear in the detail level of the transaction set.
Detail
Item Identification
To specify basic item identification data
This segment is required except when only sending pre-assigned purchase order numbers in the XPO segment.
Effective with the UCS version coinciding with the UCC-published sunset date (2005) for the discontinuation of the use of 12-digit product identifiers, the qualifier UA (U.P.C./EAN Case Code) (2-5-5) in DE235 will be marked as not used and will be replaced with the qualifier UK (U.P.C./EAN Shipping Container Code) (1-2-5-5-1). The corresponding 14-digit product code will be reflected in DE234. This parallels the global transition to the 14-digit and UCC/EAN product identification numbering structure. In preparation for this transition, the UK qualifier and the corresponding 14-digit product code would be communicated in LIN04 and LIN05, respectively.
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.
- UD
- U.P.C./EAN Consumer Package Code (2-5-5)
Identifying number for a product or service
12 digit Case UPC (2-5-5 format).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- U2
- U.P.C. Shipping Container Code (1-2-5-5)
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.
Identifying number for a product or service
If LIN_24 = U2, LIN_25, 13 digit Case UPC (1-2-5-5 format).
Price per unit of product, service, commodity, etc.
- 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.
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.
For WINS applications, when ZA01 contains code QI (Quantity in Transit), QR (Quantity Received), or QS (Quantity Sold), ZA06 should contain code SI (Shipper's Identifying Number for Shipment (SID) and ZA07 should contain the shipment number. When ZA01 contains code QT (Adjustment to Inventory Quantity) or PA (Production Quantity Adjustment), ZA06 should contain code BP (Adjustment Control Number) and ZA07 should contain the adjustment control number.
When specifying additional demand quantities, use code QD (Additional Demand Quantity) in ZA01, code 002 (Delivery Requested) in ZA04, and the delivery requested date in ZA05. Send one ZA segment to request a single delivery of additional demand quantities, and multiple ZA segments for incremental deliveries of additional demand quantities.
When ZA01 contains code QD (Additional Demand Quantity), the G95 loop may be used to identify an associated promotion and its start and end dates.
When ZA01 contains code QW (Quantity Withdrawn from Warehouse Inventory) and is used to define the portion of warehouse withdrawals pertaining to a promotion for a specific product, the quantity should be placed in the G95 segment in G95_04.
When ZA01 contains code QT (Adjustment to Inventory Quantity) or PA
(Production Quantity Adjustment), negative quantities should be preceded by a minus sign.
ZA04 is used to specify timing of delivery of product when ZA01 contains code QD (Additional Demand Quantity).
Code identifying activity details for the product being reported
All zeros indicates a discontinued item and QD (Additional Demand Quantity) used to send promo quantities and the receive date, a positive number, multiple quantities for same item/same day are added together -reductions in quantities and date changes are made manually.
- QS
- Quantity Sold
Sales at retail.
Code specifying type of date or time, or both date and time
- 139
- Estimated
- 140
- Actual
- 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
- LB
- Pound
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 HEB Store number.
Numeric value of quantity
Quantity sold at the store.
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
Code identifying a party or other code
Parties may define multiple identification codes for a location in order to support warehouse or depositor processing. For example, multiple identification codes might be used to differentiate product lines or stocks for a depositor. Also see Data Elements 66 (Identification Code Qualifier) and 98 (Entity Identifier Code).
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.
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
Sample
XQ*G*20100526
N1*BY*HEB GROCERY CO*9*0079247560000
N9*DP*12E*DEPT/SUB_DEPT
LIN**UD*DDDDDDDDDDDD
CTP**UCP*5.5
ZA*QS***140*20100525
SDQ*EA*92*00421*1
CTT*1
SE*10*3240001
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.