Task: Update Bulk Ticket Mod

This task updates a specified fare within the itinerary such that a bulk ticket (specific to Apollo) or a bulk tour (specific to Galileo) is created or the current bulk ticket (bulk tour) is modified.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_6

Can any other transaction(s) perform this same task?

No, only DocProdFareRequote_6 can perform this task.

Can this task be performed in a sessionless environment?

No, the task cannot be performed in a sessionless environment. A PNR/booking file must exist with a stored fare to accomplish this task.

Are the request and response identical on both the Apollo and Galileo systems?

Yes, they are identical on both the systems.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

The user should have an understanding of Ticketing, Fares and Reservation.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

Bulk Ticket is not valid with HBQ - (Queue ticketing)
Bulk Ticket is not valid with TKPN - (Open Ticket)

The following modifiers are not allowed with Bulk Ticket (GB or BT) modifier:

Modifier GBN Ц Non-Refundable Bulk Ticket
Modifier IT - Inclusive Tour
Modifier DGD Ц Demand Global MIR
Modifier DJD Ца Non-Faring MIR to Remote location
Modifier DND Ц Non-Ticketing MIR to remote
Modifier DXD Ц Dual MIR
Modifier DPD Ц Pocket Itinerary only
Modifier DDD Ц Delivery Document
Modifier GF Ц Free Ticket
Modifier GFPЦ Freeform Information
Modifier GT Ц Tour Ticket Mod
Modifier GVR Ц Value Removed (UA Modifier)

Processing notes for Bulk Ticket (GB or BT) modifier:

The Bulk Ticket modifier is usually used with the Tour Code (TC) modifier.
BT: When tickets are issued at bulk tour fares, 'BT' is printed in the fare box. The currency code and 'IT' are printed in the total box of the ticket, instead of the actual fare charged.
Certain BSPs have requirement to show the fare construction as normal. The override is *PC appended to the BT. For example, BT*PC. 'IT' is printed in fare box and fare calculation.
Prints 'BT' in the fare box of the ticket.
GB prints the following text in the fare calculation box:
VALID ON TICKETED CARRIER ONLY/VOLUNATRY ROUTING CHANGES NOT PERMITTED/NON EXCHANGEABLE/REFUND ONLY THROUGH TOUR OPERATOR.

Section 2: Detailed Description

Request:

Following are the steps required to carry out this task:

Create the PNR/booking file with a fare.
Send the fare number in the <FareNumInfo>.
Send the Bulk Ticket (GB/BT modifier) in the <BulkTicket>.

Prerequisite tasks:

PNR/booking file must be present on AAA, with fares.

Expected response:

The response <UpdateModifiers> includes the <FareNumInfo> fare number and <DPOK>.

Error and warning responses:

If there is an error, it is sent back in the <ErrText> sub-element of the <UpdateModifiers>.

The <ErrText> can generated the following messages.

Error Message	Reason for Error
ERROR 4355 - BT NOT COMBINABLE WITH IT	This error response is generated when BT is combined with an invalid modifier (for this example IT was used).
ERROR 4373 - INVALID MODIFIER FOR OPEN TICKETING	This error response is generated when BT is combined with an invalid modifier (for this example Open Ticket -TKPN was used).
ERROR 4355 - BT NOT COMBINABLE WITH DJD	This error response is generated when BT is combined with an invalid modifier (for this example DJD was used).

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<UpdateModifiersMods>		Terminal Equivalents:			Apollo: C:nT:/GB		Galileo: TMUnBT or TMUnBT*PC
	Ordering		KLR	Min/Max		XML Tag
	A		DPFI	1-1		<FareNumInfo>
	B		DP28	1-1		<BulkTicket>

Response (Output) Tags

<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	1-1	<FareNumInfo>
B	EROR	0-1	<ErrText>

Related Samples

DocProdFareRequote_6_s5