The Enable Stored Fares task allows the user to enable stored manual fares in the PNR.
Transaction Name:
DocProdFareManipulation_6
Can any other transaction(s) perform this same task?
No other transaction can perform this task.
Can this task be performed in a sessionless environment?
This task must be used in a sessioned environment.
Are the request and response identical on both the Apollo and Galileo systems?
The request and response are available on Apollo only.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
A knowledge of Reservation, Ticketing and Manual Pricing is beneficial for this task.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
There are no special limitations.
Request:
The <EnableStoredFareMods> (4044) is required to send a request to enable stored fares in a PNR. In the request to Enable Manual Fares, the <FareNumInfo> element is optional.
If all the manual fares are required to be ‘ENABLED’, then the request is an <EnableStoredFareMods> (4044) without a <FareNumInfo> element. This request internally loops through all fares present in the PNR, and enables all of the manual fares; in other words, the Fares Status code in the ATFQ for all manual fares are changed to 'OK'.
To enable specific manual fares (i.e., for the terminal emulation equivalent >T:OK1|4|5), the user must send an <EnableStoredFareMods> (4044) request with the <FareNumInfo> element that contains the details of fares to be enabled.
Prerequisites:
The PNR, with stored manual fares, must be present in the AAA.
Response:
If the Enable Stored Fares transaction completes successfully, the <DPOK> and <FareNumInfo> elements are returned to indicate a good response. The <FareNumInfo> element returns the fare number array of the manual fares that were enabled in Enable Stored Fares transaction.
Error and warning responses:
If the Enable Stored Fare task encounters an error, the error is returned in the <ErrText> tag. The following error messages can be received:
3076 - INVALID MULTI-PRICING MODIFIER
2307 - BAD ENTRY (When fare number is not given in <FareNumInfo> element.)
Follow-on requests:
No follow-on requests exist.
Additional capabilities:
T:OK2 - Enables user to store single pricing record.
T:OK1|4 - Enables user to store multiple pricing record.
Only manually stored fares can be enabled by this task.
|
<EnableStoredFareMods> |
Terminal Equivalents: |
Apollo: T:OK |
Not applicable on Galileo |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
Required |
DPFI |
1-1 |
<FareNumInfo> (Optional) Note: This element is required to request a specific fare be enabled. It is not required if the request is to enable all the fares. |
||||
|
<EnableStoredFare> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
|||
| A | DPFI | 1-1 | <FareNumInfo> | |||
|
B |
DPOK |
1-1 |
<DPOK> |
||
|
<EnableStoredFare> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
| A | DPFI | 1-1 | <FareNumInfo> | |||
|
B |
EROR |
1-1 |
<ErrText> |
||