Rite Aid
/
Product Activity Data
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Rite Aid. Contact Rite Aid for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Rite Aid logo

X12 852 Product Activity Data

X12 Release 5010

This X12 Transaction Set 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 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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/rite-aid/product-activity-data/01H3CCPH3RYWJ2M0DQFWR2FJY1
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
Transaction Set Header
Max use 1
Required
XQ
0200
Reporting Date/Action
Max use 1
Required
Vendor
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
ISA-15
I14
Interchange Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PD
Product Activity Data (852)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

005010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

Heading

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) is 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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

XQ
0200
Heading > XQ

Reporting Date/Action

RequiredMax use 1

To specify reporting dates, actions to be taken and an identifying number

Usage notes

XQH20070510~

Example
XQ-01
305
Transaction Handling Code
Required
Identifier (ID)

Code designating the action to be taken by all parties

H
Notification Only
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

  • XQ02 is the reporting date. If reporting a date range, then XQ02 is the start date and XQ03 is the end date.
Usage notes

Reporting Date

N1 Vendor
RequiredMax >1
Variants (all may be used)
Place of Business
N1
0600
Heading > Vendor > N1

Party Identification

RequiredMax use 1

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).
Usage notes

N1VN**9254321~

The N104 is Rite Aid's internal vendor number for your company. When calling Rite Aid, this number should be provided as a reference number.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

VN
Vendor
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

Vendor Number Assigned by Rite Aid

N1 Vendor end
N1 Place of Business
RequiredMax >1
Variants (all may be used)
Vendor
N1
0600
Heading > Place of Business > N1

Party Identification

RequiredMax use 1

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).
Usage notes

N1BURITE AID HDQTRS. CORP.1014578892~

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BU
Place of Business
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

RITE AID HDQTRS. CORP.

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet
92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)

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.
Usage notes

014578892 Rite Aid's Duns Number

014578892
Rite Aid's Duns Number
N1 Place of Business end
Heading end

Detail

LIN Loop
RequiredMax >1
LIN
0100
Detail > LIN Loop > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

LIN*UI03456701234IN0034567~

Example
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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)
UI
U.P.C. Consumer Package Code (1-5-5)
VN
Vendor's (Seller's) Item Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-04
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

IN
Buyer's Item Number
LIN-05
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

N9
0400
Detail > LIN Loop > N9

Extended Reference Information

RequiredMax use >1

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

N9*82**ACCU-CHEK CMPT STR 102CT~

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

82
Data Item Description (DID) Reference

Specific data elements that the government will ask a contractor to provide and are spelled out in specific requirement documents

N9-03
369
Free-form Description
Required
String (AN)
Min 1Max 45

Free-form descriptive text

ZA Loop
RequiredMax >1
ZA
0800
Detail > LIN Loop > ZA Loop > ZA

Product Activity Reporting

RequiredMax use 1

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.
Usage notes

ZA*QA~

Example
ZA-01
859
Activity Code
Required
Identifier (ID)

Code identifying activity details for the product being reported

QA
Current Inventory Quantity Available for Shipment or Sale
QO
Quantity Out of Stock
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
SDQ
1100
Detail > LIN Loop > ZA Loop > SDQ

Destination Quantity

RequiredMax use >1

To specify destination and quantity detail

Usage notes

More than one SDQ segment may be sent for each type of product activity sent in a ZA segment.

Example
If either Identification Code (SDQ-05) or Quantity (SDQ-06) is present, then the other is required
If either Identification Code (SDQ-07) or Quantity (SDQ-08) is present, then the other is required
If either Identification Code (SDQ-09) or Quantity (SDQ-10) is present, then the other is required
If either Identification Code (SDQ-11) or Quantity (SDQ-12) is present, then the other is required
If either Identification Code (SDQ-13) or Quantity (SDQ-14) is present, then the other is required
If either Identification Code (SDQ-15) or Quantity (SDQ-16) is present, then the other is required
If either Identification Code (SDQ-17) or Quantity (SDQ-18) is present, then the other is required
If either Identification Code (SDQ-19) or Quantity (SDQ-20) is present, then the other is required
If either Identification Code (SDQ-21) or Quantity (SDQ-22) is present, then the other is required
SDQ-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
SDQ-02
66
Identification Code Qualifier
Required
Identifier (ID)

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
SDQ-03
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • SDQ03 is the store number.
SDQ-04
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-05
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-06
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-07
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-08
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-09
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-10
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-11
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-12
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-13
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-14
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-15
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-16
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-17
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-18
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-19
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-20
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

