Tractor Supply Co
/
DTC Inventory Inquiry/Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Tractor Supply Co. Contact Tractor Supply Co for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Tractor Supply Co logo

X12 846 DTC Inventory Inquiry/Advice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.

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

    00400
    Standard Issued as ANSI X12.5-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

    IB
    Inventory Inquiry/Advice (846)
    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

    004000
    ASC X12 Standards Approved by ANSI in 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).
    846
    Inventory Inquiry/Advice
    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

    BIA
    020

    Beginning Segment for Inventory Inquiry/Advice

    RequiredMax use 1

    To indicate the beginning of an Inventory Inquiry/Advice Transaction Set

    Usage notes

    At minimum TSC expects the 846 once a day. Please plan the extract accordingly. Thank you.

    Example: BIA00SIX20190413*1515~

    Example
    BIA-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    Usage notes

    When you send a REPLACE status it is going to replace the original that you had sent earlier in the day. When you send a CHANGE it should represent an incremental change from the original.

    00
    Original
    04
    Change
    05
    Replace
    BIA-02
    755
    Report Type Code
    Required

    Code indicating the title or contents of a document, report or supporting item

    SI
    Seller Inventory Report
    BIA-03
    127
    Reference Identification
    Required
    Min 1Max 30

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

    • BIA03 identifies the number of the inquiry/advice that is transferred.
    Usage notes

    The 846 unique reference number assigned by the vendor.

    BIA-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIA04 identifies the date of the inquiry/advice that is transferred.
    Usage notes

    Date extract was generated.

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

    • BIA05 identifies the time of the inquiry/advice that is transferred.
    Usage notes

    Time extract was generated.

    REF
    060

    Reference Identification

    RequiredMax use 12

    To specify identifying information

    Usage notes

    Example: REFIA800000*Name of Vendor~

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IA
    Internal Vendor Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 6

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

    Usage notes

    TSC's 6-digit vendor number.

    REF-03
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Detail

    LIN Loop
    RequiredMax >1
    LIN
    010

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    Example: LIN1UP012345678912VNVNUM001IN1234567CH*US~

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    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
    European Article Number (EAN) (2-5-5-1)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    LIN-03
    234
    Product/Service ID
    Required
    Min 12Max 13

    Identifying number for a product or service

    Usage notes

    UPC is a min 12 / max 13 no extra characters such as spaces or anything else. Just the UPC or the transaction will fail.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    LIN-06
    235
    Product/Service ID Qualifier
    Optional

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

    IN
    Buyer's Item Number
    LIN-07
    234
    Product/Service ID
    Optional
    Min 7Max 7

    Identifying number for a product or service

    Usage notes

    The TSC SKU is exactly 7 digits. This is a numeric field. Do not send spaces, alpha or any other characters except the 7 digit TSC SKU.

    LIN-08
    235
    Product/Service ID Qualifier
    Optional

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

    CH
    Country of Origin Code
    LIN-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes
    PID
    030

    Product/Item Description

    RequiredMax use 200

    To describe a product or process in coded or free-form format

    Usage notes

    Example: PIDF***PRODUCT DESCRIPTION~

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-05
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    QTY Loop
    RequiredMax >1
    QTY
    320

    Quantity

    RequiredMax use 1

    To specify quantity information

    Usage notes

    Example: QTY339*EA~

    Example
    QTY-01
    673
    Quantity Qualifier
    Required

    Code specifying the type of quantity

    33
    Quantity Available for Sale (stock quantity)
    QTY-02
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    Not used by TSC. The quantity available should be reported in the SCH segment with today's date.

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

    EA
    Each
    SCH Loop
    RequiredMax >1
    SCH
    360

    Line Item Schedule

    RequiredMax use 1

    To specify the data for scheduling a specific line-item

    Usage notes

    Example: SCH9EA**01820190405~

    Example
    SCH-01
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SCH-02
    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
    SCH-05
    374
    Date/Time Qualifier
    Required

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

    • SCH05 specifies the interpretation to be used for SCH06 and SCH07.
    018
    Available
    SCH-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Summary

    CTT
    010

    Transaction Totals

    OptionalMax use 1

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

    • Number of line items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the values of the quantities (QTY02) of each QTY segment.
    Usage notes

    Example: CTT*9~

    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*846*262001~
    BIA*00*SI*000000001*20190726*080016~
    REF*IA*800000*VENDOR NAME GOES HERE~
    LIN**UP*123456789010*VN*001*IN*1097421*CH*CHN~
    PID*F****PRODUCTION MANT~
    QTY*33*21*EA~
    SCH*21*EA***018*20190726~
    LIN*010*UP*123456789011*VN*002*IN*1096474*CH* CHN ~
    PID*F****SITE HEATER~
    QTY*33*448*EA~
    SCH*448*EA***018*20190726~
    LIN*020*UP*123456789012*VN*003*IN*1097420*CH*CHN~
    PID*F****CUBE STOVE CFS-300-BLK~
    QTY*33*748*EA~
    SCH*748*EA***018*20190726~
    LIN*030*UP*123456789013*VN*004*IN*1097422*CH*CHN~
    PID*F****240V UTILITY HEATER~
    QTY*33*483*EA~
    SCH*483*EA***018*20190726~
    LIN*040*UP*123456789014*VN*005*IN*1061116*CH*CHN~
    PID*F****OIL-FILLED SPACE HEA~
    QTY*33*164*EA~
    SCH*164*EA***018*20190726~
    LIN*050*UP*123456789015*VN*006*IN*1061123*CH*CHN~
    PID*F****PARABOLIC HEATER (1)~
    QTY*33*600*EA~
    SCH*600*EA***018*20190726~
    LIN*060*UP*123456789016*VN*007*IN*1096475*CH*CHN~
    PID*F****DESKTOP HEATER 6/CA~
    QTY*33*111*EA~
    SCH*111*EA***018*20190726~
    LIN*070*UP*123456789017*VN*008*IN*1096476*CH*CHN~
    PID*F****4/CASE~
    QTY*33*79*EA~
    SCH*79*EA***018*20190726~
    LIN*080*UP*123456789018*VN*009*IN*1096479*CH*CHN~
    PID*F****LOG SET~
    QTY*33*276*EA~
    SCH*276*EA***018*20190726~
    LIN*090*UP*123456789019*VN*010*IN*1030857*CH*CHN~
    PID*F****SPACE HEATER~
    QTY*33*52*EA~
    SCH*52*EA***018*20190726~
    CTT*10~
    SE*45*262001~

    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.