SAP S/4HANA Public Cloud

Developer Roadmap: The Cloud-Native Path

Based on the latest trends and essential skills for 2025.

Slide 1 of 6 | Source: wtfsolution.com

1. Core Cloud Development Philosophy

Key Principles:

  • Continuous Innovation: Automatic updates ensure access to the latest features.
  • Seamless Scalability: Cloud-native design allows flexible resource scaling.
  • Key User Development: Emphasis on development tools accessible to non-traditional developers.
  • Side-by-Side Extensibility: Use of SAP BTP for custom applications and integrations, keeping the core clean.

Required Foundation:

Developers need basic functional knowledge of core modules like **MM, SD, FI, PP, QM, and PM** to understand business contexts.

Slide 2 of 6 | Concepts and Foundation

2. Pillar 1: Adobe Forms (Documents)

Adobe Forms are the modern, widely used standard for digital document generation, replacing older technologies like SmartForms.

Core Development Areas:

  • Maintain Form Template App: Used for custom form modifications.
  • Pre-delivered & Custom Templates: Starting point for development.
  • Custom Fields & Logic: Extending forms via Business Contexts and BADIs (Business Add-Ins).

Design & Logic Tools:

  • Adobe LiveCycle Designer (ADLC): For layout design.
  • Form Scripting: Utilizes **FormCalc** and **JavaScript** for dynamic logic.
  • Page Structures: Mastering Master Pages and Content Pages.
Slide 3 of 6 | Adobe Forms and Document Design

3. Pillar 2: UI & Reporting (RAP)

The ABAP RESTful Application Programming (RAP) model is essential for creating robust Fiori-based applications and APIs.

RAP Development Essentials:

  1. **Custom CDS Views:** Defining the data model and exposing data for consumption.
  2. **Service Binding (V2/V4 API):** Exposing the application service as an OData API.
  3. **Metadata for Fiori:** Defining the Fiori application layout and UI annotations.
  4. **Custom Screens/Tables:** Developing custom business objects using Managed or Unmanaged RAP development approaches.

Enhancements & Extensibility:

  • **Standard Screen Enhancement:** Using Custom Fields and Custom Logic (BADIs).
  • **Custom Business Objects (BO):** Defining entirely new persistence and logic within the SAP core.
Slide 4 of 6 | ABAP RESTful Application Programming (RAP)

4. Integration & Transport Management

API and Communication:

APIs are the only way to interact with the Public Cloud from external systems.

  • API Types: REST, SOAP, OData V2, OData V4.
  • Communication: Configuring Inbound (receiving data) and Outbound (sending data) communication scenarios.
  • ABAP Development Tools (ADT): The primary environment for core ABAP Cloud development.

Transport Management (TR):

Understanding how development moves between systems.

  • **Key User TR:** For changes made by non-developers (e.g., custom fields).
  • **Customizing TR:** For configuration changes.
  • **Development TR:** For ABAP/RAP code and repository objects.
Slide 5 of 6 | APIs and System Lifecycle

Roadmap Summary

The modern SAP Developer focuses on **Clean Core** principles, using **RAP** for Fiori/API development, **Adobe Forms** for documents, and **APIs** for all external integration.

Skills are centralized around the **ABAP Development Tools (ADT)** environment and **Key User Development** for simple extensions.

Suggested Next Learning Steps:

  • Deep Dive into RAP: Focus on creating a fully managed Custom Business Object.
  • Explore SAP BTP: Understand how Side-by-Side extensions are built and connected.
  • OData Service Implementation: Practice building and consuming OData V4 services.
Slide 6 of 6 | End of Presentation