Fiori and the BTP platform

In S/4HANA, users no longer see transactions but Fiori apps. Behind every app there is a simple chain: a table, a CDS view that makes it readable, an OData service that exposes it, a user interface generated by Fiori Elements, and behavior written with RAP. Extensions, for their part, increasingly go to the SAP BTP platform to keep the core clean. This module follows a single piece of data from end to end: the purchase orders of SENTINEL SA.

Audience: Key users and project managers (level 1), functional and technical consultants (level 2), developers and architects (level 3).
Prerequisites: Level 1: know a business module. Level 2: be able to read a table (TOOLS module, SE16H). Level 3: basic programming in ABAP or another language.
Duration: 3 days (0.5 + 1.5 + 1)
21 h · day-by-day schedule

Day-by-day schedule

3 days, 21 h of training. Beginner 0,5 d, intermediate 1,5 d, advanced 1 d. Durations are calculated from the content of each chapter. Click a line to open the chapter.

BeginnerIntermediateAdvancedAssessment

Day 1Beginner · Intermediate

Morning · 9:00 – 12:30

Afternoon · 13:30 – 17:00

Day 2Intermediate

Morning · 9:00 – 12:30

Afternoon · 13:30 – 17:00

Day 3Advanced

Morning · 9:00 – 12:30

Afternoon · 13:30 – 17:00

FIORI curriculum

3 parts, 19 topics. Open a part, then follow the link to the chapter, the guide or the mini-process.

Level 1 · Beginner : Understanding Fiori and the platform

From SAP GUI to Fiori apps
A transaction does everything for everyone; an app does one thing for one role.
Chapter →
The launchpad, catalogs and roles
A tile only appears if a role grants access to it.
Chapter →
App types and the reference library
Create, analyze, look up: three families, and a library to find them.
Chapter →
The architecture in one picture
A click in the browser crosses five layers.
Chapter →
Clean core and BTP in plain words
Do not touch the engine so you can change it without pain.
Chapter →

Level 2 · Intermediate : Building: CDS, OData and Fiori Elements

CDS views: making a table readable
A CDS view states plainly what the table hides behind technical names.
Chapter →
Writing a CDS view step by step
Associations, paths, calculated fields, parameters, aggregations: the complete toolbox, on purchase orders.
Chapter →
SAP’s data model in practice
Before writing a view, find the one SAP already ships, and know whether you may use it.
Chapter →
Annotations: meaning inside the view
A few lines above a field decide the screen, the security and the value helps.
Chapter →
OData: the front door
A web address, a verb, a few options: that is the whole protocol.
Chapter →
Expose and test a service
Three ways to create a service, only one way to check that it works.
Chapter →
Fiori Elements: the generated app
No screen to draw: annotations describe, the floorplan builds.
Chapter →
Authorizations and troubleshooting
Four symptoms, four causes: knowing where to look saves hours.
Chapter →

Level 3 · Advanced : Developing and extending: RAP and BTP

Analytical views and performance
The same CDS views also serve for analysis: cubes, dimensions, queries. And a slow view can be diagnosed.
Chapter →
RAP: the programming model
Data, behavior, service: three layers, each in its place.
Chapter →
Behavior: validate, calculate, act
A behavior definition reads like a set of rules.
Chapter →
EML and ABAP Cloud
Talk to business objects through their interface, never directly to the tables.
Chapter →
The SAP BTP platform
An account, subaccounts, environments, services.
Chapter →
Choosing where to extend
The right place depends on who uses it, which data, and how long it lives.
Chapter →