Updates a specific stored fare within the itinerary, such that a different plating (override) carrier is used.
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. Fields in the AAT are used to validate the provided carrier code.
Are the request and response identical on both the Apollo and Galileo systems?
Yes, they are the same but error responses can have different message numbers.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
The user must specify the carrier code for the plating carrier (example, United is UA).
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
A booking file must exist.
A fare must exist.
The task is available through structured data and Focalpoint (terminal emulation).
Processing notes for Plating Carrier:
Checks the AUTH field of the AAT record and the Airline Agreement Record to determine if the carrier is valid.
International agencies (I/ in AAT table) must use carrier override when issuing tickets.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
The following steps are required to carry out this task:
Prerequisite tasks:
A booking file/PNR must exist.
A fare must exist.
The plating carrier must exist in the AUTH field of the AAT.
Expected response:
On the host the following checks are made:
Checks the AUTH field of the AAT record and the Airline Agreement Record to determine if the carrier is valid.
International agencies (I/ in AAT table) must use carrier override when issuing tickets.
The response <UpdateModifiers> will include <FareNumInfo> and <DPOK>.
If there is an error, it is sent back in <ErrText> in the <UpdateModifiers> response.
Error and warning responses:
|
Error Message |
Reason for Error |
|
ERROR 8527 UNAUTHORIZED/INVALID PLATING CARRIER CODE |
Plating carrier not in AAT. This error is on Galileo only. |
|
ERROR 3851 – PLATING CARRIER FORMAT ERROR |
Plating carrier not in AAT. This error is on Apollo only. |
Follow-on requests:
None.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo |
Galileo |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
REQUIRED |
DPFI |
1-1 |
<FareNumInfo> |
||||
|
|
DP0H |
1-1 |
<PlatingAirVMod> |
||||
|
<UpdateModifiers> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
DPFI |
1-1 |
<FareNumInfo> |
||
|
|
DPOK |
1-1 |
<DPOK> |
||
|
<UpdateModifiers> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
DPFI |
1-1 |
<FareNumInfo> |
||
|
|
EROR |
1-1 |
<ErrText> |
||