Requotes fare based on current itinerary and modifiers.
Transaction Name:
DocProdFareRequote_1_0
Can any other transaction(s) perform this same task?
No, only DocProdFareRequote_1_0 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:
Unless otherwise specified, use ALL CAPS in any request data.
Following are the steps required to carry out this task:
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.
The following error messages are returned from Category 35 fares:
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> |
||