TBG1 Supply Chain
This specification provides the definition of the Product inquiry message (PROINQ) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1.1 Functional definition
A message enabling the sender to inquire on a product or a group of products from a master product catalogue or file according to criteria defined in the message.
1.2 Field of application
The Product inquiry message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
The message usually relates to a manufacturer and/or a supplier of goods and a buyer, or their respective agents.
The buyer may specify in the message the attributes of a product or group of products for which additional information is required. This will allow a manufacturer and/or supplier to send the requester only information for those products the requester is specifically interested in rather than the entire product catalogue.
The Product inquiry message may request information in order to:
- select a specific group or family or products from a supplier entire product catalogue, e.g. a buyer requesting a supplier of medical equipment all product information related to sterilized products.
- select a product or group of products according to attributes or product characteristics as defined by the sender in the message, e.g. a retailer requesting a clothing manufacturer to send product information for all blue, white or stripped men's shirts, sizes medium to extra-large.
- determine the availability, lead-time and/or general commercial and/or sales conditions for a specific product.
The response to a product inquiry message will be either a Price/sales catalogue (PRICAT) or Product data message (PRODAT).
PROINQ shall not be used to request a code.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1 Standard terms and definitions
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1 Data segment clarification
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:
- All specified dates and/or times should be in the format 'ccyymmdd'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format.
- Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, months, etc.).
- Where a choice of code or text is given only the code element should be used wherever possible.
- Conditional data that is not required in the message should not be included.
- Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of a group.