Task: Update Tour Box

Updates a specific stored fare within the itinerary, such that a different tour number displays in the tour box.

Section 1: Short Answer

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?

No. A PNR/booking file must exist. A fare must exist.

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

Yes, they are identical.

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

User will need to create a booking file/PNR and a fare.

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

Galileo only:

Apollo only:

"IT" will not be output as part of the tour code unless entered as part of the 15 characters.
Special character pillow (@) appears as blank space.
The asterisk (*), if entered, will appear as a slash (/).
The hyphen (-), if entered, will appear as a hyphen.
On OPTAT tickets only, the last 14 characters will print.
Not valid with the following modifiers:
- Modifier DGD – Demand Global MIR
- Modifier DJD – Non-Faring MIR to Remote Location
- Modifier DND – Non-Ticketing MIR to Remote
- Modifier DXD – Dual MIR

Request:

Prerequisite tasks:

User will need to create a booking file/PNR and a fare.

Expected response:

The response <UpdateModifiers> will include <FareNumInfo> and <DPOK>.

Error and warning responses:

If there is an error, it is sent back in the <ErrText> in the <UpdateModifiers> response.

Follow-on requests:

None.

<UpdateModifiersMods>		Terminal Equivalents:			Apollo C:nT:/ITxxxxxxxxxxxxxx		Galileo TMUnTCxxxxxxxxxxxxx
	Ordering		KLR	Min/Max		XML Tag
	REQUIRED		DPFI	1-1		<FareNumInfo>
			DP33 v1	1-1		<TourCode>