onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

SAP-samples/abap-platform-rap130

A workshop building a RAP travel app entirely from Visual Studio Code, generated and edited through the ADT MCP Server and a coding agent.

Builds the same RAP Travel and Booking business object and its OData UI service from Visual Studio Code rather than Eclipse, using the ADT MCP Server built into ADT for Visual Studio Code to generate the business object, adjust the CDS views and behavior definitions, and run ABAP unit tests. GitHub Copilot is named as the coding agent tested against the workshop, though the material states any agent that supports Visual Studio Code's virtual workspace filesystem can call the MCP tools. It closes with publishing the service binding, previewing the Fiori elements app in the browser and debugging it from Visual Studio Code.

GitHub43 ★

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
ABAP
Demonstrates
Transactional modelABAPTransactional modelcapabilityHow a business object's behaviour is defined and who owns the transaction — the choice that shapes everything downstream in an application.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222@SAP-samplesmaintainerCarine Tchoutouo DjomoPersonContributes to this
In the atlas: contributes to 17, wrote 1@CarineTDSebastian BaskovichPersonContributes to this
In the atlas: contributes to 3@sebasbaskovich2 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
Workshop or CodeJam material

Connections1

Download
SAP-samples/abap-platform-rap130 connectionsSAP-samples/abap-platform-rap130PROVIDES→ demonstrates1demonstrates authoredTransactional model

README

quoted from SAP-samples/abap-platform-rap130 under Apache-2.0, read
SAP-samples/abap-platform-rap130/README.mdOn GitHub

Home - Workshops about the ABAP RESTful Application Programming Model (RAP)

REUSE status

RAP130 - Build SAP Fiori Apps with ABAP Cloud and SAP Joule for Developers in Visual Studio Code

Description

This repository contains the material for the hands-on session RAP130 - Build SAP Fiori Apps with ABAP Cloud and SAP Joule for Developers in Visual Studio Code 💎

You will build a transactional SAP Fiori elements app for travel management using the ABAP RESTful Application Programming Model (RAP) — entirely from Visual Studio Code, powered by the ADT MCP Server to generate and enhance your application.

Table of Content

Requirements

To complete the practical exercises, you need:

  • Visual Studio Code — Download from https://code.visualstudio.com/
  • ADT for Visual Studio Code — ADT for Visual Studio Code includes the built-in ADT MCP Server. Here is the link to download the extension.
  • IMPORTANT! ℹ️ A coding agent extension in Visual Studio Code that supports Visual Studio Code's virtual workspace filesystem — required to call MCP tools and read/edit ABAP files. GitHub Copilot is the primary tested agent and the one used and recommended for this tutorial.
  • Access to an SAP BTP ABAP Environment or SAP S/4HANA Cloud Public Edition or SAP S/4HANA Cloud Private Edition system that has the ABAP Flight Reference Scenario imported and SAP Joule for developers, ABAP AI capabilities enabled.

(*) SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private 2025 Edition are currently supported.

⚠ Exception regarding SAP-led events, such as "ABAP Developer Day" and "SAP CodeJam"

→ A dedicated ABAP system for the hands-on workshop participants will be provided. → Access to the system details for the workshop will be provided by the SAP instructors during the session.

Overview

In this hands-on session, you will learn how to use the ADT MCP Server to build a transactional SAP Fiori elements app entirely from Visual Studio Code — using AI-powered generation, code enhancement, and unit test support — powered by ABAP Cloud and the ABAP RESTful Application Programming Model (RAP).

🔵 Click to expand!

This hands-on workshop covers the full developer journey from Visual Studio Code environment setup to a fully functional, AI-enhanced transactional app:

  • Set up Visual Studio Code with the ADT for Visual Studio Code extension and connect to your ABAP Cloud system
  • Configure the built-in ADT MCP Server and connect it to your coding agent
  • Use ADT MCP tools to generate a complete RAP business object (Travel + Booking) and its OData UI service — all via natural language prompts
  • Explore and adjust the generated artifacts (CDS views, behavior definitions, metadata extensions) directly in Visual Studio Code
  • Publish the service binding and preview the SAP Fiori elements app in the browser
  • Add backend validations
  • Run ABAP unit tests from Visual Studio Code
  • Debug the SAP Fiori App from Visual Studio Code

Exercises

Follow these steps to build a SAP Fiori App using the ADT MCP Server and a coding agent (GitHub Copilot or compatible) in Visual Studio Code.

Exercises--
Getting Started--
Exercise 1: Enable the ADT MCP Server--
Exercise 2: Generate the SAP Fiori App via MCP Tools--
Exercise 3: Publish and Preview the Travel App--
Exercise 4: Add a Validation--
Exercise 5: Generate ABAP Unit Tests--
Optional Exercises
Exercises--
Exercise 6: Debug ABAP Code in Visual Studio Code--
Exercise 7: Create a Custom Agent--

Known Issues

How to obtain support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Further Information

You can find more information about ABAP AI, ABAP Cloud, RAP, and ADT for Visual Studio Code here:

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company and abap-platform-rap130 contributors. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file; you may not use any file of this project except in compliance with the License.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/abap-platform-rap130tree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, data-and-persistence
Contributors2
Carine Tchoutouo DjomoSebastian Baskovich

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-abap-platform-rap130
JSON
/artifacts/sap-samples-abap-platform-rap130.json
MCP
Connecting an agent