United Nations Directories
for Electronic Data Interchange for
Administration, Commerce and Transport
Message Type : TUPREQ Version : D Release : 09A Contr. Agency: UN Revision : 2 Date : 2009-12-16 SOURCE: TBG9 Travel, Tourism and Leisure CONTENTS Travel, tourism and leisure data update request - interactive 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.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 Travel, tourism and leisure data update request - interactive message (TUPREQ) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE 1.1 Functional definition An interactive Travel, tourism and leisure data update request is sent by a supplier of a product or service to a global distribution system (GDS) to update the receiverís data base for rates, availability, policy, and general information. It may also be used to initialize the receiverís system with a new product or service. The message may also be sent by a GDS to a supplier when a travel agent has made updates to a travellerís profile or a GDS needs to update an agencyís profile. 1.2 Field of application The Travel, tourism and leisure data update request - interactive 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 TUPREQ may be used for the following types of updates: (1) Update availability in the GDS system. May be sent when a single product is no longer available or may be a weekly or monthly update of availability for all services and products. (2) Update rates in the GDS system. (3) Update policy or general information or a corporate account profile in the GDS system. This information may be at chain code or vendor level or for a specific product location. (4) Initialize a new product or service in the GDS system. (5) Update an agency or traveller profile in the supplier system. The message is made up of five distinct groups for updating the information listed above. The information shown in items 1-3 can be sent as individual messages or a combination of the three groups can be sent in one message to the GDS. The data to initialize a new product or service or the update to an agency or traveller profile can not be sent with any other update. The message has the capability to tie an identification number to an individual update for purposes of reporting errors in TUPRSP, Travel, tourism, and leisure update response message. The sending of TUPREQ may be preceded by the sending of the Travel, tourism and leisure product application status request and response messages (PASREQ/PASRSP). In this scenario a supplier would send PASREQ to a GDS to indicate what type of update is to be made and the number of records to be sent. The GDS would respond with the PASRSP to indicate if they can accept the update now or if it should be sent at a later date and what that date and time is. The GDS may also respond with how many records can be sent in one message. The supplier would then send TUPREQ at the specified time to update the GDS data base. 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. 0010 UIH, Interactive message header A service segment starting and uniquely identifying a message. The message type code for the Travel, tourism and leisure data update request - interactive message is TUPREQ. Note: Travel, tourism and leisure data update request - interactive messages conforming to this document must contain the following data in segment UIH, composite S306: Data element 0065 TUPREQ 0052 D 0054 09A 0051 UN 0020 MSD, Message action details A segment identifying the industry type (e.g. air, car, train, accommodations, etc.) and what type of data update is to be done (e.g. availability, rates, etc.). 0030 ORG, Originator of request details A segment providing data pertaining to the originator of the interactive request. 0040 NUN, Number of units A segment to indicate how many updates are being sent or are to be sent in the update. 0050 Segment group 1: TVL-ITM-SG2 A group of segments for updating availability information based on location information. 0060 TVL, Travel product information To specify a rental car location or a hotel property. 0070 ITM, Item number To specify an item number for this rental car location or hotel property. 0080 Segment group 2: DTI-ITM-NUN-SG3-SG5 A group of segments to specify the applicable dates, number of days, the availability status code, and rate code information. 0090 DTI, Date and time information To specify the begin and/or end date(s) and times for an availability period. 0100 ITM, Item number An item number associated with a date range. 0110 NUN, Number of units The minimum number of nights for a hotel stay. 0120 Segment group 3: RPI-SG4 A group of segments to specify availability status codes and the associated rate codes and categories. 0130 RPI, Quantity and action details To specify the availability status codes such as open, waitlisted, and on request. 0140 Segment group 4: RTC-SDT-PRD-TFF A group of segments to specify a rate code, the rate category, and room type. 0150 RTC, Rate types A segment to specify a rate code. 0160 SDT, Selection details A segment to indicate if the rate code is included or excluded from the availability status. 0170 PRD, Product identification The room types that are applicable for a rate code. 0180 TFF, Tariff information The rate category associated with the rate code. 0190 Segment group 5: PDT-ITM-TFF-RTC-POS-RPI A group of segments to specify availability based on the product code which includes yield level and car type and the associated rate category, rate plans, and rate types. 0200 PDT, Product information A segment to specify the product code. 0210 ITM, Item number A segment to specify an item number associated to the product code. 0220 TFF, Tariff information A segment to specify the rate category and rate plan. 0230 RTC, Rate types A segment to specify the rate codes. 0240 POS, Point of sale information A segment to specify agents either by agency identification or locations for whom the availability applies. 0250 RPI, Quantity and action details To specify the availability status codes such as open, waitlisted, and on request. 0260 Segment group 6: MAP-SG7 A group of segments for updating supplier rates in another system. 0270 MAP, Message application product information A segment to specify the type of action, add, delete, or replace. 0280 Segment group 7: TVL-ITM-DTI-SG8-SG12 A group of segments detailing all the applicable rate information. 0290 TVL, Travel product information A segment to identify the product by either location or product identification for which the rate applies. 0300 ITM, Item number An item number associated to the product.