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.
Transaction Name:
PNRBFManagement_11
Can any other transaction(s) perform this same task?
Previous versions of PNRBFManagement, PNRBFBuildModify_7_7_1, FareQuoteReprice_6_0, and DocProdFareManipulation.
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.
Request:
A <FareQuoteRepriceMods> element must be sent in the request. An <AssumedPointMods> element can also be sent to change the assumed city, if necessary.
Prerequisite tasks:
To retain the stored price when a change is made to the PNR/BF, there must be an existing PNR/BF with a stored price. When a change is made to the itinerary section of the PNR/B, this client is prompted to retain or verify the stored price.
Expected response:
The response <FareQuoteReprice> element returns with no data, even thought the stored fare is put into reprice status. The client must retrieve the PNR/BF or use the PNRBFManagement transaction to view the data.
Error and warning responses:
Not available.
Follow-on requests:
There are no follow on requests.
|
<FareQuoteRepriceMods> |
Terminal Equivalents: |
Apollo: T:R |
Galileo: |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
1412 |
1 – 1 |
<FareQuoteRepriceMods> |
|
<AssumedPtMods> |
Terminal Equivalents: |
Apollo: |
Galileo: |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
1440 |
0 – 1 |
<AssumedPtMods> |
|
<FareQuoteReprice> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
1413 |
1-1 |
<FareQuoteReprice> |
|
<AssumedPt> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
1441 |
0-1 |
<AssumedPt> - No data is returned. |