X12 846 CommerceHub Inventory Inquiry/Advice
The Belk 846 guide outlines the specific business rules and functional requirements that apply to the Belk
relationship.
During the supplier on boarding process with CommerceHub you may contact the Vendor Implementation team by sending an email to partnersetup@commercehub.com. Please include the following information in your email:
- Your company name
- Your contact information
- The fact that you are working with Belk
- A detailed description of the issue
Once your account is live and in the production environment you will need to work with the
CommerceHub Customer Support team on all production related issues. You can contact Customer Support at: 844-HUB-HELP or customersupport@commercehub.com.
- ~ 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
- 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
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).
- 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).
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
Quantity
To specify quantity information
Code specifying the type of quantity
- 20
- Unusable Quantity
This qualifier indicates that the quantity passed in the QTY02 is currently unavailable to Belk. When a status of 20 is used, Belk will zero the quantity for the product in their system. Once a new status is sent to Belk, the quantity will be updated.
- 33
- Quantity Available for Sale (stock quantity)
This qualifier indicates that the quantity passed in the QTY02 is available to Belk.
- 61
- Remaining Authorized Quantity
- 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.
Date/Time Reference
To specify pertinent dates and times
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
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.
Date the indicated qty is expected to be available
- 018
- Available
- Date the indicated qty is expected to be available
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)
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.
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
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)
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
Code indicating the date format, time format, or date and time format
Loop Trailer
To indicate that the loop immediately preceding this segment is complete
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.