SAP Build Process Automation — Workflow, RPA, and Business Rules on BTP Guide

Last year I spoke with a finance manager at a European manufacturing firm running S/4HANA. Every time a vendor invoice exceeded $50,000, his team executed a 7-step manual approval routine.

The junior clerk opened S/4HANA, copied invoice details into an Excel sheet, composed an email to the regional director, waited for an email reply, logged back into S/4HANA, attached the approved PDF, and executed transaction FB60.

They processed 80 high-value invoices every week. The manual effort consumed 15 hours of staff time weekly, created data entry typos, and delayed vendor payments by days.

When I asked why they hadn’t automated it, the manager replied: “Because building a custom workflow in S/4HANA requires 3 months of ABAP development, custom tables, and Basis security roles.”

SAP Build Process Automation on SAP BTP eliminates that barrier. It brings together Workflow management, Robotic Process Automation (RPA), Business Rules, and drag-and-drop Forms into a single low-code platform.

This guide explains what SAP Build Process Automation is, how its core components fit together, and how to automate business processes on SAP BTP without writing complex code.

---

What is SAP Build Process Automation?

SAP Build Process Automation is a cloud service on SAP Business Technology Platform (BTP).

It consolidates three previously separate SAP cloud products into one unified solution:

1. SAP Workflow Management (multi-step approval workflows and task management)
2. SAP Intelligent Robotic Process Automation (iRPA) (software bots that automate repetitive UI tasks)
3. SAP Business Rules (central decision tables and business logic management)

┌────────────────────────────────────────────────────────────────────────┐
│                   SAP Build Process Automation (BTP)                   │
├───────────────────┬───────────────────┬────────────────────────────────┤
│   Process Builder │   RPA Bots (iRPA) │   Business Rules Engine        │
│ (Flows & Approval)│ (Screen Scraping) │  (Decision & Matrix Tables)    │
└───────────────────┴───────────────────┴────────────────────────────────┘

The key advantage: business analysts and developers design end-to-end automation flows using a visual drag-and-drop canvas. You don’t need to write custom ABAP code or configure complex background jobs.

---

The 4 Pillars of SAP Build Process Automation

To design automations effectively, you need to understand the four core building blocks.

---

Pillar 1: Process Builder (Visual Workflow Canvas)

The Process Builder is your main design environment inside the SAP Build Studio.

You build workflows using a flowchart-like canvas. You drag steps onto the screen and connect them with arrows:

[Start Event] ──► [Approval Form] ──► [Condition Check] ──┬──► (Approved) ──► [Create S/4HANA PO]
                                                         └──► (Rejected) ──► [Send Email Notice]

Process Builder supports:

• Approval Steps: Assigns interactive approval tasks to specific users or user groups.
• Form Triggers: Captures input data from web forms submitted by users.
• Service Calls: Calls S/4HANA OData APIs or BTP REST endpoints.
• Sub-processes: Triggers secondary nested workflows.

---

Pillar 2: Low-Code Forms

Forms capture input from users or present data for approval.

Instead of writing HTML/CSS or SAPUI5 code, you drag form fields onto a layout canvas:

• Text inputs (Vendor Name, Invoice ID)
• Currency inputs (Total Amount)
• Dropdown selectors (Cost Center, Department)
• File attachment controls (Invoice PDF copies)

When a workflow reaches an approval step, the approver receives a notification in their SAP Build Work Zone or Fiori Launchpad My Inbox app. The approver views the form, checks the details, and clicks Approve or Reject.

---

Pillar 3: Business Rules Engine

Business logic changes constantly. Discount thresholds change, approval limits change, and regional routing rules update quarterly.

Hardcoding business rules inside ABAP code or workflow scripts means you have to modify code and deploy transports every time business policy changes.

The Business Rules Engine separates business logic from code. You define rules using decision tables:

Condition Table: Purchase Order Approval Matrix

Amount (USD)  │ Department  │ Required Approver      │ Auto-Approve?
──────────────┼─────────────┼────────────────────────┼───────────────
<= 10,000     │ Any         │ Direct Manager         │ Yes
> 10,000      │ Manufacturing│ Plant Director        │ No
> 50,000      │ Any         │ VP of Procurement      │ No

