C&S Wholesale 852 - Product Activity Data Specifications

Modified on Tue, May 26 at 9:53 AM

**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.


X12 852 Product Activity Data

X12 Release 4010Revised February 28, 2024

Print

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.

Delimiters

~ Segment

* Element

> Component

EDI samples

None included

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*00*          *00*          *XX*XXXXXXXXXXXXXXX*XX*XXXXXXXXXXXXXXX*250328*0958*U*00401*000000000*X*X*>~

ISA-01

I01

Authorization Information Qualifier

Required

Identifier (ID)

Code to identify 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 to identify 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

Qualifier to designate 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

Qualifier to designate 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

I10

Interchange Control Standards Identifier

Required

Identifier (ID)

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

ISA-12

I11

Interchange Control Version Number

Required

Identifier (ID)

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

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 sent by the sender to request an interchange acknowledgment (TA1)

0

No Acknowledgment Requested

1

Interchange Acknowledgment Requested

ISA-15

I14

Usage Indicator

Required

Identifier (ID)

Min 1Max 1

Code to indicate 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

GS

Functional Group Header

RequiredMax use 1

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

Example

GS*PD*XX*XXXXXX*20250328*0947*000*XX*004010UCS~

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

GS-04

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

GS-05

337

Time

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 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

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

004010UCS

Heading

ST

010

Transaction Set Header

RequiredMax use 1

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

Example

ST*852*0001~

ST-01

143

Transaction Set Identifier Code

Required

Identifier (ID)

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

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

020

Reporting Date/Action

RequiredMax use 1

To specify reporting date and action to be taken

Usage notes

Example: XQG20110512

Example

XQ*G*20231202~

XQ-01

305

Transaction Handling Code

Required

Identifier (ID)

Code designating the action to be taken by all parties

G

Plan Order(s) and Ship Product

XQ-02

373

Date

Required

Date (DT)

CCYYMMDD format

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.

N1 Loop Ship To

OptionalMax 1

Variants (all may be used)

N1 Loop Vendor

N1

060

Name

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

Example: N1STC&S WHOLESALE GROCERS, INC.90018424670001

Example

N1*ST*X*ZZ*XXXXXX~

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

N1-01

98

Entity Identifier Code

Required

Identifier (ID)

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

ST

Ship To

N1-02

93

Name

Optional

String (AN)

Min 1Max 60

Free-form name

N1-03

66

Identification Code Qualifier

Optional

Identifier (ID)

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

N1-04

67

Identification Code

Optional

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

C&S Ship-To D-U-N-S Number

DTM

120

Date/Time Reference

OptionalMax use >1

To specify pertinent dates and times

Usage notes

Example: DTM00920110511

Example

DTM*009*20231202~

DTM-01

374

Date/Time Qualifier

Required

Identifier (ID)

Code specifying type of date or time, or both date and time

009

Process Date

DTM-02

373

Date

Optional

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

N1 Loop Vendor

OptionalMax 1

Variants (all may be used)

N1 Loop Ship To

N1

060

Name

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

Example:
 
N1VNC&S WHOLESALE GROCERS, INC.ZZ0000996 (our internal buyer vendor number)

Example

N1*VN*XXX*ZZ*XXXXXX~

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

N1-01

98

Entity Identifier Code

Required

Identifier (ID)

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

VN

Vendor (internal buyer number)

N1-02

93

Name

Optional

String (AN)

Min 1Max 60

Free-form name

N1-03

66

Identification Code Qualifier

Optional

Identifier (ID)

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

N1-04

67

Identification Code

Optional

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

C&S Ship-To D-U-N-S Number

DTM

120

Date/Time Reference

OptionalMax use >1

To specify pertinent dates and times

Usage notes

Example: DTM00920110511

Example

DTM*009*20231202~

DTM-01

374

Date/Time Qualifier

Required

Identifier (ID)

Code specifying type of date or time, or both date and time

009

Process Date

DTM-02

373

Date

Optional

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

Detail

LIN Loop

OptionalMax >1

LIN

010

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

Example: LIN*UA001234567890

Example

LIN**UA*XXXXXXXXXXXX~

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)

LIN-03

234

Product/Service ID

Required

String (AN)

Min 12Max 12

Identifying number for a product or service

Usage notes

UPC Case Code (12 digits)

PO4

030

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

Example: PO41224*OZ

Example

PO4*00*0000000*FO~

If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) is present, then the other is required

PO4-01

356

Pack

Optional

Numeric (N0)

Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

PO4-02

357

Size

Optional

Decimal number (R)

Min 1Max 8

Size of supplier units in pack

PO4-03

355

Unit or Basis for Measurement Code

Optional

Identifier (ID)

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

ZA Loop

RequiredMax >1

ZA

080

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

Example:
 
ZAQA245CA~
 
ZAQS34CA~
 
ZAQT22CA~
 
ZAQD194CA01520110504ZZ5/15/2011~
 
ZAQD0CA01620110515ZZ5/15/2011~ To provide end date of promotion only
 
ZAQP250CA00420110518PO275193~

Example

ZA*QD*000000000000*CA*015*20231202*PO*XXXXX~

If either Quantity (ZA-02) or Unit or Basis for Measurement Code (ZA-03) is present, then the other is required

If either Date/Time Qualifier (ZA-04) or Date (ZA-05) is present, then the other is required

If either Reference Identification Qualifier (ZA-06) or Reference Identification (ZA-07) is present, then the other is required

ZA-01

859

Activity Code

Required

Identifier (ID)

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

ZA-02

380

Quantity

Optional

Decimal number (R)

Min 1Max 15

Numeric value of quantity

ZA-03

355

Unit or Basis for Measurement Code

Optional

Identifier (ID)

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

CA

Case

ZA-04

374

Date/Time Qualifier

Optional

Identifier (ID)

Code specifying type of date or time, or both date and time

004

Purchase Order

015

Promotion Start

016

Promotion End

ZA-05

373

Date

Optional

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Delivery requested date.

ZA-06

128

Reference Identification Qualifier

Optional

Identifier (ID)

Code qualifying the Reference Identification

PO

Purchase Order Number

ZZ

Mutually Defined

ZA-07

127

Reference Identification

Optional

String (AN)

Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Summary

CTT

010

Transaction Totals

OptionalMax 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.

Usage notes

Example: CTT*15

Example

CTT*0000~

CTT-01

354

Number of Line Items

Required

Numeric (N0)

Min 1Max 6

Total number of line items in the transaction set

Usage notes

Contains the number of LIN segments present in the transaction set.

SE

020

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*0*0001~

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

GE

Functional Group Trailer

RequiredMax use 1

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

Example

GE*00000*000~

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

IEA

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*0*000000000~

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

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article