Task: Update OB Fee Exemptions

The task is used to specify any Carrier Ticketing Fees Sub-code that will be exempted. If all Carrier Ticketing Fees are to be treated as exempt then the OBX without OB Fee Sub-Codes will be entered.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_8

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

No.

Can this task be performed in a sessionless environment?

No. A Booking File / PNR is required

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

This is only on the Galileo (1G) CRS.

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

Knowledge of Ticketing, Reservations and Fare Quote.

The knowledge of the CGNR/BSP for the particular PCC is a must, because Carrier Ticketing (OB) Fees usage in general is dependent upon the CGNR/local BSP Carrier Fees Application Switch.

CARRIER FEES MAY APPLY: Y

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

No more than Eight Carrier Ticketing Fees OB Fees sub-codes can be entered.
Duplicate Sub-codes will generate an error response.
Invalid Sub-code formats will generate an error response.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

The following steps are required to carry out this task:

Create a Booking File.
Send the fare number in the <FareNumInfo> element.
Send the OB Exempt (OBX) data in the <OBFExemptMods> element.

Prerequisite tasks:

A PNR/BF must exist.
A fare must exist.

Expected response:

The <UpdateModifiers> includes the <FareNumInfo> and <DPOK> elements.

Error and warning responses:

Errors are returned in the <Ticketing> response, in the <ErrText> element.

If the modifier contains duplicate Carrier Ticketing Fee OB Fee sub-codes:
ERROR 9127 – DUPLICATE OB FEE EXEMPT SUBCODE
If an invalid Carrier Ticketing Fee OB Fee sub-code exemption is requested. when OB Fees are present:
ERROR 9128 – INVALID OB FEE EXEMPT FORMAT

Follow-on requests:

N/A

See the Follow-on Request in the tables in section 3.

Section 3: Tables

Request (Input) Tags

<UpdateModifiersMods>

Terminal Equivalents:

Apollo
N/A:

Galileo
TMUnOBX-xxx…-xxx

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DP0H	1-1	<PlatingAirVMod>
C	DP2A	1-1	<OBFExemptMods>

Response (Output) Tags

<UpdateModifiers>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	DPOK	1-1	<DPOK>

<UpdateModifiers>
	Ordering	KLR	Min/Max	XML Tag
	A	DPFI	1-1	<FareNumInfo>
	B	EROR	1-1	<ErrText>

Related Samples

DocProdFareRequote_8_s42