This task updates a specified fare within the itinerary such that back office information is added or the current back office information is modified. The task is only used by Italy BSP. The BOI modifier can be used with OP, PC, SK, IV, PZ, CM, BL, and CL options.
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?
This task cannot be performed in a sessionless environment. A Booking File is required for this task.
Are the request and response identical on both the Apollo and Galileo systems?
This task is only applicable on the Galileo system.
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, fares and ticketing.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
The BOI modifier is only valid in Italy.
Request:
Following are the steps required to carry out this task:
Set the BOTR field in the AAT of the pseudo city code to 'Y'.
Create a booking file with fares.
Send the fare number in the <FareNumInfo>.
Send the BOI in the <BackOfficeInfo>.
Prerequisite tasks:
A booking file must be present in the AAA, with fares.
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.
The following table lists
possible errors.
|
Error Message |
Reason for Error |
|
ERROR 8509 - BOI ERROR - BL MUST CONATIN CHARACTER/HYPEN. |
This error is returned when the wrong data/format is entered in the BL. |
|
ERROR 8508 - BOI ERROR - CL MUST CONATIN CHARACTER/HYPEN. |
This error is returned when the wrong data/format is entered in the CL. |
|
ERROR 8514 - BOI ERROR - SK MUST CONATIN CHARACTER/HYPEN. |
This error is returned when the wrong data/format is entered in the SK. |
|
ERROR 8573 - INVALID FORMAT/DATA - AGENT NOT PERMITTED TO USE BOI |
This error is generated when the BOTR field is not set to 'Y'. |
|
ERROR 8527 - UNAUTHORISED/INVALID PLATING CARRIER CODE |
The error is generated when an invalid plating carrier is used. |
The following table lists possible warning messages.
|
Warning Message |
Reason for Message |
|
User Code is required |
This warning is generated when no data is entered in the User Code (OP). |
|
Process Code is required |
The warning is generated when no data is entered for the Process (PC). |
|
Actual Fare must be between 4 and 8 characters in length. |
The warning is generated when no data is entered in for the Actual Fare (AF). |
|
At least one character must be entered. |
The warning is generated when no data is entered in the Exchange Rate (CM). |
Follow-on requests:
None.
|
<UpdateModifiersMods> |
Terminal Equivalents: |
Apollo: N/A |
Galileo: TMUnBOI or (TMUnBOI**OPx*PCx*CLxxx-C*SKxxxx-x*CMxxxxx*PZxxxxx*BLa-xxxxx*IVxx) |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
A |
DPFI |
1-1 |
<FareNumInfo> |
|
B |
DP0H |
1-1 |
<PlatingAirVMod> |
|
C |
DP47 |
1-1 |
<BackOfficeInfo> |
|
<UpdateModifiers> |
|
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
DPFI |
1-1 |
<FareNumInfo> |
||
|
B |
DPOK |
0-1 |
<DPOK> |
||
|
<UpdateModifiers> |
|
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
A |
DPFI |
0-1 |
<FareNumInfo> |
||
|
B |
EROR |
0-1 |
<ErrText> |
||