2 Logical Data Model

The logical data model of the Oracle Airlines Data Model defines the business entities and their relationships and provides an understanding of the business and data requirements for the Oracle Airlines Data Model data warehouse.

This chapter includes the following sections:

Reference Entities
Lookup Entities
Base Entities
Derived Entities
Aggregate Entities
Logical Data Model Entity Dictionary
Logical Data Model Dimensions Dictionary

Note:

The figures showing complete diagrams with attributes and entities are available with the Oracle Airlines Data Model IP Patch. The IP Patch includes additional documentation. For information on obtaining the IP Patch, see the Oracle Airlines Data Model Release Notes and for the latest information about Oracle Airlines Data Model patch sets, go to My Oracle Support at https://support.oracle.com.

Reference Entities

Reference Entities define the entities within, and associated with the airline organization for which data would be recorded and analyzed. Reference entities help define the structure of the organization.

Table 2-1 lists the reference entities.

Table 2-1 Reference Entity List

Entity List
ACCOUNT
AIRPORT
AWARD VOUCHER
BANK CARD
BOOKING CAMPAIGN
BOOKING OFFICE
BOOKING OFFICE USER
BOOKING PASSENGER DOCUMENT INFORMATION
BOOKING PASSENGER
BOOKING PRODUCT
BOOKING SEAT PREFERENCE
BOOKING SERIES
BOOKING SSR BRDG
BOOKING TRANSITIONAL STORE TICKET
BOOKING TST PRICE
BOOKING TST SEGMENT
CARRIER
CHECKIN BAGGAGE GROUP
CHECKIN INDIVIDUAL BAGGAGE
CODESHARE
CODESHARE BRIDGE
CUSTOMER SEGMENTATION
CUSTOMER SEGMENTATION DETAILS
FLIGHT
FREQUENT FLYER
GROUPING
INFLIGHT MEAL
LEG
LOYALTY ACCOUNT
LOYALTY LEVEL
ODT ACCOUNT
OPTION
PARTY
PASSENGER CONTACT
PASSENGER COUNTRY ADDRESS INFORMATION
PASSENGER VISA INFORMATION
PDI CHARACTERISTIC
PNR PARENT CHILD RELATIONSHIP
POINT OF SALE GDS OFFICE
SEAT
SEGMENT
SERVICE
SMS AGENT
SMS CUSTOMER
STATION
TICKET COUPON
TSM
TSM PASSENGER
VEHICLE
VIP PASSENGER INFORMATION

Lookup Entities

In Oracle Airlines Data Model lookup entities describe the relatively static or descriptive data in the data warehouse. Lookup entities define the descriptions for frequently used attributes. Using lookup entities saves space, as the referring fact table holds only a small key or code and foreign key, and Oracle Airlines Data Model stores the space consuming description in a lookup table and does not repeat the description in each transaction row in which it is referenced.

Table 2-2 lists the lookup entities.

Table 2-2 Lookup Entity List

Entity List
ACCOUNT LEVEL
ACCOUNT TRANSFER REASON
ACCOUNT TYPE
AIRCRAFT TYPE
AIRCRAFT VERSION
BANK CARD TYPE
BOOKING CLASS
BOOKING OTHER SERVICE
BOOKING REMARK
BOOKING SPECIAL SERVICE REQUEST
CARRIER TYPE
COMPENSATORY REASON
COMPLAIN CLASS
COMPLAIN TYPE
FARE ELEMENT
INTERACTION REASON
INTERACTION RESULT TYPE
LETTER TYPE
PARTY INTERACTION ITEM STATUS
PARTY STATUS
PASSENGER NAME RECORD TYPE
PDI CHANNEL
SALES CHANNEL
TRAFFIC CATEGORY
TSM EXCESS BAGGAGE
TSM MCO
TSM PRICE
TSM ROUTE
TSM SERVICE

Base Entities

Base entities define atomic level transaction data. Data in the base tables support the derived and aggregate layers, and act as a source for Data Mining for advanced analysis.

Table 2-3 lists the Base entities.

Table 2-3 Base Entity List

Entity List
ACCOUNT LEVEL HISTORY
ACCOUNT TRANSFER
AUX
BOOKING
CAR RENTAL
CHECKIN
COMPENSATORY EARNING
COMPLAIN ADVICE
DIRECT EARNING
EARNING EVENT
FLIGHT CHANGE
FLIGHT SCHEDULE
HOTEL BOOKING
LOYALTY ACCOUNT BALANCE HISTORY
LOYALTY ACCOUNT LEVEL HISTORY
LOYALTY CONVERSION
LOYALTY POINTS EXPIRE
LOYALTY PROGRAM
PARTNER EARNING
PARTY INTERACTION CALL
PARTY INTERACTION EMAIL
PARTY INTERACTION
PARTY INTERACTION FAX
PARTY INTERACTION ITEM
PARTY INTERACTION LETTER
PARTY INTERACTION SMS
PARTY INTERACTION THREAD
PARTY INTERACTION VISIT
PASSENGER NAME RECORD
PDI
SEGMENT SCHEDULE
TAS
TICKET
TICKET DELIVERY ARRANGEMENT
TOUR
TRANSFER EARNING

