Frames | No Frames

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

Schedule request - interactive message

Message Type:SKDREQ
Version:D
Release:02B
Contr. Agency:UN
Revision:1
Date:2003-02-13
SOURCE:D10 Travel, Tourism and Leisure (SWG)

CONTENTS
Schedule request - interactive message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
    2. Message terms and definitions
  5. 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:
D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Schedule request - interactive message (SKDREQ) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional definition

The message is used to request travel service schedule update information aimed to update the schedule data base of the requester. It allows to the specification of selection criteria for the requested information.


1.2. Field of application

The Schedule 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

  • A schedule request is sent to a travel service provider by an other service provider or by an agency in order to obtain travel schedule information for the update of the senders' schedule database. The sender can add selection criteria to specify the scope of requested data.
  • The interactive message SKDUPD (Schedule update - interactive message) and / or TSDUPD (Timetable static data update - interactive message) are utilised to provide a response to the schedule request.
  • A schedule request may also be used to formulate a request for re-transmission of the data in case of error.

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.


3.2. Message terms and definitions

See UNTDID, Part 4, Chapter 2.6 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 Schedule request - interactive message is SKDREQ.

Note: Schedule request - interactive messages conforming to this document must contain the following data in segment UIH, composite S306:

Data element0065SKDREQ
0052D
005402B
0051UN

0020 MSD, Message action details

A segment to specify the type and business function of the message.

0030 ORG, Originator of request details

A segment to specify details related to the originator of the schedule update

0040 HDR, Header information

A segment to specify information applicable to the entire message.

0050 POP, Period of operation

A segment to specify a period of operation of the service.

0060 ODI, Origin and destination details

A segment to specify the origin and destination locations of a service leg or segment.

0070 Segment Group 1: RFR-LKP

A group of segments to specify selection criteria.

0080 RFR, Reference

A segment to specify a reference to one of the elements of the selection criteria.

0090 LKP, Level indication

A segment to specify the hierarchical order of the occurrence of the segment group.

0100 Segment Group 2: ERI-RFR-IFT

A group of segments to specify an error condition

0110 ERI, Application error information

A segment to specify the type of application error

0120 RFR, Reference

A segment to reference the erroneous element.

0130 IFT, Interactive free text

A segment to provide text related to the error.

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

ERI Application error information
HDR Header information
IFT Interactive free text
LKP Level indication
MSD Message action details
ODI Origin and destination details
ORG Originator of request details
POP Period of operation
RFR Reference
UIH Interactive message header
UIT Interactive message trailer

4.3. Message structure


4.3.1. Segment table

├─UIH Interactive message header ×1 (M)
├─MSD Message action details ×1 (M)
├─ORG Originator of request details ×1 (M)
├─HDR Header information ×1 (C)
├─POP Period of operation ×1 (C)
├─ODI Origin and destination details ×99 (C)
├─Segment Group 1 ×99 (C)
├─RFR Reference ×1 (M)
└─LKP Level indication ×1 (C)
├─Segment Group 2 ×99 (C)
├─ERI Application error information ×1 (M)
├─RFR Reference ×1 (C)
└─IFT Interactive free text ×1 (C)
└─UIT Interactive message trailer ×1 (M)

Return to Stylus Studio EDIFACT D02B 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 Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
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-2011 All Rights Reserved.