At runtime, the workflow passes the order amount and department to the Business Rules engine. The engine evaluates the table and returns the required approver ID.

When approval policies change next month, a business analyst edits the decision table in a web browser without touching code or creating SAP transport requests.

---

Pillar 4: Robotic Process Automation (RPA Bots)

Not all applications have modern OData or REST APIs. You might need to extract data from a legacy Windows application, a third-party supplier portal, or a legacy web system with no API access.

RPA Bots solve this by automating human user actions on screen:

• Opening a desktop application or browser
• Clicking buttons and entering text into input boxes
• Extracting data from PDF invoices using optical character recognition (OCR)
• Copying data between systems

RPA bots run in two modes:

• Attended Bots: Run on a user’s desktop, assisting the user with repetitive steps while they work.
• Unattended Bots: Run autonomously on dedicated background servers, processing work queues 24/7 without human supervision.

---

Real-World Scenario: Automating Vendor Invoice Processing

Let’s build a complete mental model by stepping through a real-world automation architecture.

The Problem

A company receives 500 PDF vendor invoices per month via email. Accounts Payable staff manually open each PDF, re-type data into S/4HANA transaction FB60, and email managers for approval if the invoice exceeds $10,000.

The Automated Architecture with SAP Build

[Email Arrival (PDF)]
        │
        ▼
[Unattended RPA Bot] ──► (Extracts PDF text using Document Information Extraction AI)
        │
        ▼
[Business Rules Engine] ──► (Determines approval path based on Invoice Amount)
        │
        ├────────────── Amount <= $10,000 ──────────────┐
        │                                                │
        ▼                                                ▼
[Manager Approval Form]                      [Auto-Post API Call]
(Sent to Fiori My Inbox)                                 │
        │                                                │
        ▼                                                │
[S/4HANA OData API] ◄────────────────────────────────────┘
(Posts Financial Document automatically)

The Step-by-Step Flow:

1. Trigger: A new email with an attached PDF invoice arrives in the accounts payable mailbox.
2. Extraction: An unattended RPA bot triggers automatically. It passes the PDF to SAP’s Document Information Extraction service (AI/OCR). The service extracts Vendor Name, Invoice Date, Line Items, and Total Amount into JSON format.
3. Decisioning: The JSON payload passes to the Business Rules Engine. The engine checks the invoice amount.
4. Approval Routing:
   • If Amount <= $10,000: The rule returns AutoApprove = True.
   • If Amount > $10,000: The rule returns Approver = Finance_VP. A process instance starts, sending an interactive approval form to the Finance VP’s Fiori My Inbox.
5. Posting: Once approved (or if auto-approved), a service task calls the S/4HANA OData API API_SUPPLIERINVOICE_PROCESS_SRV to post the invoice directly into S/4HANA.
6. Audit Log: The entire execution history (who approved, when, extracted JSON values, posted document number) saves automatically to BTP process audit logs.

Total human effort reduced from 15 minutes per invoice to 10 seconds (only when high-value manual approval is required).

---

How to Get Started with SAP Build Process Automation

You can test SAP Build Process Automation using your free BTP developer setup.

---

Step 1: Enable the Service on BTP Free Tier

1. Log into your SAP BTP Cockpit free subaccount.
2. Go to Service Marketplace → Search for SAP Build Process Automation.
3. Create an instance (select the free plan).
4. Go to Instances and Subscriptions → Click Go to Application to open the SAP Build Lobby.

---

Step 2: Open the SAP Build Lobby

The SAP Build Lobby is your central hub for creating apps, processes, and business rules.

Click Create → Select Build an Automated Process.

Select Business Process and give it a name (e.g., Purchase_Requisition_Approval).

---

Step 3: Build Your First Simple Process

In the visual editor:

