Role: SAP BTP / CAP Full-Stack Engineer (Fiori Elements + CAP CDS + Integration)
Context
: SAT (Supplier Allocation Tool) solution on SAP BTP using CAP backend, Fiori Elements (V4) with Flexible Programming Model, IAS (Identity Authentication Service), AMS (Authorization Management Service), CPI / S4HANA integration, HTML5 App Repository, and Standalone Approuter.
Purpose:
To design, develop, and secure end-to-end BTP applications, covering CAP domain models, Fiori Elements UIs, security integration with IAS/AMS, and connectivity to S/4HANA and CPI services.
1️
⃣ CAP \& CDS Modeling
Strong expertise in SAP Cloud Application Programming Model (CAP).
Proven experience designing and implementing domain models in CDS (entities, associations, compositions, views, projections).
Hands-on delivery of draft-enabled OData V4 services with active/draft entity modeling, late ID generation, transactional save/discard flows, and conflict handling aligned to Fiori Elements draft UIs.
Custom logic implementation using Node.js / TypeScript handlers (CREATE, UPDATE, DELETE, ACTIONS).
Modeling on replicated S/4HANA data in SAP HANA Cloud (external schemas / synonyms) while maintaining decoupled, performant CAP models.
Ability to design normalized, scalable data schemas separating master, transactional, and technical entities.
Apply HANA push-down and performance optimization (indices, pagination, projection vs consumption views).
2️
⃣ Fiori Elements (V4) with Flexible Programming Model \& UI Modeling
Hands-on experience developing Fiori Elements (V4) apps (List Report, Object Page, Analytical) backed by CAP services.
Use CDS / OData annotations (UI, ValueHelp, SelectionFields, FieldGroup, Identification, SideEffects, Draft etc) to design and develop feature-rich UIs with minimal custom code.
Configure inline editing, mass actions, value helps, side effects, and message handling.
Ensure draft-aware, non-blocking save/discard flows consistent with Front End behaviour.
Deep understanding of manifest.json, routing, dataSources, and model binding.
Experience integrating apps into BTP Launchpad / Work Zone and embedded S/4 FLP.
Implement role-based UI adaptations using AMS policies (authorization-driven field visibility and actions).
3️
⃣ BTP Infrastructure, Approuter \& Security (IAS + AMS)
Proven experience configuring and managing a Standalone Approuter (xs-app.json, routes, destinations, HTML5 Repo).
Set up and consume BTP Destinations with IAS-based authentication and principal propagation to CAP.
Understanding of:
IAS as IdP and AMS as centralized authorization layer.
Secure routing patterns for Fiori Elements apps calling CAP via approuter.
Destination: OAuth2 grant types (OAuth2JWTBearer, OAuth2UserTokenExchange) and App-to-App SSO patterns.
Apply authentication and authorization checks at both CAP service and Fiori levels.
Configure apps in BTP Work Zone (tiles, target mappings, role collections) and collaborate with the Identity Management team for IAS/AMS-based role assignment.
4️
⃣ Integration \& Connectivity (CPI / S4HANA)
Proven experience consuming S/4HANA APIs (OData / REST) through BTP Destinations.
Design and implement robust CAP → CPI interfaces for data publishing to S/4HANA (1:1 API calls, payload validation, status tracking).
Handle asynchronous integration scenarios (correlation IDs, callbacks, error logging).
5️
⃣ Quality, Operations \& Lifecycle
Hands-on experience implementing unit and integration tests for CAP services.
Design technical / audit logging, correlation ID propagation, and error messaging (OData V4 → Fiori Elements).
Manage environment configuration (VCAP, service bindings, destinations).
Understanding to CI/CD setup, working experience with GITHUB.
6️
⃣ Behavioural / Ways of Working
Simplifies designs without over-engineering (e.g., status models, publish flows).
Communicates clearly with architects, functional consultants, security, CPI and S/4 teams.
Detail-oriented—recognises technical nuances (example code issues, draft vs active entities, persist vs reference designs).
Works effectively and a good team player.