🚀 Introduction
Welcome to our second blog of SAP RAP Tutorial on Mastering ABAP RAP for beginners. You can also checkout our first blog below:
SAP RAP Tutorial : Naming Conventions for Development Objects
The ABAP Flight Reference Scenario is a foundational demo model provided by SAP to help developers get started with the ABAP RESTful Application Programming Model (RAP). It offers a rich set of interconnected database tables that simulate a real-world travel booking system, making it ideal for learning and prototyping RAP applications.
In this blog, we’ll explore the key components of the Flight Reference Model, understand the purpose of each table, and see how they fit into the RAP development workflow. You can also get more understanding of perquisites like Mastering ABAP RAP: Business Object Behavior & Runtime Implementation Explained or ABAP RAP Business Objects: Mastering Composition vs. Association from our SAP RAP Tutorial blog series.
🧱 What Is the ABAP Flight Reference Scenario?
SAP’s Flight Reference Scenario is a demo data model designed to support RAP tutorials and development guides. It includes entities like travel agencies, customers, flights, bookings, and supplements—all structured in a way that mirrors real-world business processes.
This model is used extensively in SAP’s Develop section to demonstrate RAP features such as CDS views, behavior definitions, and service bindings.
📊 Key Tables in the Flight Model : SAP RAP Tutorial
Here’s a breakdown of the most important tables in the scenario:
1. /DMO/AGENCY
Stores general data about travel agencies that operate travel services for customers.
2. /DMO/TRAVEL
Contains travel data including administrative fields for tracking creation and changes.
3. /DMO/CUSTOMER
Holds general and administrative data about customers.
4. /DMO/BOOKING
Captures booking details for flights, including customer ID and travel ID references.
5. /DMO/FLIGHT
Stores general information about flights.
6. /DMO/BOOK_SUPPL
Contains data about booking supplements like meals or insurance options.
7. /DMO/SUPPLEMENT
Defines general data about supplements that can be booked for flights.
8. /DMO/CONNECTION
Stores data about flight connections between airports.
9. /DMO/AIRPORT
Holds information about airports involved in flight connections.
10. /DMO/SUPPL_TEXT
Provides localized text descriptions for supplements in multiple languages.
11. /DMO/CARRIER
Stores data about flight carriers.
🔄 How These Tables Work Together
The Flight Reference Model is designed to simulate a complete travel booking system:
- Agencies manage travels.
- Customers book flights through bookings.
- Each booking can include supplements like meals or insurance.
- Flights are operated by carriers, connected via airports.
This interconnected structure allows developers to build realistic RAP applications with CDS views, behavior definitions, and OData services.
🧠Why Use the Flight Model for Our SAP RAP Tutorial?
- Hands-on learning: Ideal for practicing RAP concepts.
- Realistic data: Simulates actual business scenarios.
- Reusable structure: Can be extended for custom applications.
- Supports all RAP layers: From data modeling to service exposure.
📌 Conclusion
The SAP RAP Flight Reference Scenario is a powerful tool for mastering RAP development. By understanding the purpose and relationships of each table, you can build robust, scalable applications that follow SAP’s best practices.
Whether you’re creating a Fiori UI, exposing a Web API, or implementing business logic, this model provides the perfect starting point.
Next Part – SAP RAP Programming: Building Your First OData Service
Also Read – Understanding S/4HANA for Beginners: Key Concepts Explained