You have reached the final chapter. Over the last 19 chapters, you have learned classic ABAP, modern ABAP, RAP, CDS Views, Fiori, debugging, performance tuning, and interfaces. That is a lot of knowledge — but knowledge alone does not get you hired. Proof of skill does.

This chapter is where you turn everything into one working application — a capstone project that demonstrates what you can actually do. Not a tutorial exercise. Not a copy-paste from a book. Your own business scenario, your own design, your own code, your own app.

And at the end, you will have something to show recruiters, hiring managers, and interviewers — a link they can click, screenshots they can review, and a story you can tell.

🎯 What You Will Achieve in This Chapter

• A complete, working, end-to-end SAP application on your own system
• A GitHub repository with your source code exported via abapGit
• A README document explaining your design and architecture
• Screenshots and a demo of the working Fiori app
• A prepared interview presentation (5-10 minutes)
• A polished portfolio entry for your resume, LinkedIn, and blog
• Confidence that you can build real SAP applications independently

📘 What is a Capstone Project?

A capstone project is a self-designed, self-built, end-to-end application that demonstrates your skills. Unlike a tutorial (where you follow steps someone else wrote), a capstone is your own project — you choose the scenario, design the solution, and implement it.

Why capstone projects matter for SAP careers

🎬 Step 1 — Choose Your Business Scenario

Do not try to build something huge. Choose a scenario that is small enough to finish but real enough to be meaningful. The Travel scenario from Chapter 17 is a great default. Here are three options.

Option A — Travel Management (Recommended)

An app for managing business trips. Fields: Travel ID, Employee, Destination, Start Date, End Date, Cost, Currency, Status. Actions: Submit, Approve, Cancel.

Option B — Employee Leave Requests

An app for HR to manage employee leave. Fields: Request ID, Employee, Leave Type, Start Date, End Date, Days, Status. Actions: Approve, Reject.

Option C — Purchase Requisition Tracking

An app for procurement to track internal purchase requests. Fields: PR Number, Requester, Department, Item, Amount, Status. Actions: Submit, Approve.

🏗️ Step 2 — Design the Data Model

Every capstone starts with a table. What data does your scenario need? Write the fields down on paper first — then build.

Example — Travel table (ZTRVL_HEADER)

Build the table

⚙️ Step 3 — Build the RAP Business Object

This is the heart of your capstone. You will create six objects that work together.

Step 3a — Create the Interface View

@AbapCatalog.sqlViewName: 'ZITRAVEL'
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Travel Interface View'

define view ZI_Travel as select from ztrvl_header
{
  key travel_id     as TravelId,
      employee_id   as EmployeeId,
      destination   as Destination,
      start_date    as StartDate,
      end_date      as EndDate,
      cost          as Cost,
      currency      as Currency,
      status        as Status,
      created_by    as CreatedBy,
      created_at    as CreatedAt
}