SDQ-21
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

SDQ-22
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

ZA Loop end
LIN Loop end
Detail end

Summary

CTT
0100
Summary > CTT

Transaction Totals

RequiredMax use 1

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-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
0200
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample

ST*852*000010463~
XQ*H*20110408~
N1*BU*RITE AID HDQTRS. CORP.*1*014578892~
N1*VN**92*34092~
LIN**UI*07553759884*IN*0310945~
N9*82**ACCU-CHEK CMPT STR 102CT~
ZA*QA~
SDQ*EA*92*00010*1337*00035*207*00055*849*00081*741~
ZA*QP~
SDQ*EA*92*00010*1440*00035*96*00081*480~
ZA*QS~
SDQ*EA*92*00010*134*00035*21*00055*66*00081*34~
LIN**UI*07553700971*IN*0313920~
N9*82**SOFTCLIX LANCETS 100 S!!M~
ZA*QA~
SDQ*EA*92*00010*975*00035*204*00055*534*00081*420~
ZA*QP~
SDQ*EA*92*00010*576*00035*192*00055*192*00081*192~
ZA*QS~
SDQ*EA*92*00010*152*00035*6*00055*45*00081*25~
LIN**UI*36570210110*IN*0323433~
N9*82**ACCU-CHEK AVIVA METER~
ZA*QA~
SDQ*EA*92*00010*1114*00035*142*00055*438*00081*773~
ZA*QS~
SDQ*EA*92*00010*45*00035*11*00055*20*00081*19~
LIN**UI*36570210310*IN*0324477~
N9*82**ACCU-CHEK AVIVA STRP 50CT~
ZA*QA~
SDQ*EA*92*00010*2402*00035*313*00055*584*00081*765~
ZA*QP~
SDQ*EA*92*00010*864*00035*144*00055*396*00081*936~
ZA*QS~
SDQ*EA*92*00010*189*00035*26*00055*55*00081*88~
LIN**UI*36570210410*IN*0325335~
N9*82**ACCU-CHEK AVIVA STRP 100CT~
ZA*QA~
SDQ*EA*92*00010*2869*00035*495*00055*1955*00081*1627~
ZA*QP~
SDQ*EA*92*00010*648*00035*216*00055*648*00081*1296~
ZA*QS~
SDQ*EA*92*00010*339*00035*28*00055*179*00081*117~
LIN**UI*07553745097*IN*0325368~
N9*82**MULTICLIX LANCETS 102CT~
ZA*QA~
SDQ*EA*92*00010*1775*00035*309*00055*367*00081*768~
ZA*QP~
SDQ*EA*92*00055*864*00081*432~
ZA*QS~
SDQ*EA*92*00010*164*00035*14*00055*61*00081*59~
LIN**UI*07553731463*IN*0331240~
N9*82**ACCU-CHEK ACTV STR 50CT~
ZA*QA~
SDQ*EA*92*00010*1017*00035*79*00055*204*00081*251~
ZA*QP~
SDQ*EA*92*00035*48*00055*96*00081*120~
ZA*QS~
SDQ*EA*92*00010*84*00035*6*00055*18*00081*8~
LIN**UI*07553749070*IN*0331242~
N9*82**ACCU-CHEK CMPT PLUS METER~
ZA*QA~
SDQ*EA*92*00010*289*00035*60*00055*83*00081*179~
ZA*QP~
SDQ*EA*92*00010*88*00035*8*00055*24*00081*48~
ZA*QS~
SDQ*EA*92*00010*19*00035*3*00055*14*00081*6~
LIN**UI*07553747419*IN*0331243~
N9*82**ACCU-CHEK CMPT STR 51CT~
ZA*QA~
SDQ*EA*92*00010*941*00035*143*00055*415*00081*492~
ZA*QP~
SDQ*EA*92*00010*288*00035*48~
ZA*QS~
SDQ*EA*92*00010*67*00035*2*00055*21*00081*33~
LIN**UI*07553730381*IN*0387169~
N9*82**ACCU-CHEK CMF CURVE 100CT~
ZA*QA~
SDQ*EA*92*00010*960*00035*72*00055*522*00081*417~
ZA*QP~
SDQ*EA*92*00010*576*00035*48*00081*576~
ZA*QS~
SDQ*EA*92*00010*96*00035*3*00055*40*00081*40~
CTT*10~
SE*84*000010463~

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.