United Nations Directories
for Electronic Data Interchange for
Administration, Commerce and Transport



 UN/EDIFACT

Message Type : REQOTE Version : D Release : 05B Contr. Agency: UN Revision : 9 Date : 2006-01-17 SOURCE: TBG1 Supply Chain CONTENTS Request for quote message 0. INTRODUCTION 1. SCOPE 1.1 Functional definition 1.2 Field of application 1.3 Principles 2. REFERENCES 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions 4. MESSAGE DEFINITION 4.1 Segment clarification 4.1.1 Header section 4.1.2 Detail section 4.1.3 Summary section 4.2 Segment index (alphabetical sequence by tag) 4.3 Message structure 4.3.1 Segment table ---------------------------------------------------------------------- For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction ---------------------------------------------------------------------- 0. INTRODUCTION This specification provides the definition of the Request for quote message (REQOTE) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE 1.1 Functional definition A message which provides potential buyers with the ability to solicit price, delivery schedule, and other conditions from potential sellers of goods or services. 1.2 Field of application The Request for quote 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. 1.3 Principles - A potential buyer may solicit offers for one or more goods items or services. - A request for quote may refer to goods items or services related to one or more delivery schedules, call-offs, etc. - A request for quote for cross border transactions may contain additional information for customs and/or statistical purposes. 2. REFERENCES 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 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/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. Data that is not necessary to meet the functional requirements of 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. Free text information within the message should be avoided as this inhibits automatic processing. 4.1.1 Header section Information to be provided in the Header section: 0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Request for quote message is REQOTE. Note: Request for quote messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 REQOTE 0052 D 0054 05B 0051 UN 0020 BGM, Beginning of message A segment by which the sender must uniquely identify the request for quote by means of its type and number and when necessary it's function. 0030 DTM, Date/time/period A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the request date. Examples of the use of this DTM segment are: Date the request for quote was made, and the last date the quotation will be accepted. The Date/time/period segment within other segment groups should be used whenever the date/time/period requires to be logically related to another specified data item e.g. Payment due date is specified within the PYT segment group. 0040 PAI, Payment instructions A segment requesting or confirming conditions of payment, guarantee and method of payment for the whole request for quotation, if accepted. An example of the use of this segment is to specify that a documentary credit will be used. 0050 ALI, Additional information A segment indicating special conditions related to the total request for quotation owing to origin, customs preference, or other commercial factors. 0060 IMD, Item description A segment providing a description common to all line items of the request for quotation. 0070 IRQ, Information required A segment to specify information to be supplied in the quotation. 0080 FTX, Free text A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the received to process this segment manually. 0090 Segment group 1: RFF-DTM A group of segments for giving references and where necessary, their dates, relating to the whole message, e.g. contract number, import/export license number, reservation number. 0100 RFF, Reference A segment identifying the reference by its number and where appropriate a line number. 0110 DTM, Date/time/period A segment specifying the date/time related to the reference. 0120 Segment group 2: AJT-FTX A segment group to give information about adjustment. 0130 AJT, Adjustment details A segment giving adjustment details. 0140 FTX, Free text A segment giving additional information on the adjustment. 0150 Segment group 3: TAX-MOA-LOC A group of segments specifying tax related information, and when necessary, the location(s) to which that tax information relates. 0160 TAX, Duty/tax/fee details A segment specifying a tax type, category and rate, or exemption, relating to the whole order, e.g. Value Added Tax at the standard rate is applicable for all items. 0170 MOA, Monetary amount A segment specifying the amount for the identified tax/fee. 0180 LOC, Place/location identification A segment indicating the location to which the tax or exemption specified in the TAX segment applies, e.g. city or state or country. 0190 Segment group 4: CUX-DTM A group of segments specifying the currencies and related dates/times/period valid for the whole request for quotation. Currency data may be omitted in national applications but will be required for international transactions. 0200 CUX, Currencies A segment identifying the currencies required in the request for quotation. A rate of exchange may be given to convert a reference currency into a target currency. 0210 DTM, Date/time/period A segment specifying the date/time/period related to the rate of exchange. 0220 Segment group 5: PYT-DTM-PCD-MOA A group of segments specifying the terms of payment applicable for the whole order. 0230 PYT, Payment terms A segment identifying the payment terms and date/time basis. 0240 DTM, Date/time/period A segment giving the specific date/time/period, if needed, of any payments, discounts, instalments etc. 0250 PCD, Percentage details A segment specifying the discount, interest, penalty as well as instalment percentage. 0260 MOA, Monetary amount A segment specifying amounts related to payment discounts, penalties or instalments. 0270 Segment group 6: TOD-LOC A group of segments indicating the terms of delivery for the whole order. 0280 TOD, Terms of delivery or transport A segment identifying the delivery terms to be used. e.g. UN INCOTERMS code could be used to specify the delivery terms. 0290 LOC, Place/location identification A segment identifying locations relevant to the delivery