Step 3b — Create the Consumption View with UI Annotations

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Travel App'
@UI.headerInfo: {
  typeName: 'Travel',
  typeNamePlural: 'Travels',
  title: { type: #STANDARD, value: 'TravelId' }
}

define view entity ZC_Travel
  as select from ZI_Travel
{
  @UI.lineItem: [{ position: 10 }]
  @UI.identification: [{ position: 10 }]
  key TravelId,

  @UI.lineItem: [{ position: 20 }]
  @UI.selectionField: [{ position: 10 }]
      EmployeeId,

  @UI.lineItem: [{ position: 30 }]
      Destination,

  @UI.lineItem: [{ position: 40 }]
      StartDate,

  @UI.lineItem: [{ position: 50 }]
      EndDate,

  @UI.lineItem: [{ position: 60 }]
  @Semantics.amount.currencyCode: 'Currency'
      Cost,

  @Semantics.currencyCode: true
      Currency,

  @UI.lineItem: [{ position: 70 }]
      Status
}

Step 3c — Create the Behavior Definition

managed implementation in class ZBP_Travel unique;

define behavior for ZI_Travel
persistent table ztrvl_header
lock master
authorization master ( global )
{
  create;
  update;
  delete;

  field ( readonly ) TravelId;

  validation validateDates   on save { field StartDate, EndDate; }
  validation validateCost    on save { field Cost; }

  determination setInitialStatus on modify { field Status; }
  determination setCreatedInfo   on save   { field CreatedBy, CreatedAt; }

  action ( features : instance ) approve;
  action ( features : instance ) reject;
}

Step 3d — Implement the Behavior

The class ZBP_Travel is generated automatically when you activate the BDEF. Open it and implement the methods you declared:

• validateDates — check that EndDate is not before StartDate
• validateCost — check that Cost is not negative
• setInitialStatus — set Status to ‘N’ if empty
• setCreatedInfo — fill CreatedBy and CreatedAt from sy-uname and sy-datum
• approve — set Status to ‘A’
• reject — set Status to ‘R’

Step 3e — Create the Service Definition and Binding

@EndUserText.label: 'Travel Service Definition'
define service ZUI_TRAVEL {
  expose ZC_Travel as Travel;
}

Then create a Service Binding named ZUI_TRAVEL_O4 with type OData V4 – UI, activate it, and click Preview.

✅ Step 4 — Test and Polish

Before you publish, verify your app works end to end. Here is a testing checklist.

Functional testing

Edge cases to test

• What happens with an empty filter?
• What happens with a very long destination name?
• What happens on simultaneous saves (lock conflicts)?
• What happens if you enter a Cost of 0 or negative?

📄 Step 5 — Document Your Project

A working app without documentation is invisible to recruiters. Write a README that explains your design.

README structure

# Travel Management App — ABAP RAP Capstone

## Business Scenario
A Travel Management app for HR to create, approve,
and track business travel requests.

## Architecture
- Database Table: ZTRVL_HEADER
- CDS Interface View: ZI_Travel
- CDS Consumption View: ZC_Travel
- Behavior Definition: ZI_Travel
- Behavior Implementation: ZBP_Travel
- Service Definition: ZUI_TRAVEL
- Service Binding: ZUI_TRAVEL_O4 (OData V4)

## Key Features
- Full CRUD operations on Travel records
- Validation: End date must be >= Start date
- Validation: Cost must be positive
- Determination: Status defaults to 'N' on creation
- Determination: CreatedBy and CreatedAt filled on save
- Action: Approve / Reject

## Screenshots
- List Report view
- Object Page view
- Validation error example
- Success message after approval

## Tech Stack
- SAP BTP ABAP Environment (or S/4HANA 2020+)
- ABAP RESTful Application Programming Model (RAP)
- OData V4
- Fiori Elements

## How to Run
1. Import the objects into your ABAP system
2. Activate in this order: Table → CDS Views → BDEF → ZBP → Service Def → Binding
3. Open Service Binding → Preview

## Author
[Your Name] — [Your LinkedIn / GitHub]

🌐 Step 6 — Publish and Share

Your capstone is done. Now make it visible.

Publish to GitHub with abapGit

Write a blog post

Publish a blog post describing your project. Include:

• The business scenario and why you chose it
• The architecture diagram
• The key technical decisions (Managed RAP, OData V4, Fiori Elements)
• What you learned building it
• Link to the GitHub repository

Share on LinkedIn

Post a short summary of the project with 2-3 screenshots. Include the GitHub link and tag it with #SAP #ABAP #RAP #Fiori.

Add to your resume

In the “Projects” section of your resume, list the project with:

• Business scenario (one line)
• Tech stack (RAP, CDS, OData V4, Fiori Elements)
• Link to GitHub

🎤 Step 7 — Present in an Interview

When an interviewer asks “tell me about a project you’ve built” — this is your moment.

The 5-minute presentation structure

🚀 What’s Next After the Capstone

You have finished the series. But your learning is only beginning. Here is what comes next.

Build a second capstone

Two projects are better than one. Pick a different scenario — HR Leave Requests, Procurement, or Sales — and build the same RAP pattern. This time faster, because you already know the workflow.

Deepen your knowledge

Apply for jobs

You are ready. Your resume should include:

• Your capstone project (with GitHub link)
• Your blog posts from this series
• Your LinkedIn with the project pinned
• Interview practice on the 165 Q&A across all 20 chapters

📝 Final Chapter Summary

• Capstone projects prove skill — a working app beats a certificate or a tutorial.
• Choose a small, real scenario — Travel, Leave, or Procurement.
• Build the data model first — a table, then CDS Views, then RAP.
• Use Managed RAP + OData V4 + Fiori Elements — the modern standard.
• Add validations, determinations, and actions — this is where real business logic lives.
• Test thoroughly — create, read, update, delete, edge cases.
• Document with a README — scenario, architecture, features, screenshots.
• Publish with abapGit — get your code on GitHub.
• Share on LinkedIn and your blog — make it visible.
• Present in 5 minutes — scenario, architecture, demo, challenges, link.
• Build a second project — two capstones doubles your credibility.