Flight Reference Scenario for the ABAP RESTful Programming Model

The ABAP RESTful programming model defines the architecture for efficient end-to-end development of intrinsically SAP HANA-optimized Fiori apps in SAP Cloud Platform ABAP Environment. 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 Flight Reference Scenario provides sample data and services as well as legacy business logic to get familiar with the ABAP RESTful Programming Model. You can check out the end-to-end scenarios or build your own app based on the sample data.

For more information, see Downloading the ABAP Flight Reference Scenario.

Prerequisites

Make sure to fulfill the following requirements:

• You have access to an SAP Cloud Platform ABAP Environment instance (see here for additional information).
• You have downloaded and installed ABAP Development Tools (ADT). Make sure to use the most recent version as indicated on the installation page.
• You have created an ABAP Cloud Project in ADT that allows you to access your SAP Cloud Platform ABAP Environment instance (see here for additional information). Your log-on language is English.
• You have installed the abapGit plug-in for ADT from the update site http://eclipse.abapgit.org/updatesite/.

Download

Use the abapGit plug-in to install the Flight Reference Scenario by executing the following steps:

1. In your ABAP cloud project, create the ABAP package /DMO/FLIGHT (using the superpackage /DMO/SAP) as the target package for the demo content to be downloaded (leave the suggested values unchanged when following the steps in the package creation wizard).
2. To add the abapGit Repositories view to the ABAP perspective, click Window > Show View > Other... from the menu bar and choose abapGit Repositories.
3. In the abapGit Repositories view, click the + icon to clone an abapGit repository.
4. Enter the following URL of this repository: https://github.com/SAP/abap-platform-refscen-flight.git and choose Next.
5. Select the branch Cloud-Platform and enter the newly created package /DMO/FLIGHT as the target package.
6. Create a new transport request that you only use for this demo content installation (recommendation) and choose Finish to link the Git repository to your ABAP cloud project. The repository appears in the abapGit Repositories View with status Linked.
7. Right-click on the new ABAP repository and choose pull to start the cloning of the repository contents. Note that this procedure may take a few minutes.
8. Once the cloning has finished, the status is set to Imported. Then refresh your project tree.

As a result of the installation procedure above, the ABAP system creates an inactive version of all artifacts from the demo content and adds the following sub packages to the target package:

• /DMO/FLIGHT_LEGACY
• /DMO/FLIGHT_REUSE
• /DMO/FLIGHT_READONLY - represents a read-only list reporting app (see also: corresponding end-to-end guide).
• /DMO/FLIGHT_UNMANAGED - represents the transactional app with implementation type unmanaged (see also: corresponding end-to-end guide).
• /DMO/FLIGHT_MANAGED - represents the transactional app with implementation type managed (see also: corresponding end-to-end guide).

NOTE: The demo packages do not include service bindings. They must be created in your own namespace to complete the service (see configuration section). Then you can run, for example, the UI services with the Fiori Elements preview in the service binding.

Configuration

To activate all development objects from the /DMO/FLIGHT package:

1. Click the mass-activation icon (Activate Inactive ABAP Development Objects) in the toolbar.
2. In the dialog that appears, select all development objects in the transport request (that you created for the demo content installation) and choose Activate.

To fill the demo database tables for the read-only and the unmanaged scenario with sample business data:

1. Expand the package structure in the Project Explorer /DMO/FLIGHT_LEGACY > Source Code Library > Classes.
2. Select the data generator class /DMO/CL_FLIGHT_DATA_GENERATOR and press F9 (Run as Console Application).

To create a service binding for the read-only list reporting app (package /DMO/FLIGHT_READONLY):

1. Right-click the service definition /DMO/FLIGHT_R and choose New Service Binding (see here for additional information).
2. Specify your own package and your own namespace when following the steps in the creation wizard.

To create a service binding for the transactional app with implementation type unmanaged (package /DMO/FLIGHT_UNMANAGED):

1. Right-click the service definition /DMO/TRAVEL_U and choose New Service Binding (see here for additional information).
2. Create the service binding in your own package and your own namespace.

To create service bindings for the transactional app with implementation type managed (package /DMO/FLIGHT_MANAGED):

1. Right-click the service definition /DMO/UI_TRAVEL_PROCESSOR_M and choose New Service Binding (see here for additional information).
2. Create the service binding in your own package and your own namespace.
3. Right-click the service definition /DMO/UI_TRAVEL_APPROVER_M and choose New Service Binding (see here for additional information).
4. Create the service binding in your own package and your own namespace.

NOTE: The database tables for transactional processing in the managed scenario do not contain any business data. Instead you create your business data from scratch.

NOTE: The namespace /DMO/ is reserved for the demo content. Apart from the downloaded demo content, do not use the namespace /DMO/ and do not create any development objects in the downloaded packages. You can access the development objects in /DMO/ from your own namespace.

Limitations

The abapGit plug-in currently only supports to download content. It's not possible to upload any changes.

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 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.