S/4 HANA Cloud Application Development Extensibility Model

To help you understand how different extensibility options work in SAP S/4HANA, here’s a sequence-based explanation:

This part contains the following topics:

• ??? Key-User Extensibility
• ?? Classic Extensibility
• ???? Developer Extensibility
• ?? Side-by-Side Extensibility

??? Key-User Extensibility

Summary This extension option empowers business users to make customizations and enhancements directly in the SAP application. Perfect for quick tweaks that don’t need deep technical know-how! ??

Introduction Key User Extensibility is the easiest way to extend functionality in SAP S/4HANA Cloud. ???? It’s all about enabling non-technical users (citizen developers) to customize the system without touching the SAP code, keeping the core clean! ??

Range of Functions With Key User tools in SAP S/4HANA Cloud or On-Premise, you can:

• ?? Adapt the UI
• ??? Create Custom Fields
• ??? Develop Custom Business Objects
• ?? Implement Business Logic

Examples

• ?? Customizing screen layouts (moving/hiding fields, changing labels)
• ?? Creating custom CDS views and analytical applications
• ?? Adding custom fields to processes (from quote to invoice)
• ?? Copying and customizing print/email form templates

Advantages

• ?? Fully managed and integrated into SAP S/4HANA
• ?? Minimal development knowledge required
• ?? Available in SAP S/4HANA Cloud (private and public) and On-Premise

Differences in Deployment Key-User tools are primarily designed for SAP S/4HANA Cloud but are also available for private and on-premise versions. ??

?? Classic Extensibility

Summary This traditional method involves directly customizing the SAP code. ?? It offers great flexibility but can pose challenges during updates and maintenance. ???

Introduction Classical ABAP-based enhancement is recommended only in exceptional cases. It’s a method from the past, and in most scenarios, other options are preferred. ???

Advantages

• ?? Extremely powerful and flexible
• ?? No restrictions on extension methods
• ??? Highest degree of freedom

Availability Classic Extensibility is available for SAP S/4HANA On-Premise and Private Cloud installations. ??

???? Developer Extensibility

Summary Developers can perform advanced customizations and extensions beyond key-user options. ??? This requires deep technical knowledge but offers vast customization opportunities. ??

Introduction Developer Extensibility is the way to implement extensions while keeping the core clean. It uses ABAP RESTful Application Programming Model (RAP), available on all SAP S/4HANA deployment options. ???

Core Features

• ??? Core Data Services (CDS) for SAP HANA-optimized queries
• ?? Modernized ABAP language for business logic
• ?? OData protocol for stateless communication
• ?? Business objects and services for transactional and analytical apps

Advantages

• ?? Standardized development processes
• ?? Efficient development practices
• ?? Full access to SAP S/4HANA stack
• ?? Supports both cloud and on-premise environments

Use Cases

• ?? Custom applications requiring SQL access to SAP S/4HANA data
• ?? Extensions running in the same Logical Unit of Work (LUW) as SAP apps
• ?? Custom APIs or services for SAP BTP applications

?? Side-by-Side Extensibility

Summary This method enables extensions to be developed and integrated outside the SAP system, specifically on SAP BTP. ??? It allows flexible customizations without touching the core system, simplifying maintenance and upgrades. ??

Introduction Side-by-Side Extensibility uses SAP’s released APIs to perform CRUD operations on SAP S/4HANA Cloud data. ?? Different concepts, tools, and services are available, utilizing these remote APIs. ??

Options

1. Full Stack Development on SAP BTP: Three-tier architecture (Database, Business Logic, Front-End)
2. UI Development on SAP BTP: Pure UI development based on APIs from SAP S/4HANA back-end

Advantages

• ?? Flexibility in content and timing
• ?? Fast response to innovations and changes
• ?? Decoupled extensions that are independent of SAP S/4HANA operation
• ?? Independent lifecycle management
• ??? Supports both ABAP and non-ABAP development