1. Add a Form Trigger: Click + -> Form. Create an entry form with fields Employee Name, Item Description, and Estimated Cost.
2. Add an Approval Step: Click + -> Approval. Link the fields from your form trigger to the approval view.
3. Add a Condition: Click + -> Condition.
   • If Estimated Cost > 500 -> Route to Manager Approval.
   • If Estimated Cost <= 500 -> Route to Auto-Approved.
4. Add Mail Notifications: Add email tasks to inform the requester of the decision.
5. Save and Deploy: Click Release -> Deploy.

You have just created and deployed a working cloud workflow on BTP.

---

SAP Build Process Automation vs Classic ABAP Workflow (SWDD)

Many traditional SAP developers wonder how SAP Build compares to classic on-premise ABAP Workflow (transaction SWDD).

Feature	Classic ABAP Workflow (SWDD)	SAP Build Process Automation
Platform	On-premise S/4HANA / ECC system	SAP Business Technology Platform (Cloud)
Development Style	Heavy ABAP coding, container elements	Drag-and-drop visual low-code canvas
UI Integration	SAP GUI screens, basic WebDynpro	Fiori Launchpad My Inbox, SAP Build Work Zone
Cross-System Workflow	Difficult (requires ALE/IDocs/RFC)	Native (connects SAP and non-SAP cloud APIs)
RPA / AI Integration	Not available natively	Built-in (Screen scraping, OCR document extraction)
Business Rules	Hardcoded ABAP or BRF+	Decision Tables with visual web editor
Target Developer	Senior ABAP Specialist	Business Analyst + Citizen Developer + IT Developer

Classic ABAP Workflow still works well for internal S/4HANA-only processes. But whenever a process crosses system boundaries (connecting S/4HANA to Salesforce, BTP, or cloud apps) or requires RPA/AI document extraction, SAP Build Process Automation is the recommended choice.

---

Quick Checkpoint — Test your understanding

Question 1: Which four core capabilities are consolidated inside SAP Build Process Automation?

Answer: Process Builder (Workflows), Low-Code Forms, Business Rules Engine, and Robotic Process Automation (RPA Bots).

Question 2: Why is it better to use the Business Rules Engine for approval thresholds rather than hardcoding IF-ELSE logic inside ABAP code?

Answer: Business rules can be updated instantly by business analysts in a visual web editor without writing code, modifying programs, or creating transport requests through the development landscape.

Question 3: What is the difference between an Attended RPA Bot and an Unattended RPA Bot?

Answer: Attended bots run on a user’s local desktop to assist them with manual tasks. Unattended bots run autonomously on dedicated background servers, processing work queues 24/7 without human intervention.

---

Common mistakes to avoid

Mistake 1: Trying to use RPA when a clean API exists. RPA screen scraping should be your last resort. If S/4HANA or your target system provides an OData or REST API, always use service calls. APIs are faster, more reliable, and don’t break when a user interface layout changes slightly.

Mistake 2: Building monolithic workflows. Don’t try to cram 50 approval steps, 10 RPA bots, and 20 business rules into a single process flow. Break complex automation projects into modular sub-processes. This makes testing and error isolation significantly easier.

Mistake 3: Forgetting exception routing. Every service call or RPA bot step can fail (API endpoint down, invalid payload). Always add error handling branches in your Process Builder flow so failed steps route to an administrator notification rather than stalling the entire workflow silently.

Mistake 4: Not testing forms on mobile viewports. Users frequently approve requests from their smartphones via Fiori My Inbox. Always test your custom forms on mobile viewports in the SAP Build form editor to ensure fields render legibly on smaller screens.

---

Summary

SAP Build Process Automation transforms how companies automate business operations on SAP BTP.

By combining visual Process Builder workflows, low-code Forms, Business Rules, and RPA Bots, you eliminate manual repetitive tasks, accelerate approval cycles, and extend S/4HANA business processes without cluttering your core ERP with custom ABAP code.

---

Related reads on this site:

• SAP BTP Explained — complete guide to SAP Business Technology Platform
• SAP Build Apps Low Code Guide — building web and mobile apps without code
• SAP BTP Event Mesh Guide — asynchronous event-driven integration