Derived Entities

Table 2-4 lists the Derived entities.

Table 2-4 Derived Entity List

Entity List
BOOKING FACT
CALL CENTER PERFORMANCE
CHECKIN FACT
CUSTOMER LIFE TIME VALUE SUPPORT VECTOR MACHINE FACTOR
CUSTOMER LOYALTY DECISION TREE RULES
CUSTOMER LOYALTY SUPPORT VECTOR MACHINE FACTOR
CUSTOMER MINING
CUSTOMER RECENCY FREQUENCY MONETARY PROFITABILITY SCORE
CUSTOMER SURVEY
FLIGHT DETAILS FACT
FREQUENT FLIER PREDICTION DECISION TREE RULES
FREQUENT FLIER PREDICTION SUPPORT VECTOR MACHINE FACTOR
LOYALTY ACCOUNT BALANCE HISTORY
LOYALTY ACCOUNT LEVEL HISTORY
LOYALTY PROGRAM
NON FREQUENT FLIER MINING
PASSENGER NAME RECORD
TICKET

Aggregate Entities

Aggregate entities hold data rolled up from the Base or Derived entities at different levels across different dimensional hierarchies.

Table 2-5 lists the Aggregate entities.

Table 2-5 Aggregate Entity List

Entity List
BOOKING DAILY INVENTORY SNAPSHOT
CHECKIN DAILY FACT
CUSTOMER SURVEY
DAILY BOOKING FACT
DAILY CALL CENTER PERFORMANCE
DAILY FLIGHT DETAILS
DAILY LOYALTY ACCOUNT
DAILY LOYALTY ACCOUNT BOOKING

Logical Data Model Entity Dictionary

Table 2-6 through Table 2-8 list the logical data model entities, in alphabetical order.

Table 2-6 A to G Entity Descriptions

