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:
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 athttps://support.oracle.com
.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.
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.
Entity List |
---|
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.
Entity List |
---|
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-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 |
---|---|---|
Reference |
Specifies the account number and the cost center associated with each BOOKING. |
|
Lookup |
Lookup for the domain of account levels achievable within a LOYALTY PROGRAM. For example:
|
|
Base |
Specifies ACCOUNT LEVEL change history. |
|
Base |
Specifies details of each allocation of money from a receipt made by a party to a specific account. It is the receipt of a single sum of money from a party as a credit against an outstanding balance for the provision or supply of products or services. |
|
Base |
Represents the earnings transferred to or from an ACCOUNT. |
|
Lookup |
Lookup for why the customer transfers points. |
|
Lookup |
Lookup for the type of account. For example:
|
|
Reference |
An ordinary postal address for the PARTY or site. |
|
Reference |
History of the names and addresses associated with an ORGANIZATION, PROSPECT, or CUSTOMER. |
|
Reference |
This is an operational layer entity which stores the relationship between two addresses. Associates one address with other addresses. For example:
|
|
Lookup |
Lookup for address type. For example:
|
|
Reference |
Subtype of party, who collects the customer debt on behalf of the CARRIER under some financial agreements. For example:
|
|
Reference |
An aircraft is a machine that is able to fly. It counters the force of gravity by using either static lift or by using the dynamic lift of an airfoil, or in a few cases the downward thrust from jet engines. |
|
Lookup |
Lookup for the type of Aircraft. For example: Boeing 737. |
|
Reference |
Specifies information about the AIRCRAFT TYPE. For example, if AIRCRAFT TYPE is Boeing 737 then aircraft version could be 800. |
|
Reference |
Specifies an International Air Transport Association (IATA) recognized location that serves as an Origin or Destination of one or more flights, including details for the Airport. For example:
|
|
Lookup |
Specifies the different types of amount. This is similar to the different types of revenue and cost. For example:
|
|
Reference |
Specifies the award voucher given by an airline. |
|
Reference |
Specifies information about banks. |
|
Reference |
A bank card issued by a bank or credit organization. |
|
Lookup |
Lookup for the type of the BANK CARD. For example:
|
|
Lookup |
Lookup defining reasons a customer may be banned from using a service. |
|
Reference |
The abstracted information about a day, which serves as a base for DAY. |
|
Base |
Billing Analysis System Output Information |
|
Base |
Billing Office Subtotals per Transaction Code and Currency Type |
|
Base |
The header of a billing office transaction document. |
|
Base |
Billing Office Subtotals per Transaction Code and Currency Type |
|
Base |
Billing Office Totals per Currency Type. |
|
Base |
Airline agency detailed information from billing transaction data. |
|
Base |
The information about billing transaction complete form of payment |
|
Base |
The billing transaction complete ticket document information. |
|
Base |
Additional information of billing transaction coupon. |
|
Base |
Detailed amount data from transaction document. |
|
Base |
The control data of each billing transaction. |
|
Base |
The billing transaction coupon detail data from ELECTRONIC MISCELLANEOUS DOCUMENT (EMD). |
|
Base |
The billing transaction remarks from ELECTRONIC MISCELLANEOUS DOCUMENT(EMD). |
|
Base |
The fare calculation elements of billing transaction. |
|
Base |
The currency information of billing transaction. |
|
Base |
The payment data of each billing transaction. |
|
Base |
Billing transaction header data. |
|
Base |
Billing transaction additional information from MISCELLANEOUS DOCUMENT. |
|
Base |
Billing transaction amount information from MISCELLANEOUS DOCUMENT. |
|
Base |
Billing transaction issuance reason information from MISCELLANEOUS DOCUMENT. |
|
Base |
Billing transaction netting values. |
|
Base |
Billing transaction payment authorization information. |
|
|
Base |
Billing transaction prepaid ticket advice sponsor information. |
Base |
The information about billing transaction related ticket. |
|
Base |
The information about billing transaction ticket. |
|
Base |
The amount information about billing transaction ticket. |
|
Base |
The commission information about billing transaction ticket. |
|
Base |
Form of payment information of billing transaction ticket. |
|
Base |
Billing transaction ticket itinerary data segment. |
|
|
Base |
Billing transaction ticket miscellaneous additional print lines. |
Base |
The passenger information of billing transaction ticket. |
|
Base |
Billing transaction ticket qualifying issue information. |
|
Base |
The tax on commission data for billing transaction ticket. |
|
Base |
The Value Added Tax (VAT) information of billing transaction ticket. |
|
Base |
To keep track of black listed customers. Those records might be because of late payment, default, or fraud. |
|
Base |
The entity used to store all the main booking related information. This is at each individual passenger level and segment level. |
|
Base |
The detailed operations for each agent and each booking. |
|
Base |
The billing information about each booking. |
|
Base |
This is an operational layer entity which stores the details of the campaigns related to the booking. |
|
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. |
|
Reference |
Booking class type is another type of grouping of booking class, other than "Service Class". You can define your own grouping rule according to your business scenario. |
|
Aggregate |
Specifies 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:
|
|
Derived |
Defines at the granularity of BOOKING SSRs, BOOKING REMARKs, OPTIONs and BOOKING OTHER SERVICEs attached to each BOOKING. |
|
Reference |
Designator for a Travel Agent or Airline office as designated by IATA, a Global Distribution System (GDS), or an Airline. |
|
Reference |
This is an operational layer entity which stores the user ids given to the agent using which they login to the system to do the booking. All agents belong to an office. These signs are sets of user ids assigned to the offices. |
|
Reference |
Specifies free text of the booking for a CARRIER. |
|
Reference |
Passenger information for the booking. For example:
Note: one booking can have two passengers only if there is an unseated infant. |
|
Reference |
Personal details of the passenger. For example:
|
|
Reference |
Product information associated with the BOOKING. For example a CAMPAIGN. |
|
Reference |
Specifies the details of the booking products. For example:
|
|
Lookup |
Specifies the product type. For example:
|
|
Reference |
||
Reference |
This is an operational layer entity which stores the name of the seat number and seat status for the BOOKING. |
|
Reference |
Represents preferences of seat by the passenger specified during BOOKING. One seat can have multiple preferences. For example: window, aisle. |
|
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. |
|
Base |
Represents the status of the Special Service Request (SSR) and CARRIERs of the Special Service Requests for BOOKINGs. |
|
Reference |
Represents a bridge table used to store information about the Special Service Requests (SSRs) used in a BOOKING. |
|
Base |
This entity is used to store the BOOKING change history. |
|
Lookup |
This entity is used to store the BOOKING change reason. |
|
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. |
|
Base |
Booking transaction store ticket fare data. |
|
Base |
Booking transaction store ticket tax data. |
|
Reference |
Pricing information details for Transitional Store Ticket (TST). |
|
Reference |
Segment details of Transitional Store Ticket (TST), which has fare basis and stop over indicator information. |
|
Base |
Booking TST Tax information. |
|
Reference |
Defines month-in-half in a business calendar. |
|
Reference |
Defines half year in a business calendar. |
|
Lookup |
The legal status of the company. For example:
|
|
Reference |
Defines month in a business calendar. |
|
Reference |
Defines quarter in a business calendar. |
|
Reference |
Capture the specific job role for an organization. |
|
Reference |
Work shift associated with the Business Unit, mapped to the EMPLOYEE job roles for the allocation for these shifts. For example, there could be two shifts for a cashier in a store per day: 6:00am-2:00pm, 2:00am-10:00pm. |
|
Reference |
Weeks as defined in the business calendar. |
|
Reference |
Defines year in a business calendar. |
|
Reference |
This is a global entity which stores date hierarchy with a granularity as date and then gives week, month, quarter, and year. |
|
Reference |
Defines month-in-half in a Gregorian or Normal Calendar. |
|
Reference |
Defines half year in a Gregorian or Normal Calendar. |
|
Reference |
Calender month in a Gregorian or Normal Calendar. |
|
Reference |
Defines quarter in a Gregorian or Normal Calendar. |
|
Reference |
Defines weeks in a Gregorian or Normal Calendar. |
|
Reference |
Defines years in a Gregorian or Normal Calendar. |
|
Reference |
The carrier may have multiple call centers in different locations, for different time zones or language purposes. |
|
Reference |
All the possible agents with whom the customer can make a contact. For example:
|
|
Derived |
Specifies the daily performance summary data about call center. |
|
Reference |
Assigns the languages, products, or geographical areas which the call center can serve to the call center. |
|
Reference |
A campaign is a concentrated effort to enhance the image of the enterprise in order to retain, acquire or consolidate customers. |
|
Reference |
The history of campaign party role about the management of a campaign. The party can be not only the sales or marketing employee at the carrier, it can also be a campaign partner. |
|
Reference |
Items presented to customer or public as part of the CAMPAIGN. |
|
Reference |
Holds details about the execution message used in a CAMPAIGN. |
|
Lookup |
This entity keeps strategy or business objective of the CAMPAIGN. |
|
Lookup |
This entity keeps types of CAMPAIGNs. For example:
|
|
Reference |
One of the product type, car, example: rental car service |
|
Base |
The main entity to store the car rental transaction information. |
|
Base |
Car rental additional rate related information. |
|
Base |
The rental car charge period information. |
|
Base |
Car rental estimate distance with different rental type |
|
Base |
Car rental form of payment. |
|
Reference |
Car rental related location information. For example pick up location. |
|
Base |
The rental car model information. |
|
Base |
The other rules of the different type of rental car package. |
|
Base |
The other rate rule related date information of the car rental. |
|
Base |
The customer preference car type data. |
|
Base |
The remarks of rental car transaction. |
|
Base |
The surcharge period of the car rental transaction. |
|
Base |
The car rental surcharge period tariff. |
|
Base |
The car rental tariff information. |
|
Base |
The car rental tariff charge information. |
|
Reference |
This entity stores the details about the carrier, such as carrier code and description. Carrier means the airline issuing the ticket and all airlines that carry or undertake to carry the Passenger and or his baggage thereunder or to perform any other service related to such air carriage (IATA PAT-GR-1). |
|
Reference |
Carrier type details. For example:
|
|
Reference |
A certificate with a face monetary value issued by a store for subsequent exchange for merchandise. |
|
Reference |
The different types of channel of airline, including booking or ticketing channel, checkin channel, marketing channel, and so on. |
|
Base |
Specifies the checking information at the LEG level. TICKET, flight ID, passenger 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: |
|
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. |
|
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:
Includes other measures. For example, total number of passengers checked-in in a particular day and is also based on other dimensions. |
|
Derived |
Check-in information at the LEG level. |
|
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. |
|
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. |
|
Reference |
Details about the code share flights along with the segment and CARRIER to which the flight belongs. |
|
|
Aggregate |
This entity stores details about the codeshare flights along with the segment and CARRIER to which the flight belongs. |
Reference |
A characteristic quality or distinctive feature of a Competitor Intelligence. The characteristic can be take on a discrete value, such as number of press releases, can take on a range of values, (for example, number customers within a MARKET SEGMENT (50,000 - 100,000), or can be derived from a formula (for example, number of products offered in a MaketSegment = the number of the Competitor's Product instances associated to the MARKET SEGMENT). |
|
Reference |
A number or text that can be assigned to a COMP INTEL CHARACTERISTIC. |
|
Reference |
A MARKET SEGMENT in which a Competitor makes Product available. |
|
Reference |
Assign the Competitor Product Correlation CHARACTERISTIC to the related competitor intelligence characteristic. |
|
Reference |
A number or text that can be assigned to a CompProdCorrelationCharacteristic. |
|
Base |
Specifies what the airline company awards, as points to customer as compensation for baggage lost or for a complaint. |
|
Lookup |
Lookup for the reason why compensatory points are awarded to a customer. |
|
Reference |
Type of Competitors according to their size, revenue, line of product, and so on. A classification of a Competitor, such as by size, product lines offered, and so forth. |
|
Reference |
A PARTY that offers Product similar to the enterprise's PRODUCT ENTITY in a MARKET SEGMENT. |
|
Reference |
Intelligence gathered about each competitor. Facts gathered about a Competitor's plans and activities. These facts can be used to perform Competitor SWOT analysis in order to better understand a Competitor. |
|
Reference |
Specifies the PARTY who generated the intelligence. |
|
Reference |
A MARKET SEGMENT served by a Competitor. |
|
Reference |
Strength, Weakness, Opportunity, or Threat in a MARKET SEGMENT served by a Competitor. |
|
Reference |
How the product market plan are related to competitor product market plans, with its all flexible characteristics. |
|
Reference |
General (non-MARKET SEGMENT specific) Strength, Weakness, Opportunity, or Threat when compared to a Competitor. |
|
Reference |
A classification of a Competitor, such as by size, product lines offered, and so forth. |
|
Base |
Defines a complaint or advice from customer, it is a subtype of PARTY INTERACTION THREAD. |
|
Lookup |
Lookup for the level of the complaint. For example:
|
|
Lookup |
Lookup for the complaint type. For example:
|
|
Reference |
The details for the corporate customer. For example:
|
|
Base |
Define the cost might incurred from any operation or event which is trackable at certain level. For example are:
|
|
Reference |
To categorize the different cost charges inside the CARRIER for different purpose. 1 organization can own multiple cost center for different project/product operation. |
|
Reference |
Specifies reference financial rating scores for each customers to the service provider. It is also called Credit rating agency. |
|
Lookup |
Currency information |
|
Reference |
A customer is the recipient of a good, service, product, or idea, obtained from a seller, vendor, or supplier for a monetary or other valuable consideration. For example:
|
|
Reference |
Subtype of CUSTOMER (and PARTY), which contains details of individuals as opposed to organizations. |
|
Derived |
Represents Support Vector Machine (SVM) factors of attributes of customers, derived from customer life time value support vector machine mining model. |
|
Derived |
Represents Decision Tree rules, derived from customer loyalty decision tree mining model. |
|
Derived |
Represents Support Vector Machine (SVM) factors of attributes of customers, derived from customer loyalty support vector machine mining model. |
|
Derived |
Represents results of customer related mining models on latest customer data. |
|
Reference |
It stores an event celebrated or observed by a customer. For example:
|
|
Lookup |
A categorization of CUSTOMER OCCASIONs. |
|
Base |
ORDER placed by a CUSTOMER for merchandise or services to be provided at some future date and time. |
|
Base |
A line item component of a CUSTOMER placed ORDER. |
|
Reference |
Subtype of CUSTOMER (and PARTY), which contains details of organizations as opposed to individuals. Note: an organization can also consist of one individual only. |
|
Derived |
Represents customers recency, frequency, monetary, and profitability score at month level. |
|
Reference |
It captures the restricted information for the customer or prospects. |
|
Lookup |
Customer classification in its income/revenue term. For example:
|
|
Reference |
Determine revenue band of customer. CUSTOMER REVENUE BAND may drift month by month. |
|
Lookup |
Lookup for type of revenue customer may bring to the CARRIER. |
|
Reference |
Scores or Score ranges that may be assigned to a customer based on credit, behavior, or other criteria.For example,1,2,3,4,5 or 1~10,11~20. Customer score can be rated based on the Customer Behavior, Credit, or another criteria. |
|
Reference |
The Segments table holds details of customer segments identified by business analysis activities, for example data mining. A segment identifies distinct groupings of customers or accounts with similar characteristics. The segments are typically used in marketing campaigns |
|
Reference |
Represents details of customer segments such as profile, support record count, dispersion, and so on. |
|
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. |
|
Reference |
The segmentation model used to profile the customers. For example, KMeans by Revenue from Market Department, O-Clustering by IT department, and so on. |
|
Aggregate |
How the customer came in touch to the sales team. Like Campaign, Advertisement, Call center, Dealer, and so on. It is important for campaign planning and management |
|
Aggregate |
This entity contains the daily summary data about customer survey result. |
|
Derived |
This entity contains the daily summary data about customer survey result. |
|
Lookup |
This level identifies or groups customers as Corporate customers or Individuals. |
|
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. This entity is a fact table storing 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, and waitlisted information are calculated based on the fact that they are done on the current date. |
|
Aggregate |
Specifies the daily performance summary data about the call center. |
|
Aggregate |
Specifies the daily summary data about customer survey results. |
|
Aggregate |
Specifies the daily summary data about FLIGHT details. |
|
Aggregate |
Specifies the daily summary data about LOYALTY ACCOUNT (for a FREQUENT FLYER). |
|
Aggregate |
Specifies the daily summary data about LOYALTY ACCOUNT booking (for a FREQUENT FLYER). |
|
Reference |
Day level in the normal calendar. |
|
Reference |
The PARTY who resells products or services from the CARRIER. |
|
Reference |
A sub-level group or category further qualifying a set of data (Profile Group) collected about a customer to assist in marketing efforts. For example:
|
|
Reference |
The domain of classifications used to group profile information about a PARTY. For example:
|
|
Reference |
This entity stores the derived value of the customer. These value could have multiple value types or value measures. |
|
Base |
Earn points from flying with this airline. |
|
Reference |
Keeps the special discount groups of employee or Partner. EMPLOYEEs in different level have a different discount group. For example:
Different Dealer or partner may also have different discount policy according to their relationship with Service provider and sales volume. |
|
Base |
This event records all the point earnings of LOYALTY ACCOUNT. |
|
Reference |
The education level of the customer |
|
Reference |
E-mail address associated with a location. |
|
Reference |
Employee of the carrier. This is a sub entity of party individual. |
|
Base |
The actual shifts the hourly employees have worked in, including break time. |
|
Base |
This table records the actual shifts worked in for the salaried employees. To be further investigated, difference with "xxx hourly". |
|
Lookup |
The various designations present in an organization for the employees. |
|
Reference |
The relationship between employee discount group.1 employee should have several discount group, several employee should have the same discount group. |
|
Reference |
Keep the relationship between employee and job role. |
|
Reference |
The languages the employee can serve, especially for call center agent and sales shopper representatives. |
|
Reference |
Specifies the restricted information for the employee. |
|
Reference |
This entity stores the planned schedule for an employee, which consists of the store, job role and shift the employee is planned to be working for. |
|
Base |
A record that a particular employee has been trained in performing a particular task. |
|
Lookup |
This lookup describes types of EMPLOYEE. For example:
|
|
Base |
This entity relates parties with events. A PARTY can have many events; and an event can involve many parties. |
|
Base |
The PARTY INTERACTION table records all interactions or communications with the customer. The interactions include:
|
|
Reference |
A source of information that helps define a credit worthiness of the customer. |
|
Reference |
To indicate which external agency/institute provided the credit profile for the given customer. |
|
Lookup |
The type of different external organization. |
|
Reference |
This entity specifies the fare element details of the BOOKING and the TSM. This is an operational layer entity which stores the fare element details of the booking and TSM. |
|
Reference |
Fare Type means a designator that is used to Categorize Fares. For example:
It stores booking class fare types. This is an analytical layer dimension which stores the booking class fare types. |
|
Reference |
Defines half-month in a fiscal calendar. |
|
Reference |
Defines half-year in a fiscal calendar. |
|
Reference |
Defines month in a fiscal calendar. |
|
Reference |
Defines quarter in a fiscal calendar. |
|
Reference |
Defines week in a fiscal calendar. |
|
Reference |
Defines year in a fiscal calendar. |
|
Reference |
Information about the FLIGHT is stored. For example the CARRIER which it belongs to or if there is an alpha suffix. This is an operational layer entity which stores the information about the flight. For example, the CARRIER which it belongs to or if there is an alpha suffix associated. |
|
Base |
Subtype of PARTY INTERACTION THREAD, about flight change or cancel. |
|
Derived |
Provides information about LEG and segment of a particular flight. The airport and the aircraft information is at the LEG level. This entity is a factless fact table which provided information about leg and segment of a particular flight. The airport and the aircraft information is at the leg level |
|
Reference |
The main entity for airline flight inventory information. |
|
Reference |
This entity specifies the number of units of data which will be used to present different KPIs about flight inventory. |
|
Lookup |
The different operation type of flight inventory. |
|
Reference |
The operations of flight inventory. |
|
Reference |
The assignment entity to manage the many to many relationship between flight inventory and flight schedule. |
|
Reference |
The status of flight inventory. |
|
Reference |
The flight inventory data at LEG level. |
|
Reference |
The cabin configuration data at LEG level. |
|
Reference |
The block space information about each cabin at LEG level. |
|
Reference |
The LEG level cabin configuration for each aircraft. |
|
Reference |
Revenue control value for the leg-cabin. |
|
Reference |
The LEG level cabin configuration for marking sales. |
|
Reference |
The detailed characteristic about cabin configuration. |
|
Reference |
The special service request (SSR) for flight inventory at LEG level. |
|
Reference |
The other options for special service request (SSR) at LEG level. |
|
Reference |
The LEG level inventory status. |
|
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. This entity gives information about the schedule of the flight from the FLD system. This gives on a daily basis what are the flights and how each flights are having segments and legs and what are their expected departure and arrival time at the leg level. |
|
Reference |
The Segment level inventory main entity. |
|
Reference |
This is the flight segment inventory information at cabin level. |
|
Reference |
The segment level inventory update by DCS input. |
|
Reference |
The cabin class data at segment level. |
|
|
Reference |
The segment level cabin booking class boarding data. |
|
Reference |
The segment level boarding figures related to code share flight |
Reference |
The segment level cabin class configuration. |
|
Reference |
Segment level cabin class status. |
|
Reference |
Segment level cabin subclass. |
|
|
Reference |
Segment level cabin subclass availability. |
Reference |
The segment level cabin subclass counters |
|
Reference |
The segment level cabin subclass date flags. |
|
Reference |
The segment level cabin subclass flag data. |
|
Reference |
The segment level cabin subclass NEGO. |
|
Reference |
Segment level cabin subclass yield. |
|
|
Reference |
The segment level cabin boarding data from DCS. |
Reference |
The segment level cabin inventory data for code share flight. |
|
Reference |
The segment level cabin blockspace data for code share flight. |
|
Reference |
The segment level inventory data for code share flight. |
|
Reference |
The segment level inventory status data. |
|
Reference |
The segment level inventory traffic restriction data. |
|
Reference |
All kinds of form of payment. |
|
Mining |
Represents customer booking related facts for a period of months in the past. |
|
Mining |
Represents customer booking related facts for a period of months in the past. |
|
Mining |
Represents customer life time value prediction mining model. |
|
Mining |
Represents customer life time value prediction mining model can be applied to predict the life time value of customers. |
|
Mining |
Specifies customer loyalty prediction mining model can be applied to predict the loyalty of customers. |
|
Mining |
Provides source information for customer loyalty prediction mining model. |
|
Mining |
Represents customer segmentation mining model can be applied. |
|
Mining |
Represents the source for customer segmentation mining model. |
|
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:
|
|
Reference |
The different types of preference of frequent flyer passenger. |
|
Mining |
Represents customer LOYALTY ACCOUNT balance details for the last number of months. |
|
Mining |
Represents customer LOYALTY ACCOUNT balance details for a period of months in the past. |
|
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. |
|
Derived |
Represents Decision Tree (DT) rules, derived from frequent flier prediction decision tree mining model. |
|
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. |
|
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. |
|
Reference |
Specifies the gender. For example, male or female. |
|
Reference |
This is a type of dimension with a granularity of city. It has country, continent, and so on as other levels of hierarchy. This is an analytical layer entity of the type dimension with a granularity of city. It has country, continent, and so on, as other levels of hierarchy. |
|
Reference |
User defined classifications for Demographic attributes. For example:
|
|
Reference |
User defined classifications for a demographic profile group. For example:
|
|
Reference |
Values associated with a geographic location as defined by the GEOGRAPHY DEMOGRAPHY ATTRIBUTES. |
|
Reference |
Geographic entities to define the location of an address. For example:
|
|
Reference |
Type of geographic hierarchy. For example:
|
|
Reference |
Associative entity for GEOGRAPHY HIERARCHY and GEOGRAPHY LEVEL, mapping levels to hierarchies. |
|
Reference |
Assignment of a GEOGRAPHY HIERARCHY LEVEL to a GEOGRAPHY ENTITY; assigns geography values to hierarchy levels. |
|
Reference |
The different versions of geography hierarchy. |
|
Reference |
User defined Hierarchical levels for the GEOGRAPHY HIERARCHYs. |
|
Reference |
Values as defined by geography level attributes for a GEOGRAPHY HIERARCHY LEVEL. |
|
Reference |
User defined attributes associated with a specific GEOGRAPHY LEVEL. |
|
Reference |
Grouping information required to determine the connecting flight. The grouping types can be marriages or physical connection. This is an operational layer entity which stores the grouping information required to determine the connecting flight. The grouping types can be marriages or physical connection |
Table 2-7 H to Q Entity Descriptions
Entity Name | Type | Description |
---|---|---|
Reference |
Half-hours defined as part of time. |
|
Reference |
Todate transformation information at the half-month level. |
|
Reference |
Transformations for half-month. For example:
|
|
Reference |
Cumulative time transformations at the half-year level. |
|
Reference |
Transformations for half-year. For example:
|
|
Base |
HOT File Control Information The Hand Off Tape (HOT) is so called because originally, this file was made available to users on a magnetic tape or floppy disk. The term has stuck and the universal generic term for the flat or text (.txt) billing file is HOT file. |
|
Base |
Represents hotel booking information. |
|
Base |
The billable information for hotel booking transaction. |
|
Base |
The commission data for hotel booking. |
|
Reference |
The customer contact information for hotel booking. |
|
Reference |
Hotel booking reference information, it can be used to linked to any event. For example flight booking or any customer interaction. |
|
Reference |
The form of payment information for hotel booking. |
|
Reference |
The miscellaneous remarks of hotel booking. |
|
Reference |
The free text for different booking options. |
|
Reference |
The booking saving amount. For example, if the booking is done with other booking this hotel booking can save a certain amount of money. |
|
Reference |
The status of hotel booking. |
|
Reference |
The details of hotel facility. |
|
Reference |
The payment information of hotel booking. |
|
Reference |
The service or product provided by the hotel. |
|
Reference |
What kind of hotel facility is offered inside the booking package. |
|
Reference |
The details of hotel room. |
|
Reference |
The tariff data of hotel booking. |
|
Reference |
The tariff charge transaction of hotel booking. |
|
Reference |
Hours defined as part of time. |
|
Reference |
Captures household information which the individual customer may belong to. |
|
Reference |
Individual demography value, the detailed information and its value collected about customers. For example age will have Demography group as AGE, Attribute as various bands and value as 15 years which will be stored in this entity. |
|
Reference |
Specifies all names used by the individual party along the history. |
|
Reference |
The types of meals given during the flight. For example:
|
|
Lookup |
Lookup for all possible result of initiatives. |
|
Lookup |
The lookup for different types of Initiatives. |
|
Lookup |
Lookup for the reason of the interaction thread. For example:
|
|
Lookup |
Lookup for result of response received from customer interaction. For example:
|
|
Lookup |
Lookup for type of response received from customer interaction. For example:
|
|
Reference |
A level in a product hierarchy frequently used for business analysis. An item can be a group of Stock Keeping Units (SKU)s where each SKU is the same item but varies in size, weight, color, or other attributes. Item is sometimes referred to as Article.Product, article or bundle of SKUs. For example, Item could be Acme shirt, with associated SKUs for each color and size of the shirt. |
|
Reference |
||
Reference |
The type of occupation that customer is currently taking, which is the principal activity customer do to earn money. |
|
Reference |
The job role employee might take. For example:
|
|
Lookup |
Speaking or written language. |
|
Reference |
A special type of Speaking or written language dialect |
|
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:
|
|
Base |
The detailed schedule at LEG level. |
|
Lookup |
The different types of LEG. |
|
Lookup |
Lookup for type of letter sent to customer according to the content and purpose. For example:
|
|
Lookup |
Lookup for type of Local Authority. For example:
|
|
Reference |
Government authority that levies sales taxes or imposes rules or statutory compliance. |
|
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. For example:
|
|
Derived |
The history of all the changes of one account. Including the earnings, redemption, and expiration. Specifies the current and historical balances of an account. |
|
|
Derived |
This table contains the daily summary data about LOYALTY ACCOUNT (Frequent Flyer). |
Derived |
The change history of loyalty account level. |
|
|
Derived |
The daily summary of the LOYALTY ACCOUNT details. |
Base |
When the airline wants to merge several loyalty programs together or let the customer from a partner use points in a program. This entity lets you specify the related data. |
|
Reference |
There are different levels in one loyalty program. For example:
|
|
Base |
Airline may have a points expiration policy. The points expire after a certain period of time the points in the account will expire. |
|
Reference |
Structured marketing efforts that reward, and therefore encourage loyal buying behavior. |
|
Lookup |
Marital status. |
|
Reference |
Market Area denotes a geographic area for which resident demographic data is available. Market Area may not contain a store. Trade Area and Market Area have been used interchangeably in this model. The definition of a trade/market area is the geographic region from which a town draws most of its retail customers. For example:
|
|
Reference |
Level of classification inside the market areas. this classification can be based on,
|
|
Reference |
A market segment is identified to group certain common areas where business can be conducted, for example, a group of person, a specific geographical area, and so on. |
|
Reference |
Different characteristics of a market segment. For example, customer age, customer income, and so on. |
|
Reference |
The different characteristic value of market segment. |
|
Reference |
Relationship between two market statistics. |
|
Reference |
The market statistical information gathered about the competitors and the market. |
|
Reference |
This is any object the campaign message may appear on. Like a Page in the newspaper, or a time slot in TV broadcasting. |
|
Reference |
A customer account in a membership program. For example a loyalty program. |
|
Base |
The minimum connecting time between different flights. |
|
Reference |
This entity is used to convey additional information which are entered by the agent and stored on the hotel booking |
|
Reference |
Defines related calendar elements for performing to-date time transformations. |
|
Reference |
Transformations for a month. For example:
|
|
Lookup |
The nationality information. |
|
Derived |
Represents apply results of non-frequent flier related mining models on non-frequent fliers latest data. |
|
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. |
|
Reference |
Information about the message queues sent to a different office which holds different information about the BOOKING. |
|
Reference |
A company, association, institution, or other enterprise of interest to a organization including retail enterprise, or the retail organization itself. |
|
Reference |
Areas within an organization chain. |
|
Reference |
The name of Company, ORGANIZATION, or subsidiary that is recognizable to the consumer or the name of the store as it appears on the catalog, web channel, or brick and mortar store. Holds the information about different organization banners under which product or service are sold |
|
Reference |
Any logical entity that is recognized as a part of the enterprise for business analysis and transactions. Classification for a business entity can include company, operation unit, store, or warehouse. Business Entity in an ORGANIZATION represent any logical entity that is recognized as an enterprise for Business analysis and transactions. Possible classifications for a Business Entity can include, Company, Operation Units, Stores, Warehouse, and so on. |
|
Reference |
Represents the lowest level of carrier's organization hierarchy, it can be a local airline office or a call center. |
|
Lookup |
Type of ORGANIZATION business unit. For example:
|
|
Reference |
Organization hierarchy level within an ORGANIZATION COMPANY and is the parent of one or more ORGANIZATION AREAs. |
|
Reference |
Organization hierarchy level within an ORGANIZATION CORPORATE and is the parent of one or more ORGANIZATION CHAINs. |
|
Reference |
Highest level of ORGANIZATION HIERARCHY and is the parent of one or more ORGANIZATION COMPANYs. |
|
Reference |
Organization hierarchy level within ORGANIZATION CORPORATE. |
|
Reference |
User defined. Master list of all of the hierarchies in an organization. |
|
Reference |
The description of different level in organization hierarchy. |
|
Reference |
Assignment of Hierarchy Levels to ORGANIZATION HIERARCHY. |
|
Reference |
Version of ORGANIZATION HIERARCHY. |
|
Reference |
List of all the business levels within an organization. |
|
Reference |
Attributes applicable only to the corresponding level in the organization. Possible values that can be stored in this entity can be, Regional Language |
|
Reference |
The attribute value of organization hierarchy. |
|
Reference |
Publicly available and statistical information regarding the internal or external parties, such as DUNS number and number of employees. Market related information about an ORGANIZATION. In LDM the Organization Market Data entity has the SIC code and DUNS number. Duns Numbers are specific to ORGANIZATIONs where as SIC codes are for Industry sectors. So many Organizations with different Duns number can have same SIC code |
|
Reference |
Different types of ORGANIZATION NAME represent their business legal status. |
|
Reference |
Holds region within a company, chain area. Organization hierarchy level within an ORGANIZATION AREA and is the parent of one or more ORGANIZATION DISTRICTs. |
|
Reference |
Sub-type of the ORGANIZATION BUSINESS UNIT, it collects all information on (normally public) website managed by the carrier. A website owned/commissioned by the organization from where product/services can be purchased and supported. |
|
Reference |
Location in which goods or merchandise (routers, maintenance parts, computers, and so on) are stored but not sold, before they are sent to the shops or utilized by carriers. For example:
A place in which goods or merchandise are stored; a storehouse. The warehouse is to store the equipment instance like maintenance parts before delivering to the customer. |
|
Reference |
User defined attribute definitions and corresponding values regarding demographic statistics as related to an ORGANIZATION BUSINESS UNIT. This entity stores the detailed information and its value collected about organizations. |
|
Reference |
Individual party associated with a PARTY organization other than those defined For example:
|
|
Base |
The entity is used store all the miles earning activity from carrier's partners. |
|
Reference |
Assigns costs of a given promotion to a partner or PARTY participating in the promotion. |
|
Reference |
Any individual or organization of interest to the enterprise. A party is a real person, organization, branch, subsidiary, legal entity, holding company, and so on. Any real thing that you would want to put a name to is a party. The attributes of a party are universal. In other words, they are independent of your selling (or ultimately buying) relationship with the party. A party is not necessarily a customer. It can represent prospects as well as parts of an organization hierarchy (branches, head offices, corporate conglomerates) that may not necessarily have a billing relationship with the company. Any party that has an active account can be considered a customer. Historical information concerning the party is available in the Parties History table. |
|
Reference |
This entity keeps the relationship between PARTY and account. For example A party owns the account. It maybe owned by other parties than customer, such as content provider. Then this assignment tracks the owning party of the account. A party is a warrantor of an account. A party is responsible for payment of the account. |
|
Reference |
Associates one or more Addresses with a PARTY. Captures history of the names and addresses associated with a party or customers. |
|
Reference |
Association of a PARTY with one or more other PARTY. The relationships may include those among customers or between customers and the airline. |
|
Lookup |
Contact information for a party. For example email, cell phone number. |
|
Lookup |
Keep the type of contact information. For example:
|
|
Reference |
Relationship between PARTY and contact list. For example, a party belongs to a contact list. |
|
Base |
Assignment of cost items to a PARTY. One party may incur multiple costs. For example, for a customer acquisition the customer might be given any of the following items that lead to costs:
|
|
Reference |
A demographic profile for a PARTY. |
|
Reference |
Defines individual and organization demography value for a given party demographic profile. |
|
Reference |
Assigns a PARTY to one or more GEOGRAPHY ENTITYs. Depending on type of PARTY, the relationship might be:
|
|
Reference |
Identifying information unique to a PARTY. For example:
|
|
Lookup |
Lookup for valid Types of PARTY IDENTIFICATION. For example:
|
|
Base |
Specifies all interactions or communications with the customer. For example:
|
|
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. |
|
Base |
Subtype of PARTY INTERACTION, which represents the email interaction from customers. |
|
Base |
Subtype of PARTY INTERACTION, which represents the FAX interaction from customers. |
|
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:
|
|
Lookup |
Documents the various states an interaction with a customer may be in. For example:
|
|
Base |
Subtype of PARTY INTERACTION, which represents the interaction with customer through letter. |
|
Base |
Subtype of PARTY INTERACTION, which represents the SMS interaction from customers. |
|
Base |
If customer makes multiple calls to complain about same issue, those calls are grouped into single thread. |
|
Base |
Subtype of PARTY INTERACTION, which represents the visit interaction from customers. |
|
Reference |
Store the language capability as the reference to the related party attribute. |
|
Reference |
Lists any other names along the life history used by a given PARTY. |
|
Base |
Assignment of party to a given Order. For example: The Sales Agent gets a sales commission because of the customer order. |
|
Base |
Response of a PARTY to a PROMOTION. For example, positive responses:
|
|
Reference |
Lookup for Roles a PARTY may be assigned in an Event. For example:
|
|
Reference |
Assigns party roles that the party acted as to the PARTY. PARTY ROLE are X-X relationship and it may change due to contract change and so on. |
|
Reference |
The list of skills which a party may have. |
|
Reference |
The status of a party. |
|
Lookup |
Lookup for valid reasons that may be assigned for a PARTY STATUS change. For example:
|
|
Reference |
Keep track of current party status history, regarding to what carrier may be interested. Historical information captured for all lifetime of the customer or dealer. The information may be calculated from internal data. For example:
|
|
Reference |
Status type of the party. For example:
|
|
Lookup |
Lookup for party type that classifies involved parties according to their inherent characteristics and structure. For example:
|
|
Reference |
This is an operational layer entity stores the contact information of the passenger in the BOOKING. |
|
Reference |
Essential documents about the passenger. For example:
|
|
Reference |
Visa details of the passenger. |
|
Reference |
The passport as a type of PARTY IDENTIFICATION. |
|
Reference |
The passenger ticket coupon data. |
|
Reference |
The passenger invoice header data. |
|
Reference |
Check-in channel origins. Acceptance channel types can be Front-End, KSK for Kiosk, MBL for Mobile check-in channel origin. For example:
|
|
Reference |
Characteristics of the PDI. |
|
Base |
This entity describes the passenger checking details at the transaction level. |
|
Reference |
Period within a SEASON. |
|
Reference |
Quarter level in the planning calendar. |
|
Reference |
Season level in the planning calendar. |
|
Reference |
Week level in the planning calendar. |
|
Reference |
Year level in the planning calendar. |
|
Reference |
The complete details of a passenger's BOOKING, including itinerary, contact details, and special requests. A PNR is uniquely identified by a record locator. |
|
Base |
The global distribute system (GDS) information of each PNR. |
|
Reference |
Parent child relationship of the PNR and gives details about the split PNRs. |
|
Base |
Specifies the different relationships between two PNR, like split PNR. |
|
Reference |
This is an operational layer entity which stores the information of the PNR type. It contains the type of PNR. IND= ”Individual”, GRP= ”Group”, COR= ”Corporate” or NCO= ”Non Commercial” Lookup for the type of PNR. |
|
Reference |
Point of Sale (POS) grouping of items with similar point of sale control and processing attributes. The entity type may also be used to control sales that are not properly identified at the item level. |
|
Reference |
This is a entity in the operational layer to cater to a particular condition used to interpret the office. Apart for the five offices mentioned below all the other offices follow a standard logic:
|
|
Reference |
A simple cross-reference between the barcode, point of sale scan code or other keyed identifying number used at POS and the internal stock keeping Item ID for the item. The POS Item ID will generally be filled with the GTIN (UPC, EAN, and so on) for an item -- but it is not mandatory. |
|
Reference |
Postal codes and associative demographic information of interest to the carrier. |
|
Specifies the different PNR preference types. |
||
Reference |
The specification of a method to be used to transform the current sell unit retail amount to the price charged to account based on a discount group. |
|
Reference |
A line item component of a RETAIL TRANSACTION that records the granting of a reduction or increase of price on all ITEMs in the transaction. |
|
Reference |
Any logical entity that is recognized as a product or item for Business Analysis and transactions. |
|
Reference |
Defines how a product is brought to market, including: positioning, pricing, and bundling details. For example:
|
|
Reference |
The source from which a GEOGRAPHY DEMOGRAPHY VALUE is acquired or populated. For example, a mailing list provider. |
|
Reference |
The promotion reflects the tactics a carrier undertakes to generate increased incremental PAX volume for specific segment combinations within a promotional event. Promotions are frequently communicated as part of a marketing campaign to ensure that awareness is generated with the target audience. A collection of eligibility and price derivation rules, during a specific time. |
|
Base |
Assigns a particular customer segment (cluster) to a given promotion or list of promotions. The customer segments are generated by certain analytical application (including Oracle Mining) and this assignment tracks the usage of customer segment in the promotion. |
|
Reference |
Associative entity connecting any level of the item hierarchy and organization hierarchy, and optionally a VENDOR, with the promotion. |
|
Base |
A history of campaign party role about management of a campaign episode. |
|
Reference |
Details regarding each CAMPAIGN MESSAGE broadcast through a MEDIA OBJECT. For example, if channel is a newspaper, then media object will be the page and the picture. For a tv advertizement, how frequently it broadcast, how much time in each broadcast. |
|
Reference |
Associates product market plans to a promotion, typically, when a given market plan will be offered by the promotion only during a certain period. |
|
Reference |
Associative entity linking promotion item and campaign media selling item, and the prices which may be used for the item during the promotional period. |
|
Lookup |
Lookup for the type of PROMOTION (normally for a limited time). For example:
|
|
Reference |
An individual, collection of individuals, company, or public institution who has not purchased merchandise or services, but who may in the future. A prospect may also be a CUSTOMER of one PRODUCT (already purchased) that does not currently purchase another PRODUCT (may purchase). |
|
Reference |
Specifies attributes of an individual prospect, one who is not an organization. |
|
Reference |
Specifies attributes of an organization prospect. |
|
Reference |
Quarter Hour level in Time of Day. |
|
Reference |
Cumulative time transformations at the quarter level. |
|
Reference |
Transformation for a quarter. For example:
|
Table 2-8 R to Z Entity Descriptions
Entity Name | Type | Description |
---|---|---|
Reference |
This lookup keeps information on religions. Examples are Christianity, Islamic, Hinduism. |
|
Base |
A line item component of a RETAIL TRANSACTION that records the exchange in ownership of a merchandise item (for example, a sale or return) or the sale or refund related to a service. |
|
Reference |
Allows the user to categorize each item according to different seasons and phases within a season. That is, a user may assign a season of ”Spring” to a group of items, according to the supplier's deliveries of fashion items. Those relationships can be further broken down into the phases, such as ”Spring I and Spring II.”. |
|
Reference |
Subtype of internal organization. This usually lists the shops where the communications service provider presents the products and sells directly to customers. Note: a retail store may contain several SELLING LOCATIONs. |
|
Base |
A type of transaction that records the business conducted between the carrier and another party involving the exchange in ownership or accountability, or both, for merchandise or tender, or both, or involving the exchange of tender for services. |
|
Base |
A detail line item of a RETAIL TRANSACTION that records the business conducted between the ORGANIZATION STORE and another party involving the exchange in ownership or accountability, or both, for merchandise or tender, or both, or involving the exchange of tender for services. |
|
Derived |
Summary level entity which represents the cost related summary calculation. |
|
Lookup |
This is a lookup entity to hold the different types of revenue cost items. The data in this entity is the lowest level of the revenue cost group hierarchy. For example: Fuel Surcharge, Mail Revenue, Fuel Tax |
|
Lookup |
Lookup entity to roll up different cost elements into different categories. For example: Passenger Revenue, Fuel, Landing and Parking. |
|
Lookup |
This is a lookup entity to roll up different revenue cost element categories into different groups. For example: Revenue, Variable DOCS, Fixed Expenses |
|
Base |
This is the base transaction entity to store each and every single revenue or cost transaction record. |
|
Reference |
Hierarchy among the job roles within an organization. |
|
Reference |
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:
|
|
Reference |
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) |
|
Reference |
A code denoting how the item is being treated in the line item. For example:
|
|
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. |
|
Reference |
The sales representatives who sell the product to the customer. For example:
|
|
Reference |
Weekly sales forecast Information at given levels of ITEM, and organization hierarchies. |
|
Reference |
Weekly sales plan including Returns, Cost of Sales, PROMOTION, Clearance, at given levels of ITEM and ORGANIZATION HIERARCHYs. |
|
Reference |
A type of limitation that restricts the sale of a particular class of item. |
|
Lookup |
This is the description of the different seasons defined by the airline. |
|
Reference |
Second hierarchy level as defined in Time Hierarchy. |
|
Reference |
Minimum and Maximum scores for each segment associated with an ACCOUNT SEGMENT or CUSTOMER SEGMENT. |
|
Base |
Stores the details of the date and time that a CARRIER has scheduled to the market. 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 them. Passengers reserve Segments on a BOOKING. This is an operational layer entity which stores segment details such as the board point airports and offpoint airports. |
|
Reference |
An area of floor space or shelf space within the ORGANIZATION STORE to which sales can be assigned. The selling location may be assigned to or rented by a VENDOR. |
|
Lookup |
Lookup for type code and description used to define a SELLING LOCATION: For example:
|
|
Reference |
The type of the postal service. For example:
|
|
Reference |
Specifies the coverage area of a given Service Spec. The geographic area covered by service provider with certain product combination. Service areas are defined so that service providers can determine the demographic / psychographic / population data the geography served by the carrier. |
|
Reference |
Specifies the detailed geographical data about each service coverage area. |
|
Mining Support |
Represents settings for Decision Tree algorithm. |
|
Mining Support |
Represents settings for Support Vector Machine (SVM) algorithm. |
|
Mining Support |
Represents settings for K-means clustering algorithm. |
|
Mining Support |
Represents user settings. |
|
Lookup |
Lookup of SKILL TYPE for a individual party |
|
Reference |
Stock Keeping Unit or unit identification, typically the UPC, used to track store inventory and sales. Each SKU is associated with an item, variant, product line, bundle, service, fee, or attachment. Aggregate SKU: Subtype of SKU that is an aggregation of one or more constituent SKU. The constituent items may be sold individually. Group Select: An item, which is a group of items, only one of which is sold. The choice of which item is made by the customer at the POS. Prepared: A sub-type of SKU ITEM that is manufactured (or prepared) for sale from a set of BULK ITEM with a RECIPE. A PREPARED SKU ITEM is different from a SKU ITEM because a PREPARED Item is not booked into inventory when the item is manufactured; nor is it removed from inventory when it is sold; rather the inventory for the BULK ITEM constituent parts as defined by the recipe is reduced when the Prepared Item is sold. Service SKU: A type of SKU that provides a detailed identifier and description for a service offered for a sale to customer in the retail store. Service SKU also identifies and describes rental items and other tangible items that are used by customer for a contracted period, but not purchased. Stock: A unit of merchandise that may be sold to a customer or used by the ORGANIZATION STORE. |
|
Reference |
The most detailed level of job code from Standard Occupational Classification (SOC) System. For example:
|
|
Reference |
System of Record from which OADM data was loaded. For example, GDS system, CRM system. |
|
Reference |
Track Key of the PARTY (customer or employee) in the originating source system. This key can be used back to track information back to source management system. The party can consolidate different people from different source systems, such as CRM, Billing, into a unique one. Therefore, the multiple keys for the same unique party is saved here. |
|
Reference |
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. |
|
Reference |
Vendor of any service or product to support the operation of carrier. |
|
Lookup |
Type of SWOT analysis. A Strength, Weakness, Opportunity, Threat (SWOT) that an enterprise has when compared to a Competitor. SWOT analysis is a formal framework of identifying and framing organizational growth opportunities. |
|
|
Control |
This is a system management table used by ETL to populate the audit columns and generated ids for the audit columns and stores the details of the ETL data load. |
Reference |
The Access Methods included in a specific CAMPAIGN. |
|
Reference |
The Customer Accounts included in a specific CAMPAIGN. |
|
Reference |
The Geography information included in a specific CAMPAIGN. |
|
Lookup |
Indicates the type of targets in a specific Promotion: Examples: Customer ACCOUNTs, Access Method, geography area, and so on. |
|
Reference |
A line item component of a RETAIL TRANSACTION that records the charging and offsetting liability credit for sales tax on merchandise items and services sold by the store or debit for merchandise returned to the store. |
|
Reference |
A group of ITEMs for which a TAX AUTHORITY defines TAX GROUP RULEs. For example:
|
|
Reference |
Specifies the airport terminal related information. |
|
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 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 (IATA PAT-GR-1). This is a operational layer entity which stores the ticket number and the issuing office of the ticket. |
|
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. This is an operational layer entity which stores details about the coupons. |
|
Base |
The ticket delivery arrangement for the TICKET. For example:
|
|
|
Derived |
This is a summary entity which used to store the summary information related to ticket. |
Base |
This is the base level entity which used to store the details of ticket price. |
|
Base |
This is the base level entity which used to store the details of ticket price discount related data like rate. |
|
Base |
This is the base level entity which used to store the details of ticket price document. |
|
Reference |
This is a reference entity which used to store the form of payment for ticketing. |
|
Reference |
This is a global dimension which stores the details in the granularity of minutes which rolls up to hour. |
|
Reference |
Relates the calendar day to a season and to a standard day. Specifies the relationship between a given day and all days of a given season up to that day. |
|
Reference |
Relates the calendar week to a season and to a standard week. Specifies the relationship between a given week and all days of a given season up to that week. |
|
Reference |
Represents the top most level of Time. This is needed to enable Ad-Hoc Reporting involving the Time Dimension. |
|
Base |
Time zone relative to Greenwich Mean Time (GMT). |
|
Base |
Represents tour and tour related information. |
|
Reference |
Traffic Category is a term used for the purposes of categorization and reporting on Route Profitability to categorize the flights into:
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. |
|
Lookup |
Further classifications of TRANSACTION CATEGORY. |
|
Base |
Points are transferred from one account to another. |
|
Reference |
The TSM is a pricing record associated to one passenger only, the one the MD PNR element is associated to. There is a TSM for each type of MD PNR 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. |
|
Base |
This is the base level entity which is used to store the details of TSM document data. |
|
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. This is an operational layer entity which stores information about the pricing carrier, price routing department, weight value, weight piece currency of the excess baggage. |
|
Reference |
This is subset of TSM which stores the miscellaneous charge order of the TSM. Stores the details of the MCO. For example:
|
|
Reference |
This is a reference level entity which used to store the TSM MCO fare information. |
|
Base |
This is the base level entity which used to store the details of TSM MCO tax. |
|
Reference |
Specifies passenger personal information associated with a TSM. |
|
Base |
This is the base level entity which used to store the details of TSM payment data. |
|
Reference |
Information about the fares and taxes, depending on the TSM type. |
|
Base |
This is the base level entity which used to store the details of TSM RFI. |
|
Reference |
The routes of TSM mainly the CARRIER from city to city and stop over indicator. |
|
Reference |
This is a subset of TSM which stores the service fee for the TSM. Stores the details of Service Fee (SVC). For example:
|
|
|
Base |
This is the base level entity which used to store the details of TSM XSB rate data. |
Reference |
Associative entity for EMPLOYEE and JOB ROLES. Assigns a unique ID for each job role that an employee performs at a particular department. |
|
Lookup |
Value type describes the type of value. Value type could be time or money. |
|
Reference |
Details of the Vehicle which can be an aircraft, bus, ship, rail, and so on. |
|
Reference |
The virtual team beside department hierarchy formed for a specific purpose. For example:
|
|
Reference |
Cumulative time transformations at the week level. |
|
Reference |
Time transformations at the week level. |
|
Reference |
Calendar weekdays. |
|
Reference |
Transformations at the year level. |