SAP-samples/abap-platform-refscen-flight
The Flight Reference Scenario for the ABAP RESTful Application Programming Model, with sample data, RAP services and legacy logic for a flight-booking app, in branches for cloud and on-premise ABAP releases.
Provides sample master and transaction data, RAP services and legacy business logic for a flight-booking scenario, the SFlight dataset carried over into RAP. Separate branches cover the two deployment lines: ABAP Environment on SAP BTP or SAP S/4HANA Cloud Public Edition, and on-premise ABAP Platform releases from Application Server ABAP 7.54 through 8.16 for SAP S/4HANA on-premise and Private Edition. A reader imports the branch matching their system and either works through the end-to-end scenarios or builds a new app on the sample data.
Facts
Where it sits
Who is behind it
In the atlas: maintains 222@SAP-samplesmaintainerBrian BernardContributes to this
In the atlas: contributes to 64@btbernardGeorg ReichertContributes to this
In the atlas: contributes to 1@GeorgReichert1Jonathan BakerContributes to this
In the atlas: contributes to 9@jonathanbaker7MarcSAPContributes to this
In the atlas: contributes to 2@MarcSAPMarinaBlankContributes to this
In the atlas: contributes to 2@MarinaBlankThomas GauweilerContributes to this
In the atlas: contributes to 1@ThomasGauweilerVolker DreesContributes to this
In the atlas: contributes to 9@VolkerDrees7 contributors
What it declares
Every artifact
- Type
- Sample
- Origin
- By SAP
- Use as
- A reference
As a sample
- Form
- A reference application
Connections
Defining business object behaviour and who owns the transaction
abap2UI5 apps in front of OData, RAP, events and other technology
TechEd 2025 workshop on a Fiori app with ABAP Cloud and Joule
Download
Learn more
- What's new with draft handling in RAP?What's new with draft handling in RAP?An ABAP-day session at Devtoberfest 2026 on two additions to draft handling in RAP: collaborative draft, where two users work on the same draft instance and a field is locked only while the other is in it, and draft scope, where editing an instance of one draft-enabled business object puts the related instances of a dependent one into draft as well. Andre Fischer shows what each costs in the behaviour definition and projection, the draft query view and its DCL that collaborative draft needs over a table-based business object, and the CDS table entities that remove both the draft query view and the persistence table, with their current restrictions in ABAP analytics and extensibility; the from-scratch generator in ADT grows a checkbox for them. Both demos run against the DMO flight scenario of SAP-samples/abap-platform-refscen-flight, and the last part hides the draft-related features of an OData V4 app in its manifest, which the session gives as the reason a simple create-update-delete app no longer needs a V2 service binding.published 2026-09-21Andre Fischer, YouTube — SAP Developers playlists
README
quoted from SAP-samples/abap-platform-refscen-flight under Apache-2.0, readABAP Flight Reference Scenario for the ABAP RESTful Application Programming Model
The ABAP RESTful Application Programming Model (RAP) defines the architecture for efficient end-to-end development of intrinsically SAP HANA-optimized Fiori apps. It supports the development of all types of Fiori applications as well as Web APIs. It is based on technologies and frameworks such as Core Data Services (CDS) for defining semantically rich data models and a service model infrastructure for creating OData services with bindings to an OData protocol and ABAP-based application services for custom logic and SAPUI5-based user interfaces.
The ABAP Flight Reference Scenario provides sample data and services as well as legacy business logic to get familiar with RAP. You can check out the end-to-end scenarios or build your own app based on the sample data.
Note:
The branches of this repository were renamed recently. If you have already linked an ABAP Package to a branch with an outdated name, unlink the repository first and then pull the link to the branch with the new name, as described in step 3 of the Download section in the respective README.
ABAP Platform Cloud
Choose this if you are working on SAP BTP or SAP S/4HANA Cloud, public edition. To import the reference scenario into your ABAP Environment, follow the steps in the README file of the branch ABAP-platform-cloud and download the sources from this branch.
For more information, see Downloading the ABAP Flight Reference Scenario.
ABAP Platform
Choose this if you are working on SAP S/4HANA, on-premise edition or SAP S/4HANA Cloud, private edition. To import the reference scenario into your ABAP system, follow the steps in the relevant README file and download the sources from the branch corresponding to your your backend version:
- README of branch ABAP-platform-2019 (Application Server ABAP 7.54)
- README of branch ABAP-platform-2020 (Application Server ABAP 7.55)
- README of branch ABAP-platform-2021 (Application Server ABAP 7.56)
- README of branch ABAP-platform-2022 (Application Server ABAP 7.57)
- README of branch ABAP-platform-2023 (Application Server ABAP 7.58)
- README of branch ABAP-platform-2025 (Application Server ABAP 8.16)
For more information about the ABAP Flight Reference Scenario, see Downloading the ABAP Flight Reference Scenario.
How to obtain support
This project is provided "as-is": there is no guarantee that raised issues will be answered or addressed in future releases.
License
Copyright (c) 2018-2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the SAP Sample Code License except as noted otherwise in the LICENSE file.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-samples-abap-platform-refscen-flight- JSON
- /artifacts/sap-samples-abap-platform-refscen-flight.json
- MCP
- Connecting an agent