Task: Flight Service

This task provides flight information including the elapsed flying time, meal service, terminal information, electronic ticketing, change of gauge, charter flight and affiliated carrier information, plus in-flight service, traffic restriction, passenger check-in and comment 201/507 information.

Section 1: Short Answer

Transaction Name: 

FlightService_6_0

Can any other transaction(s) perform this same task?

No, the combination of information provided by this transaction is unique to this transaction.

Can this task be performed in a sessionless environment?

Yes

Are the request and response identical on both the Apollo and Galileo systems?

Yes, both the request and response are identical on both systems.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

None.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

None.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

Prerequisite tasks:

This task may be carried out either from an Availability entry or from a PNR (Booking) entry.

You need to know the following before this this task:

Expected response:

Request record = <InFltServiceReq>

Response records = <FltData>, <InFltLegData>, <InFltServiceCode>, <InFltCodeShare>, <PassengerCheckIn>, <TrafficRestriction>, and <CommentInfo>

The <FltData> and at least one <InFltLegData> will always be returned.  The others may or may not be returned, depending upon the presence or absence of the associated information.  

Error and warning responses:

The error responses include the following:

'SERVICE DATA NOT AVAILABLE'

‘INVLD FORMAT'

‘CK SGMT NBR'

‘INVLD AIR SGMT'

‘NO ACTIVE SGMTS'

‘SEG NOT ACTIVE'

‘NEED AVAILABILITY DISPLAY'

‘CHECK FORMAT'

‘CHECK LINE NUMBER'

‘CHECK CLASS'

‘INVLD CITY'

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<InFltServiceMods>

Terminal Equivalents:

Apollo
*SVC

Galileo
*SVC

Ordering

KLR

Min/Max

XML Tag

 

AAI4

1-
Theoretical max limit of 150. Limit is based on size of segment.

<InFltServiceReq>

 

Response (Output) Tags

<InFltService>

 

Ordering

KLR

Min/Max

XML Tag

 

AAI5

1-13

<FltData>

 

AAI6

1 per leg (observed max = 23)

<InFltLegData>

 

AAI7

1-13

<InFltServiceCode>

 

AAI8

0-1 (per leg/segment)

<InFltCodeShare>

 

AAI9

0-1 (per leg/segment)

<PassengerCheckIn>

 

AAIA

0-1 (per leg/segment)

<TrafficRestriction>

 

AAIB

0-1 (per leg/segment)

<CommentInfo>

 

Related Samples

FlightService_6_0_1

FlightService_6_0_2