This task enables the agent to override the Apollo record locator with the record locator and airline code of a PNR originally booked directly in another airline reservation system, at the time of ticket issue.
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 with stored fares must be present to update the ticket modifier.
Are the request and response identical on both the Apollo and Galileo systems?
No, the task is only applicable to the Apollo system.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Knowledge of reservations, fares and ticketing is required.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Processing notes for the GRL modifier:
Request:
The following steps are required to carry out this task:
1. Create a PNR
2. Send the fare number in the <FareNumInfo>.
3. Send the Print RECLOC (GRL) modifier in the <PrintRLoc>.
Prerequisite tasks:
A PNR with stored fares must be present in the AAA.
Expected response:
The response <UpdateModifiers> includes the <FareNumInfo> (which indicates the fare relationship) and the <DPOK> sub-elements.
Error and warning responses:
|
Warning Message |
Reason for Warning |
|
“More information is required or incomplete information”. |
This warning is generated if the GRL modifier is selected and no data is keyed in the provided text boxes. |
Follow-on requests:
None.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo: C:nT:/GRLXXXXXX*1A |
Galileo: N/A |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
A |
DPFI |
1-1 |
<FareNumInfo> |
||||
|
B |
DP25 |
1-1 |
<PrintRLoc> |
||||
|
<UpdateModifiers> |
|
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
DPFI |
1-1 |
<FareNumInfo> |
||
|
B |
DPOK |
1-1 |
<DPOK> |
||