Task: Exchange Ticket

The task exchanges a ticket for a PNR/BF with Filed Fares.

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_23

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

No other transaction can perform this task.

Can this task be performed in a sessionless environment?

No. An PNR/BF with a Filed Fare is required. This task requires several steps to complete.

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

This process is similar for Apollo and Galileo. However, there are some differences, mostly because of the various terminal functionality existing on each GDS. For example, on Galileo system only eight paid taxes can be used, but on the Apollo system, there are three for the USA and up to twenty in Canada.

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

Knowledge of ticketing, fares, and reservations is required.

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

There are no special limitations.

Section 2: Detailed Description

Request:

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

Following are the steps required to carry out this task:

Attach Ticket Printer with the pseudo.
Create a Booking File / PNR with fares:
- The <TicketingMods> (DR 4032) must be used.
  - The <TicketingControl> is initially sent using the "TK" (Initial ticketing entry) transaction type to request a ticket (see Task Issue Ticket).
  - The <OtherFOP> with FOP id 13 ("exchange") is sent with the ticket number as data – "Additional Data ind" 9.
- The GDS returns <Ticketing> (DR 4033) with <TicketingControl> using "EX" (Exchange) transaction type.
  - See Section 3 for list of elements which can be returned.
  - These elements have the information about the new fare, the old fare, and some other information about original ticket.
Client should return <TicketingMods> with <TicketingControl> using "EX" (Exchange) transaction type with updated elements for exchange. See Section 3 for list of elements which can be sent.

Prerequisite tasks:

Booking file / PNR with Filed fares must be present in AAA.

Must have a Ticket printer attached with the pseudo.

Expected response:

The response <Ticketing> will include the <FareNumInfo> fare number and <TicketingControl> elements. The expected response depends on the stage of exchange transaction (the reply from the GDS depends on result of the calculations for the exchange).

Even Exchange response

If the result is "even exchange:"

The client receives <Ticketing> with regular "ticket issued" response.
<TicketingControl> will have "OK" transaction type.

Additional Collection response

If the result is "additional collection":

The client receives <Ticketing> with regular "multiple receivable" (MR) response. <TicketingControl> will have "MR" transaction type.
The client needs to send <TicketingMods> with "MR" (Multiple Receivable) transaction type in <TicketingControl> and <CreditCardFOP>, <CheckFOP> or <OtherFOP> elements for the Form of Payments used for additional collection amount(s).
On Galileo (1G) if the credit card requires Extra Billing Data (EBD) in response to "MR" the client can receive <Ticketing> with transaction type of "DB" (Detailed Billing Data for Credit Cards) in <TicketingControl> along with a <DetailedBillingMask>.
- In this case Client will need to send <TicketingMods> with transaction type of "DB" in <TicketingControl> along with a <DetailedBillingMask> with extra billing data.
- If there is more than one credit card which requires EBD, the client might receive another <Ticketing> with transaction type of "DB" in <TicketingControl> instead of "ticket issued" response.
The GDS will replies with <Ticketing> with a regular "ticket issued" response. <TicketingControl> will have "OK" (Ticket Issued) transaction type.

Refund Response

If result is "refund" there are several possibilities depending on agency setup:

Cash/Credit Card

If the agency allows refund to cash/credit card to be issued:

The GDS replies with <Ticketing> with transaction type of "ER" (Refund) in <TicketingControl> and options of "cash/credit" in <ExcRefundOptSelection>.

The client must send <TicketingMods> with "ER" transaction type in <TicketingControl> and data for credit card in <ExcRefundOptSelection>, and an option of "Cash" or "Credit" = Y in <ExcRefundOptSelection>. If "Credit" = Y the data for credit card needs to be returned in <ExcRefundOptSelection>.

The GDS returns <Ticketing> with regular "ticket issued" response with transaction type of "OK" in <TicketingControl>.

EMD (Electronic Miscellaneous Document)

If agency allows an EMD to be issued:

The GDS replies with <Ticketing> with transaction type of "ER" in <TicketingControl> and an option of "EMD"=Y in <ExcRefundOptSelection>.

The client needs to send <TicketingMods> with "ER" transaction type in <TicketingControl> and

If option of "EMD" is Y in <ExcRefundOptSelection>:

The GDS returns <Ticketing> with "EM" (EMD Refundable Balance) transaction type in <TicketingControl> and data for EMDRB information in <ExcEMDRBRefundInfo> elements.

The client must send <TicketingMods> with "EM" transaction type in <TicketingControl> and EMD endorsement data in <ExchangeEndorEMDRBRefund>.

If option of "EMD" is N in <ExcRefundOptSelection> a ticket is issued.

The GDS returns <Ticketing> with a regular "ticket issued" response, with a transaction type of "OK" in <TicketingControl>.

If agency doesn"t allow EMD to be issued:

The GDS replies with <Ticketing>, with transaction type of "ER" in <TicketingControl> and an option of "EMD"=N in <ExcRefundOptSelection>.

If the client wants to proceed with exchange, it must send <TicketingMods> with "ER" transaction type in <TicketingControl>:

