- >
- Workflow>
- SAP Workflow Integration: Connect SAP S/4HANA to Governed Approvals in Kissflow
SAP Workflow Integration: Connect SAP S/4HANA to Governed Approvals in Kissflow
TL;DR
- SAP workflow integration connects S/4HANA or ECC processes with cloud platforms and external systems, and Kissflow governs approvals around them.
- SAP Build Process Automation is the SAP BTP suite for workflow, robotic process automation (RPA), AI document processing, and rules. Kissflow sits beside it as the governed layer for approvals and exceptions.
- Kissflow fits approvals that start in SAP and finish across procurement, finance, HR, and IT teams.
- Kissflow’s SAP S/4HANA connector creates purchase requisitions and fetches vendor lists and material master data.
- Kissflow keeps an audit trail for every approval step it runs.
SAP workflow integration connects SAP processes in SAP S/4HANA or SAP ECC with cloud platforms, external systems, and automation tools. SAP Build Process Automation (SBPA) on SAP Business Technology Platform (BTP) is the cloud engine. It combines workflow management, RPA, AI document processing, and business rules. SAP Integration Suite links S/4HANA, SAP Ariba, SuccessFactors, and non-SAP systems. Inside the ERP, SAP Business Workflow and Flexible Workflow remain the in-system engines.
The question usually becomes urgent during an ECC to S/4HANA move. IT inventories custom workflows and finds approvals that leave SAP after the first step. A plant manager signs off by email. IT checks an asset register. Finance confirms the budget in a spreadsheet. Clean-core rules say that logic should not go back into the ERP. That logic still needs a home, an owner, and an audit trail. With AI, the slow part of an approval changes. An agent gathers the documents, checks them against policy, and flags what is missing. The approver then decides with the full picture.
The sections below cover the SAP-side engines, the patterns that join them, and the scenarios each one serves. A decision table shows which layer owns which job. A later section explains where Kissflow fits for steps that cross SAP and non-SAP teams.
What are the core components of SAP workflow integration?
These SAP components do most of the work.
- SAP Build Process Automation (SBPA): SAP’s low-code and no-code service on SAP BTP for workflows, bots, document extraction, and decisions. These run across S/4HANA, Ariba, SuccessFactors, and non-SAP applications.
- SAP Business Workflow and Flexible Workflow: These are the in-system engines. Business Workflow runs classic ABAP-defined processes in ECC and S/4HANA on-premise. Flexible Workflow is S/4HANA only. It adds configurable approval steps for documents such as purchase requisitions.
- SAP Fiori My Inbox and SAP Task Center: These are the approval surfaces where users act on the workflow tasks that SAP engines assign, on desktop or mobile.
- SAP Integration Suite: SAP’s integration platform as a service (iPaaS). It connects applications, data, and processes across SAP and third-party environments through prebuilt integrations, APIs, and event-driven messaging.
- OData and REST APIs: These are the interfaces S/4HANA exposes for reading and writing business objects. The SAP Business Accelerator Hub catalogs them, so integration teams find the right API before they build.
- SAP Cloud Connector: This component links SAP BTP services to on-premise SAP systems through configured destinations. That keeps ECC and privately hosted S/4HANA landscapes reachable from cloud workflows.
- Process Visibility: This BTP capability tracks workflow instances from start to finish, including classic ABAP workflows from S/4HANA. Process owners see where each case sits.
SAP Basis, integration, and workflow specialists own each piece. None of these belongs to the procurement manager who changes an approval threshold every budget cycle.
How does SAP Build Process Automation handle workflow automation for SAP integration?
SBPA covers workflow automation for SAP integration in one suite with four parts. Four kinds of triggers start a process. It merged the former SAP Workflow Service (also called SAP Workflow Management) and SAP intelligent robotic process automation (iRPA). The result is a single low-code offering. Redwood’s SBPA integration guide and SAP’s own features page describe it this way.
The four parts:
- Workflow management routes approvals and tasks across people and systems.
- Robotic process automation runs bots for screens that have no API, including attended ones on the SAP Desktop Agent.
- AI document processing extracts fields from invoices and other documents before a workflow acts on them.
- Business rules hold decision logic, such as an approval threshold, outside the process model.
Processes start from an API call, a form, an event, or a schedule. Approval steps land in SAP Fiori My Inbox or SAP Task Center. SAP also describes hybrid workflow automations that blend AI reasoning with deterministic logic across multi-step, cross-departmental processes.
SBPA keeps extension logic on BTP and off the ERP, which supports a clean-core S/4HANA. For cloud-side workflows that touch SAP, it is the main option. Native S/4HANA approvals stay in Flexible Workflow.
What are the key SAP integration patterns?
Three patterns connect SAP to other systems. A fourth, the classic ABAP workflow, stays inside the ERP.
- S/4HANA business events published through SAP Event Mesh start a BTP workflow the moment a document changes, with no polling.
- Integration flows in SAP Integration Suite map fields and apply rules between SAP and non-SAP systems. Many teams still call this capability Cloud Integration or CPI.
- Approval tasks reach Microsoft Teams and Outlook through SAP and partner integrations, where approvers already work.
- Classic ABAP workflows use SWDD, the Workflow Builder, to design processes and SBWP, the Business Workplace, as the user inbox.
What does a four-step SAP integration look like?
- Establish connectivity: Set up SAP Cloud Connector and BTP destinations so cloud services reach on-premise ECC or S/4HANA.
- Expose APIs or events: Select OData or REST APIs from the SAP Business Accelerator Hub, or publish business events through Event Mesh.
- Unify tasks in an inbox: Route approval steps to SAP Fiori My Inbox or SAP Task Center so users see one queue.
- Monitor and audit: Add workflows to Process Visibility, ABAP ones included, so owners track cycle time and stuck cases.
Steps one and two belong to IT. Steps three and four are where business owners begin to ask for changes.
Which scenarios use SAP workflow integration?
The textbook case is a purchase requisition routed by value, department, and budget. Invoice discrepancies and cross-system approvals follow close behind. Requisition routing and invoice discrepancies both sit inside Procure-to-Pay. That value stream spans requisition, PO approval, goods receipt, three-way match, invoice and AP, and payment.
- Purchase requisition routing: A requisition created in S/4HANA goes to the right approver by value, department, or remaining budget. Flexible Workflow or SBPA holds the rule.
- Invoice discrepancies: A finance workflow validates invoice data, with AI document processing pulling the fields. A reviewer then resolves the mismatch against the purchase order.
- Cross-system approvals: A capital request approved in SAP still needs facilities, IT security, and the controller to sign off. Those teams work in their own tools, which sit outside SAP.
The first two scenarios fit well inside SAP’s own layers. The third is where approvals drift back to email, because no single SAP team owns every participant.
Which layer owns which job, and what evidence should it leave?
Give each job to the layer whose owner changes it most often. Then ask what record survives an audit. The table answers both questions for the jobs that come up most in SAP workflow integration.
| Job to be done | Layer SAP provides | Layer the business owns | Governance evidence needed |
|---|---|---|---|
| Native S/4HANA approval, such as a purchase order release | Flexible Workflow or SAP Business Workflow, with tasks in My Inbox | None needed. Keep it in SAP. | Workflow log in S/4HANA, with ABAP workflows visible in Process Visibility on BTP |
| Document extraction before an approval | AI document processing in SBPA | Exception review by the finance team | Extracted values and reviewer decisions stored with the case |
| Cross-system approval owned by the business | SBPA on BTP, or an S/4HANA business event through Event Mesh | A governed approval layer such as Kissflow | An audit trail that names the person who acted |
| Message transformation between systems | Integration flows in SAP Integration Suite | None. The integration team owns it. | Flow configuration and run records held by the integration team |
| Scheduled job orchestration | SAP job scheduling, or a third-party scheduler such as RunMyJobs by Redwood | None. Operations or basis owns it. | Job run history in the scheduler |
Three questions sort the ownership of each job:
- Who owns the rule: a named business owner, or an SAP specialist working from a ticket?
- Who changes it without a release cycle, and who approves that change before it reaches production?
- What evidence exists afterward, and does it name the person who acted and the rule version in force?
An auditor checking a cross-system approval wants a single trail from the SAP document to the final sign-off. Two partial logs in two systems do not meet that need.
Where does a governed approval layer fit around SAP?
A governed approval layer sits beside SAP and handles approvals and exceptions that cross SAP and non-SAP teams. Kissflow works with large enterprises to redesign how work gets done, builds it on its own agentic platform, and stays with the change until the customer’s team owns it. Kissflow works with more than 1,200 customers. Kissflow starts from the business outcome. Agents prepare. People decide. With Kissflow, the ERP, SBPA, Integration Suite, and job schedulers all stay where they are. Kissflow handles the structured work that falls at the edges of what the core systems were built to do. It reaches S/4HANA only through the connector actions described below.
IT directors need every app that touches SAP to stay visible and audited. The process carries an audit trail and defines human authority.
Which approvals belong in Kissflow, and which stay in SAP?
- Capital requests that need sign-off from facilities, IT security, and the controller after approval in SAP.
- HR onboarding exceptions that reach IT and finance when a hire needs an SAP role, equipment, and a cost center.
- Vendor onboarding approvals that need finance and procurement sign-off before a vendor record is created in SAP.
- Field mapping between systems stays in SAP Integration Suite. Native S/4HANA releases stay in Flexible Workflow.
Kissflow also offers connectors for Microsoft Teams and Microsoft Outlook.
What controls does IT keep?
- Access: Role-based access and data controls.
- Records: An audit trail, with human authority defined in the process.
- Compliance: SOC 1 and SOC 2 Type II attestations, a SOC 3 report, and alignment with GDPR, HIPAA, and CCPA.
- Hosting: Kissflow is hosted primarily on Google Cloud Platform, with a 99 percent uptime commitment.
- Data residency: Production data and backups stay in the region the customer selects, such as the United States, European Union, India, or Australia.
How do AI-built changes stay auditable?
Teams describe the business in a prompt, a sketch, a photo, or a requirements document. Business teams do not write code. Governance comes from role-based access, data controls, an audit trail, and human authority defined in the process.
How do you connect SAP S/4HANA to Kissflow?
The Kissflow SAP S/4HANA connector runs SAP actions from inside a Kissflow integration. Each action starts from a trigger in a Kissflow process, such as an approval completing its workflow.
Which SAP S/4HANA actions does the connector run?
- Create a purchase requisition: Starts a new purchase requisition in your SAP S/4HANA account.
- Make an API request: Send a custom request to your SAP S/4HANA account.
- Fetch vendor list: Retrieves the complete list of vendors or suppliers available in your SAP S/4HANA account.
- Fetch material master data: Retrieves the general information held in the material master records of your SAP S/4HANA account.
Purchase requisition creation fits at the end of an approval cycle, once the review steps have completed.
How do you set up the connector?
- Create integration: In Kissflow, click Create > Integration, name your integration, and click Create.
- Configure trigger: Set up a trigger step, for example “When an item completes its workflow” from a Kissflow process.
- Add SAP action: Click Add next to your trigger, search for SAP S/4HANA, and select “Create a purchase requisition.”
- Authenticate: Click +Add an account and enter your SAP S/4HANA username and password.
- Map fields: Add values to the SAP S/4HANA form fields. Use Refresh fields to see every available option, and map data from your trigger or earlier steps.
- Test connection: Click Test to verify the setup. The connector pulls data from SAP, displays the JSON output, and shows any errors to fix before you continue.
- Activate: Switch the toggle on, and SAP actions run automatically whenever the trigger event occurs.
What if the SAP action you need is not prebuilt?
Use the Make an API request action, or describe the call in plain English. Kissflow’s AI fills in the HTTP method, endpoint URL, and request payload. You choose the authentication type (no auth, basic auth, API key, or OAuth2). Then you run a live test and add the action to your workflow. Kissflow also offers an open API with HTTP, REST, and SOAP support, scheduled triggers, and webhooks from any system.
Frequently asked questions
What is SAP integration?
SAP integration is how SAP systems such as S/4HANA or ECC connect to cloud platforms, Ariba, SuccessFactors, and non-SAP applications. Data and processes then move between them. SAP Integration Suite, SAP’s iPaaS, is one common route, through prebuilt integrations, APIs, and event-driven messaging. Teams also use OData and REST APIs and SAP Cloud Connector to reach on-premise systems.
What is the definition of workflow in SAP?
A workflow in SAP is a defined sequence of tasks that moves a business object between people and systems. Defined rules govern each step, as with a purchase requisition. SAP runs it in-system through Business Workflow or Flexible Workflow, or on SAP BTP through SAP Build Process Automation.
What does workflow integration mean?
Workflow integration means connecting the steps of a business process across separate systems and teams. A task started in one system continues in the next. In SAP terms, an approval that starts in S/4HANA can continue through cloud services and non-SAP tools. Each handoff needs connectivity, an owner, and an audit trail.
How can I automate SAP processes?
Start by deciding which layer should own each process. Native approvals stay in Flexible Workflow or SAP Business Workflow. Cross-system flows can run in SAP Build Process Automation on SAP BTP or in a governed approval layer. To connect the layers, set up SAP Cloud Connector and BTP destinations. Next, expose OData or REST APIs, or publish business events. Route tasks to one inbox, then add the workflows to Process Visibility to monitor them.