7/29/2019 Flight Model Abap

1/2

Flight Model

The flight model is the basis of all the examples in this documentation. All the tables mentioned inthe examples exist in your system, so you can reproduce the examples directly in the system.

The flight model is based on data model BC_TRAVEL, which you can look at in your system usingthe Data Modeler.

Procedure for Displaying the Flight Model

1. Go to the initial screen of the ABAP Workbench and choose DevelopmentData Modeler.

The initial screen of the Data Modeler is displayed.

2. Enter BC_TRAVEL in field Modeling objectand choose Display.

The description of the flight model is displayed.

3. You can display the data model as a graphic with UtilitiesGraphic.

You can find further information on data modeling and on using the Data Modeler in thedocumentation on the Data Modeler.

Flight Model (Simplified Representation)

The flight model gives a simple description of seat bookings in passenger airplanes by flightcustomers. The booking can be made either at the sales desk of a carrier or at a travel agency.

http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21f304446011d189700000e8322d00/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/cf/21f304446011d189700000e8322d00/frameset.htm

7/29/2019 Flight Model Abap

2/2

A flight booking is based on the individual flight connections described in the flight schedule. Thereare concrete flights for every flight connection.

Assigned Tables in the ABAP Dictionary

There is a table in the ABAP Dictionary containing the data of the corresponding entities (versions

of the entity type) for each entity type.

The most important tables of the flight model are:

T000: Client table

SCURX: Currencies (key: currency key)

SBUSPART: Business partner (key: client, partner number)

STRAVELAG: Travel agencies (key: client, travel agency number)

SCUSTOM: Customers (key: client, customer number)

SCARR: Carriers (key: client, carrier ID)

SCOUNTER: Sales counters (key: client, carrier ID, sales counter number)

SPFLI: Flight schedule (key: client, carrier ID, connection number)

SFLIGHT: Flights (key: client, carrier ID, connection number, date of flight) SBOOK: Flight bookings (key: client, carrier ID, connection number, date of flight, booking

number, customer number)

Relationships between the Tables

Table SBUSPART contains all the business partners of a carrier. A business partner is identified byhis number in this table. The data of the contact person for the business partner is also stored. Abusiness partner can be a travel agency or a customer (e.g. company that frequently books flightsdirectly with the carrier). Different data is required for these two types of business partner. The datafor a travel agency is stored in table STRAVELAG and the data for a customer in table SCUSTOM.There is therefore an entry with the same key in either table STRAVELAG or table SCUSTOM foreach entry in table SBUSPART.

Table SCARR contains the IDs and names of the carriers. Each carrier has a number ofconnections. These flight connections are stored in table SPFLI. Table SFLIGHT contains theconcrete flight data for each connection Bookings can be made for each flight in table SFLIGHT.The bookings made for each flight are entered in table SBOOK.

The carriers have sales counters in the airports. These sales counters are entered in tableSCOUNTER. The customer number or agency number for which the booking was made is stored intable SBOOK for each booking. If the customer books his flight directly at a counter, the counternumber is also entered in the booking data in table SBOOK