Skip to content

Latest commit

 

History

History
51 lines (33 loc) · 3.37 KB

README.md

File metadata and controls

51 lines (33 loc) · 3.37 KB

README file for WEEK 4: DEALING WITH EXISTING CODE

In week 4, you are going to build a UI service for a transactional SAP Fiori elements-based app using the unmanaged runtime implementation which allows the integration of existing business logic (i.e. Brownfield implementation).

Motivation

The topic of this week is Dealing with Existing Code.

So, we start with having a look at the legacy business logic that we want to leverage for our unmanaged business object implementation.

For this we investigate the sub package /DMO/FLIGHT_LEGACY that resides in the package /DMO/FLIGHT.

The data is read from already existing legacy data base tables /DMO/TRAVEL and /DMO/BOOKING.

In addition, we will use function modules such as /DMO/FLIGHT_TRAVEL_CREATE, /DMO/FLIGHT_TRAVEL_UPDATE or /DMO/FLIGHT_TRAVEL_DELETE that are used to create, update and delete the data in a buffer. We also have a read function module that reads the data from the buffer rather than from the database level that comes handy when implementing the business logic that is required when the business object is called via EML rather than by a SAP Fiori UI. And there is finally a function module that saves the travel and booking data to the database tables.

Hints and Tips
Speed up the typing by making use of the Code Completion feature (shortcut Ctrl+Space) and the prepared code snippets provided. You can easily open an object with the shortcut Ctrl+Shift+A, format your source code using the Pretty Printer feature Shift+F1 and toggle the fullscreen of the editor using the shortcut Ctrl+M.

Please note that the placeholder #### used in object names in the exercise description must be replaced with the suffix of your choice during the exercises. The suffix can contain a maximum of 4 characters (numbers and letters). Numbers and letters are allowed.
The screenshots in this document have been taken with the suffix 1234. Please note that the ADT dialogs and views may change in the future due to software updates - i.e. new and/or optimized features.

Follow the instructions below.

Tables_and_function_modules

HANDS-ON EXERCISES

Find the links to the different hands-on exercises below.

Week 4 Unit 1: The Business Scenario

There is no hands-on exercise available for this unit, but you can watch the corresponding video on openSAP.com..

Week 4 Unit 2: Creating the CDS Data Model

Link to the hands-on exercise.

Week 4 Unit 3: Defining and Implementing the Business Object Behavior

Link to the hands-on exercise.

Week 4 Unit 4: Creating the Business Object Projection

Link to the hands-on exercise.

Week 4 Unit 5: Building and Previewing the OData UI Service

Link to the hands-on exercise.

Additional Reading Material

For more information, links to documentation, and more, please visit the RAP at openSAP information page.

License

Copyright (c) 2020 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.