| Version: | D |
|---|---|
| Release: | 99B |
| Contr. Agency: | UN |
| Revision: | 1 |
| Date: | 1999-09-11 |
| SOURCE: | Pan American EDIFACT Board - JM10 |
|
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 |
|
This message also occurs in the following versions of this standard: D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Travel, tourism and leisure product application status request - interactive message (PASREQ) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The Travel, tourism and leisure product application status request message is sent by either a service supplier to a product supplier to ask if the application or product is available for request or by a product supplier to a service supplier to notify them that they will not be receiving requests during a specified time period.
The Travel, tourism and leisure product application status 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.
PASREQ may be used for the following functions that facilitate the operation of the interactive scenario for travel, tourism and leisure:
(1) to ask the supplier of a service or product if the application is available for requests. The request may specify an application, a message type, a scenario, and a dialogue type.
(2) to notify a service supplier, such as a travel agent system, that they will not be taking requests for a specific application(s), message type, scenario, or dialogue type, or from specific agents based on location.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Travel, tourism and leisure product application status request - interactive message is PASREQ.
Note: Travel, tourism and leisure product application status request - interactive messages conforming to this document must contain the following data in segment UIH, composite S306:
| Data element | 0065 | PASREQ |
| 0052 | D | |
| 0054 | 99B | |
| 0051 | UN |
A segment providing data pertaining to the originator of the interactive request (e.g., travel agent identity and location and the commercial computer reservations system delivering the message).
A group of segments to specify the message application information and effective dates and times.
A segment to specify the action to be taken, the message, scenario, and dialogue affected, and the supplier of the product.
A segment to specify start and stop dates and times for the action.
A group of segments to specify the products that are affected by the action and the related effective dates and times.
A segment to identify the products or services that are affected.
A segment to specify the start and stop dates and times for the action.
A group of segments to specify the travel agencies and locations that might be affected by the action and the effective dates.
A segment to specify the travel agencies by identification numbers and the locations that are affected.
A segment to specify the start and stop dates and times for the action for specific agencies and locations.
A group of segments to identify the product or service and the start and stop date and time.
A segment to identify the product or service that is affected for the point of sale information.
A segment to specify the start and stop dates and times.
A service segment ending a message, giving the total number of segments in the message (including the UIH & UIT) and the control reference number of the message.
| DTI | Date and time information | |
| MAP | Message application product information | |
| ORG | Originator of request details | |
| POS | Point of sale information | |
| TVL | Travel product information | |
| UIH | Interactive message header | |
| UIT | Interactive message trailer |
| ├─UIH Interactive message header | ×1 | (M) |
| ├─ORG Originator of request details | ×1 | (C) |
| ├─Segment Group 1 | ×2 | (M) |
| │─├─MAP Message application product information | ×1 | (M) |
| │─├─DTI Date and time information | ×1 | (C) |
| │─├─Segment Group 2 | ×999 | (C) |
| │─│─├─TVL Travel product information | ×1 | (M) |
| │─│─└─DTI Date and time information | ×1 | (C) |
| │─└─Segment Group 3 | ×999 | (C) |
| │───├─POS Point of sale information | ×1 | (M) |
| │───├─DTI Date and time information | ×1 | (C) |
| │───└─Segment Group 4 | ×999 | (C) |
| │─────├─TVL Travel product information | ×1 | (M) |
| │─────└─DTI Date and time information | ×1 | (C) |
| └─UIT Interactive message trailer | ×1 | (M) |