Task: Fare Quote Verify

This task is used to verify a stored price. It re-prices an itinerary after the itinerary has been changed (since the previous stored price) and confirms whether the stored price is still valid. Then, it stores the changed price in the PNR/BF.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_7_8

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

The PNRBFBuildModify_7_7_1 and FareQuoteVerify_6_0 transaction can perform this same task.

Can this task be performed in a sessionless environment?

No.

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.

• A user must understand the fare quote process.
• To receive web/private fares, a user must know the Pseudo City Code under which the fare was filed.
• A user must know valid passenger types.

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

Not applicable.

Section 2: Detailed Description

Request:

The user must send in a <FareQuoteVerifyMods> (1410 6.0). Additionally, the user could send in a <BeginTransMods> (2028 5.0) to open the PNR/BF if it is not already open.

Prerequisite tasks:

To use this task, the user must be using a record which has a stored fare (PNR in the AAA). Verification can only be performed on a retrieved PNR/BF in which the fare has already been stored, such as with FareQuoteStorePrice_8_0. To ensure the updated information is saved, finish with the PNRBFEnd_9_0 transaction.

Expected response:

The response is a <FareQuoteVerify> (1411 6.0).

Error and warning responses:

Not available.

Follow-on requests:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags