Requotes fare based on current itinerary and modifiers.
Transaction Name:
DocProdFareRequote_7
Can any other transaction(s) perform this same task?
No, only DocProdFareRequote_7 can perform this task.
Can this task be performed in a sessionless environment?
No. A PNR/booking file must exist. A fare must exist.
Are the request and response identical on both the Apollo and Galileo systems?
This task is available on Apollo only.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
None
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Request:
Prerequisite tasks:
Expected response:
The response <UpdateModifiers> will include <FareNumInfo> and <DPOK>.
Error and warning responses:
If there is an error, it is sent back in <ErrText> in the <UpdateModifiers> response.
When trying to requote a fare and the host has a problem (for this example, the third fare was requoted for a segment that does not exist), the user will get the following response:
Unable to process Stored Fare 3. The Host has returned the following error:
UNABLE TO UPDATE FARE
Follow-on requests:
None.
<DocProdFareRequoteMods> |
Terminal Equivalents: |
Apollo |
Galileo |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
REQUIRED |
DPFI |
1-1 |
<FareNumInfo> |
||||
<DocProdFareRequote> |
|
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
DPFI |
1-1 |
<FareNumInfo> |
||
|
|
DPOK |
0-1 |
<DPOK> |
||
<UpdateModifiers> |
|
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
DPFI |
1-1 |
<FareNumInfo> |
||
|
|
EROR |
0-1 |
<ErrText> |
||