Entity Name	Type	Description
`ACCOUNT`	Reference	Specifies the account number and the cost center associated with each BOOKING.
`ACCOUNT LEVEL`	Lookup	Lookup for the domain of Account Levels achievable within a Rewards Program. For example: Standard Premier Executive Premier
`ACCOUNT LEVEL HISTORY`	Base	Specifies ACCOUNT LEVEL change history.
`ACCOUNT TRANSFER`	Base	Represents the earnings transferred to or from an account.
`ACCOUNT TRANSFER REASON`	Lookup	Lookup for why the customer transfers points.
`ACCOUNT TYPE`	Lookup	Lookup for the type of account. For example: Bank Card Loyalty Card
`AIRCRAFT TYPE`	Lookup	Lookup for the type of Aircraft. For example Boeing 737.
`AIRCRAFT VERSION`	Reference	Specifies information about the AIRCRAFT TYPE. For example, if AIRCRAFT TYPE is Boeing 737 then Aircraft Version could be 800.
`AIRPORT`	Reference	Specifies an IATA recognized location that serves as an Origin or Destination of one or more flights, including details for the Airport. For example: Country City Region
`AUX`	Base	Represents ancillary information.
`AWARD VOUCHER`	Reference	Specifies the award voucher given by an airline.
`BANK CARD`	Reference	A bank card issued by an bank or credit organization.
`BANK CARD TYPE`	Lookup	Lookup for the type of the BANK CARD. For example: Credit card Debit card
`BOOKING`	Base	Captures Booking per Passenger (Segment wise per passenger). DOCO, DOCS, DOCA kept in a separate table with booking and passenger combination. Check for client indicator and other services which is explicitly linked to passengers.
`BOOKING CAMPAIGN`	Reference	Defines details of the Campaigns related to booking. One booking can be associated with a campaign.
`BOOKING CLASS`	Reference	Information about the booking class and its corresponding service class for the CARRIER. For example Service Class is Economy, and Booking Class may be A, B, C, and D. This booking class can fall under different services at a different point of time.
`BOOKING DAILY INVENTORY SNAPSHOT`	Aggregate	The status of bookings, cancellations, confirmations, and so on, as on date for future departures (starting the next day). The major dimensions of analysis for this fact are: Traffic category Segments Flights Snapshot date Booking Class Segment departure date
`BOOKING FACT`	Derived	Defines at the granularity of BOOKING SPECIAL SERVICE REQUESTs, BOOKING REMARKs, OPTIONs and BOOKING OTHER SERVICEs attached to each booking.
`BOOKING OFFICE`	Reference	Designator for a Travel Agent or Airline office as designated by IATA, a Global Distribution System (GDS), or an Airline.
`BOOKING OFFICE USER`	Reference	Represents Agent User Ids.
`BOOKING OTHER SERVICE`	Reference	Free texts of the booking for a CARRIER.
`BOOKING PASSENGER`	Reference	Passenger information for the booking. For example: Last name First name Gender Note: one booking can have two passengers only if there is an unseated infant.
`BOOKING PASSENGER DOCUMENT INFORMATION`	Reference	Personal details of the passenger. For example: Gender Nationality Date of birth
`BOOKING PRODUCT`	Reference	Product information associated with the booking which is mainly campaigns.
`BOOKING REMARK`	Reference	Different remarks for the BOOKING and the PASSENGER NAME RECORD.
`BOOKING SEAT PREFERENCE`	Reference	Represents preferences of seat by the passenger specified during BOOKING. One seat can have multiple preferences. For example: Aisle
`BOOKING SERIES`	Reference	Tour Operators (or sales people/Group Analysts on their behalf) enter their series requests for the upcoming season into the system. Each series request is for a certain number of seats, one-way on a certain SEGMENT, on a certain weekday for a certain period. The series itself is entered as a BOOKING and then every BOOKING that is part of that series is also entered as a BOOKING with a similar identifying Series-OSI- line. All bookings that belong to a certain series, whether it is the series itself or real BOOKINGs belonging to that series, have to be grouped together in a series-container.
`BOOKING SPECIAL SERVICE REQUEST`	Reference	Represents the status of the Special Service Request (SSR) and CARRIERs of the SSR for BOOKINGs.
`BOOKING SSR BRDG`	Reference	Represents a bridge table used to store information about the Special Service Requests (SSRs) used in a BOOKING.
`BOOKING TRANSITIONAL STORE TICKET`	Reference	Defines a Transitional Store Ticket (TST) generated with the BOOKING. The TST can be reused for other BOOKINGs having similar parameters. This determines the booking fare. A BOOKING can have two TSTs only if the passenger has an unseated infant.
`BOOKING TST PRICE`	Reference	Pricing information details for Transitional Store Ticket (TST).
`BOOKING TST SEGMENT`	Reference	Segment details of Transitional Store Ticket (TST), which has fare basis and stop over indicator information.
`CALL CENTER PERFORMANCE`	Derived	Specifies the daily performance summary data about call center.
`CAR RENTAL`	Base	Represents car rental related information.
`CARRIER`	Reference	This entity stores the details about the carrier, such as carrier code and description.
`CARRIER TYPE`	Reference	Carrier type details. For example: Airline Railway On road transport Ship
`CHECKIN`	Base	Entity specifies the checking information at the LEG level. TICKET, flight ID, pax ID can be derived from the booking ID for the PDI record. Provides the departure and arrival airport of the PDI from the LEG of the PDI. The LEG of the PDI is obtained using the booking ID and board and offpoint: You can refer booking ID for the PDI and get the flight and segment information for that particular date. Then refer flight schedule with the flight, SEGMENT and date for that booking ID it will give a unique LEG ID.
`CHECKIN BAGGAGE GROUP`	Reference	Defines information about the number of baggage checked-in, part of a baggage group, weight of the checked baggage of a group, number of hand baggage contained in the baggage group, and so on.
`CHECKIN DAILY FACT`	Aggregate	Daily fact for which data gets uploaded once at the end of day for the data to be available to the business users the next day. For example: Total number of check in for a day for a particular flight Total number of check in for a day for a SEGMENT Total number of check in for a day for a LEG Includes other measures. For example, total number of passengers checked-in in a particular day and is also based on other dimensions.
`CHECKIN FACT`	Derived	Checkin information at the LEG level.
`CHECKIN INDIVIDUAL BAGGAGE`	Reference	Information about the individual baggage during the check-in process. This information is mainly baggage tag, baggage source, baggage tag number, baggage tag final destination, and airline code.
`CODESHARE`	Reference	A marketing practice in which two or more airlines agree to share for marketing purposes. The same two letter code used to identify CARRIERs in the computer Reservation systems used by travel agents. Stores the details of the code share.
`CODESHARE BRIDGE`	Reference	Details about the code share flights along with the SEGMENT and CARRIER to which the flight belongs.
`COMPENSATORY EARNING`	Base	Specifies what the airline company awards, as points to customer as compensation for baggage lost or for a complaint.
`COMPENSATORY REASON`	Lookup	Lookup for the reason why compensatory points are awarded to a customer.
`COMPLAIN ADVICE`	Base	Defines a complaint or advice from customer, it is a subtype of PARTY INTERACTION THREAD.
`COMPLAIN CLASS`	Lookup	Lookup for the level of the complaint. For example: HIGH NORMAL
`COMPLAIN TYPE`	Lookup	Lookup for the complaint type. For example: Service complaint Baggage lost complaint
`CUSTOMER LIFE TIME VALUE SUPPORT VECTOR MACHINE FACTOR`	Derived	Represents Support Vector Machine (SVM) factors of attributes of customers, derived from customer life time value support vector machine mining model.
`CUSTOMER LOYALTY DECISION TREE RULES`	Derived	Represents Decision Tree rules, derived from customer loyalty decision tree mining model.
`CUSTOMER LOYALTY SUPPORT VECTOR MACHINE FACTOR`	Derived	Represents Support Vector Machine (SVM) factors of attributes of customers, derived from customer loyalty support vector machine mining model.
`CUSTOMER MINING`	Derived	Represents results of customer related mining models on latest customer data.
`CUSTOMER RECENCY FREQUENCY MONETARY PROFITABILITY SCORE`	Derived	Represents customers recency, frequency, monetary, and profitability score at month level.
`CUSTOMER SEGMENTATION`	Reference	Represents details of customer segments such as profile, support record count, dispersion, and so on.
`CUSTOMER SEGMENTATION DETAILS`	Reference	Provides details of customer segments, such as attributes and their values of customers in a segment. The segments are obtained from segmentation mining model.
`CUSTOMER SURVEY`	Derived	Specifies the daily summary data about customer survey result.
`DAILY CUSTOMER SURVEY`	Aggregate	Specifies the daily summary data about customer survey result.
`DAILY BOOKING FACT`	Aggregate	Defines the number of BOOKINGs, confirmed, canceled, ticketed, and so on, for a particular BOOKING date and SEGMENT departure date. The granularity of the fact is at a current date. All the bookings, confirmations, waitlisted information are calculated based on the fact that they are done on the current date.
`DAILY CALL CENTER PERFORMANCE`	Aggregate	Specifies the daily performance summary data about call center.
`DAILY LOYALTY ACCOUNT`	Aggregate	Specifies the daily summary data about loyalty account (for a FREQUENT FLYER).
`DAILY LOYALTY ACCOUNT BOOKING`	Aggregate	Specifies the daily summary data about loyalty account booking (for a FREQUENT FLYER).
`DAILY FLIGHT DETAILS`	Aggregate	Specifies the daily summary data about FLIGHT details.
`DIRECT EARNING`	Base	Earn points from flying with this airline s flight.
`EARNING EVENT`	Base	This event records all the point earnings of loyalty account.
`FARE ELEMENT`	Reference	This entity specifies the fare element details of the BOOKING and the TSM.
`FLIGHT`	Reference	Information about the FLIGHT is stored. For example the CARRIER which it belongs to or if there is an alpha suffix.
`FLIGHT CHANGE`	Base	Subtype of PARTY INTERACTION THREAD, about flight change or cancel.
`FLIGHT DETAILS FACT`	Derived	Provides information about LEG and SEGMENT of a particular flight. The airport and the aircraft information is at the LEG level.
`FLIGHT SCHEDULE`	Base	Information about schedule of the flight from the FLD system. Provides, on a daily basis, what are the FLIGHTs and how each FLIGHTs SEGMENTs and LEG and what are their expected departure and arrival time at the LEG level.
`FREQUENT FLIER BOOKING FACT APPLY`	Mining	Represents customer booking related facts for a period of months in the past.
`FREQUENT FLIER BOOKING FACT SOURCE`	Mining	Represents customer booking related facts for a period of months in the past.
`FREQUENT FLIER CUSTOMER LIFE TIME VALUE APPLY`	Mining	Represents customer life time value prediction mining model.
`FREQUENT FLIER CUSTOMER LIFE TIME VALUE SOURCE`	Mining	Represents customer life time value prediction mining model can be applied to predict the life time value of customers.
`FREQUENT FLIER CUSTOMER LOYALTY APPLY`	Mining	Specifies customer loyalty prediction mining model can be applied to predict the loyalty of customers.
`FREQUENT FLIER CUSTOMER LOYALTY SOURCE`	Mining	Provides source information for customer loyalty prediction mining model.
`FREQUENT FLIER CUSTOMER PROFILE APPLY`	Mining	Represents customer segmentation mining model can be applied.
`FREQUENT FLIER CUSTOMER PROFILE SOURCE`	Mining	Represents the source for customer segmentation mining model.
`FREQUENT FLIER LOYALTY ACCOUNT BALANCE APPLY`	Mining	Represents customer loyalty account balance details for the last number of months.
`FREQUENT FLIER LOYALTY ACCOUNT BALANCE SOURCE`	Mining	Represents customer loyalty account balance details for a period of months in the past.
`FREQUENT FLIER PREDICTION APPLY`	Mining	Represents non-frequent flier passengers demographic and BOOKING details. Frequent flier prediction among non-ffp mining model can be applied to predict frequent fliers among non-frequent flier passengers.
`FREQUENT FLIER PREDICTION DECISION TREE RULES`	Derived	Represents Decision Tree (DT) rules, derived from frequent flier prediction decision tree mining model.
`FREQUENT FLIER PREDICTION SOURCE`	Mining	Represents non-frequent flier passengers demographic and BOOKING details for a period months. Represents frequent flier prediction among non-frequent flier passengers mining model.
`FREQUENT FLIER PREDICTION SUPPORT VECTOR MACHINE FACTOR`	Derived	Provides SVM factors for attributes of non-frequent flier passengers. Those SVM factors can be derived from frequent flier prediction support vector machine mining model. SVM factor is a numeric value, which quantifies the importance of attribute in predicting the target.
`FREQUENT FLYER`	Reference	Frequent Flyer is an individual, whose frequency of usage of the airline is higher than normal passengers. Entity represents information about the frequent flyer. For example: Membership level Start date Airline
`GROUPING`	Reference	Grouping information required to determine the connecting flight. The grouping types can be marriages or physical connection.

