Updates a specific stored fare within the itinerary, such that a new or different commission rate will be applied.
Transaction Name:
DocProdFareRequote_5
Can any other transaction(s) perform this same task?
No, only DocProdFareRequote_5 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?
They are the same on Apollo and Galileo.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
The user can enter the commission by amount or percentage.
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 the <FareNumInfo> and <DPOK>.
Error and warning responses:
If there is an error, it is sent back in <ErrText> in the <UpdateModifiers> response.
The commission amount modifier (ZA) is BSP specific. If the commission amount modifier (ZA) is used for a BSP that does not allow the modifier, the following error will display.
|
Error Message |
Reason for Error |
|
ERROR 8549 – ZA INVALID MODIFIER |
Commission by amount not available for BSP. |
Follow-on requests:
None.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo |
Galileo |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
REQUIRED |
DPFI |
1-1 |
<FareNumInfo> |
||||
|
|
DP1 |
1-1 |
<CommissionMod> |
||||
|
<UpdateModifiers> |
|
|
||||
|
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> |
||