SAP RAP Managed Scenario vs Interactive ABAP
Report
1. SAP RAP Managed Scenario — Simple Example
This project demonstrates building a simple CRUD Fiori app using the SAP RESTful Application
Programming Model (RAP) in a managed scenario. In the managed scenario, the framework
automatically handles common behaviors like Create, Read, Update, and Delete, minimizing
custom coding.
Step What is done Purpose
1 Define a database table in ABAP Dictionary To hold data; basis for the entity model.
2 Generate sample data with ABAP class To have test data for testing the UI / service.
3 Define CDS root view entity Defines how the data is exposed logically.
4 Add metadata/UI annotations Control how fields and lists appear in Fiori UI.
5 Define behavior (managed) Specify operations (CRUD) and let RAP handle them.
6 Service definition + binding Expose entity via OData service for consumption.
At the end, you get a working service and Fiori UI with CRUD operations, with minimal coding
thanks to managed RAP behavior.
2. Interactive Reporting in ABAP
This project demonstrates creating an interactive ABAP classical report where the user can click a
line in the report output to drill down into further details (e.g., employee → salary → address). It
uses ABAP events like AT LINE-SELECTION.
Feature Implementation Purpose
Selection screen input Takes Employee ID as input Filter data for reporting
List output (first page) Displays employee details Provide overview
AT LINE-SELECTION Trigger event on user click Navigate to detailed data
Multiple lists/pages Different levels of detail shown Drill-down navigation
Modular coding Using FORMs for clarity Maintainability
3. Comparison
Aspect SAP RAP (Managed) Interactive ABAP Report
UI / Frontend Fiori / modern web-based with annotations
SAP GUI classic report output
CRUD ease Framework handles standard CRUD Manual coding required
Flexibility Unmanaged needed for complex logic Full control via coding
Best suited for New apps, Fiori, modern UX Reports, drill-down in SAP GUI
