The task is used to denote that all programmatic endorsement (auto and system generated) are overridden except the manual endorsements, if entered.
Transaction Name:
DocProdFareRequote_5
Can any other transaction(s) perform this same task?
No.
Can this task be performed in a sessionless environment?
No. A Booking File / PNR is required.
Are the request and response identical on both the Apollo and Galileo systems?
This is only on the Apollo (1V) CRS.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Knowledge of Ticketing, Reservations and Fare Quote.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
N/A
Request:
Unless otherwise specified, use ALL CAPS in any request data.
The following steps are required to carry out this task:
Create a Booking File.
Send the fare number in the <FareNumInfo> element.
Send the Auto Endorsement Override modifier <ProgEndorsement> element.
Prerequisite tasks:
Expected response:
The <UpdateModifiers> includes the <FareNumInfo> and <DPOK> elements.
Error and warning responses:
Errors are returned in the <Ticketing> response, in the <ErrText> element.
Follow-on requests:
N/A
See the Follow-on Request in the tables in section 3.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo Pxxxx| Dddmmmyyyy |
Galileo: N/A |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
A |
DPFI |
1-1 |
<FareNumInfo> |
|
B |
DP58 |
0-1 |
<ProgEndorsement> |
| <UpdateModifiers> | ||||||
| Ordering | KLR | Min/Max | XML Tag | |||
| A | DPFI | 1-1 | <FareNumInfo> | |||
| B | DPOK | 1-1 | <DPOK> | |||
|
<UpdateModifiers> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
DPFI |
1-1 |
<FareNumInfo> |
||
|
B |
EROR |
1-1 |
<ErrText> |
||