Clean Core Architecture Guide #55

SAP Build Process Automation (SPA) & Clean Core Workflow Guide

⏱️ 15 min read 🏢 Enterprise Orchestration Blueprint ⚡ S/4HANA Cloud & BTP Ready

Core Architectural Mandate: In SAP S/4HANA Clean Core, custom Business Workflow developments (classic BOR objects, SWDD, custom approval tables) are classified as high-risk technical debt. Clean Core mandates side-by-side orchestration using SAP Build Process Automation (SPA) on SAP BTP. Core S/4HANA transactions publish asynchronous domain events, while SPA manages decision rules, human approval forms, and automated REST/OData callbacks.

1. The Problem: Classic Business Workflow vs. SAP Build SPA

For over twenty years, SAP developers built complex approval logic inside the ABAP runtime using Business Object Repository (BOR) objects, custom workflow containers, and direct table updates.

Workflow Dimension	Classic SAP Workflow (SWDD)	SAP Build Process Automation (SPA)
Runtime Execution	Directly on S/4HANA ABAP application server	Side-by-side on SAP BTP Cloud
Trigger Mechanism	SWE2 event linkages on legacy database tables	Native CloudEvents 1.0 (Event Mesh / AEM)
Decision Logic	Hardcoded custom ABAP function modules	Visual Business Rules decision tables
Approver Experience	SAP GUI Business Workplace (SBWP)	SAP My Inbox, Microsoft Teams & Mobile Start
Clean Core Compliance	Tier 3 modification (ATC warning)	✅ Official Tier 1 Clean Core Standard

2. Event-Driven Workflow Orchestration

In Clean Core architecture, the S/4HANA transactional application is completely decoupled from the workflow lifecycle:

Entity Creation: A user creates a sales order with an unusually high discount (e.g. 20%).
Atomic State Lock: In the RAP save_modified phase, the sales order status is set to APPROVAL_PENDING, blocking downstream delivery and billing.
CloudEvent Publication: A native RAP event (SalesOrder.ApprovalRequired.v1) is raised. SAP Event Mesh routes this event to the SPA trigger endpoint.
BTP Orchestration: SPA starts a process instance, queries decision tables, and assigns approval tasks to the appropriate sales vice-president.

Master SAP Process Automation & Clean Core Architecture

Explore complete architectural blueprints for SAP Build Process Automation, Event-Driven Architecture, Principal Propagation, and human-in-the-loop AI in The SAP Enterprise Architecture Suite.

Get the Full Architecture Suite (FLASH80 - 80% Off) →

3. Secure Callback with Principal Propagation

When the executive approves the request in Microsoft Teams or SAP My Inbox:

SPA triggers a Destination Action calling S/4HANA. Using OAuth 2.0 SAML Bearer Assertion, the executive's identity is propagated to S/4HANA (ABAP SY-UNAME). The RAP Action ReleaseOrder executes under the executive's authorizations, updating the audit trail without exposing service account credentials.

4. Low-Code Form Design & Document Extraction

Unlike classic SAP GUI screens, SPA allows business analysts to design intuitive mobile-friendly approval forms with drag-and-drop ease. Furthermore, SPA integrates with SAP Document Information Extraction (DOX), enabling generative AI to automatically parse supplier invoice PDF attachments and pre-fill form fields before human verification.

Summary Architectural Checklist

✅ Zero BOR Objects: No custom development in transaction SWDD.
✅ CloudEvents Ingestion: Processes initiated strictly via asynchronous standard events.
✅ Principal Propagation: Approver identity preserved during S/4HANA core callback.
✅ Audit Compliance: Complete process execution timeline stored in BTP audit logs.

← Back to Interactive SPA Workflow Architect Tool