Testing the Flight Data Application
Currently there is no user interface for testing the scenarios of the flight data application.
You can, however, test individual functions. In theFunctions section under the description of the functions, there is a list of the corresponding function modules and programs. You can test/execute them in the Function Builder (SE37) or in the ABAP Editor (SE38).
From the SAP flight data model, the following tables are of interest for this application: SCARR (airlines), SPFLI (flight schedules), SFLIGHT (flights), SBOOK (flight bookings), SCUSTOM (flight customers), SFLCONN (flight connections), SFLCONNPOS (route segments of flight connections), SFLTRIP (flight trips), SFLTRIPPOS (flight trip passengers), and SFLTRIPBOK (booking numbers for flight trips).
Use the Data Browser (SE16) to get existing data from the tables of the flight data model. You can use this data to find suitable entry data to test functions and check the results of the test.
To test the functions, the tables of the flight data application must be filled with data. For information about filling the tables with suitable data, seeSetting Up the Flight Data Application.
You are interested in implementing a GetDetail BAPI. For this purpose, you could test the method Flight.GetDetail. First go to the Data Browser and determine existing flights in the SFLIGHT table. In this table you find a flight LH 400 on January 1, 2002, for example. You can now test the function module BAPI_FLIGHT_GETDETAIL for this flight. You get detailed information that you can compare with the data in the SFLIGHT table and the SPFLI table (for LH 400).
You are interested in implementing a (potentially) distributed scenario (look for flight connection, for example). First you test the function module BAPI_FLCONN_GETLIST in the travel agency system. You can limit the test to a departure location, destination, or a time period. You get a list of flight connections Now test the function module BAPI_FLCONN_GETDETAIL and enter the ID of one of the flight connections in the list. You get detailed data about the flight connection that you can check in the tables SFLCONN, SFLCONNPOS, and SPFLI. You can also see the number of available seats for all route segments of the flight connection. To check whether this data is correct, you can look at the flight data in the SFLIGHT table in the original system of the relevant airline.
The BAPI concept ensures that BAPIs do not drop Commit Work commands. Write BAPIs can be tested in the Function Builder but the results are not written to the database since no commit command is executed.
Therefore, if you want to test write BAPIs create a test report. This report first calls the relevant function module with the corresponding data. Then the command Commit Work is executed. If the report is executed successfully, the changed data can be checked in the database tables.
The complete scenario was set up as a distributed ALE scenario in internal SAP demo systems. For information about this demo scenario, go to the integration alias in SAPNet and then IBF Standards. This includes the following: Availability, systems, users, and test procedure. You are then able to examine and test a distributed scenario that has already been set up without having to make all the necessary ALE settings yourself.