Task: Fare Quote Store Price

This task allows a user to obtain a fare quote for a booked itinerary, which is the lowest fare for the booking code, origin/destination, and dates, and then store the fare quote in the PNR/BF. This step is a prerequisite to ticketing the PNR/BF.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_44

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

Previous versions of PNRBFManagement, PNRBFBuildModify_7_7_1, and FareQuoteStorePrice transactions can perform this task.

Can this task be performed in a sessionless environment?

No. The task needs data from the AAA.

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

No. See Section 2 - Request.

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

A user must understand the fare quote (pricing) process. The various optional parameters require more detailed knowledge of pricing to use this transaction.
To receive web/Private Fares, a user must know the Pseudo City Code under which the fare was filed.
A user must know valid passenger type codes in order to quote fares that may pertain just to certain passenger types.

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

Not applicable.

Section 2: Detailed Description

Request:

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

A <StorePriceMods> (1408) is sent with the request, with both pricing elements (GQ KLRs) and ticketing elements (DP KLRs). The pricing elements are used during the fare quote process, while the ticketing elements data is used for storing data in the PNR/BF. See the Pricing and Ticketing Comparison for FareQuoteStorePrice table.

The following points should be considered when making a Store Price request:

It is important to ensure that if a pricing modifier is used, the corresponding ticketing modifier is also included. For example, if the <PlatingAirVMods> (GQPC KLR) is included to specify plating carrier, the <PlatingAirVMod> (DP0H KLR) should also be specified. The <PlatingAirVMods> will be used to produce an accurate quote for that plating carrier, and the <PlatingAirVMod> will be used to ensure that information is saved in the PNR/BF.
Additionally, a <PsgrMods> or a <FqPicOnly> must be sent in the request. <PsgrMods> requests prices for the specified passenger type, but accepts prices for the default passenger type if they are cheaper than the specified passenger type. <FqPicOnly> requests prices for the specified passenger type ONLY, whether they are less expensive than the default, or not.
The following points are CRS-specific
- On the Apollo (1V):
  - All pricing modifiers tags should have corresponding ticketing modifier tags.
  - The <ServiceFees> element contains information about service fee associated ticketing modifiers. For example, the service fee number (mandatory), PCC (optional) and date (optional) which needs to be associated with the ticket.
  - The <ProgEndorsement> denotes that programmatic endorsements are overridden; only manual endorsements are accepted.
  - The <DiscPriceModifier> (DP17) accepts discount pricing modifiers (increase or decrease percentage, or flat amount, before or after taxes), in conjunction with a specific PTC for <StorePriceMods> requests. <DiscPriceModifier> displays in the <DocProdDisplayStoredQuote> (4015) response.
  - The <FOPRestrict> (DPF0) can be included to indicate whether the additional form of payment (FOP) restriction check by the airline is required.
- On Galileo (1G):
  - Only C (Plating Carrier), ET (Electronic ticket), PT (Paper ticket) and Z, ZA, ZC (Commission) should have both pricing and ticketing tags.
  - The Galileo CRS includes cancel/rebook change fees (coded in Category 16 Penalties) in a fare quote. Under certain conditions, the airline may waive these fees by providing a waiver to the agency. The <WaiverMods> allows the agent to provide a waiver to bypass automated change fee collection. This waiver code can be 10-14 alpha-numeric characters long. The <WaiverInfo> element displays in the response displays if a waiver present in PNR. Galileo (1G) only.
  - The <GenQuoteInfo> (GQQM KLR) / <UseCurntTax> displays current or historical tax on a historical fare quote request (Galileo [1G] CRS only).
If the user wishes to define whether the most restrictive rules for the entire quote (single fare component) are returned in <RsvnRules>, <GenQuoteInfo> must be sent with the <RulesProcess> indicator set to N. If the indicator is set to Y, applicable rules are returned in <AdvRsvnTktRule>/ <MinStayRule>/ <MaxStayRule>/ <SalesRestrictionsRule>/ <PenaltiesRule> per fare component.
Fares with rule category 35 (CAT 35) data, which is net fare information, will potentially contain multiple fare levels: sell, net, ticket-audit, ticket-passenger. For users requesting the additional CAT 35 data, this information is returned in the elements identified with an asterisk (*) within the <FareInfo> (1425 Data Record) response (see the <FareInfo> Response table in Section 3).
Note: The <EnhancedPrivateFare> (GFPX KLR) is used for rules follow-ons. It is returned with rules follow-on transactions so that the correct rules text displays. Do not use or modify anything in this element.
The <CtrlAirVMods> (GQCC KLR) provides the ability to override fare selection logic and specify carriers in cases where carriers have filed fares with interline partners and they are not the significant carrier on a fare component (they are not the owning or significant carrier on an itinerary so the fares do not quote). The associated <OCMods> (DPOC KLR) is used in conjunction with <CtrlAirVMods> for a store fare quote request with a fare selection override.

Prerequisite tasks:

On Apollo, if the user wants to store the fare, but the PNR already has an ATFQ with the same passengers/segment combination, then the user must cancel the existing stored quote. See Task Cancel Stored Fare.

Expected response:

The expected response is the <FareInfo> (1425), with tags that reflect the price of the booked itinerary.

The <BaggDispInfo> and subsequent <BaggDispFQandFQBB> display free baggage allowance and baggage charges at fare quote (specific itinerary pricing) and are added to e-ticket confirmations.

Error and warning responses:

