This task is a sale and ticketing indicator. Following are the different combinations that can be used within the sold and ticketing modifier.
(SITI) Sold Inside – Ticketed Inside country of commencement of travel.
Transaction Name:
DocProdFareRequote_2
Can any other transaction(s) perform this same task?
No, only DocProdFareRequote_2 can perform this task.
Can this task be performed in a sessionless environment?
This task cannot be performed in a sessionless environment. A PNR is required for the task.
Are the request and response identical on both the Apollo and Galileo systems?
The task is applicable only on Apollo.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
The user should have an understanding of Reservations, Fare Quote and Ticketing Modifiers.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
The following modifiers are not allowed with the Sold and Ticketed (GSITO; GSITI; GSOTO;GSOTI) modifier:
Modifier DJD – Non-Faring MIR to Remote location
Modifier DGD – Demand Global MIR (works only through Focalpoint entry for ticketing)
Modifier DXD – Dual MIR(works only through Focalpoint entry for ticketing)
Modifier DND – Non-Ticketing MIR to remote(works only through focal point entry for ticketing)
Only one sold and ticketing modifier (GSOTI, GSITO, GSOTI and GSITI) can be used at a given time.
Processing notes for the Sold and Ticketing (GSOTI; GSITO; GSOTI; GSITI) modifier:
Used for manual price only – not Auto FQ.
Used only for pricing records.
Applies to the country of commencement of travel.
Does not override a fare quoted (T:$B) entry.
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 Sold and Ticketed (GSITO etc) modifiers in the <SoldTicketed>.
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:
If there is an error, it is sent back in the <ErrText> of the <UpdateModifiers> element.
|
Error Message |
Reason for Error |
|
ERROR 8209 – ‘Invalid format/data- modifier already exists’ |
This error is generated when the GSOTI, GSOTO, GSITI and GSITO are given together. |
|
ERROR 5964 – ‘Invalid format/data-check modifier’ |
This error is generated when the sold and ticketed modifier is combined with the DJD modifier. |
Follow-on requests:
None.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo: C:nT:/GSITO; C:nT:/GSITI; C:nT:/GSOTO; C:nT/GSOTI |
Galileo: N/A |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
A |
DPFI |
1-1 |
<FareNumInfo> |
||||
|
B |
DP20 |
1-1 |
<SoldTicketed> |
||||
|
<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 |
0-1 |
<ErrText> |
||