The task unables fare quote on Apollo core (1V).
Transaction Name:
DocProdFareManipulation_4_1
Can any other transactions(s) perform this same task?
No other transaction can perform this task.
Can this task be performed in a sessionless environment?
No. As we have to book segments and fare quote, which requires a session.
Are the request and response identical on both the Apollo and Galileo systems?
This task is only applicable on Apollo.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Knowledge of ticketing and fare quote is required.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Not applicable.
Request:
Following steps are required to carry out this task:
Data record 4026 works while transmitting the T:UNABLE entry to unable the Fare Quote on Apollo core.
Prerequisite tasks:
There are no prerequisite tasks.
Expected response:
The response <PretendFareCreation> includes the <DPOK>.
Error and warning responses:
If there is an error, it is sent back in the <ErrText> in the <PretendFareCreation> response.
Follow-on requests:
None.
<PretendFareCreationMods> |
Terminal Equivalents: |
Apollo T:UNABLE |
Galileo Not applicable on Galileo. |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
|
4026v1.0 |
1-1 |
<PretendFareCreationMods> |
||||
<PretendFareCreation> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
DPOK 1.0 |
1 - 1 |
<DPOK> |
||
<PretendFareCreation> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
EROR 1.0 |
1 - 1 |
<ErrText> |
||