Rite Aid
/
Price/Sales Catalog
  • Specification
  • EDI Inspector
Import guide into your account
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 832 Price/Sales Catalog

X12 Release 5010

This X12 Transaction Set contains the format and establishes the data contents of the Price/Sales Catalog Transaction Set (832) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to furnishing or requesting the price of goods or services in the form of a catalog.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
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
    detail
    LIN 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

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    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 Interchange Acknowledgment Requested
    1
    Interchange Acknowledgment Requested (TA1)
    ISA-15
    I14
    Interchange 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

    SC
    Price/Sales Catalog (832)
    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

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

    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).
    832
    Price/Sales Catalog
    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

    BCT
    0200

    Beginning Segment for Price/Sales Catalog

    RequiredMax use 1

    To indicate the beginning of the Price/Sales Catalog Transaction Set and specify catalog purpose and number information

    Example
    BCT-01
    683
    Catalog Purpose Code
    Required

    Code indicating purpose of catalog

    PC
    Price Catalog
    BCT-02
    684
    Catalog Number
    Required
    Min 1Max 15

    Identifying number for catalog or superseded catalog

    Detail

    LIN Loop
    RequiredMax >1
    LIN
    0100

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    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.
    EN
    EAN/UCC - 13
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    SLN Loop
    RequiredMax >1
    SLN
    3500

    Subline Item Detail

    RequiredMax use 1

    To specify product subline detail item data

    Usage notes

    Notes on Unit of Measure
    CA Converts to Cases
    CS Converts to Cases
    BX Converts to Cases
    CT Converts to Cases
    DZ Converts to Dozens
    EA Converts to Inner-Packs
    PC Converts to Pieces

    Example
    SLN-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SLN01 is the identifying number for the subline item.
    • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
    SLN-03
    662
    Relationship Code
    Required

    Code indicating the relationship between entities

    • SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
    I
    Included
    SLN-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SLN-05
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-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

    BX
    Box
    CA
    Case
    CS
    Cassette
    CT
    Carton
    DZ
    Dozen
    EA
    Each
    PC
    Piece
    SLN-06
    212
    Unit Price
    Required
    Min 1Max 15

    Price per unit of product, service, commodity, etc.

    SLN-08
    662
    Relationship Code
    Required

    Code indicating the relationship between entities

    • SLN08 is a code indicating the relationship of the price or amount to the associated segment.
    I
    Included
    PO4
    4100

    Item Physical Details

    RequiredMax use >1

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

    Example
    PO4-01
    356
    Pack
    Required
    Min 1Max 6

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

    Usage notes

    Number of Inner Containers

    Summary

    CTT
    0100

    Transaction Totals

    RequiredMax use 1

    To transmit a hash total for a specific element in the transaction set

    • Number of line items (CTT01) is the accumulation of the number of LIN segments.
      Hash total (CTT02) is not used in this transaction.
    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*832*000003913~
    BCT*PC*38006~
    LIN**UI*30005417719~
    SLN*1**I*376*CA*73.92**I~
    PO4*12~
    LIN**UI*30005423918~
    SLN*1**I*112*CA*96.72**I~
    PO4*24~
    LIN**UI*30005423930~
    SLN*1**I*15*CA*102.84**I~
    PO4*12~
    LIN**UI*30005432920~
    SLN*1**I*105*CA*155.28**I~
    PO4*12~
    LIN**UI*30005550919~
    SLN*1**I*22*CA*176.4**I~
    PO4*36~
    LIN**UI*30005555619~
    SLN*1**I*82*CA*189.36**I~
    PO4*36~
    LIN**UI*30031223413~
    SLN*1**I*226*CA*93.6**I~
    PO4*24~
    LIN**UI*30031861614~
    SLN*1**I*141*CA*88.08**I~
    PO4*24~
    LIN**UI*30031862413~
    SLN*1**I*266*CA*82.32**I~
    PO4*24~
    CTT*9~
    SE*1*000003913~

    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.