Table 2-7 H to P Entity Descriptions

Entity Name	Type	Description
`HOTEL BOOKING`	Base	Represents hotel booking information.
`INFLIGHT MEAL`	Reference	The types of meals given during the flight. For example: VGML - Vegetarian Meal
`INTERACTION REASON`	Lookup	Lookup for the reason of the interaction thread. For example: Baggage lost Change flight
`INTERACTION RESULT`	Lookup	Lookup for result of response received from customer interaction. For example: Satisfy Dissatisfy
`INTERACTION RESULT TYPE`	Lookup	Lookup for type of response received from customer interaction. For example: Showed Interest without Decision Offer accepted Never call again
`LEG`	Reference	Leg is an operational term and means the physical operation between a departure station and the next arrival station. CARRIERs fly aircraft on Legs. This entity represents the attributes of the leg. For example: Terminal Board point Off point city
`LETTER TYPE`	Lookup	Lookup for type of letter sent to customer according to the content and purpose. For example: Direct Marketing Legal Letter Contract Confirmation letter (Welcome)
`LOYALTY ACCOUNT`	Reference	Typically, airline customers enrolled in the program accumulate frequent flyer miles (kilometers, points, segments) corresponding to the distance flown on that airline or its partners. Customers can acquire points on flights or by some other means. The acquired points can be redeemed for free air travel; for other goods or services; or for increased benefits such as travel class upgrades, airport lounge access, or priority bookings.
`LOYALTY ACCOUNT BALANCE HISTORY`	Base	The history of all the changes of one account. Including the earnings, redemption and expiration. Entity contains the current and historical balances of an account.
`LOYALTY ACCOUNT BALANCE HISTORY`	Derived	The daily summary of the LOYALTY ACCOUNT details.
`LOYALTY ACCOUNT LEVEL HISTORY`	Derived	The history of changes in the level of one LOYALTY ACCOUNT.
`LOYALTY ACCOUNT LEVEL HISTORY`	Base	The history of changes in the level of one LOYALTY ACCOUNT.
`LOYALTY CONVERSION`	Base	One airline can have several loyalty programs, customer may change their from one program to another program.
`LOYALTY LEVEL`	Reference	There are different levels in one loyalty program. For example: Bronze Silver Gold
`LOYALTY POINTS EXPIRE`	Base	Airline may have a points expiration policy. The points expire after a certain period of time the points in the account will expire.
`LOYALTY PROGRAM`	Base	Structured marketing efforts that reward, and therefore encourage loyal buying behavior.
`LOYALTY PROGRAM`	Derived	Structured marketing efforts that reward, and therefore encourage loyal buying behavior in derived layer.
`NON FREQUENT FLIER MINING`	Derived	Represents apply results of non-frequent flier related mining models on non-frequent fliers latest data.
`ODT ACCOUNT`	Reference	The ODT account tracks the financial or services interactions of a customer with the airline. Once set up, the customer can use the account to do self service at airlines Website or terminal. In this case normally the ODT account is protected by a password.
`OPTION`	Reference	Information about the message queues sent to a different office which holds different information about the BOOKING.
`PARTNER EARNING`	Base	Earn points from a partner.
`PARTY`	Reference	Any individual or organization of interest to the enterprise.
`PARTY INTERACTION`	Base	Specifies all interactions or communications with the customer. The interactions include: Faults Inbound and outbound telemarketing Direct mail SMS Email Service calls Debt collection Complaints
`PARTY INTERACTION CALL`	Base	Subtype of PARTY INTERACTION which represents all phone call interactions from the customer with details information including: holding, queuing, interaction time, run by the Automated Voice Response - AVR - or not.
`PARTY INTERACTION EMAIL`	Base	Subtype of PARTY INTERACTION, which represents the email interaction from customers.
`PARTY INTERACTION FAX`	Base	Subtype of PARTY INTERACTION, which represents the FAX interaction from customers.
`PARTY INTERACTION ITEM`	Base	The interaction items in each PARTY INTERACTION event. For example, in one party interaction event: customer call to the call center there can be several party interaction items: Change flight A to B Change flight C to D. Complain about food on flight E.
`PARTY INTERACTION ITEM STATUS`	Lookup	Documents the various states an interaction with a customer may be in. For example: Planned In-progress Executed Closed
`PARTY INTERACTION LETTER`	Base	Subtype of PARTY INTERACTION, which represents the interaction with customer through letter.
`PARTY INTERACTION SMS`	Base	Subtype of PARTY INTERACTION, which represents the SMS interaction from customers.
`PARTY INTERACTION THREAD`	Base	If customer makes multiple calls to complain about same issue, those calls are grouped into single thread.
`PARTY INTERACTION VISIT`	Base	Subtype of PARTY INTERACTION, which represents the visit interaction from customers.
`PARTY STATUS`	Lookup	The status of different types of party.
`PASSENGER CONTACT`	Reference	This is an operational layer entity stores the contact information of the passenger in the BOOKING.
`PASSENGER COUNTRY ADDRESS INFORMATION`	Reference	Essential documents about the passenger. For example: Country State Zip
`PASSENGER NAME RECORD`	Base	The complete details of a passenger's BOOKING, including itinerary, contact details, and special requests. A PASSENGER NAME RECORD is uniquely identified by a record locator. It stores RLOC and the offices which issues, owns and updates the PASSENGER NAME RECORD.
`PASSENGER NAME RECORD`	Derived	The complete details of a passenger's BOOKING, including itinerary, contact details, and special requests. A Passenger Name Record (PNR) is uniquely identified by a record locator. It stores RLOC and the offices which issues, owns and updates the PASSENGER NAME RECORD.
`PASSENGER NAME RECORD TYPE`	Lookup	Lookup for the type of PASSENGER NAME RECORD.
`PASSENGER VISA INFORMATION`	Reference	Visa details of the passenger.
`PDI`	Base	Passenger departure information.
`PDI CHANNEL`	Reference	Check-in channel origins. Acceptance channel types can be Front-End, KSK for Kiosk, MBL for Mobile check-in channel origin. For example: A for airline (check-in agent) S for Self-Service
`PDI CHARACTERISTIC`	Reference	Characteristics of the PDI.
`POINT OF SALE GDS OFFICE`	Reference	This entity stores to cater to a particular condition used to interpret the office.
`PNR PARENT CHILD RELATIONSHIP`	Reference	Parent child relationship of the PASSENGER NAME RECORD and gives details about the split PASSENGER NAME RECORDs.

