SAP S/4HANA Key-User In-App Extensibility Architecture & Rules

1. The 3-Tier Extensibility Placement of Key-User In-App

SAP defines three distinct extensibility tiers. Determining whether an extension belongs in Tier-1 In-App vs. Developer Extensibility is the first governance gate of Clean Core architecture:

2. Business Contexts: The Extensibility Foundation

In SAP S/4HANA, custom fields cannot be arbitrarily attached to database tables via classic APPEND STRUCTURE. Instead, SAP provides pre-engineered Business Contexts that bundle:

• Underlying primary persistence tables (e.g., VBAK, VBAP, BKPF, BSEG, BUT000).
• Core CDS Views exposed to UI layers and OData APIs.
• Search views, CDS analytical projections, and print form interfaces (Adobe Forms).
• In-App Cloud BAdIs associated with transactional validation and calculation events.

Standard Enterprise Business Context Examples

3. The Restricted ABAP Sandbox: Syntax Rules

Key-User Custom Logic executes in a sandboxed, security-hardened environment known as Restricted ABAP (Language Version 2). This guarantees that custom business logic cannot crash the application server, corrupt memory, or introduce SQL injection vulnerabilities.

Allowed vs. Forbidden Statements in Restricted ABAP

4. Production Code Blueprint: Key-User Custom Logic

The following is a production-grade implementation of an S/4HANA Key-User Custom Logic enhancement for the SALESDOCUMENT context, calculating order prioritization and validating compliance:

" Business Context: SALESDOCUMENT
" Extension Point: BAdI Definition 'SD_SLS_MODIFY_HEAD' (Sales Order Header Modification)
" Language Version: Restricted ABAP (Language Version 2)

CLASS zcl_keyuser_sales_logic DEFINITION PUBLIC FINAL CREATE PRIVATE.
  " In Key-User Custom Logic, class scaffolding is handled by SAP Fiori
ENDCLASS.

" Implementation logic injected into Custom Logic Fiori App:
DATA: lv_user      TYPE syuname,
      lv_sys_date  TYPE sydatum,
      lv_amount    TYPE p DECIMALS 2.

" 1. Retrieve runtime context via released system utility
lv_user     = cl_abap_context_info=>get_user_technical_name( ).
lv_sys_date = cl_abap_context_info=>get_system_date( ).

" 2. Guard Clause: Skip execution if sales order is already locked for billing
CHECK salesdocument-billingblockstatus IS INITIAL.

" 3. Custom Field Derivation (YY1_ApprovalRequired_SDH)
" If net amount exceeds threshold, enforce mandatory VP approval flag
IF salesdocument-totalnetamount > 50000.
  salesdocument-yy1_approvalrequired_sdh = abap_true.
  salesdocument-yy1_approvernotes_sdh    = 'High-value order exceeding 50,000 EUR threshold'.
ELSE.
  salesdocument-yy1_approvalrequired_sdh = abap_false.
ENDIF.

" 4. Audit Trail Population
salesdocument-yy1_lastauditedby_sdh   = lv_user.
salesdocument-yy1_lastauditeddate_sdh = lv_sys_date.

" 5. Validation Check: Raise business message if delivery block missing on restricted accounts
IF salesdocument-yy1_customerrisklevel_sdh = 'HIGH' AND salesdocument-deliveryblockreason IS INITIAL.
  " Raise message into SAP Fiori message log
  messages-add_message(
    iv_msgid = 'ZSD_CLEAN_CORE'
    iv_msgno = 001
    iv_msgty = 'E'
    iv_msgv1 = 'High-risk customer requires an active Delivery Block reason'
  ).
ENDIF.

5. The Custom Field Enablement Pipeline

Creating a custom field via the Custom Fields app is only the first step. To make it functional, it must be published through the enablement pipeline:

1. Field Definition: Enter Field Label, Tooltip, and select Data Type (Text, Number, Date, Amount, or Code List).
2. Business Context Binding: The system automatically assigns the YY1_ prefix and provisions the field in the underlying CDS views.
3. UIs & Reports Enablement: Enable visibility on target SAP Fiori applications (e.g., Manage Sales Orders, Manage Customer Returns).
4. OData APIs & SOAP Enablement: Expose the field to standard released OData APIs for Tier-3 BTP consumption.
5. CDS Views Exposing: Automatically propagate the custom field into analytical cube and projection views without manual DDL edits.
6. Publishing: Trigger automated generation of active CDS artifacts and DDL extensions.
7. Transport Packaging: Add the field to an Export Software Collection for staging and production import.

6. Decision Tree: Key-User vs. Developer vs. Side-by-Side

Use this architectural decision tree to determine the correct placement for any incoming extension request: