Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D01C Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Travel, tourism and leisure product application status request - interactive message

Message Type:PASREQ
Version:D
Release:01C
Contr. Agency:UN
Revision:2
Date:2001-11-07
SOURCE:D10 Travel, Tourism and Leisure (SWG)

CONTENTS
Travel, tourism and leisure product application status request - interactive message 0. INTRODUCTION
  1. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  2. REFERENCES
  3. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  4. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      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


This message also occurs in the following versions of this standard:
D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

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.


1. SCOPE


1.1. Functional definition

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.


1.2. Field of application

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.


1.3. Principles

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.

(3) to ask the service supplier, such as a travel agent system, if they can send a message to update their 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 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 element0065PASREQ
0052D
005401C
0051UN

0020 ORG, Originator of request details

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).

0030 Segment Group 1: MAP-DTI-NUN-SG2-SG3

A group of segments to specify the message application information and effective dates and times.

0040 MAP, Message application product information

A segment to specify the action to be taken, the message, scenario, and dialogue affected, and the supplier of the product.

0050 DTI, Date and time information

A segment to specify start and stop dates and times for the action.

0060 NUN, Number of units

A segment to indicate the number of records or messages that a supplier has to send in a data base update message.

0070 Segment Group 2: TVL-DTI

A group of segments to specify the products that are affected by the action and the related effective dates and times.

0080 TVL, Travel product information

A segment to identify the products or services that are affected.

0090 DTI, Date and time information

A segment to specify the start and stop dates and times for the action.

0100 Segment Group 3: POS-DTI-SG4

A group of segments to specify the travel agencies and locations that might be affected by the action and the effective dates.

0110 POS, Point of sale information

A segment to specify the travel agencies by identification numbers and the locations that are affected.

0120 DTI, Date and time information

A segment to specify the start and stop dates and times for the action for specific agencies and locations.

0130 Segment Group 4: TVL-DTI

A group of segments to identify the product or service and the start and stop date and time.

0140 TVL, Travel product information

A segment to identify the product or service that is affected for the point of sale information.

0150 DTI, Date and time information

A segment to specify the start and stop dates and times.

0160 UIT, Interactive message trailer

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.


4.2. Segment index (alphabetical sequence by tag)

DTI Date and time information
MAP Message application product information
NUN Number of units
ORG Originator of request details
POS Point of sale information
TVL Travel product information
UIH Interactive message header
UIT Interactive message trailer

4.3. Message structure


4.3.1. Segment table

├─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)
├─NUN Number of units ×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)

Return to Stylus Studio EDIFACT D01C Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.