Task: Update Actual Selling Fare Mod

This task is used to specify that the actual selling fare has been updated from the originally filed fare. The use of this task is dependent on the CGNR/local BSP net remittance scheme.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_1_0

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

No, only DocProdFareRequote_1_0 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 the task.

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

No. This task is only available on the Galileo system.

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

Users should have a knowledge of ticketing, reservations, and Fare Quote. Users should also be familiar with the CGNR/BSP for the particular pseudo city, because the usage of this task is dependant upon the CGNR/local BSP net remittance scheme.

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

In some countries, notably Scandinavia and Thailand, there is a BSP requirement for agents to report an Actual Selling Fare as part of their net remittance agreement.
The ASF amount is recorded separately on the TINS report in addition to the net or published (gross) fare for BSP purposes.
This modifier returns an error when the Form of Payment is specified as ‘cash’ or ‘cheque’.

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/booking file.
Send the fare number in the <FareNumInfo> sub-element.
Send the Actual Selling Fare (ASF) in the <ActualSellingFare> sub-element.

Prerequisite tasks:

A booking file with fares must be available on AAA.

Expected response:

The response <UpdateModifiers> includes the <FareNumInfo> (which indicates the fare relationship) and a <DPOK>.

Error and warning responses:

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

Error Message	Reason for Error
ERROR 8502 - NF INVALID MODIFIER’	This error is generated when the modifier is not applicable to a particular pseudo city.
ERROR 8532 – CASH NOT PERMITTED WITH NET REMITTANCE	This error is generated when the Form of Payment is ‘Cash’.
ERROR 8532 - CHEQUE NOT PERMITTED WITH NET REMITTANCE	This error is generated when the Form of Payment is ‘Cheque’.

The following error messages are returned from Category 35 fares:

Error Message	Reason for Error / Resolution
9095 – NET TICKET DATA MAY NOT BE MODIFIED	To resolve, cancel it and re-quote for published fares or other fare types.
9096 – UNABLE TO TICKET – NET FARE TOUR CODE EXCEEDS MAXIMUM LENGTH	To resolve, cancel and re-quote, changing parameters to get a new quote, such as a public fare, specific fare, etc.
9097 - NOT AUTHORISED TO TICKET THE FILED FARE. CANCEL AND REFILE	To resolve, cancel the stored fare and re-quote as own identity.
9099 – INVALID CAT35 COMMISSION RETURNED. CANCEL AND REFILE	To resolve, cancel and re-quote, changing parameters to get a new quote, such as a public fare, specific fare, etc.

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<UpdateModifiersMods>

Terminal Equivalents:

Apollo: N/A

Galileo: TMUnASFxxxx

Ordering

KLR

Min/Max

XML Tag

A	DPFI	1-1	<FareNumInfo>
B	DP0H	1-1	<PlatingAirVMod>
C	DP35	1-1	<ActualSellingFare>

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_1_0_s1