Table 2-8 R to Z Entity Descriptions

Entity Name	Type	Description
`SALES CHANNEL`	Reference	Sales channel or alternatively called booking channel is derived from the BOOKING OFFICE which gives us the channel from which the BOOKING is performed.
`SEAT`	Reference	Passenger name of the seat number and seat status for the BOOKING.
`SEGMENT`	Reference	Segment is a commercial term and means a portion of a journey between boarding and disembarkation points. A Segment may cover one or more LEGs. CARRIERs publish schedules of segments and publish availability for each segment. Passengers reserve segments in a BOOKING. The Segment provides details such as board point airport and off-point airport.
`SEGMENT SCHEDULE`	Base	Stores the details of the date and time that a CARRIER has scheduled to the market.
`SERVICE`	Reference	The type of the postal service. For example: Ordinary mail Express
`SETTING CUSTOMER DECISION TREE`	Mining Support	Represents settings for Decision Tree algorithm.
`SETTING CUSTOMER SUPPORT VECTOR MACHINE`	Mining Support	Represents settings for Support Vector Machine (SVM) algorithm.
`SETTING PROFILE KMEANS`	Mining Support	Represents settings for K-means clustering algorithm.
`SETTING USER ALL`	Mining Support	Represents user settings.
`SMS AGENT`	Reference	Stores the corporate customer information.
`SMS CUSTOMER`	Reference	Stores the corporate customer information.
`STATION`	Reference	This entity stores the co-ordinates of a city (in hierarchy of a region). For example: Latitude Degrees
`TAS`	Base	Represents travel agency service related information.
`TICKET`	Base	Ticket means a document entitled "Passenger Ticket and Baggage Check" is issued by or on behalf of a CARRIER and includes the Conditions of Contract and notices and the Flight Coupons and Passenger Coupons contained therein. The ticket stores the ticket number and the issuing office for the ticket.
`TICKET`	Derived	Ticket means a document entitled "Passenger Ticket and Baggage Check" issued by or on behalf of a CARRIER and includes the Conditions of Contract and notices and the Flight Coupons and Passenger Coupons contained therein. It stores the ticket number and the issuing office of the ticket.
`TICKET COUPON`	Reference	Coupon means either a Flight Coupon or a Passenger Coupon. When used alone, it usually refers to a Flight Coupon. Stores details about the coupons.
`TICKET DELIVERY ARRANGEMENT`	Base	The ticket delivery arrangement for the TICKET. For example: Queue number Delivery system
`TOUR`	Base	Represents tour and tour related information.
`TRAFFIC CATEGORY`	Reference	Traffic Category is a term used for the purposes of categorization and reporting on Route Profitability to categorize the flights into: Atlantic Scheduled Flights Atlantic Ad-hoc Flights European Scheduled Flights European Ad-hoc Flights Near-East Scheduled Flights Near-East Ad-hoc Flights Domestic Flights Far East Flights Traffic category is used in combination with Traffic Area/Traffic Type for this purpose. In CADS, this categorization is split into two categorizations: Traffic Flight Type and Route Hierarchy Level 1. It stores the detailed information about the traffic category.
`TRANSFER EARNING`	Base	Points are transferred from one account to another.
`TSM`	Reference	The TSM is a pricing record associated to one passenger only, the one the MD PASSENGER NAME RECORD element is associated to. There is a TSM for each type of MD PASSENGER NAME RECORD element, composed of common TSM attributes, presented in this class, and specific ones (presented in class TSMMCO, TSMSVC, and TSMXSB). Stores details of the TSM.
`TSM EXCESS BAGGAGE`	Reference	This is a subset of TSM which stores the excess baggage charge details of the passenger of the TSM. This corresponds to the description of the charge for excess baggage. Stores information about the pricing carrier, price routing department, weight value, weight piece currency of the excess baggage.
`TSM MCO`	Reference	This is subset of TSM which stores the miscellaneous charge order of the TSM. Stores the details of the MCO. For example: Endorsement restrictions Tour code
`TSM PASSENGER`	Reference	Passenger personal information associated with a TSM.
`TSM PRICE`	Reference	Information about the fares and taxes, depending on the TSM type.
`TSM ROUTE`	Reference	The routes of TSM mainly the CARRIER from city to city and stop over indicator.
`TSM SERVICE`	Reference	This is a subset of TSM which stores the service fee for the TSM. Stores the details of Service Free (SVC). For example: Remarks Presento Presentat
`VEHICLE`	Reference	Details of the Vehicle which can be an aircraft, bus, ship, rail, and so on.
`VIP PASSENGER INFORMATION`	Reference	Information whether a passenger of the BOOKING is a VIP passenger.

