Data Events and Triggers

The following events or actions cause a Travelport Booking Feed message to be generated to a customer’s unique data queue when a booking record (PNR/Booking File) is end transacted. For Travelport Booking Feed, three types of events are created:

Booking Event: A booking is created, or an existing booking is modified by adding or deleting an itinerary item.
Fare Quote Event: A fare quote is added or deleted.
Ticketing Event: A ticket is issued, voided, un-voided, refunded, or has a service fee attached. (Galileo only).

For customers who do not require all of the data sent by Travelport Booking Feed, data triggers can be used to control certain types of data sent from the Apollo or Galileo GDS to the Travelport Booking Feed adapter. Specific data triggered by a Galileo or Apollo event can either be sent or not sent to the adapter depending on a setting in the TBF Trigger table in the PCC’s AAT (Agency Account Table). For example:

If the primary traveler’s phone number is deleted from the PNR/BF, a Booking event is created in Travelport Booking Feed. A trigger can be set in the TBF Trigger Table to either send or not send the change in phone data to the Travelport Booking Feed client adapter when a Booking event occurs.

If the phone trigger (FONE/EMAIL CHNG) is enabled, then the modified phone data is received in the corresponding PhoneSeg table in the customer’s SQL database. Or, if the customer uses XML data instead of the database, the phone data is received in the corresponding BookingData/PassengerInformation/Phone element.

If the phone trigger is disabled, then the corresponding phone change data is not received in the corresponding PhoneSeg table or Phone element.

In this way, TBF triggers can be used to fine-tune the types of data received from Travelport Booking Feed to best meet an agency or other travel provider’s business processes or reporting needs. Similarly, an agency can limit unnecessary data to streamline their booking feed and avoid processing and storage of irrelevant data.

AAT Settings for TBF Triggers

Access to modify TBF Triggers is a PCC set by Travelport in the AAT, which governs functional capabilities for each PCC. The TBFA (Travelport Booking Feed Activation) field (formerly the GIDS field) has two flags:

The first flag controls access for customers with sign on credentials for that PCC to view and/or modify the TBF Triggers screen.
The second flag indicates the presence of six default TBF triggers (previously known as the ADAT (All Data All the Time) triggers). These triggers vary by GDS:

Trigger Screen	Field	Apollo	Galileo
Ticketing Remarks change	TKT RMKS CHNG	x
Invoice Remarks change	INV RMRKS CHNG		x
Phone/email change	FONE/EMAIL CHNG	x	x
Remarks change	REMRKS CHNG	x
Notepad change	NOTEPAD CHNGE		x
Form of Payment change	FOP CHNG	x	x

The additional triggers are:

Trigger Screen	Field	Apollo	Galileo
Create PNR/Booking File	CREATE PNR/BF	x	x
Itinerary change	ITIN CHNG	x	x
Name change	NAME CHG	x	x
PNR Booking File split/divide	SPLIT/DIVIDE	x	x
Transacted ticket	TKT EVENT	x	x
Refunded ticket	REFUND	x	x
Service fees	SVC FEE	x	x
Fare change	FARE CHNG	x	x

The following table indicates the levels of access and default trigger settings depending on the values for the first and second flags in the TBFA field in the AAT.

Access Based on TBF Table Data Flag Settings

First/Second Flag Settings	Customer Access	Default Trigger Settings
N/N (default)	Customers cannot access the TBF Triggers screen. Updates can be made by Travelport administrators only.	The default (ADAT) triggers are set to ‘Y’; all other triggers are set to ‘N’. The administrator must enable or disable individual triggers.
N/Y	Customers cannot access the TBF Triggers screen. Updates can be made by Travelport administrators only.	All triggers are set to ‘Y’; data is sent for all triggers. To disable a specific trigger, the administrator must set the trigger to ‘N’.
Y/N	Customers can access the TBF Triggers screen: Users with agent-level credentials (Duty Code ‘AG) to the PCC can view, but not modify, the screen. Users with second-level authorizer credentials can view and modify the screen.	The default (ADAT) triggers are set to ‘Y’; all other triggers are set to ‘N’. Change the settings for individual triggers to enable or disable.
Y/Y	Customers can access the TBF Triggers screen: Users with agent-level credentials (Duty Code ‘AG) to the PCC can view, but not modify, the screen. Users with second-level authorizer credentials can view and modify the screen.	All triggers are set to ‘Y’; data is sent for all triggers. To disable a specific trigger, the trigger must be set to ‘N’.

Table Lock Setting

The Table Lock setting (TBFU) locks the TBF table so that only one update can be made at a time. If the table is locked, the FBFA screen display with a warning message at the top of the screen and the tab stops are disabled.

