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
- None included
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
Code identifying purpose of transaction set
- 00
- Original
Code indicating the title or contents of a document, report or supporting item
- AA
- Agent Inventory Report
This code is used for "Unassigned" inventory relationships only.
- 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
Code qualifying the Reference Identification
- IO
- Inbound-to or Outbound-from Party
For inventory being reported by a vendor to CommerceHub using report type code (BIA-02) = SI, indicates that REF-02 contains the vendor's internal ID for the merchant (seller).
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This element must contain a value of okl
When this value is not included correctly, CommerceHub will not process the contents of your file and One King's Lane will not receive your update.
Detail
Item Identification
To specify basic item identification data
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
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Merchant's SKU
Identifying number for a product or service
If "PQ" qualified, indicates the 'newness' condition of the product being offered for sale - if omitted, assumed to be 'NEW'
Value must be one of:
NEW
USED
PRE-OWNED
REFURBISHED
USEDLIKENEW
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)
GS1 ID for product. Must be unique per SKU.
Period End
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 194
- Period End
Availability end date
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Time Code (DTM-04) is always recommended to be populated (even there is no time to be reported) in order to be specific about the UTC
offset for the time zone from which a date is being reported.
When there is no time to be reported, set DTM-03 = 0000 to indicate that the DTM-02 date covers the 24 hour period that begins at midnight on the specified date with a UTC offset specified by the DTM-04.
For example CCYY0515 reported from Hawaii with time 0000 represents the twenty four hours from May 15 09:00 UTC through May 16 08:59:59.99 UTC (Note: Hawaii time is UTC -09:00 on May 15th because of Daylight Savings). The time code that should be sent with a date of CCYY0515 reported from Hawaii would be 16 which is Equivalent to ISO M09.
If the intent is to represent midnight as a specific point in time rather than the 24 hour period that beings at midnight, then the DTM-03 value should be 00000001 (one one-hundreth of a second after midnight).
Period Start
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 193
- Period Start
Availability start date
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Time Code (DTM-04) is always recommended to be populated (even there is no time to be reported) in order to be specific about the UTC
offset for the time zone from which a date is being reported.
When there is no time to be reported, set DTM-03 = 0000 to indicate that the DTM-02 date covers the 24 hour period that begins at midnight on the specified date with a UTC offset specified by the DTM-04.
For example CCYY0515 reported from Hawaii with time 0000 represents the twenty four hours from May 15 09:00 UTC through May 16 08:59:59.99 UTC (Note: Hawaii time is UTC -09:00 on May 15th because of Daylight Savings). The time code that should be sent with a date of CCYY0515 reported from Hawaii would be 16 which is Equivalent to ISO M09.
If the intent is to represent midnight as a specific point in time rather than the 24 hour period that beings at midnight, then the DTM-03 value should be 00000001 (one one-hundreth of a second after midnight).
Expiration
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 036
- Expiration
Date that replenishment purchasing for this product will end (i.e. discontinue date)
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Time Code (DTM-04) is always recommended to be populated (even there is no time to be reported) in order to be specific about the UTC
offset for the time zone from which a date is being reported.
When there is no time to be reported, set DTM-03 = 0000 to indicate that the DTM-02 date covers the 24 hour period that begins at midnight on the specified date with a UTC offset specified by the DTM-04.
For example CCYY0515 reported from Hawaii with time 0000 represents the twenty four hours from May 15 09:00 UTC through May 16 08:59:59.99 UTC (Note: Hawaii time is UTC -09:00 on May 15th because of Daylight Savings). The time code that should be sent with a date of CCYY0515 reported from Hawaii would be 16 which is Equivalent to ISO M09.
If the intent is to represent midnight as a specific point in time rather than the 24 hour period that beings at midnight, then the DTM-03 value should be 00000001 (one one-hundreth of a second after midnight).
Quantity
To specify quantity information
Code specifying the type of quantity
- 20
- Unusable Quantity
Indicates that orders are not currently being accepted for the product, even if the quantity is greater than zero. This should be a temporary 'stop-sell' situation.
- 29
- Projected Available Inventory
Pre-order. Orders for SKU can be booked but SKU is not available for immediate fulfillment. When a SKU is in this status, quantity represents the maximum number of pre-orders that can be accepted. This number can rise or fall as preorders are being booked
- 33
- Quantity Available for Sale (stock quantity)
Indicates that current stock is available to be sold and that stock levels for this product are actively managed and replenished.
- 70
- Maximum Order Quantity
Sourced on demand. A quantity of zero indicates no ceiling on quantity that can be ordered per day.
- TH
- Theoretical Quantity
Indicates that availability for the product is guaranteed regardless of the quantity (i.e. stock level / replenishment is not a concern).
- V2
- Available Quantity
Seasonal. Indicates that the quantity is available to be sold. Stock is actively managed and replenished on a seasonal basis, which may be defined by the period start and period end qualified DTM segments.
Numeric value of quantity
If reporting warehouse specific inventory in REF loops below, this quantity must be the sum of the REF-03 elements of the in those loops.
Line Item Schedule
To specify the data for scheduling a specific line-item
Numeric value of quantity
Quantity expected to become available by date/time indicated in SCH-06/07. This quantity should NOT be included in the value reported in QTY-02.
If reporting warehouse specific inventory in REF loops below, this quantity must be the sum of the DTM-06 elements of the DTM segment in those loops.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
This code must be a valid X12 code but it has no significance. Unit is assumed to match QTY-03
- 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
Date the indicated qty is expected to be available
Date expressed as CCYYMMDD
Represents date the next shipment of product is expected to be received.
If reporting warehouse specific inventory in REF loops below, this date must be the earliest of the DTM-02 dates in the DTM segment in those loops.
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)
Represents time the next shipment of product is expected to be received on the date specified in the SCH-06.
If reporting warehouse specific inventory in REF loops below, this time must be from the DTM segment in those loops with the earliest DTM-02 date.
Loop Header
To indicate that the next segment begins a loop
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.
The DTM segment in the loop is used to report future availability for the warehouse.
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 idendified 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
Required whenever a quantity with a future availability date is being reported for a warehouse. Stock with a future availability date should NOT be included in the REF segment of this loop.
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.
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)
Represents time the next shipment of product is expected to be received on the date stipulated in the DTM-02 for the warehouse identified in the REF 02.
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Time Code (DTM-04) is always recommended to be populated (even there is no time to be reported) in order to be specific about the UTC offset for the time zone from which a date is being reported.
When there is no time to be reported, set DTM-03 = 0000 to indicate that the DTM-02 date covers the 24 hour period that begins at midnight on the specified date with a UTC offset specified by the DTM-04.
For example CCYY0515 reported from Hawaii with time 0000 represents the twenty four hours from May 15 09:00 UTC through May 16 08:59:59.99 UTC (Note: Hawaii time is UTC -09:00 on May 15th because of Daylight Savings). The time code that should be sent with a date of CCYY0515 reported from Hawaii would be 16 which is Equivalent to ISO M09.
If the intent is to represent midnight as a specific point in time rather than the 24 hour period that beings at midnight, then the DTM-03 value should be 00000001 (one one-hundreth of a second after midnight).
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
The quantity that is expected to be received on the date referenced in the DTM 02. Integer values only must be used.
Values here must sum to the corresponding aggregate quantity value (SCH 01)
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.
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
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.