BTP & Integrationbeginner

BTP Build Process Automation Part 2: Build Your First Approval Workflow

Key takeaway

Build an approval process step by step: a trigger form for the request, an approval form with approve/reject outcomes, a condition on the decision, notification to the requester, release and deploy, and testing the full cycle in the inbox.

Explanation

📌 KEY POINTS
✅ A trigger form starts the process and fills the process context (e.g. amount, requester).
✅ An approval form assigns a task with outcomes (Approve/Reject).
✅ Conditions route based on outcome or context values.
✅ Release creates a version; deploy makes it runnable in an environment.
⚠️ Forgetting to map form fields to process context leaves later steps without data.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced BPA. Now your first workflow.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TRIGGER FORM

Fields; start process.

━━━━━━━━━━━━━━━━━━━━
▶ 2. APPROVAL FORM

Recipients; outcomes.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CONDITION

Approved vs rejected paths.

━━━━━━━━━━━━━━━━━━━━
▶ 4. NOTIFICATION

Inform requester.

━━━━━━━━━━━━━━━━━━━━
▶ 5. RELEASE & DEPLOY

Version, environment, test.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create trigger and approval forms.
Add condition and notifications.
Release, deploy, test both outcomes.

✅ CHECKPOINT: both approve and reject paths complete correctly.

Code example

ABAP Code

===== PROCESS =====Trigger form "Purchase Request" (item, amount, justification)→ Approval form (recipient: manager from decision/group) outcomes Approve | Reject→ Condition: outcome == Approve → notify requester "approved" (+ action to create PR)                          else → notify requester "rejected" with comment→ End ===== TEST =====Submit form → approver opens My Inbox → approve → check instance completed in Monitor

Real project scenario

A team released a workflow that worked for approvals, but rejections ended in an error because a mapping was missing on the reject path. Testing both outcomes before deploy became part of the checklist.

Common mistakes

Unmapped context.
Only testing approve.
Hard-coded recipients.
No notifications.
Skipping versions.

Best practices

Map fields carefully.
Test all outcomes.
Dynamic recipients.
Notify requesters.
Version releases.

Interview angle

Questions: "How do you build an approval in BPA?", "Release vs deploy?", "How do you test a process?"
Strong answer: forms, outcomes, conditions, notifications, lifecycle.

Practice this lesson

Quick check

1. What is the difference between releasing and deploying a process?

2. Why must both approve and reject paths be tested?

3. What starts a simple request-approval process in BPA?

Interview questions

1. What are the most important concepts in SAP Build Process Automation, and how do they connect to SAP Build Process Automation Fundamentals: Processes, Forms, Decisions and Automations in a real SAP landscape?

Answer it in your own words first, then compare.

2. A project team is working on SAP Build Process Automation. Using the Build Process Automation Architecture: APIs, Task Center, Work Zone and Governance scenario, how would you approach the requirement from design through validation?