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_15

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

Previous versions of PNRBFManagement, 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:

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

<FareQuoteVerifyMods> (1410) must be sent in the request. Additionally, a <BeginTransMods> element (2028) can be sent using FareQuoteVerify_6_0, to open the PNR/BF if it is not already open.

Prerequisite tasks:

This task requires a record that has a stored fare (PNF/BF in the AAA). Verification can only be performed on a retrieved PNR/BF where the fare has already been stored, such as with the task Fare Quote Store Price. To ensure the updated information is saved, finish with the task Finish Active PNR/BF.

Expected response:

The response is a <FareQuoteVerify> (1411).

Error and warning responses:

Not available.

Follow-on requests:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

PNRBFManagement_15_s15