The GDS returns <Ticketing> with regular "ticket issued" response.

The transaction type of "OK" displays in <TicketingControl>.

If client doesn"t want to proceed with exchange, it will need to send "Ignore" or "Ignore and retrieve" transaction (for example PNRBFManagement with <IgnoreMods>) to cancel the exchange transaction.

At any point Client may cancel the exchange transaction by sending a regular "ignore" transaction (for example PNRBFManagement with <IgnoreMods>).

Error and warning responses:

If there is an error, it is sent back in the <ErrText> in the <Ticketing> response.

Follow-on requests:

The exchange transaction consists of initial request and several follow on responses/requests.

Section 3: Tables

Part 1

Initial Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
HB:FEX<ticket number>

Galileo
TKPFEX<ticket number>

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPEF	1-1	<ElectronicTicketFailed>
D	DPP9	1-1	<OtherFOP>

Initial Response (Output) Tags

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPPI	1-1	<RecordLocator>
	D	DPNM	1-1	<PassengerInfo>
	E	DPXC	1-1	<ExcRefundTktCoupon>
	F	DPXO	1-1	<ExchangeOldFareDataBase>
	G	DPTU	0-1	<TaxInfo>
	H	DPTW	0-1	<TaxBreakDownInfo>
	I	DPXI	1-1	<ExcOrigEchangedInfo>
	J	DPCM	1-1	<Commission>
	K	DPXN	1-1	<ExcNewFareDataBase>
	L	DPTU	0-1	<TaxInfo>
	M	DPTW	0-1	<TaxBreakDownInfo>

Part 2

Exchange Data Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
$EX

Galileo
*EX

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPPI	1-1	<AssocPsgrs>
D	DPNM	1-1	<PassengerInfo>
E	DPXC	1-1	<ExcRefundTktCoupon>
F	DPXO	1-1	< ExchangeOldFareDataBase>
G	DPTU	0-1	<TaxInfo>
H	DPTW	0-1	<TaxBreakDownInfo>
I	DPXI	1-1	<ExcOrigEchangedInfo>
J	DPCM	1-1	<Commission>
K	DPXN	1-1	<ExcNewFareDataBase>
L	DPTU	0-1	<TaxInfo>
M	DPTW	0-1	<TaxBreakDownInfo>
N	DPXL	0-1	<ExchangePenaltyAmt>
O	DPCP	0-1	<CommissionPen>
P	DPXP	0-1	<PenaltyInfo>

Exchange Data Response (Output) Tags for additional collection

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPXA	1-1	<ExchangeAmtInfo>

Error Response

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	0-1	<FareNumInfo>
	B	DPTK	0-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Part 3

Multiple receivable Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
$MR

Galileo
*MR

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPP0	0-3	<CreditCardFOP>
D	DPP1	0-3	<CheckFOP>
E	DPP9	0-3	<OtherFOP>

Multiple receivable Response (Output) Tags

Data Record Format if EBD(DBI) data required for credit card

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPDB	1-1	<DetailedBillingMask>

Error Response

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Part 4

EBD(DBI) data Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
none

Galileo
*DBI

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPDB	1-1	<DetailedBillingMask>

Exchange Data Response (Output) Tags for refund

Format if EBD(DBI) data required for credit card: <Ticketing>

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPXA	1-1	<ExchangeAmtInfo>
	D	DPXS	1-1	<ExcRefundOptSelection>
	E	TEXT	0-1	<TextMsg>

EBD(DBI) data Response (Output) Tags - ERROR

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	EROR	1-1	<ErrText>
	D	DPDB	0-1	<DetailedBillingMask>

Part 5

Cash, Credit Refund Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
$ER

Galileo
*N/A

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPXS	1-1	<ExcRefundOptSelection>

Cash, Credit, EMD Response (Output) Tags - ERROR

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	0-1	<FareNumInfo>
	B	DPTK	0-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Part 6

EMD Refund Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
$ER

Galileo
*ER

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPXS	0-1	<ExcRefundOptSelection>

EMD Response (Output) Tags

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPXA	1-1	<ExchangeAmtInfo>
	D	DPXF	1-1	<ExcEMDRBRefundInfo>
	E	DPXI	1-1	<ExcOrigEchangedInfo>

EMD Response (Output) Tags - ERROR

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Refund/ER Response (Output) Tags - ERROR

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Part 7

EMDRB Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo
$EMRDB

Galileo
*EMRDB

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DPTK	1-1	<TicketingControl>
C	DPXM	0-1	<ExchangeEndorEMDRBRefund>

EMDRB Response (Output) Tags - ERROR

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	0-1	<FareNumInfo>
	B	DPTK	0-1	<TicketingControl>
	C	DPRL	0-1	<RecordLocator>
	D	EROR	1-1	<ErrText>

Part 8

Good Response (Output) Tags

Note: When there was no error on any of steps, then the normal ticket issue will take place:

<Ticketing>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPTK	1-1	<TicketingControl>
	C	TEXT	0-n	<TextMsg>
	D	DPRL	0-1	<RecordLocator>

Related Samples

DocProdFareManipulation_23_s32