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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Inventory Inquiry/Advice
To indicate the beginning of an Inventory Inquiry/Advice Transaction Set
EXAMPLE:
BIA00SISYSTEMINV396319911108
Code identifying purpose of transaction set
- 00
- Original
This is the first transaction set for the current period. Items with zero quantity are not reported. Items that have not changed values from previous reports are still reported as long as quantity is not zero. On the Original transaction set BIA03 is a unique number.
- 05
- Replace
This transaction set replaces the preceding specified transaction. The recipient is expected to back out the previous transaction set and replace it with this transaction set. Where the Inventory Advice covers more than one replacement for an end user or reporting location, the replacement transaction purpose should cover only those locations where replacement data is applicable.
REPLACEMENT TRANSACTIONS SHOULD ONLY BE SENT AFTER CONTACTING ADOBE DIRECTLY
Code indicating the title or contents of a document, report or supporting item
CompTIA recommends that "DD" be used when Distributors and "SI" be used when Resellers report inventory to their trading partners. CompTIA recommends that "LC" be used when trading partners other than distributors, manufacturers, or resellers report their inventory. Locations providing inventory reports from multiple stock locations should provide
inventory reports in separate X12 846 transactions.
- DD
- Distributor Inventory Report
- LC
- Location Inventory Report
- 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.
Identifying Number for Advice assigned by Sender.
Date expressed as CCYYMMDD
- BIA04 identifies the date of the inquiry/advice that is transferred.
Effective Inventory Date. Adobe requires an inventory report be done weekly, reported by Monday for the previous week.
Name
To identify a party by type of organization, name, and code
COMPTIA:
It is strongly encouraged that the trading partners codify all addresses within their systems through use of N103 and N104. The use of codes would eliminate the need for transmittal of N2, N3, and N4 segments below.
EXAMPLE:
N1DSCOMPUTER RESELLER912345678912324
Code identifying an organizational entity, a physical location, property or an individual
Locations providing inventory reports from multiple stocking locations should provide a separate 846 transaction from each location.
- DS
- Distributor
This N1 loop is used to identify the reporting partner and their relationship with Adobe.
Code designating the system/method of code structure used for Identification Code (67)
CompTIA recommends the use of Dun & Bradstreet (DUNS) number to identify the trading partners. D&B assigns a nine-digit unique identifier to each trading partner. The trading partner then assigns a four-digit (DUNS + 4) code to uniquely identify the specific location. E.g. 0000 may be a central warehouse, 0002 may be one of the trading partners' sites.
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
EXAMPLE:
N2~M. BUYER
Address Information
To specify the location of the named party
EXAMPLE:
N3~123 MAIN STREET
Geographic Location
To specify the geographic place of the named party
EXAMPLE:
N4CEDAR RAPIDSIA~524032140
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
5/9 digit ZIP Code or Postal Code.
Code identifying the country
US - United States
CA - Canada
For US and Canadian locations CompTIA does recommend the use of N404. For non-US/Canadian locations the two-character country code qualifier established by ISO 3166(E/F) should be used. ISO 3166:1998 (E/F) is available from: American National Standards Institute, 11 West 42nd Street, New York, NY 10036, Telephone: 212.642.4900, FAX: 212.302.1286.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
EXAMPLE:
PERICJ SMITHTE8015551234FX8015554321
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Communications number with country or area code in the format 800-555-1212x1234.
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
COMPTIA:
It is strongly encouraged that the trading partners codify all addresses within their systems through use of N103 and N104. The use of codes would eliminate the need for transmittal of N2, N3, and N4 segments below.
EXAMPLE:
N1DSCOMPUTER RESELLER912345678912324
Code identifying an organizational entity, a physical location, property or an individual
Locations providing inventory reports from multiple stocking locations should provide a separate 846 transaction from each location.
- DU
- Resale Dealer
Code designating the system/method of code structure used for Identification Code (67)
CompTIA recommends the use of Dun & Bradstreet (DUNS) number to identify the trading partners. D&B assigns a nine-digit unique identifier to each trading partner. The trading partner then assigns a four-digit (DUNS + 4) code to uniquely identify the specific location. E.g. 0000 may be a central warehouse, 0002 may be one of the trading partners' sites.
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
EXAMPLE:
N2~M. BUYER
Address Information
To specify the location of the named party
EXAMPLE:
N3~123 MAIN STREET
Geographic Location
To specify the geographic place of the named party
EXAMPLE:
N4CEDAR RAPIDSIA~524032140
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
5/9 digit ZIP Code or Postal Code.
Code identifying the country
US - United States
CA - Canada
For US and Canadian locations CompTIA does recommend the use of N404. For non-US/Canadian locations the two-character country code qualifier established by ISO 3166(E/F) should be used. ISO 3166:1998 (E/F) is available from: American National Standards Institute, 11 West 42nd Street, New York, NY 10036, Telephone: 212.642.4900, FAX: 212.302.1286.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
EXAMPLE:
PERICJ SMITHTE8015551234FX8015554321
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Communications number with country or area code in the format 800-555-1212x1234.
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
COMPTIA:
It is strongly encouraged that the trading partners codify all addresses within their systems through use of N103 and N104. The use of codes would eliminate the need for transmittal of N2, N3, and N4 segments below.
EXAMPLE:
N1WHWAREHOUSE912345678912324
Code identifying an organizational entity, a physical location, property or an individual
Locations providing inventory reports from multiple stocking locations should provide a separate 846 transaction from each location.
Adobe: This N1 loop is to be used to identify each individual reporting location.
- SN
- Store
Code designating the system/method of code structure used for Identification Code (67)
CompTIA recommends the use of Dun & Bradstreet (DUNS) number to identify the trading partners. D&B assigns a nine-digit unique identifier to each trading partner. The trading partner then assigns a four-digit (DUNS + 4) code to uniquely identify the specific location. E.g. 0000 may be a central warehouse, 0002 may be one of the trading partners' sites.
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 93
- Code assigned by the organization originating the transaction set
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.
Name
To identify a party by type of organization, name, and code
COMPTIA:
It is strongly encouraged that the trading partners codify all addresses within their systems through use of N103 and N104. The use of codes would eliminate the need for transmittal of N2, N3, and N4 segments below.
EXAMPLE:
N1WHWAREHOUSE912345678912324
Code identifying an organizational entity, a physical location, property or an individual
Locations providing inventory reports from multiple stocking locations should provide a separate 846 transaction from each location.
Adobe: This N1 loop is to be used to identify each individual reporting location.
- WH
- Warehouse
Code designating the system/method of code structure used for Identification Code (67)
CompTIA recommends the use of Dun & Bradstreet (DUNS) number to identify the trading partners. D&B assigns a nine-digit unique identifier to each trading partner. The trading partner then assigns a four-digit (DUNS + 4) code to uniquely identify the specific location. E.g. 0000 may be a central warehouse, 0002 may be one of the trading partners' sites.
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 93
- Code assigned by the organization originating the transaction set
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
Item Identification
To specify basic item identification data
COMPTIA:
CompTIA discourages the use of Buyer's Part Number because of maintenance difficulties involved.
EXAMPLE:
LIN~~UP098756100013BP~P1234567
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.
- MG
- Manufacturer's Part Number
Identifying number for a product or service
Adobe SKU
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)
UPC code
Identifying number for a product or service
UPC Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Your SKU
Product/Item Description
To describe a product or process in coded or free-form format
EXAMPLE:
PID~F~~~~PHOTOSHOP V5.0 WIN 95/WIN NT CD
Adobe:
Product description from Adobe price list required.
(See Glossary: Adobe product description)
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
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
COMPTIA:
In this detail position of the Inventory Advice document, this segment identifies the quantity of the product being reported. Quantities should be reported as sales quantities (eaches) of the reporting location. Inventory quantities may include quantities on hand, quantities in transit, and returns where credit has not yet been granted.
EXAMPLE:
QTY1715
Adobe:
(1) NOTE: The sum of the quantities reported as “On-Hand”, “In-Float” and “Returns” should equal to TOTAL physical inventory of Adobe product. (2) Please do not include those inventory quantities equaling zero. This will result in smaller data transmissions and savings on all
VAN charges.
ADOBE STATEMENT of INTENT: The primary goal of Adobe’s Channel Partner Inventory Reporting program is to ensure that the TOTAL physical inventory of Adobe product held at distributor sites is accurately reported on a weekly basis, such that this information can be reliably used to manage distribution channel inventory levels.
Code specifying the type of quantity
Internal: QTY14120
QTY17385
QTY27100
QTY33250
QTY63350
QTY7610
QTYBQ25
QTYIQ75
- 14
- Quantity in Float
Inventory that is in-transfer between a distributor’s stocking locations (warehouses) that is not included in those locations’ “On-Hand” quantities. (“In-Float” and “On-Hand” quantities are mutually exclusive.) “In-Float” Requires multiple stocking locations: Distributor owns and controls the product transfer.
- 17
- Quantity on Hand
Saleable inventory still in physical inventory for the specified reporting location. This includes quantity committed, but not quantity in float (see below). Quantity on hand does not include nonsaleable or defective product, or product for return to a vendor (stock balancing, for instance)—these should be reported as “Returns” (76).
- 27
- Committed Quantity
Committed On-Hand inventory -- the number of units in stock that are allocated, reserved or committed to an order, but not yet relieved from physical inventory. “Committed quantity” is a subset of what should be reported in the “On-Hand” quantity (17).
- 63
- On Order Quantity
The number of units of the specified item on order (not yet received) with all vendors for delivery to the specified reporting location. When reporting to a manufacturer for instance, the reported quantity could include quantities on order from several distributors as well as from the manufacturer receiving this inventory report.
- 76
- Returns
Inventory that is being returned to the vendor (includes ALL Non-saleable, defective, stock balancing, etc, --even if it may not be returned to Adobe for credit.). It has been relieved from the
sender's “On-Hand” inventory, and may be staged in a “Non-Saleable” or “Returns” status, OR picked and 1) sitting on the sender's dock awaiting shipment; 2) actually in-transit back to vendor; 3) sitting on the vendor's dock awaiting receipt; 4) received by the vendor, but not yet credited. Returns quantities may be reported until shipment or until credit is issued by Adobe. - IQ
- In-Transit Quantity
A subset of “On-Order Quantity”, the Quantity “In Transit” is the product flow in-bound against open purchase orders (from all vendors) for delivery to the reporting location. The reported quantities could actually be 1) sitting on the vendor's dock awaiting shipment; 2) physically in-transit; or 3) sitting on the receiver's dock awaiting receipt. To report “In Transit” quantities requires knowledge of shipment prior to goods receipt.
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.
COMPTIA:
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
Total number of line items in the transaction set
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
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.