Balkamp
/
Inventory Inquiry/Advice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Balkamp. Contact Balkamp for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Balkamp logo

X12 846 Inventory Inquiry/Advice

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/balkamp/inventory-inquiryadvice/01HW5SFSKWG21DRE9KNHVQWPDS
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIA
020
Beginning Segment for Inventory Inquiry/Advice
Max use 1
Required
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

IB
Inventory Inquiry/Advice (846)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIA
020
Heading > BIA

Beginning Segment for Inventory Inquiry/Advice

RequiredMax use 1

To indicate the beginning of an Inventory Inquiry/Advice Transaction Set

Usage notes

Example: BIA22SIDAILY20130904

Example
BIA-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

22
Information Copy
BIA-02
755
Report Type Code
Required
Identifier (ID)

Code indicating the title or contents of a document, report or supporting item

SI
Seller Inventory Report
BIA-03
127
Reference Identification
Required
String (AN)

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.
DAILY
Daily Consignment Reporting
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIA04 identifies the date of the inquiry/advice that is transferred.
N1 Loop
RequiredMax >1
N1
080
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Example: N1SUACME WIDGETS

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SU
Supplier/Manufacturer
Required
String (AN)
Min 1Max 60

Free-form name

N3
100
Heading > N1 Loop > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Usage notes

Example: N3*1601 WHITAKER ROAD

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
110
Heading > N1 Loop > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4PLAINFIELDIN*46168

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N1 Loop end
Heading end

Detail

LIN Loop
RequiredMax >1
LIN
010
Detail > LIN Loop > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

Example: LIN01*BP123-4567VP9999999MF88888888

Example
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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.
BP
Buyer's Part Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

USAG Part Number

LIN-04
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VP
Vendor's (Seller's) Part Number
LIN-05
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

MF
Manufacturer
LIN-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

CTP
110
Detail > LIN Loop > CTP

Pricing Information Distributor's Price

RequiredMax use 25

To specify pricing information

Usage notes

Example: CTP*DIS2.56*

Example
Variants (all may be used)
CTPPricing Information Noncontract Tier 2
CTP-02
236
Price Identifier Code
Required
Identifier (ID)

Code identifying pricing specification

DIS
Distributor's Price
CTP-03
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

  • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
  • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Usage notes

Price supplier will bill Balkamp when product is ordered.

CTP
110
Detail > LIN Loop > CTP

Pricing Information Noncontract Tier 2

OptionalMax use 1

To specify pricing information

Usage notes

Example: CTP*N0240.00

Example
CTP-02
236
Price Identifier Code
Required
Identifier (ID)

Code identifying pricing specification

N02
Noncontract Tier 2

Code identifying pricing for and applicable core charge.

CTP-03
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

  • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
  • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Usage notes

Core Charge

QTY Loop
RequiredMax >1
QTY
320
Detail > LIN Loop > QTY Loop > QTY

Quantity

RequiredMax use 1

To specify quantity information

Usage notes

Example: QTY17256*EA

Example
QTY-01
673
Quantity Qualifier
Required
Identifier (ID)

Code specifying the type of quantity

17
Quantity on Hand
29
Projected Available Inventory
QTY-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

Supplier’s quantity balance for item. The field must be 6 bytes with leading zeros. No negative quantities allowed.

QTY-03
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
LDT
350
Detail > LIN Loop > QTY Loop > LDT

Lead Time

RequiredMax use 12

To specify lead time for availability of products and services

Usage notes

Example: LDTAE5*DA

Example
LDT-01
345
Lead Time Code
Required
Identifier (ID)

Code indicating the time range

AE
From date of PO receipt to shipment
LDT-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • LDT02 is the quantity of unit of time periods.
LDT-03
344
Unit of Time Period or Interval
Required
Identifier (ID)

Code indicating the time period or interval

DA
Calendar Days
DTM
355
Detail > LIN Loop > QTY Loop > DTM

Date/Time Reference Available

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Example: DTM01820100801

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

018
Available
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM
355
Detail > LIN Loop > QTY Loop > DTM

Date/Time Reference Product Availability Date

OptionalMax use 1

To specify pertinent dates and times

Example
Variants (all may be used)
DTMDate/Time Reference Available
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

169
Product Availability Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

QTY Loop end
LIN Loop end
Detail end

Summary

CTT
010
Summary > CTT

Transaction Totals

RequiredMax use 1

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.
Usage notes

Example: CTT*1

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240509*1548*U*00401*000000001*0*T*>~
GS*IB*SENDERGS*RECEIVERGS*20240509*154802*000000001*X*004010~
ST*846*0001~
BIA*22*SI*DAILY*20130904~
N1*SU*ACME WIDGETS~
N3*1601 S HOLT RD~
N4*INDIANAPOLIS*IN*46107~
LIN**BP*123-4567*VP*9999999*MF*1~
CTP**DIS*5.49~
QTY*17*256*EA~
LDT*AE*3*DA~
DTM*018*20170801~
LIN**BP*353-4867*VP*9225319*MF*1~
CTP**DIS*100.14~
QTY*17*120*EA~
LDT*AE*3*DA~
DTM*018*20170801~
LIN**BP*353-4928*VP*9269117*MF*1~
CTP**DIS*1.49~
QTY*17*240*EA~
LDT*AE*3*DA~
DTM*018*20170801~
LIN**BP*388-7277*VP*9956332*MF*1~
CTP**DIS*189.49~
QTY*17*1253*EA~
LDT*AE*1*DA~
DTM*018*20170801~
CTT*4~
SE*27*0001~
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.