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
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
Code designating the action to be taken by all parties
- 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.
Preassigned Purchase Order Numbers
To transmit preassigned purchase order numbers
Burlington Stores uses the 'XPO segment only when purchase order number assignment has not previously been established with the trading partner.
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.
Identifying number for Purchase Order assigned by the orderer/purchaser
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.
- 1
- D-U-N-S Number, Dun & Bradstreet
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- UL
- UCC/EAN Location Code
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
- SU
- Supplier Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
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
- BS
- Bill and Ship To
- BT
- Bill-to-Party
- BY
- Buying Party (Purchaser)
- FR
- Message From
- RL
- Reporting Location
- ST
- Ship To
- TO
- Message To
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- UL
- UCC/EAN Location Code
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- CF
- Collect, Freight Credited Back to Customer
- DF
- Defined by Buyer and Seller
- MX
- Mixed
- PC
- Prepaid but Charged to Customer
- PO
- Prepaid Only
- PP
- Prepaid (by Seller)
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- BU
- Bus
- C
- Consolidation
- CE
- Customer Pickup / Customer's Expense
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- L
- Contract Carrier
- M
- Motor (Common Carrier)
- R
- Rail
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Cancel After
To specify pertinent dates and times
Burlington Stores uses the DTM segment to provide specific processing dates.
Delivery Requested
To specify pertinent dates and times
Burlington Stores uses the DTM segment to provide specific processing dates.
Requested Ship
To specify pertinent dates and times
Burlington Stores uses the DTM segment to provide specific processing dates.
Detail
Item Identification
To specify basic item identification data
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.
- IN
- Buyer's Item Number
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style 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
- QI
- Quantity in Transit
Burlington Stores is testing the Quantity of stock replenishment shipped but not received, i.e Quantity in transit. This data is not currently available to most Trading Partners... If there are any questions about any Burlington Stores EDI or EDI specifications contact EDI Support at (609) 387-7800 Ext 3340 (EDI-0) or EDI.Support@BurlingtonStores.com, where an incident will be opened and answered by the next available EDI Coordinator.
- QS
- Quantity Sold
Destination Quantity
To specify destination and quantity detail
Burlington Stores uses the 852 Product Activity Data to transmit inventory and product sales by location to the supplier and ONLY when sales occur. If there were sales to Store 123, and Store 123 had 'on hand' inventory,
there would be a reference to Store 123; however if there were no sales to Store 123, and Store 123 had 'on hand' inventory, there would be no reference to Store 123 in the 852 document.
Burlington Stores uses the SDQ03 segment to identify the store number followed by the SDQ04 indicating the quantity repeating the store number and Quantity as necessary through SDQ21/SDQ22.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- CA
- Case
- EA
- Each
- PK
- Package
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.
Code which identifies a specific location
- SDQ23 identifies the area within the location identified in SDQ03, SDQ05, SDQ07, SDQ09, SDQ11, SDQ13, SDQ15, SDQ17, SDQ19, and SDQ21.
- SDQ23 may be used to identify areas within a store, e.g., front room, back room, selling outpost, end aisle display, etc. The value is agreed to by trading partners or industry conventions.
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
Quantity Sold
XQ|H|20130929|20131005
N9|DP|6785823
LIN||IN|80181923|IT|CI53417S2
ZA|QS
SDQ|EA|92|261|1
LIN||IN|80184577|IT|CI53419S2
ZA|QS
SDQ|EA|92|796|1
LIN||IN|92530740|IT|OIU276D|UP|886809618536
ZA|QS
SDQ|EA|92|534|1|209|1|486|1|171|1|487|1
LIN||IN|75874892|IT|OIU373H|UP|886809553998
ZA|QS
SDQ|EA|92|112|1|314|1|125|2|440|1|197|1
LIN||IN|73747497|IT|OIW512H|UP|886809607820
ZA|QS
SDQ|EA|92|167|2|759|1|48|1|344|1|857|2|839|1|431|1|480|1
LIN||IN|73747581|IT|OIW512H|UP|886809607837
ZA|QS
SDQ|EA|92|167|2|457|1|84|1|205|1|253|1|143|1|164|1|526|1|344|1|257|1
SDQ|EA|92|440|1|839|1
LIN||IN|80509893|IT|OIZ558P
ZA|QS
SDQ|EA|92|463|1|55|1
LIN||IN|73864804|IT|ONU372H|UP|886809554315
ZA|QS
SDQ|EA|92|325|1|363|1|474|2|584|1|42|2|522|1|213|1|481|1|538|1|84|1
SDQ|EA|92|433|1|523|1|404|1|315|2|143|1|110|2|232|1|279|1|318|1|447|3
SDQ|EA|92|277|1|731|1|436|2|41|1|547|1|835|2|819|2|176|1|345|2|448|1
CTT|126
SE|32|0001
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.