X12 846 Inventory Advice for SAS
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
BIA02 is the sender's internal document number and is used to identify the transaction in the supplier's system.
The date and time (BIA04 and BIA05) are the date and time of creation. The SAS application will use these elements to determine the mostcurrent transaction if more than one is transmitted. The transaction may not be more than 24 hours old or it will be rejected by the SAS system.
Time is expressed using a 24-hour clock.
Code identifying purpose of transaction set
- 00
- Original
Code indicating the title or contents of a document, report or supporting item
- MB
- Manufacturer/Distributor 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.
Date expressed as CCYYMMDD
- BIA04 identifies the date of the inquiry/advice that is transferred.
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.
Batch Number
To specify identifying information
The value of REF*BT is the batch sequence number from the last batch of purchase orders that you received and processed before producing this item availability report.
Code qualifying the Reference Identification
- BT
- Batch Number
Internal Vendor Number
To specify identifying information
The value of REF*IA is a Sears-assigned number which identifies the vendor to the SAS application. This is not the same vendor number required for the invoice.
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Name
To identify a party by type of organization, name, and code
The N104 will contain the Sears-assigned location code for the vendor's ship point. The inventory availability for each reporting location (ship point) must be reported in a separate transaction.
Code identifying an organizational entity, a physical location, property or an individual
- RL
- Reporting Location
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
9 - 9 Reporting location (ship point).
Detail
Item Identification
To specify basic item identification data
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.
- IN
- Buyer's Item Number
Identifying number for a product or service
5 - 5 Sears’ item number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Date/Time Reference
To specify pertinent dates and times
The DTM segment is sent when the item/SKU will be flagged as discontinued only. If a quantity greater than zero is sent in the first SCH segment, then Sears will continue to take orders for the item until the available inventory quantity is depleted or until 60 days after receipt of the last report on the item, whichever occurs first. If the quantity sent in the first SCH segment is zero, then Sears will flag this item as discontinued and no orders will be taken.
The date in DTM02 must be the current date; the same date as the
transaction creation date in BIA04.
Reference Identification
To specify identifying information
This segment is required to specify the department number for the associated line item (LIN). This is the same value sent on the purchase order (REF*DP) and required on the invoice.
Code qualifying the Reference Identification
- DP
- Department Number
Quantity
To specify quantity information
The QTY segment is required to specify the total quantity available of the item/SKU identified in the associated LIN segment.
Only one occurrence of the QTY loop is allowed per LIN segment.
The quantity reported in QTY02 is the sum of the quantities reported in the SCH segments which follow.
The SAS application requires a value of "EA" in QTY03.
Code specifying the type of quantity
- 33
- Quantity Available for Sale (stock quantity)
Numeric value of quantity
1 - 8 Total quantity available
The SCH segment is used to communicate the inventory availability for
a line item. Current and future item availability is reported. Refer to the SAS Guidelines available from the Vendor Information Guide.
A quantity of 9999999 indicates unlimited availability of the associated
item/SKU. This must be reported in the first occurrence of the SCH segment. If 9999999 quantity is specified, do not send additional SCH segments, only one must be used.
Up to 7 iterations of the SCH segments are allowed within each LIN/QTY loop to specify current plus 6 future availability dates. (See exception in note 2)
The first occurrence of the SCH segment must always specify the current date and current item availability. The SCH segments must be transmitted in ascending order by date and no two dates may be equal or the transaction will be rejected.
If an item/SKU is currently unavailable (SCH01 contains the value 0) and has not been discontinued, a second SCH should be sent to specify future availability if the item will be available within 180 days (6 months). An item cannot be sold or reserved unless a quantity is available to sell (current or future).
Line Item Schedule
To specify the data for scheduling a specific line-item
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
Summary
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.