The following error/warning messages might display:

Invalid sequence (origin/destination in wrong order)
Invalid dates, city codes, carriers, etc.
Invalid Format/Data
Service Fee Already Associated
Service Fee Not Available in Database, Association Not Completed
PCC not allowed – No Agreement
FOP HAS RESTRICTIONS ON QF: APPEND OK TO FOP TO ACCEPT (This error is issued for QF and carriers may vary in error response.)

Follow-on requests:

The follow-on requests for this task are:

FareQuoteMultiDisplay_# – Rules Display
Routes Display
DocProdFareManipulation_#

Section 3: Tables

Request (Input) Tags

<StorePriceMods>		Terminal Equivalents:			Apollo T:$B		Galileo: ______
	Ordering		KLR	Min-Max		XML Tag
	A		GQNP or GQPO or GQPA	1-1		<PsgrMods> or <FqPicOnly> or <PassengerType>
	B		DPPI and DP07/DP08	1-#		<AssocPsgrs> and <PICOptMod>/<PICOnlyMod>
	B		DP17	0-1 (1V only)		<DiscPriceModifier>
	B		DP0I	0-1 (1V only)		<TICMod>
	B		GQQM	0-1		<GenQuoteModifiers>
	B		GQTE	0-1		<TaxExemptMods>
	B		DP0G	0-1		<TaxExemptMod>
	B		GQSR	0-1		<SegMods>
	B		DPII and DP0A	0-#		<AssocSegs> <FICMod>
	B		DP0B	0-#		<StopoverMod>
	B		DP0C	0-#		<NoBreakMod>
	B		DP0D	0-#		<ConxMod>
	B		DP0E	0-#		<OnlyBreakMod>
	B		DP0F	0-#		<BreakMod>
	B A (1G)		GQPC	0-1 (1V) 1-1 (1G)		<PlatingAirVMods>
	B		DP01	0-1		<PenMod>
	B		DP02	0-1		<NoMinStayMod>
	B		DP03	0-1		<NoMaxStayMod>
	B		DP04	0-1		<NoMinOrMaxStayMod>
	B		DP05	0-1		<NoRestrictionsMod>
	B		DP06	0-1		<NoAdvPurchMod>
	B		DPFT	1-1		<DocProdFareType>
	B		GQSS	0-1		<SegSelection>
	B		DP09	0-1		<PFMod>
	B		DPP1	1-1		<CheckFOP>
	B		DP10	0-1		<CommissionMod>
	B		DP27	0-1		<EndorsementBox>
	B		GQWV	0-1		<WaiverMods>
	B		DP57	0-1		<ServiceFees>
	B		DP58	0-1		<ProgEndorsement>
	B		DPF0	0-1		<FOPRestrict>
	B		GQCC	0-1		<CtrlAirVMods>
	B		DPOC	0-1		<OCMods>

Response (Output) Tags

Tags with asterisks (*) in the Ordering column can contain CAT 35 elements on the Galileo CRS.

<FareInfo>

Ordering	KLR	Min/Max	XML Tag
	EROR		<ErrText>
	GFRH		<RespHeader>
	GFBC		<PrevBICSegMapping>
	GFBD		<BaggDispInfo>
	GFBF	0-16	<BaggDispFQandFQBB> Up to 16 - 1 per ticketed segment
*	GFC7	0-48	<CommNetGrossInfo> Up to 3 for each <BaggDispInfo>
	GFCI		<CityIndInfo>
	GFDR		<TkRestrictionInfo>
*	GFEQ		<ExtendedQuoteInformation>
	GFFC		<FareConstruction>
	GFFO		<OverrideInfo>
	GFGQ		<GenQuoteDetails>
	GFIS		<ItinSeg>
	GFJT		<JrnyType>
	GFMM		<InfoMsg>
*	GFN1		<SellFareConstruct>
*	GFN2		<NetFareConstruct>
*	GFN3		<TkAuditFareConstruct>
*	GFN4		<TkPsgrFareConstruct>
*	GFPF		<PsgrFacilityCharge>
	GFPI		<PsgrTypes>
	GFPU		<PlusUps>
*	GFPX		<EnhancedPrivateFare>
	GFRI		<RulesInfo>
	GFRR		<RsvnRules>
	GFJ5		<AdvRsvnTktRules>
	GFJ6		<MinStayRules>
	GFJ7		<MaxStayRules>
	GFJF		<SalesRestrictionRules>
	GFJG		<PenaltyRules>
*	GFS2		<NetStructFareConstruct>
*	GFS3		<TkAuditStructFareConstruct>
*	GFS4		<TkPsgrStructFareConstruct>
*	GFSF		<SellStructFareConstruct>
	GFSR		<SegRelatedInfo>
	GFSU		<Surcharge>
	GFT1		<TkPsgrFareConstructTaxInfo>
	GFTS		<TaxBreakdown>

Related Samples

PNRBFManagement_44_s7

PNRBFManagement_44_s8

PNRBFManagement_44_s41

PNRBFManagement_44_s86

PNRBFManagement_44_s92

PNRBFManagement_44_s95

PNRBFManagement_44_s99

PNRBFManagement_44_s112

PNRBFManagement_44_s120

PNRBFManagement_44_s122

PNRBFManagement_44_s127

PNRBFManagement_44_s128

PNRBFManagement_44_s129

PNRBFManagement_44_s131

PNRBFManagement_44_s133

PNRBFManagement_44_s135