Task: Update Service Fee Associations

The task is used to specify service fee that needs to be associated with ticket. The service fee will be associated with the first ticket of the specific filed fare and will be associated at the time of Ticket issuance.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_5

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. A fare must exist.

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

Yes.

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

Knowledge of Ticketing, Reservations and Fare Quote.

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

A fare must exist.
A PNR/BF must exist.
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 PNR/BF.
Send the fare number in the <FareNumInfo> element.
Send the Service Fee association modifier data in the <ServiceFees> 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 <UpdateModifiers> response, in the <ErrText> element.

ERROR 259 – INVALID FORMAT/DATA: This error is generated when SF association modifier is entered in any other format then specified format.
ERROR 9136 – SERVICE FEE ALREADY ASSOCIATED: This error is generated on front end when the service fee number in modifier is already associated with any other ticket.
ERROR 9137 – SERVICE FEE NOT AVAILABLE IN DATABASE, ASSOCIATION NOT COMPLETED: This error is generated on front end when service fee present in modifier is never issued.
ERROR 9078 – PCC NOT ALLOWED – NO AGREEMENT: This error is generated on front end when PCC given in SF association modifier doesn’t have any agreement with default PCC (PCC in AAA).

Follow-on requests:

N/A

Section 3: Tables

Request (Input) Tags

<UpdateModifiersMods>

Terminal Equivalents:

Apollo:
C:nT:/SFnnnnnnnnnnn|

Pxxxx|Dddmmmyyyy

Galileo:
TMUnSFnnnnnnnnnnnnn

*Pxxxx*Dddmmmyyyy

Ordering	KLR	Min/Max	XML Tag
A	DPFI	1-1	<FareNumInfo>
B	DP57	0-1	<ServiceFees>

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_s43