This is an illustrative solution blueprint. Baseline metrics, API availability, approval configuration and ROI must be validated for each customer landscape.
Executive summary
How an enterprise can modernise a heavily customised purchase requisition (PR) approval experience while keeping SAP S/4HANA as the system of record. The design applies fit-to-standard and released APIs, and uses an SAP BTP side-by-side extension only for differentiated capabilities that standard SAP functionality cannot meet.
Business context and problem
An enterprise migrating from SAP ECC to SAP S/4HANA has a custom approval cockpit built with Z tables, bespoke ABAP screens, direct database reads and point-to-point integrations. Approval policies change frequently, and regression testing after upgrades is expensive.
Requesters should submit and track PRs; approvers should review exceptions, approve or reject according to delegated policy, and receive timely notifications. Standard S/4HANA procurement and Flexible Workflow capabilities must be assessed first.
Clean core decision principles
Clean core does not mean “no extensions”. It means choosing the least invasive supported option, using stable released interfaces and governing changes across processes, data, integration, extensibility and operations.
- Adopt the standard SAP process.
- Configure, or use key-user extensibility.
- Use released on-stack developer extensibility where supported.
- Build a side-by-side extension on SAP BTP for genuine differentiation. Avoid direct changes to SAP standard objects and unreleased internal interfaces.
Before and target state
| Dimension | Legacy approach | Clean core target |
|---|---|---|
| Process | Custom approval logic embedded in ERP | Standard PR and Flexible Workflow first; external orchestration only for documented gaps |
| Extensibility | Z transactions and direct enhancements | Released extension points or a CAP service on SAP BTP |
| Integration | Direct table access and custom RFCs | Released S/4HANA APIs and supported events |
| Data | Duplicate PR master and status | S/4HANA owns the PR; BTP stores only extension metadata |
| Operations | Manual checks and tightly coupled releases | Central logs, monitoring, traceability and contract tests |
Solution architecture
- Experience: an SAP Fiori application exposed through SAP Build Work Zone or the launchpad.
- Application: CAP (Node.js) on SAP BTP manages the exception-review UI, extension metadata and policy-specific actions. Approval execution stays with standard S/4HANA Flexible Workflow and its supported task interfaces.
- Integration: SAP Integration Suite where mediation, mapping, governance or hybrid connectivity is needed; a direct released API call where no mediation is required.
- Identity and security: SAP Cloud Identity Services, least-privilege role collections, destination-based connectivity and principal propagation where feasible.
- Persistence: SAP HANA Cloud stores audit references, correlation IDs and application configuration, not a copy of procurement transactions.
End-to-end flow
- The requester creates a PR using standard S/4HANA functionality or a supported released API.
- S/4HANA validates and saves the PR; standard workflow determines the approval task.
- The CAP application reads PR details through released APIs and shows additional exception context.
- The authorised approver acts through a supported approval or task API, or the standard workflow UI; approval status is never updated directly in tables.
- Status changes surface through supported events, or controlled polling where no suitable event exists.
- Monitoring correlates the request, API call, workflow instance and business document ID.
Delivery plan
- Discover: inventory custom code, integrations and approval variants, using SAP Readiness Check and custom-code analysis tools.
- Design: fit-to-standard workshops; identify released APIs and workflow extension options for the exact S/4HANA edition and release; document architecture decisions and data ownership.
- Build: CAP service, Fiori experience, authorisation model, automated tests, and integration flows only where justified.
- Validate: segregation of duties, API contracts, exception handling, retries, idempotency, audit trail, performance and upgrade regression.
- Deploy: pilot one purchasing organisation, monitor, then expand in waves with rollback and support runbooks.
Success measures and risks
| Measure or risk | How to validate |
|---|---|
| Upgrade regression effort | Compare test person-days before and after modernisation |
| Custom code footprint | Count retired or remediated custom objects; track released-interface compliance |
| Approval cycle time | Compare median PR approval lead time over equivalent periods |
| Integration reliability | Measure success rate, retry volume and error recovery time |
| Security and controls | Prove role segregation, audit completeness and authorisation checks |
| Risk: API gaps | Validate released APIs and workflow task capabilities before committing to the CAP design |
| Risk: duplicated business logic | Keep approval determination in standard workflow wherever feasible |
Expected outcomes
A smaller upgrade-sensitive customisation footprint, clearer ownership of business data, better monitoring and faster change cycles. No numerical benefit is claimed without a customer baseline and post-implementation evidence.
Conclusion
A successful clean core transformation starts with process standardisation, not technology selection. SAP BTP is a strategic extension platform, not a replacement for standard S/4HANA capabilities. Read more in our blog on SAP clean core architecture.



