Task: Cancel Stored Fare

This task enables the user to cancels stored fares.

Note: The DocProdFareManipulation_8 task of canceling a stored fare is similar to FareQuoteCancel_6_0. However, DocProdFareManipulation_8 uses KLRs, while FareQuoteCancel_6_0 uses NWBs. DocProdFareManipulation_8 also supports the FX1P1 (cancel passenger 1 from fare 1) format while FareQuoteCancel_6_0 does not.

DocProdFareManipulation_8 is recommended to perform a Cancel Stored Fare task, unless you are an existing customer that already uses FareQuoteCancel_6_0. Galileo provides new functionality through KLRs rather than through NWBs.

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_8

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

Only DocProdFareManipulation_5 and _6 can perform this task.

Can this task be performed in a sessionless environment?

No. A PNR/BF must exist. A fare must exist.

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

They are the same on Apollo and Galileo.

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

You cannot cancel ticketed fares on Galileo.

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

A fare must exist.
A PNR/BF must exist.
The task is available through structured data and Focalpoint (terminal emulation).
You can cancel selected fares.

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:

1. Create the PNR/booking file with a fare.

2. Send the fare number in the <FareNumInfo>.

3. Send the <FareNumInfo> to cancel the fare.

Prerequisite tasks:

A fare must exist.
A PNR/BF must exist.

Expected response:

The <CancelStoredFare> response (4021) will include the <FareNumInfo> (KLR DPFI) fare number and <DPOK> (KLR DPOK).

Error and warning responses:

If there is an error, it is sent back in the <ErrText> (KLR EROR) in the <CancelStoredFare> (4021) response.

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<CancelStoredFareMods>		Terminal Equivalents:			Apollo: XT		Galileo: FX
	Ordering		KLR	Min/Max		XML Tag
	A		DPFI	1 - 1		<FareNumInfo>

Response (Output) Tags

<CancelStoredFare>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1 - 1	<FareNumInfo>
	B	DPOK	1 - 1	<DPOK>

<CancelStoredFare>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1 - 1	<FareNumInfo>
	B	EROR	1 - 1	<ErrText>

Related Samples

DocProdFareManipulation_8_s2

DocProdFareManipulation_8_s3