X12 852 Retail 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
XQH20000209*20000215
Code designating the action to be taken by all parties
The code identifying the action to be taken in the XQ01 element will be predetermined between you and Target Corporation. Most Partners will receive "H". An EDI Operations Supervisor must approve a request to receive "G".
- 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.
This represents the start date for which this transaction applies.
Date expressed as CCYYMMDD
This represents the end date for which this transaction applies.
Department Number
To transmit identifying information as specified by the Reference Identification Qualifier
N9DP088 (This segment will report each time the department changes within the 852.)
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
Internal Vendor Number
To transmit identifying information as specified by the Reference Identification Qualifier
N9IA3342078
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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).
Due to processing efficiency, store level data will only be available on a restricted basis.
Sample N1 Segment
N1BYTARGET920229 (DC/Store Level - Basic Format)
"BY" will only be sent when XQ01= "G"
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)
This element is used only for DC/Store level Basic Format.
- 92
- Assigned by Buyer or Buyer's Agent
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.
Four digit location code
This element used only for DC/Store Level Basic Format.
Due to processing efficiency, store level data will only be available on a restricted basis.
Sample N1 Segment
N1RLTARGET920001 (DC/Store Level - Basic Format)
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).
Due to processing efficiency, store level data will only be available on a restricted basis.
Sample N1 Segment
N1BYTARGET920229 (DC/Store Level - Basic Format)
"BY" will only be sent when XQ01= "G"
Code identifying an organizational entity, a physical location, property or an individual
- RL
- Reporting Location
Code designating the system/method of code structure used for Identification Code (67)
This element is used only for DC/Store level Basic Format.
- 92
- Assigned by Buyer or Buyer's Agent
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.
Four digit location code
This element used only for DC/Store Level Basic Format.
Detail
Item Identification
To specify basic item identification data
NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of receiving it and sending it back on inbound EDI documents to Target.
Target Stores Vendors may choose to receive all UPCs for an item. For additional information, see your company's specific notifications located on the secured section of Partners Online, under the Important Updates box or contact the EDI Operations Team at 612-304-3310.
Sample LIN Segment
LIN1UP012437891437CB063020400VA*70344
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Identifying number for a product or service
When the qualifier=CB, this field will contain a 9-digit DPCI.
When the qualifier=EN, this field will contain the 13-digit European Article Number.
When the qualifier=EO, this field will contain the 8-digit European Article Number.
When the qualifier=UP, this field will contain the full 12-digit UPC Code.
When the qualifier=VA, this field will contain the Vendor Style Number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Identifying number for a product or service
When the qualifier=CB, this field will contain a 9-digit DPCI.
When the qualifier=EN, this field will contain the 13-digit European Article Number.
When the qualifier=EO, this field will contain the 8-digit European Article Number.
When the qualifier=UP, this field will contain the full 12-digit UPC Code.
When the qualifier=VA, this field will contain the Vendor Style Number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Identifying number for a product or service
When the qualifier=CB, this field will contain a 9-digit DPCI.
When the qualifier=EN, this field will contain the 13-digit European Article Number.
When the qualifier=EO, this field will contain the 8-digit European Article Number.
When the qualifier=UP, this field will contain the full 12-digit UPC Code.
When the qualifier=VA, this field will contain the Vendor Style Number.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
You will receive a PO4 Segment only when XQ01="G".
Sample PO4 Segment
PO44***********6
PO424
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.
If receiving sales only, QS will be the only code used.
Negative quantities will report as negatives.
Starting in October 2003 you may receive up to four decimal places in the Quantity field.
Sample ZA Segment
ZAQS (SDQ format)
ZAQS102EA (Basic format)
Code identifying activity details for the product being reported
- QA
- Current Inventory Quantity Available for Shipment or Sale
Indicates the quantity currently available to be sold or shipped
- QP
- Quantity On Order, Not Yet Received
Total quantity expected to be received from supplier for current reporting period, but not yet received
- QS
- Quantity Sold
- QX
- Quantity Requested (Will Override Replenishment Planning)
This is sent only when XQ01 = G.
Numeric value of quantity
This quantity will be sent only when sending Basic Format.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
- LB
- Pound
Pricing Information
To specify pricing information
CTP*UCP9.99
Code identifying pricing specification
- UCP
- Unit cost price
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.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Destination Quantity
To specify destination and quantity detail
If a designation has a zero quantity then it will not report. Any location reporting zeroes for all designations will NOT report.
For Example:
Loc #1 has a quantity of zero for all designations - will not be reported.
Loc #2 has a quantity of zero for two designations and 24 for the other - only the 24 will report.
Negative quantities will report as negatives.
Sample SDQ Segment
SDQEA9205517205524805531205541040555720556120055712055924
SDQEA9200016000260003120004600051200061200076
SDQEA9200086000912001060101601056020112021012
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.
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
Code identifying a party or other code
This is Target Corporation's 4-digit location code for DC/Store Level SDQ Format.
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.
CTT*24
Total number of line items 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
Sample 852
GS*PD*SENDERGS*RECEIVERGS*20231005*011822*000000001*X*004010
ST*852*00001
XQ*H*20000209*20000215
N9*DP*088
N9*IA*3342078
N1*RL*TARGET*92*0001
N1*BY*TARGET*92*0229
LIN*1*UP*012437891437*CB*063020400*VA*70344
PO4*4*************6
ZA*QS*102*EA
CTP**UCP*9.99
SDQ*EA*92*0551*72*0552*48*0553*12*0554*104*0555*72*0556*120*0557*12*0559*24
CTT*24
SE*13*00001
GE*1*000000001
IEA*1*000000001
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.