H-E-B
/
Warehouse Product Activity Data
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from H-E-B. Contact H-E-B for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
H-E-B logo

X12 852 Warehouse Product Activity Data

X12 Release 4010

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 sample
    View the latest version of this implementation guide as an interactive webpage
    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
    010
    Transaction Set Header
    Max use 1
    Required
    XQ
    020
    Reporting Date/Action
    Max use 1
    Required
    N1 Loop
    detail
    LIN Loop
    LIN
    010
    Item Identification
    Max use 1
    Required
    ZA Loop
    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

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

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

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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

    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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

    Code identifying a group of application related transaction sets

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

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

    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

    ST
    010

    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

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

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

    Example
    XQ-01
    305
    Transaction Handling Code
    Required

    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
    XQ-02
    373
    Date
    Required
    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.
    Usage notes

    Current Date

    N1 Loop
    OptionalMax >1
    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).
    Example
    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

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

    BO
    Broker or Sales Office
    RL
    Reporting Location
    SF
    Ship From
    ST
    Ship To
    WH
    Warehouse
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    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
    11
    Drug Enforcement Administration (DEA)
    N1-04
    67
    Identification Code
    Optional
    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.

    Detail

    LIN Loop
    OptionalMax >1
    LIN
    010

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    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.

    Example
    If either Product/Service ID Qualifier (LIN-24) or Product/Service ID (LIN-25) is present, then the other is required
    LIN-02
    235
    Product/Service ID Qualifier
    Required

    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.
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Case UPC or NDC Number

    LIN-24
    235
    Product/Service ID Qualifier
    Optional

    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.

    LIN-25
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    If LIN_24 = U2, LIN_25, 13 digit Case UPC (1-2-5-5 format).

    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

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

    Example
    ZA-01
    859
    Activity Code
    Required

    Code identifying activity details for the product being reported

    Usage notes

    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.

    QA
    Current Inventory Quantity Available for Shipment or Sale

    Indicates the quantity currently available to be sold or shipped.

    QD
    Additional Demand Quantity

    Distributor/warehouse request for additional product to be added to supplier replenishment calculations.

    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

    Sales at retail.

    QX
    Quantity Requested (Will Override Replenishment Planning)

    Distributor/warehouse request for specific product quantity regardless of supplier replenishment calculations.

    ZA-02
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    Up to a 11 digit real number/ up to 3 decimal places.

    ZA-03
    355
    Unit or Basis for Measurement Code
    Required

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

    CA
    Case
    EA
    Each
    ZA-04
    374
    Date/Time Qualifier
    Required

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

    002
    Delivery Requested

    This code is used only when ZA01 contains code QD (Additional Demand Quantity). If promotion start and end dates associated with the additional demand quantity are needed, the G95 loop may be used.

    007
    Effective

    Inventory taken, on order as of, etc...

    024
    Promotion Order - End

    Last manufacturer order date.

    051
    Cumulative Quantity Start

    Out of stock cumulative to date, etc...

    173
    Week Ending
    ZA-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Summary

    CTT
    010

    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
    Min 1Max 6

    Total number of line items 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-01
    96
    Number of Included Segments
    Required
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*852*23050001
    XQ*G*20100527
    N1*ST*HEB PHARMACY WHSE*11*RH0277067
    LIN**UA*DDDDDDDDDDDD
    ZA*QA*37*CA*007*20100527
    ZA*QP*0*CA*007*20100527
    ZA*QS*1*CA*173*20100530
    ZA*QO*0*CA*173*20100530
    LIN**UA* DDDDDDDDDDDD
    ZA*QA*221*CA*007*20100527
    ZA*QP*0*CA*007*20100527
    ZA*QS*64*CA*173*20100530
    ZA*QO*0*CA*173*20100530
    CTT*2
    SE*15*23050001

    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.