Task: E-Ticket Retrieval

Section 1: Short Answer

Transaction Name:

ETicketRetrieval_1_0

Can this task be performed in a sessionless environment?

This task can be used in a sessioned or sessionless environment. See Additional Information for further details.

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

Yes.

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

Knowledge of ticketing and pricing is required to understand this task.

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.

The <EticketRetrievalMods> (4090 1.0) is used to request retrieval of an E-Ticket. The <TicketNumber> tag is sent with the ticket number to retrieve the PNR.

Prerequisite tasks:

In order to display an electronic ticket, the AAA must be initialized to the PCC of the issuing agency.

Expected response:

If the E-Ticket Retrieval transaction completes successfully, the <ETicketNum>, <AssocPsgrs>, <AirSegInfo>, <FareConstruction>, <PsgrFacilityCharge>, <GenQuoteDetails>, <PassengerInfo>, <OriginationData>, <Commission>, <FreeText>, and <CreditCardFOP>/<CheckFOP>/<OtherFOP> tags are returned with the original E-Ticket data.

Error and warning responses:

If the E-Ticket Retrieval transaction encounters an error, the error message is returned in the <ErrText> tag. The following error messages may be received:

501: Failure. Convert KLR to XML. OSTPFA

503: Failure. Convert XML to KLR. OSTPFA

600: Failure. General Error. OSWS

601: Failure. Invalid Service Request. OSWS

602: Failure. Input Transcoder conversion. OSWS

603: Failure. Output Transcoder conversion. OSWS

700: Failure. General Error. OSV

708: Failure. No Ticket Fare Construction. OSV

713: Failure. Fare quote acceptance time has expired. OSV

714: Failure. Unable to locate prior transaction. OSV

800: Failure. General Error. OSNI

801: Failure. Input Transcoder conversion. OSNI

802: Failure. Send to vendor (1N) error. OSNI

803: Failure. Receive from vendor (1N) error. OSNI

804: Failure. Output Transcoder conversion. OSNI

1000: Failure. General Error. 1N

1001: Failure. Invalid input data. 1N7

1004: Failure. This ticket is out of date. 1N

1015: Failure. Ticket fully used. 1N

1019: Failure. New-Old match exactly. No exchange. 1N

0: Informational. Upgraded Fare. 1N

1024: Failure. Ticket is Unknown. 1N

1025: Failure. Ticket is voided. 1N

1100: Failure. Input Transcoder conversion. OSHAS

1101: Failure. Unable to connect to host access servers. OSHAS

1102: Failure. Error returned from host access servers. OSHAS

1103: Failure. Output Transcoder conversion. OSHAS

1200: Failure. General Error. OSDS

1201: Failure. Database connection error. OSDS

1202: Failure. Reference data not available. OSDS

1205: Failure. Unable to read transaction. OSDS

Follow-on requests:

No follow-on requests exist.

Section 3: Tables

Request (Input) Tags

<EticketRetrievalMods>

Terminal Equivalents:

Apollo: *TE/ticketnumber

Galileo: *TE/ticketnumber

	Ordering	KLR	Min/Max	XML Tag
	Required	DPT1	1-1	<TicketNumber>

Response (Output) Tags - Successful Response

<EticketRetrieval>

Ordering	KLR	Min/Max	XML Tag
Required	DPHT	1–1	<ETicketNum>
	DPPI	1–1	<AssocPsgrs>
	DPSS	1–many	<AirSegInfo>
	GFFC	1-1	<FareConstruction>
	GFPF	1-1	<PsgrFacilityCharge>
	GFGQ	1-1	<GenQuoteDetails>
	DPNM	1-1	<PassengerInfo>
	DPOR	1-1	<OriginationData>
	DPCM	1-1	<Commission>
	DP33	0-1	<TourCode>
	DPP0	0-1	<CreditCardFOP>
	DPP1	0-1	<CheckFOP>
	DPP9	0-1	<OtherFOP>
	DPIF	0-many	<FreeText>

Response (Output) Tags - Unsuccessful Response

<EticketRetrieval>

	Ordering	KLR	Min/Max	XML Tag
		EROR	0–1	<ErrText>

Additional Information

To use ETicketRetrieval_1_0, it is not necessarily required to have a session open. The host system Agent Assembly Area (AAA) must be associated with a Pseudo City Code (PCC) in order for the retrieval request to function properly. This implies that a session is based on the Galileo Terminal IDs (GTIDs) AAA Initialization Table (UAT) configuration. However:

If a GTIDs UAT is not associated with a PCC, the AAA will not be associated with a PCC by default.
In this case, you are required to begin a session and emulate into a PCC to enable the ticket retrieval request functionality.
If a GTIDs UAT is associated with a PCC then the AAA will be associated with a PCC by default.
In this case, you are not required to emulate, and therefore are not required to begin a session.

Currently ETracker’s master GTIDs UAT is configured such that the AAA is associated with a PCC. Therefore as currently configured, ETracker is not required to begin a session.

Related Samples

ETicketRetrieval_1_0_1