X12 846 Inventory Inquiry/Advice
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- IB
- Inventory Inquiry/Advice (846)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Beginning Segment for Inventory Inquiry/Advice
To indicate the beginning of an Inventory Inquiry/Advice Transaction Set
Example: BIA00SI000120080520
Code identifying purpose of transaction set
- 00
- Original
Code indicating the title or contents of a document, report or supporting item
- SI
- Seller Inventory Report
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.
Reference Identification
To specify identifying information
Example: REFIOsnbc
Code qualifying the Reference Identification
- IO
- Inbound-to or Outbound-from Party
This qualifier indicates that the REF02 contains the assigned ID for the merchant that this file is being sent to.
Detail
Item Identification
To specify basic item identification data
Example: LIN*VN0001SK99972UP002377649388
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- VN
- Vendor's (Seller's) Item Number
This qualifier indicates that the LIN03 contains the vendor assigned SKU for the product being
reported.
Identifying number for a product or service
The vendor assigned SKU for the product being reported.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
This qualifier indicates that the LIN05 contains the SKU for the product.
Identifying number for a product or service
This element contains the SKU for the product.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
This qualifier indicates that the LIN07 contains the UPC for the product being reported.
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDF08***BLOUSE
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
Code identifying the general class of a product or process characteristic
- 08
- Product
Date/Time Reference
To specify pertinent dates and times
Example: DTM03620100203
Code specifying type of date or time, or both date and time
- 036
- Expiration
Date coverage expires.
This qualifier indicates that the DTM02 contains the discontinue date for the product being reported.
Date expressed as CCYYMMDD
This element contains the date as-of-which replenishment for the
product will cease.
Requests that this date be reported to them as soon as possible. You are still allowed to continue to report an available quantity that can continue to sell.
Once this date has been reported for a given product, this element must be included in all subsequent updates for the remaining life of the product. Once an available quantity of zero is reached, the product can be removed from the file. If this date is omitted from the file prior to the available quantity reaching zero, this items discontinued status is removed.
Quantity
To specify quantity information
Example: QTY616771*EA
Code specifying the type of quantity
- 20
- Unusable Quantity
This qualifier indicates that the quantity passed in the QTY02 is currently unavailable.
- 61
- Remaining Authorized Quantity
This qualifier indicates that the quantity passed in the QTY02 is available.
- TH
- Theoretical Quantity
This qualifier indicates that quantity is not a factor in fulfilling an order. Regardless of the quantity included in the QTY02, the supplier is guaranteeing that they can fulfill all purchase orders for this item.
Numeric value of quantity
Depending on the qualifier used in the QTY01, this element contains the
corresponding value.
Line Item Schedule
To specify the data for scheduling a specific line-item
This segment can be provided whenever a supplier wishes to report a future available quantity and date. Stock with a future availability date should not be included in the QTY segment.
Example: SCH11EA**01819990704
Numeric value of quantity
This element contains the quantity that the supplier expects will become
available at the date included in the SCH06.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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
This qualifier is used to indicate that the SCH06 contains the date that the quantity reported in the SCH01 will become available.
Loop Header
To indicate that the next segment begins a loop
The LS, REF, LE loop is required if the supplier has multiple warehouses. For single warehouse suppliers, this loop is not required.
Example:
LSREF
REFWS500150
REFWS400150
LEREF
Reference Identification
To specify identifying information
- The REF loop conveys serial number, lot number, and inventory data.
Each REF loop represents a warehouse.
The REF segment in the loop is used to identify the warehouse by an ID in the REF-02, and the current quantity available in that warehouse in the REF-03.
Examples:
REFWS500150
REFWS400150
Code qualifying the Reference Identification
- WS
- Warehouse storage location number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Warehouse ID
A free-form description to clarify the related data elements and their content
This value represents the quantity on-hand in the warehouse that is identified by the ID in the REF 02. Integer values only must be used.
Values here must sum to the corresponding aggregate quantity value (QTY 02).
Date/Time Reference
To specify pertinent dates and times
The DTM segment in the loop is used to report future availability for the
warehouse.
Example: DTM01820140808**UN50
Code specifying type of date or time, or both date and time
- 018
- Available
Date expressed as CCYYMMDD
Represents date the next shipment of product is expected to be received at the warehouse identified in the REF 02.
Code indicating the date format, time format, or date and time format
- UN
- Unstructured
Expression of a date, a time, or range of dates, times or dates and times
Next available quantity based on the date provided in the DTM02 segment.
Integer values only must be used.
Next available quantity(s) submitted in each DTM segment must sum up to the corresponding aggregate quantity of the value reported in the (SCH 01) segment.
Loop Trailer
To indicate that the loop immediately preceding this segment is complete
Summary
Transaction Totals
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.
Example: CTT*1
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*IB*SENDERGS*RECEIVERGS*20240426*165024*000000001*X*004010~
BIA*00*SI*0001*20080520~
REF*IO*snbc~
LIN**VN*0001*SK*99972*UP*002377649388~
PID*F*08***BLOUSE~
DTM*036*20100203~
QTY*61*6771*EA~
SCH*11*EA***018*19990704~
LS*REF~
REF*WS*5001*50~
REF*WS*4001*50~
DTM*018*20140808***UN*50~
LE*REF~
CTT*1~
GE*1*000000001~
IEA*1*000000001~
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.