Task: Retain a Previously Stored Fare and Set the Status to REPR

This task sets the status of an existing stored fare to reprice, but retains the existing stored fare in the PNR/BF. The itinerary needs to be re-priced before a ticket can be issued.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_7_12

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

The PNRBFManagement_7_8, 9, and 11, PNRBFBuildModify_7_7_1, DocProdFareManipulation_4_0, 4_1, and 4_2, and the FareQuoteReprice_6_0 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.

Not applicable.

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 a <FareQuoteRepriceMods> (1412 6.0) request. The user can additionally send an <AssumedPointMods> tag to change the assumed city, if necessary.

Prerequisite tasks:

There must be an existing PNR/BF with a stored price if you want to retain the stored price when a change has been made to the PNR. When a change is made to the itinerary section of the PNR, you are prompted to retain or verify the stored price.

Expected response:

The response <FareQuoteReprice> tag returns with no data, even thought the stored fare is put into re-price status. You must retrieve the PNR or use the PNRBFManagement_7_12 transaction to view the data.

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_7_12_11