This functionality is controlled by the Agency Account Table (AAT).

Sine-On Profile

The information sent to the travel companies is controlled by the TBF Trigger Table. Currently anyone in a pseudo city code (PCC) that utilizes TBF can update the fill in format of the TBF Trigger Table. The Sine-On Security field gives PCCs the ability to restrict which users are permitted to update the TBF Trigger Table.

The TBFR defaults to TBFR ·N·N status: which allows changes to the trigger table for all users of TBF.

Once changed by agencies, the first Y indicates the user has the authority to turn on/off the second field for another user: TBFR ·Y·N; the second Y indicates the user is restricted from updating the TBF trigger table: TBFR ·N·Y.

Galileo

Display the access page of the SINE-ON Profile by entering:

>STD/Z followed by the agent ID then a slash and two asterisks.

Example: >STD/ZSO/**

The following example is the default setting. All users with access to TBF are allowed to update/change the TBF Trigger Table.

Apollo

Display the access page of the SINE-ON Profile by entering:

>STD/Z followed by the agent ID then a slash and two asterisks.

Example: >STD/ZSO/**

The following example, the user has been changed to N·Y status. This restricts the user from updating/changing the TBF Trigger Table.

TBF Trigger Table

Entry

>*TBF

With the default setting of TBFR ·N·N, a TBF user is allowed to update the below table for their PCC. If a given user’s profile is changed to restrict updates to the table (TBFR ·N·Y ), one of the following error messages is returned when an attempt is made by that user to update the Trigger Table:

INVALID AUTHORITY / RESTRICTED

RESTRICTED

Product-Specific Data Feeds

In addition to the TBFA field, three other AAT fields have flags that allow Galileo, Apollo, and ARNE customers to receive product-specific data. This customized data is collected internally and specifically sent to users of related Travelport products:

View Trip (VTRP AAT field)
E-Tracker (ETRK AAT field)

Configuring TBF Triggers

The combination of settings in the TBFA AAT field and the TBF Triggers screen determine if Travelport Booking Feed data is sent to a customer as well as the type of Travelport Booking Feed data sent.

TBF Triggers can be managed by enabled customers using the TBF Triggers fill-in format screen, which is available through Galileo and Apollo Terminal Data access. This screen is accessed by entering the *TBF command.

Within the TBF Triggers screen:

A ‘Y’ setting indicates that the data is sent to the client adapter when an applicable event occurs on the Galileo or Apollo GDS.
An ‘N’ setting indicates that the data is not sent to the client adapter when an applicable event occurs on the GDS.

Important! If emulation is used to access and administer other PCCs, the screen for each emulated PCC must be configured separately.

Error Responses for the TBF Trigger Screen

The following error responses will be returned when invalid actions are taken in an attempt to update the TBF Triggers screen in Apollo and Galileo:

Error Response	Occurs	Apollo	Galileo
INVALID AUTHORITY / RESTRICTED	When the >*TBF entry is made from a duty code other than AG or not made by an agent with second level authorization.	x	x
RESTRICTED	When the >*TBF entry is made from a duty code other than AG or not made by an agent with second level authorization.		x
SYSTEM ERROR OCCURRED	General system error.	x	x
INVALID – MUST BE AUTHORIZED TBF USER	When a user without Travelport Booking Feed permissions attempts to display the TBF Triggers screen.	x	x
[FIELD] - ERROR USE: Y/N	A character other than ‘Y’ or ‘N’ is entered for a trigger field.	x	x

TBF Triggers, Events, and Corresponding Data

The following table shows:

The Event type triggered when a TBF Trigger field is enabled (set to ‘Y’).
The corresponding SQL database tables and fields that receive the triggered data.
The corresponding XML elements and attributes in the TBF schema that receive the triggered data.

The behavior of triggers and corresponding events can be affected by the relationship with other triggers or their usage in a specific circumstance:

The same TBF Trigger field can affect different events and corresponding database tables/XML elements, depending on the type of data associated with the event.

For example, the CREATE PNR/BF field can trigger either a Fare Quote event or a Booking event, depending on whether the created PNR/BF contains or does not contain a fare quote.

Some triggers can “override” other triggers.

For example, if the FONE/EMAIL CHNG trigger is disabled (set to ‘N’), a Booking event is not triggered when an email address is added to the itinerary. However, if an email address is created as a part of a new PNR/BF, a Booking event is triggered because the email address is part of the entire PNR/BF.

PNR/BF Triggers for Booking Events

The following table applies to PNRs and Booking File that do not contain a fare quote. The affected database fields/XML elements vary depending on the specific content in a PNR/Booking File at the time of the event.

TBF Trigger Field	Triggers a Booking event when:	Affected Database Tables/Fields	Affected XML Elements/Attributes
CREATE PNR/BF	A new PNR/BF that does not contain a fare quote is created.	TravelOrderEvent AddressInfo TktRemarks OtherServiceInfo ProgrammaticSSR ManualSSR Passenger FrequentFlyer PhoneSeg EmailSeg AirRsrvSeg AirSegOperatingCarrier HtlSeg HtlSegOpt CarSeg CarSegOpt TrainSeg OpenAirSeg NonAirSeg FlyingTaxiSeg SeatSeg SeatAssignment VendorRecordLocator VendorRemarks GeneralRmksNotepad ProfileClientFile CustomerID EMDInfo ChangeOfGauge TicketingArrangement TAUTicketingArrangement TAWTicketingArrangement TLTicketingArrangement TAMTicketingArrangement	BookingData/: GeneralInformation AddressInformation CorporateID RemarkInformation OtherServiceInfo SSRInformation/ProgrammaticSSR SSRInformation/NonProgrammaticSSR ProfileClientFile CustomerID BookingData/PassengerInformation/: FrequentFlyerNbr Phone Email BookingData/TravelSegments/: AirSegment AirSegment/OperatingAirline HotelSegment HotelSegment/HotelOptionalInfo CarSegment CarSegment/CarOptionalInfo TrainSegment OpenAirSegment NonAirSegment FlyingTaxiSegment AirSegment/ChangeOfGauge BookingData/SeatSegment/: SeatAssignment BookingData/VendorInformation/: VendorRecordLocator VendorRemarks BookingData/RemarkInformation/ GeneralRemark BookingData/TravelArrangements/: TicketingArrangement TAUTicketingArrangement TAWTicketingArrangement TLTicketingArrangement TAMTicketingArrangement
SPLIT/DIVIDE	A PNR/BF is split (divided).
FONE/EMAIL CHNG	A phone or email field is added, changed, or deleted
ITIN CHNG	An itinerary is added, changed, or deleted.
NAME CHNG	A passenger name in an itinerary is added, changed, or deleted.
FOP CHNG	A form of payment is added, changed, or deleted.
FARE CHNG	A fare quote is added changed or deleted.
INV RMRKS CHNG	An Invoice Remark is added, changed, or deleted. (Galileo only.)
TKT RMRKS CHNG	A Ticket Remark is added, changed, or deleted. (Apollo only.)
NOTEPAD CHNGE	A Notepad Remark is added, changed, or deleted. (Galileo only.)
REMRKS CHNG	A General Remark is added, changed, or deleted. (Apollo only.)

PNR/BF Triggers for Fare Quote Events

The following table applies to PNRs and Booking Files that contain a fare quote. Because the records contain a fare quote, both booking and fare quote data is affected by the Fare Quote event. The affected database fields/XML elements vary depending on the specific content in a PNR/Booking File at the time of the event.

TBF Trigger Field	Triggers a Booking event when:	Affected Database Tables/Fields	Affected XML Elements/Attributes
CREATE PNR/BF	A new PNR/BF that does not contain a fare quote is created.	Booking Data TravelOrderEvent AddressInfo TktRemarks OtherServiceInfo ProgrammaticSSR ManualSSR Passenger FrequentFlyer PhoneSeg EmailSeg AirRsrvSeg AirSegOperatingCarrier HtlSeg HtlSegOpt CarSeg CarSegOpt TrainSeg OpenAirSeg NonAirSeg FlyingTaxiSeg SeatSeg SeatAssignment VendorRecordLocator VendorRemarks GeneralRmksNotepad Fare Quote Data AirFareQuo AirQuoPax FareCmpnt FareCmpntRte AirSchg PlusUp PlusUpLoc AirTax AirTaxBrk ProfileClientFile CustomerID PTCInfo EMDInfo ChangeOfGauge TicketingArrangement TAUTicketingArrangement TAWTicketingArrangement TLTicketingArrangement TAMTicketingArrangement	Booking Data BookingData/: GeneralInformation AddressInformation CorporateID RemarkInformation OtherServiceInfo SSRInformation/ProgrammaticSSR SSRInformation/NonProgrammaticSSR ProfileClientFile CustomerID BookingData/PassengerInformation/: FrequentFlyerNbr Phone Email BookingData/TravelSegments/: AirSegment AirSegment/OperatingAirline HotelSegment HotelSegment/HotelOptionalInfo CarSegment CarSegment/CarOptionalInfo TrainSegment OpenAirSegment NonAirSegment FlyingTaxiSegment AirSegment/ChangeOfGauge BookingData/SeatSegment/: SeatAssignment BookingData/VendorInformation/: VendorRecordLocator VendorRemarks BookingData/RemarkInformation/ GeneralRemark Fare Quote Data FareData/: GeneralInformation FareQuote FareQuote/TicketStatus FareQuote/LinearFare FareQuote/LinearFare/SegmentInformation FareQuote/Surcharge FareQuote/PlusUp FareQuote/PlusUp/CityCodes/CityCode FareQuote/TaxRecord FareQuote/TaxRecord/TaxBreakdown FareQuote/PassengerFareQuoteRecord BookingData/TicketingArrangements/: TicketingArrangement TAUTicketingArrangement TAWTicketingArrangement TLTicketingArrangement TAMTicketingArrangement
SPLIT/DIVIDE	A PNR/BF is split (divided).
FONE/EMAIL CHNG	A phone or email field is added, changed, or deleted
ITIN CHNG	An itinerary is added, changed, or deleted.
NAME CHNG	A passenger name in an itinerary is added, changed, or deleted.
FOP CHNG	A form of payment is added, changed, or deleted.
FARE CHNG	A fare quote is added changed or deleted.
INV RMRKS CHNG	An Invoice Remark is added, changed, or deleted. (Galileo only.)
TKT RMRKS CHNG	A Ticket Remark is added, changed, or deleted. (Apollo only.)
NOTEPAD CHNGE	A Notepad Remark is added, changed, or deleted. (Galileo only.)
REMRKS CHNG	A General Remark is added, changed, or deleted. (Apollo only.)

Ticket-Related Triggers for Ticketing Events

The following triggers create Ticketing events.

TBF Trigger Field	Triggers a Booking event when:	Affected Database Tables/Fields	Affected XML Elements/Attributes
TKT EVENT	A ticket is transacted.	TravelOrderEvent TktTrans AirTktSeg Fop FopCrCrd FopExchg NRTrans Passenger AirFareQuo AirSchg PlusUp PlusUpLoc FareCmpnt FareCmpntRte AirTax AirTaxBrk AirQuoMan OBFees OBFeesTax AirQuoAuto ExchgPaidTax	TicketingData/: TicketEvent TicketTransaction OBFeesTotals FlightCoupon TicketFOP TicketFOP/CreditCard TicketFOP/Exchange NRTrans TicketTransaction FareAmount FareComponent/FareSegment/ FareSegmentSurcharge PlusUp PlusUp/PlusUp/CityCodes/CityCode FareComponent FareComponent/FareSegment TaxRecord TaxRecord/TaxBreakdown ManualFare OBFees OBFees/OBFeesTax AutomaticFare TicketFOP/Exchange/PaidTaxes
TKT VOID	A ticket is voided. For “Void/Refund”, a new Ticket Event is not created in the database.	Updated for the TKTD ticket number: TravelOrderEvent HostEventTimeStamp TransactionPseudo TransactionAgent DatabaseTimeStamp TktTrans ActiveVoidStatus = ‘V’ AirTktSeg FlightCouponStatus = ‘V’	Updated for the TKTD ticket number: TicketingData/: TicketEvent TPFTimeStamp PseudoCity TransactionAgent TicketTransaction/TicketStatus=“V” FlightCoupon/CouponStatus =”V”
REFUND	A ticket is refunded. For “Void/Refund”, a new Ticket Event is not created in the database.	Updated for the Refunded ticket number: TktTrans ActiveVoidStatus = ‘R’ AirTktSeg FlightCouponStatus = ‘R’ for refunded coupons FlightCouponStatus = ‘U’ for remaining coupons Updated with the Refund data in the event: TravelOrderEvent TktTrans RfndAirTax RfndAirTaxBrk RfndTrans Fop FopCrCrd	Updated for the Refunded ticket number: TicketingData/: TicketTransaction/TicketStatus=“R” FlightCoupon/CouponStatus =”R” for refunded coupons FlightCoupon/CouponStatus =”U” for remaining coupons Updated with the Refund data in the event: TicketingData/: TicketEvent TicketTransaction TaxRecord TaxRecord/TaxBreakdown RefundTrans TicketFOP TicketFOP/CreditCard
SVC FEE	When a Service Fee is transacted.	TravelOrderEvent SFTrans SFTax SFFop SFFopCrCrd	TicketingData/: TicketEvent ServiceFee ServiceFee/ServiceFeeTax ServiceFee/ServiceFeeFOP ServiceFee/ServiceFeeFOP/SFFOPCC