ARCHITECTURAL BLUEPRINT #84 • ENTERPRISE BUSINESS APPROVALS & ORCHESTRATION

SAP S/4HANA Flexible Workflow (SWF_FLEX): Clean Core Approval Architecture & Task Center Guide

How enterprise architects transition from classical Business Workflow (SWDD/BOR) to SAP S/4HANA Flexible Workflow. Master scenario definitions, Agent Determination BAdIs, deadlock escalations, and SAP Task Center federation on SAP BTP.

⚡ The Clean Core Workflow & Extension Blueprint

Complete production blueprints for Flexible Workflow, RAP BAdIs, and BTP Task Center in The SAP Clean Core & ABAP Cloud Handbook.

Get Enterprise Suite (-80% Off: €9.80) →

1. The Retirement of Classical SWDD & BOR

For decades, SAP Business Workflow relied on transaction SWDD, Business Object Repository (BOR) macros, and container bindings. In SAP S/4HANA and Clean Core, this architecture is deprecated for new scenarios:

Rigid transports: Changing an approval threshold required an ABAP development transport through Dev, QA, and Production.
No mobile ergonomics: Classical workflow tasks required complex SAP GUI or Web Dynpro screens that failed on mobile devices.
Clean Core violation: Modifying standard BOR objects (BUS2012) broke upgrade compatibility.

2. Flexible Workflow Architecture: Scenarios, Steps & Rules

Component	Classical Business Workflow (SWDD)	Flexible Workflow (SWF_FLEX)
Configuration Tool	SAP GUI Builder (SWDD)	Fiori App "Manage Workflows" (F1481)
Business Object Model	BOR Object Type (SWO1)	ABAP Cloud CDS View / RAP Entity
Agent Determination	Standard Tasks & Rule Containers	Cloud-Released BAdIs & Org Hierarchy
Threshold Changes	Code modification & Transport	Business Key-User directly in Production
Mobile Support	Custom SAP Fiori Gateway Service	Native My Inbox & BTP Task Center

3. Clean Core Agent Determination BAdI Pattern

When business logic requires complex multi-dimensional approval matrices (e.g. routing based on Plant, Cost Center, and Purchasing Group simultaneously), developers implement clean core released BAdIs:

CLASS zcl_mmpur_wf_agents DEFINITION
  PUBLIC FINAL CREATE PUBLIC.

  PUBLIC SECTION.
    INTERFACES if_badi_interface.
    INTERFACES if_mmpur_workflow_agents_v2.
ENDCLASS.

CLASS zcl_mmpur_wf_agents IMPLEMENTATION.
  METHOD if_mmpur_workflow_agents_v2~get_approvers.
    " Query released CDS view for Purchasing Document
    SELECT SINGLE NetAmount, Plant
      FROM I_PurchaseOrderAPI01
      WHERE PurchaseOrder = @purchasingdocument
      INTO @DATA(ls_po).

    IF ls_po-NetAmount >= 50000.
      " Route to Senior Financial Controller
      SELECT SINGLE ResponsibleUser
        FROM I_CostCenter
        WHERE CostCenter = 'CC_HEAD_01'
        INTO @DATA(lv_lead).
      APPEND VALUE #( bname = lv_lead ) TO approver_list.
    ENDIF.
  ENDMETHOD.
ENDCLASS.
    

4. Enterprise Centralization via SAP Task Center on BTP

In hybrid enterprise landscapes, business users receive approval requests from multiple SAP systems: S/4HANA Finance, SAP Ariba, SAP Fieldglass, and SAP SuccessFactors. SAP Task Center on SAP BTP unifies all tasks:

📱 How SAP Task Center Federates Approvals

1. Real-Time Push: When a Flexible Workflow work item is generated in S/4HANA, the Task Center connector pushes metadata to BTP via CloudEvents.

2. Universal Web & Mobile UI: Executives approve or reject with one click from their mobile phone or SAP Start portal.

3. Instant Callback: The decision is posted back securely to S/4HANA via the BTP Destination Service using Principal Propagation.

Master the Complete SAP Clean Core Architecture

Explore over 95 interactive tools, 80+ production architecture cheat sheets, and the complete Clean Core & ABAP Cloud Developer Handbook.

Get Enterprise Suite (-80% Off: €9.80) → Order on Amazon ($19.99) →