SAP Build Process Automation for Delivery Teams: Workflows, Decisions, S/4HANA Triggers and Testing

Keep this: job aid

BPA delivery checklist

• Placement: single-document approvals with an SAP scenario stay in S/4HANA flexible workflow; cross-system, people-centric processes go to BPA.
• Model: data types for context, explicit mappings, group recipients with backups, due dates, reject reasons.
• Decisions: decision tables with continuous, non-overlapping ranges and a defined no-match result; owner named.
• Triggers: event trigger for S/4HANA business events (thin payload, read details by action); API trigger for custom callers.
• Destinations: sap.processautomation.enabled = true, added in Control Tower; one name per subaccount (CMC_S4HANA).
• Environment variables: no hard-coded systems; values set at each deploy and recorded.
• Tests: boundary table per decision; every path incl. reject, overdue and API failure; role users only; S/4HANA checked for single writes.
• Evidence: tested released version number, instance IDs, task history, before/after data, in SAP Cloud ALM.
• Transport: release in DEV, CMC_DEV → CMC_TEST (auto import) → CMC_PROD (forward after sign-off, import in release window).
• Run: weekly review of erroneous, overdue and long-running instances; agent tools tested for odd inputs and repeat calls.