What does an SAP solution architect do?

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · certification facts checked against SAP Learning, October 2026

An SAP solution architect owns the design of one SAP solution end to end: which processes run in standard, what gets extended and how, where the data lives, and how the parts integrate into something a business can run. The role answers for the coherence of the design across every stream, not for depth in one area.

Where a functional consultant goes deep in one business area, the architect holds the whole picture — and can still explain, long after the workshops, why the solution looks the way it does.

What does an SAP solution architect decide?

The architect decides the questions that cross streams, each of which closes a door for everyone downstream. They arrive from delivery teams as practical questions — can we build this, where should this field live, which system sends the invoice — and the table maps each kind of decision to what it is based on and where it ends up written down.

The architect's decisions, their inputs and their artefacts
Decision the architect owns	Inputs	Typical artefact
Scope and fit to standard	Fit-to-standard workshop results, the SAP Best Practices scope items, business process models	Solution architecture document
Standard, configuration or extension	The gap list, the released APIs available, the clean core level each option would reach	Extension decision record, with a level A to D per object (clean core levels)
Integration topology	Interface inventory, message volumes, the APIs published on the SAP Business Accelerator Hub	Integration architecture and interface catalogue
Where each master data object is owned	Object list, existing systems of record, MDG scope	Data ownership matrix
Non-functional shape	Volumes, peak load, availability windows, archiving, the deployment option chosen	Non-functional requirements register and landscape diagram
Access model	Organisational structure, segregation-of-duties rules, audit requirements	Authorization concept, written with the security team
Sequence of delivery	Dependencies between processes, interfaces and data loads	Release and transition plan, agreed with the project manager

Running through all of them is a decision log naming the alternatives rejected and why, and the design authority — the review gate where specifications, configuration and code are read before they ship. On most programmes the reporting design belongs to the same set, because the figures the business will read decide which data the core has to carry.

How does the architect's work change across a programme?

It moves from shaping to guarding. Before the contract, the architect sizes the solution and names the assumptions the price rests on. In the early phases the work is the target design itself: deployment option, landscape, the extension and integration principles, the first cut of the decision log. During build the architect chairs the design authority, reads specifications for cross-stream consequences and settles disputes between streams before they become defects. In test and cutover the job is narrower and sharper: deciding which defects are design problems, and refusing quick fixes that would leave a level D object in the core. After go-live the architect hands over a design that matches the system, which is harder than it sounds.

Which SAP tools does a solution architect use?

Mostly documents and diagrams, plus two SAP products that have become part of the architect's kit. SAP LeanIX, acquired by SAP in 2023, is an enterprise architecture management tool: it holds the application inventory, the interfaces between applications and the target architecture, so a solution design can be placed in the landscape it will join. SAP Signavio covers process transformation — process modelling, process mining and the reference processes that fit-to-standard workshops start from. Integration choices are framed with SAP's Integration Solution Advisory Methodology, and extensions are designed against BTP and the released interfaces of the core. None of these replace the architect's judgement; they make it reviewable.

Is a solution architect the same as an enterprise architect?

No — the scope differs. An enterprise architect works above single programmes, on the application portfolio and roadmap of a whole company; a solution architect is accountable for one solution being designed and delivered. Between them sit narrower specialisms: the integration architect, and the technical architect, who usually grows out of Basis. The project manager is a different axis again: plan, budget and people, against the architect's design.

Where does SAP solution design go wrong?

Corridor decisions. Agreed in a hallway, never written down; the same debate reopens with no record of the trade-off.
Designs nobody can build. Coherent on a slide, unconfigurable in practice, or unsupportable once it reaches AMS.
Local optimization. Each stream optimizes its own area until a sales design quietly breaks revenue recognition — the cross-area seams are what an architect is there to watch (which SAP areas sit next to each other).
Happy-path interfaces. Designed for the message that arrives correctly, so the first failed one becomes a production incident.
Extensions with no level. Custom code approved without a clean core grade becomes the upgrade blocker nobody can trace back to a decision.
Drift. An architecture eroded by changes approved without it, until the live system and its documents describe different solutions.

What skills does an SAP solution architect need?

Enough depth in two or three areas to be believed, and enough breadth to see where they collide. Concretely: process knowledge across at least one end-to-end flow such as order to cash or procure to pay; a working grasp of the extension options and the clean core levels; integration patterns — synchronous APIs, events, batch files, IDocs — and when each fails; and the deployment options, because a design for SAP Cloud ERP (SAP S/4HANA Cloud Public Edition) leaves far less room for custom code than one for SAP Cloud ERP Private (SAP S/4HANA Cloud Private Edition). TOGAF, The Open Group's enterprise architecture framework, signals that an architect can also work at enterprise level — principles, capability maps, a governed roadmap — and SAP built its own Enterprise Architecture Framework as an extension of it, so the vocabulary carries over. The rest is communication: writing a decision so that someone joining next year can follow it, and saying no to a stream lead without losing the stream.

Is there an SAP solution architect certification?

Yes, and its title changes in October 2026. The exam called SAP Certified - Solution Architect - SAP BTP is withdrawn on 19 October 2026, and SAP names SAP Certified - Solution Architect - SAP Business AI Platform as the replacement, with valid certificates carried over. SAP Learning shows the new exam as a two-hour scenario-based assessment: you advise on a design in a timed, simulated conversation and no question bank is involved. A separate exam, SAP Certified - SAP Enterprise Architect, covers the enterprise level. Neither stands in for a delivered design in an interview, but at an SAP partner a current certificate can decide who is staffed (why partners count certifications).

How do you become an SAP solution architect?

Usually by doing the job before holding the title. Most solution architects come up through delivery, functional or technical, taking the cross-stream questions nobody else owns until answering them is the whole job; the other way in is the customer side, out of internal IT or enterprise architecture. Breadth across more than one SAP area, real integration awareness and the patience to document are the ingredients. Interviews test it through a design you owned: what you chose, what you rejected, and what it cost when an assumption proved wrong (what interviews test). The move on is wider programme scope, then enterprise architecture, further along the SAP career paths.