Interactive tool
SAP Treasury Module & Edition Selector
Tick what you need treasury to do; it lists the SAP components that address each need, linked to a full guide. Then weigh the edition trade-offs for your situation. It points you at the right components and questions — it doesn't decide your architecture, and it defers exact module scope to SAP's editions and official docs.
0 components shortlisted
1 · What do you need treasury to do?
2 · Your SAP component shortlist
Tick the needs above and the SAP components to scope appear here — each with a link to what it actually does.
3 · Edition & deployment
- Greenfield — you can design straight to the S/4HANA target model, so weigh fit-to-standard against the customisation you genuinely need.
- The edition choice is a trade-off between standardisation and upgrade cadence (public cloud) versus customisation and control (private cloud / on-prem).
- Exact module availability and scope change by release and edition — confirm against SAP's official documentation and the edition-comparison guide before you commit.
How this works
Methodology
A scoping aid, not a configurator. Each need maps to the SAP component whose documented job is to address it, linked to a fact-checked guide; the edition section surfaces the trade-offs to weigh for your starting point and cloud appetite.
Assumptions
- The need→component mapping reflects each component's core function — read the linked guide for what it actually does in detail.
- A shortlist is a starting point for scoping with SAP or an implementation partner, not a licensing or configuration decision.
- The edition section describes general trade-offs (standardisation vs customisation), not per-module availability.
Limitations
- It does NOT tell you which module is available in which edition or release — that changes by release; confirm it in SAP's official documentation and the edition-comparison guide.
- It does not size licences, effort or cost, or account for your existing landscape and custom code.
- Module names and boundaries evolve across S/4HANA releases; treat the components as areas to investigate, not fixed product SKUs.