Logical Data Model Dimensions Dictionary

Table 2-9 lists the logical data model dimension entities, in alphabetical order.

Table 2-9 Logical Data Model Dimensions

Entity Name	Type	Description
`ACCOUNT`	Dimension	The account number and the cost center associated with each BOOKING.
`AIRCRAFT TYPE`	Dimension	The type of Aircraft Type. For example Boeing 737.
`AIRCRAFT VERSION`	Dimension	Information about the Aircraft Type. For example Aircraft type is Boeing 737. Aircraft version for Boeing 737 is 800.
`AIRPORT`	Dimension	Airport means an IATA recognized location that serves as an Origin or Destination of one or more flights. Details of the Airport. For example: Country City Region
`BOOKING CLASS TYPE`	Dimension	The booking class hierarchy information for the BOOKING. The booking class values can be A to Z (that is 26 in number).
`BOOKING OFFICE`	Dimension	Designator for a Travel Agent or Airline office as designated by IATA, a Global Distribution System (GDS), or an Airline.
`BOOKING PASSENGER`	Dimension	Passenger information of the BOOKING. For example: Last name First name Gender One booking can have two passenger only if there is an unseated infant.
`BOOKING TST`	Dimension	This is a Transitional Store Ticket (TST) which gets generated when the booking is done. This TST can be reused for other bookings having similar parameters. This determines the fare of the booking. A booking can have two TST only if the passenger has an unseated infant.
`CALENDAR`	Dimension	This is a global entity which stores date hierarchy with a granularity as date and then gives week, month, quarter, and year.
`CARRIER`	Dimension	This entity stores the details about the carrier, such as carrier code and description.
`CITYPAIRS`	Dimension	Specifies the city pairs as provided by the source system.
`CORPORATE CUSTOMER`	Dimension	The details for the corporate customer. For example: Name Location Customer division
`COUNTRY`	Dimension	This is a global entity stores the different countries and their related attributes.
`CURRENCY`	Dimension	Currencies used for transactions in different countries.
`FARE TYPE`	Dimension	Fare Type means a designator that is used to Categorize Fares. For example: APEX PEX IT It stores booking class fare types.
`FLIGHT`	Dimension	Information about the flight is stored. For example the carrier which it belongs to or if there is an alpha suffix associated. Each flight has a number and carrier associated and is designated to fly in a particular schedule attached.
`FREQUENT FLYER`	Dimension	Frequent Flyer is an individual, who frequency of usage of the airline is higher than normal passengers. It stores information about the frequent flyer. For example: Membership level Start date Airline
`GEOAREAS`	Dimension	Specifies the GEOAREAS as assigned by the business.
`GEOGRAPHY`	Dimension	This is a type of dimension with a granularity of city. It has country, continent, and so on as other levels of hierarchy.
`INTERACTION REASON`	Dimension	The reason for the interaction thread. For example: Baggage lost Change flight
`INTERACTION RESULT`	Dimension	Result of response received from customer interaction. For example: Satisfy Dissatisfy
`LEG`	Dimension	Leg is an operational term and means the physical operation between a departure station and the next arrival station. CARRIERs fly Aircraft on Legs. It stores the attributes of the leg. For example: Terminal Board point Off point city
`LOYALTY LEVEL`	Dimension	Different levels in a loyalty program.
`MARKETAREAS`	Dimension	Market Area is a term used for grouping Operational City Pairs for REKA reporting. It stores the attributes related to market areas.
`PDI CHANNEL`	Dimension	Check-in channel origins. Acceptance channel types can be Front-End, KSK for Kiosk, MBL for Mobile check-in channel origin. For example: A for airline (check-in agent) S for Self-Service
`ROUTES`	Dimension	Route means a number of flights that carry the same Flight Number. For example: 831 HEL-LHR. Only one Flight operates on a Route on any given day. For direct flights each Route covers only one LEG (outbound or inbound). For multi-leg out-and-return flights each Route covers all legs of each direction (For example: HEL-BKK-SIN). For triangular flights each Route can either cover the whole triangle (For example: HEL-TXL-HAM-HEL), or part of it. For example: HEL-OUL-RVN part of HEL-OUL-RVN-HEL)
`ROUTEPAIRS`	Dimension	Route Pair means a grouping of Routes. It is a synonym for Route Hierarchy Level 5. Usually a Route Pair is the combination of two Route Numbers in both Directions, but sometimes not. For example: Route Pair 0152/0157/0158 MOW contains Routes 0152, 0157 and 0158. For multi-leg out-and-return flights the Route Pair is named after the end stop of the flight (0097/0098 SIN for 0097 HEL-BKK-SIN). For triangular flights the Route Pair can either be named after the whole Journey (0439/0440 OUL/RVN for 0439 HEL-OUL-RVN), or only the first stop (0911/0912 BER for 0911 HEL-TXL-HAM-HEL).
`SALES CHANNEL`	Dimension	Sales channel or alternatively called booking channel is derived from the office which gives us the channel from which the booking is done
`SEGMENT`	Dimension	Segment is a commercial term and means a portion of a journey between boarding and disembarkation points. A Segment may cover one or more LEG CARRIERs publish schedules of segments and publish availability for them. Passengers reserve segments on a Booking. It stores segment details like the board point airports and off-point airports.
`SEGMENT PAIR`	Dimension	Segment Pair is a specific term which means board and off points identified by the business are logically grouped and used for analysis of booking between these points. For example HELBOMVV, that is Helsinki Bombay, vice versa.
`SERVICE`	Dimension	The services provided by the airline company, services are grouped by service type. For example: Schedule / Itinerary Reservation&TktCheck-In Boarding Lounge
`SPECIAL SERVICE REQUEST`	Dimension	The Special Service Request (SSR) is a request to an airline for services or amenities other than standard, such as wheelchair usage, meals for special diets, and so forth. The Special Service Request captures the information of the history and current service request information added, deleted from the source system.
`TIME`	Dimension	This is a global dimension which stores the details in the granularity of minutes which rolls up to hour.
`TRAFFIC CATEGORY`	Dimension	Traffic Category is a term used for the purposes of categorization and reporting on Route Profitability to categorize the flights into: Atlantic Scheduled Flights Atlantic Ad-hoc Flights European Scheduled Flights European Ad-hoc Flights Near-East Scheduled Flights Near-East Ad-hoc Flights Domestic Flights Far East Flights It is used in combination with Traffic Area/Traffic Type for this purpose. In CADS, this categorization is split into two categorizations: Traffic Flight Type and Route Hierarchy Level 1. It stores the detailed information about the traffic category.