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

X12 852 Product Activity Data

X12 Release 4030

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 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
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free 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
    N9
    0400
    Reference Identification
    Max use 1
    Required
    N1 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 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
    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 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
    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

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

    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
    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
    I65
    Repetition Separator
    Required
    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

    Code specifying the version number of the interchange control segments

    00403
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
    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 indicating sender's request for an interchange acknowledgment

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    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
    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 where CC represents the first two digits of the calendar year

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

    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

    004030
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

    Heading

    ST
    0100

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

    Reporting Date/Action

    RequiredMax use 1

    To specify reporting date and action to be taken

    Usage notes

    XQG20030331~

    Example
    XQ-01
    305
    Transaction Handling Code
    Required

    Code designating the action to be taken by all parties

    G
    Plan Order(s) and Ship Product
    XQ-02
    373
    Date
    Required
    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.
    N9
    0400

    Reference Identification

    RequiredMax use >1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    N9IK0303310019531~

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IK
    Invoice Number

    Manufacturer's invoice number for vehicle/component

    N9-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    N1 Loop
    RequiredMax >1
    N1
    0600

    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

    N1BYALBERTSONS COMPANIES LLC90091372090400~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    CQ
    Corporate Office
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

    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
    N1-04
    67
    Identification Code
    Required
    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
    RequiredMax >1
    LIN
    0100

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    LIN*UD004154800385~

    Example
    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.
    UD
    U.P.C./EAN Consumer Package Code (2-5-5)
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    CTP
    0200

    Pricing Information

    RequiredMax use 25

    To specify pricing information

    Usage notes

    CTPUCP*3.84~
    CTP
    SPC*.31~

    Example
    CTP-02
    236
    Price Identifier Code
    Required

    Code identifying pricing specification

    UCP
    Unit cost price
    CTP-03
    212
    Unit Price
    Required
    Min 1Max 15

    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.
    ZA Loop
    RequiredMax >1
    ZA
    0800

    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

    ZAQS*00720030331~

    Example
    ZA-01
    859
    Activity Code
    Required

    Code identifying activity details for the product being reported

    QS
    Quantity Sold
    ZA-04
    374
    Date/Time Qualifier
    Required

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

    007
    Effective
    ZA-05
    373
    Date
    Required
    CCYYMMDD format

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

    SDQ
    1100

    Destination Quantity

    RequiredMax use >1

    To specify destination and quantity detail

    Usage notes

    SDQEA9208451~

    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

    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

    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
    Min 2Max 80

    Code identifying a party or other code

    • SDQ03 is the store number.
    Usage notes

    CODE IDENTIFYING A STORE NUMBER.

    SDQ-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SDQ-05
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-06
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-07
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-08
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-09
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-10
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-11
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-12
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-13
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-14
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-15
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-16
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-17
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-18
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-19
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-20
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-21
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-22
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    Summary

    CTT
    0100

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

    CTT*63~

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    0200

    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*05572001~
    XQ*G*20030331~
    N9*IK*0303310019531~
    N1*CQ*ALBERTSONS COMPANIES LLC*9*0091372090400~
    LIN**UD*004154800385~
    CTP**UCP*3.84~
    ZA*QS***007*20030331~
    SDQ*EA*92*0845*1~
    CTT*63~
    SE*10*05572001~

    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.