972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Travel and tourism

TUPRSP Travel, tourism and leisure data update response

The UN/EDIFACT interactive message a global distribution system sends to respond to a supplier's data update request.

Sent by
Global distribution system (GDS), or a supplier
Received by
Supplier, or a GDS
Standard
UN/EDIFACT · Interactive (I-EDI) message
X12 equivalent
No direct equivalent

What is the EDIFACT TUPRSP message?

TUPRSP is the UN/EDIFACT interactive travel, tourism and leisure data update response. The directory defines it as a message sent by a global distribution system to respond to a TUPREQ sent by a supplier to update rates, availability, policy or general information. It may also be sent by a supplier in the reverse exchange.

The response confirms that the update was applied or reports why it was rejected. Suppliers rely on it to know that the content agents see matches their own systems.

How the EDIFACT TUPRSP message worksDiagram of the UN/EDIFACT TUPRSP Travel, tourism and leisure data update response message. Global distribution system (GDS), or a supplier sends it to supplier, or a GDS. It usually follows TUPREQ. Inside the UIB and UIH envelopes, the directory D.21A requires, in the start of message: MSD (Message action details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT TUPRSP message worksTravel, tourism and leisure data update response: who sends it, where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSTUPREQTravel, tourism andleisure data updaterequestTUPRSPSENDERGlobal distributionsystem (GDS), or asupplierRECEIVERSupplier, or a GDSUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInteractive interchangeUIB … UIZMessage TUPRSPUIH … UITSTART OF MESSAGEMSDMessage action detailsBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:ERITVLMAPITDALSTIFBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for TUPRSP. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT TUPRSP message worksDiagram of the UN/EDIFACT TUPRSP Travel, tourism and leisure data update response message. Global distribution system (GDS), or a supplier sends it to supplier, or a GDS. It usually follows TUPREQ. Inside the UIB and UIH envelopes, the directory D.21A requires, in the start of message: MSD (Message action details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT TUPRSPmessage worksTravel, tourism and leisure data updateresponse: who sends it, where it fits and whatthe directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSTUPREQTravel, tourism and leisure dataupdate requestTUPRSPSENDERGlobaldistributionsystem (GDS),or a supplierRECEIVERSupplier, or aGDSUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInteractive interchange (UIB … UIZ)Message TUPRSP (UIH … UIT)START OF MESSAGEMSDMessage action detailsBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:ERITVLMAPITDALSTIFBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for TUPRSP.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends TUPRSP, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around TUPRSP and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Confirming applied rate or availability updates
  • Reporting rejected updates with reasons
  • Answering update requests in the reverse direction

Where it fits in the message flow

Usually follows TUPREQ Travel, tourism and leisure data update request
This message TUPRSP Travel, tourism and leisure data update response

Structure

Mandatory segments in TUPRSP (directory D.21A)

In UN/EDIFACT directory D.21A, the TUPRSP message has 166 segment positions arranged in 48 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes. This structure comes from one published copy of the directory and has not been independently verified: confirm it before you build a map.

  • UIH
  • MSD
  • UIT

Practical example

TUPRSP in practice

A GDS receives a supplier's TUPREQ with rate updates for 40 properties. It applies 39 and rejects one because the property code is unknown. It returns a TUPRSP confirming the 39 and reporting the error, and the supplier corrects the property mapping.

Implementation

Implementation considerations for TUPRSP

  • Report errors precisely so suppliers can correct them.
  • Reference the update request exactly as received.
  • Respond within the timeout the supplier's system allows.
  • Monitor rejected updates, which leave content out of date.

How ECOM helps

Automate TUPRSP with ECOM

Industry

Hospitality

Procurement, invoicing and supplier integration for hotels, restaurant groups and foodservice suppliers.

Solution

Batch and Real-Time Integration

Scheduled batch processing and real-time, API-driven integration on one platform.

Solution

API Integration

Connect partner and application APIs to your systems and bridge them with EDI processes.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related travel and tourism messages

All 16 travel and tourism messages

Need help with TUPRSP?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us