After completing this lesson, you will be able to:
The data model in this example is very simple - there is a single database table that contains details of flight connections - an airline, flight number, details of the departure airport and the destination.
NoteNot included in the figure are additional fields that the RAP runtime needs in order to manage concurrency control. We will look at these a little later on.
Let's see how to define a database table.
Create a new data element called z##_city_from.
Choose File → New → Other.
Type Data e into the filter field. The system reduces the hit list to Data Element.
Double-click Data Element.
Ensure that your package is set to ZS4D400_##. Enter the name Z##_CITY_FROM and a description. Choose Next.
Select your transport request and choose Finish.
Use the domain /dmo/city to specify the type of the data element.
In the Type Name field, enter /dmo/city.
For each of the texts (short, medium, long, heading), enter a suitable text.
Enter Departure in the Short field.
Enter Departure City in the Medium field.
Enter Departure City in the Long field.
Enter Departure in the Heading field.
Activate the data element.
Choose Ctrl + F3.
Create a new data element called z##_city_from.
Choose File → New → Other.
Type Data e into the filter field. The system reduces the hit list to Data Element.
Double-click Data Element.
Ensure that your package is set to ZS4D400_##. Enter the name Z##_CITY_FROM and a description. Choose Next.
Select your transport request and choose Finish.
Use the domain /dmo/city to specify the type of the data element.
In the Type Name field, enter /dmo/city.
For each of the texts (short, medium, long, heading), enter a suitable text to describe the departure city.
Enter Departure in the relevant fields.
Activate the data element.
Choose Ctrl + F3.
Create another data element called Z##_CITY_TO. For the data type, use the domain /dmo/city again. For the field labels, use the word To.
Repeat the exercise from step 1 to 4 using the data element name Z##_CITY_TO and the field label Destination instead of Departure.
In this series of exercises, you will create a Fiori Elements app for managing flight connections. The first step is to create the database table that will store the data.
Create a new database table called Z##ACONN.
Choose File → New → Other.
In the Filter field, enter Database. The system filters the list of object types so that only object types containing the word Database are displayed.
Double-click Database Table.
Ensure that the correct package (ZS4D400_##) is set. Enter the name Z##ACONN and a description for your table (suggestion: Group ## Active Connections). Choose Next.
Select your own transport request and choose Finish.
Enter the following list of fields between the curly brackets:
key client : abap.clnt not null;
key uuid : sysuuid_x16 not null;
carrier_id : /dmo/carrier_id;
connection_id : /dmo/connection_id;
airport_from_id : /dmo/airport_from_id;
city_from : /dmo/city;
country_from : land1;
airport_to_id : /dmo/airport_to_id;
city_to : /dmo/city;
country_to : land1;
local_created_by : abp_creation_user;
local_created_at : abp_creation_tstmpl;
local_last_changed_by : abp_locinst_lastchange_user;
local_last_changed_at : abp_locinst_lastchange_tstmpl;
last_changed_at : abp_lastchange_tstmpl;
For the field city_from, replace the data element /dmo/city with your own data element z##_city_from. For the city_to field, replace the data element /dmo/city with your own data element z##_city_to.
The definition of the city_from and city_to fields should now look like the following: city_from : z##_city_from;andcity_to : z##_city_to;.
Activate the table.
Choose Ctrl + F3.
We have just defined a database table to hold our data, but the app that we are going to create needs more objects than just this table. We can generate these objects using a wizard in ADT.
The generated objects contain all of the information that is necessary to provide a working app with create, read, update, and delete capability. Later on, we will also adjust and extend some of these objects to change the appearance of the user interface and to implement some checks and calculations.
Watch this video to learn how to generate additional objects.
In this exercise you will generate the additional repository objects.
You must already have created and activated the database table Z##ACONN.
Start the object generator in ABAP Development Tools. Ensure that the package is set to your own package, enter a description for the generated objects, and set the generator to generate a UI service.
Right-click the table name in the Project Explorer and choose Generate ABAP Repository Objects.
Enter a description in the Description field.
In the Generator field, open the dropdown list box and select ABAP RESTful Application Programming Model: UI Service.
Choose Next.
Name the objects as described in the table:
| Object Type | Object Name |
|---|---|
| Data Definition Name | Z##_R_Connection |
| Alias Name | Connection |
| Implementation Class | ZBP_##_CONNECTION |
| Draft Table Name | Z##DCONN |
| Service Projection | Z##_C_Connection |
| Service Definition | Z##_CONNECTION |
| Service Binding | Z##_UI_Connection_O4 |
| Binding Type | OData V4 - UI |
On the left-hand side of the dialog box, click Data Model. In the right-hand pane, enter the Data Definition NameZ##_R_Connection and Alias NameConnection.
On the left-hand side of the dialog box, click Behavior. In the right-hand pane, enter the Implementation ClassZBP_##_CONNECTION and the Draft Table NameZ##DCONN.
On the left-hand side of the dialog box, click Service Projection. In the right-hand pane, enter the NameZ##_C_Connection.
On the left-hand side of the dialog box, click Service Definition. In the right-hand pane, enter the NameZ##_CONNECTION.
On the left-hand side of the dialog box, click Service Binding. In the right-hand pane, enter the NameZ##_UI_Connection_O4 and select the Binding TypeOData V4 - UI.
Generate the objects.
Choose Next.
Select the appropriate transport request and choose Finish.
Using your database table and the object generator, you can generate all of the objects that you need to get a working Fiori Elements app. The only manual step is to publish the service.
You must publish the service before you can test the app. To do so, open the service binding and choose Publish. Once you have done this, the entity that you created (in this case, Connection) appears in the list of entities. Mark it and choose Preview to test the app.
When you choose Preview, a browser window opens and you can create a new flight connection. However, the app does not implement any checks other than type checks (for example, only digits are allowed in the Flight Number field).
