Projects

Use these projects to combine several course topics in a complete application. Projects 1–4 are independent checkpoints; Lesson 23 closes the course with a guided final project followed by independent improvements.

Before you start

Complete ABAP Foundations first. The checkpoint projects follow ABAP SQL, CDS & RAP: Project 1 after Lesson 5, Project 2 after Lesson 9, Project 3 after Lesson 14, and Project 4 after Lesson 18. Finish with the final Stock Check project in Lesson 23 after Lesson 22.

Project 1 — Travel Booking Inspector

When to start: after SQL & CDS Lesson 5

Approximate duration: one working day

Build a read-only ABAP Cloud console application that accepts a Travel ID and displays the related travel, customer, bookings, carriers, and flight connections. The finished application uses CDS View Entities for the data model, a Reader class for ABAP SQL access, and a Runner class for output and summary logic, including booking and distinct-carrier counts.

Start the Travel Booking Inspector project →

Project 2 — Travel Budget Review Manager

When to start: after SQL & CDS Lesson 9

Approximate duration: one working day

Build an ABAP Cloud application that stores budget reviews for existing travel requests. Combine custom persistence with CDS models, associations, calculated fields, aggregation, and safe ABAP SQL writes, using Reader and Runner classes. This checkpoint brings together Lessons 1–9 before moving on to RAP.

Start the Travel Budget Review Manager project →

After completing Project 2, continue with Lesson 10 — RAP Foundations. Lessons 10–14 take you through managed business objects, EML transactions, business rules, actions, and feature control.

Project 3 — Purchase Request Workflow Manager

When to start: after SQL, CDS & RAP Lesson 14

Approximate duration: one working day

Build a managed RAP Business Object for an internal purchase-request workflow. Combine custom persistence, a root CDS entity, managed behavior, EML transactions, determinations, validations, messages, actions, and dynamic feature control. Prove the approval and rejection paths, validation failures, and runtime enforcement through an independent console consumer.

Start the Purchase Request Workflow Manager project →

This checkpoint brings together Lessons 1–14. Next, continue with Lesson 15 — Authorization, followed by the service layer, draft editing, and compositions in Lessons 16–18.

Project 4 — Service-Ready Purchase Request Application

When to start: after SQL, CDS & RAP Lesson 18 and Project 3

Approximate duration: one working day

Extend the Purchase Request Workflow Manager with ownership, CDS DCL, RAP authorization, draft editing, and Review Notes as a composed child. Add projections, value help, UI metadata, and an OData V4 UI service. Prove the workflow and composition lifecycle through Fiori Elements and an independent EML verification class.

Start the Service-Ready Purchase Request Application project →

This checkpoint brings together Lessons 15–18 using your Project 3 Business Object. After completing it, continue with Lesson 19 — RAP Business Events.

Lesson 23 — Final Stock Check Project

When to start: after SQL, CDS & RAP Lesson 22

Approximate duration: 3 hours guided learning + 3 hours independent practice

Build a local Stock Check RAP/Fiori application on SAP BTP and connect its Product value help to the read-only S/4HANA Product API using a CDS custom entity and OData client proxy. Then improve the UI, test remote filtering and paging, diagnose failures, and demonstrate the local/remote data boundary.

The guided project creates its own Service Consumption Model. Remote access requires the shared S/4HANA demo communication scenario in your Trial tenant; if unavailable, complete the local work and document which remote tests remain unverified.

Start the final Stock Check project →

Continue with independent practice and use the companion for architecture and troubleshooting.

Need to review the required concepts first? Return to the ABAP SQL, CDS & RAP overview.