What does an SAP Basis consultant do?

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

SAP Basis is the technical administration of SAP systems, and an SAP Basis consultant runs the foundation an SAP landscape stands on: the systems themselves, the database beneath them, the route every change travels to production, and the access that lets anyone log in at all. It is the one SAP job measured by absence of events.

As of October 2026, the calendar is SAP's own: SAP NetWeaver 7.5, the stack under ECC and documented on the Help Portal, shares Business Suite 7's mainstream-maintenance end of 31 December 2027. SAP Solution Manager 7.2 leaves mainstream maintenance on the same day; sites paying for Business Suite 7 extended maintenance keep a reduced SolMan scope until 2030, and SAP recommends SAP Cloud ALM as the operations tool to move to. Conversions, upgrades and tool migrations are therefore the Basis work of the next two years.

What is SAP Basis?

SAP Basis is the platform layer every SAP application runs on — the application server, its work processes, the transport system, user administration, the connections to other systems and the database underneath — and the discipline of installing, running and upgrading it. "Basis" was SAP's own word for the kernel and administration layer of R/3, which became SAP NetWeaver under ECC and is the ABAP Platform under S/4HANA. The people who run it are called Basis administrators, SAP administrators or simply the Basis team; job adverts use all three for the same seat.

What Basis is not is equally useful to know. It is not functional configuration: a Basis person does not decide how a purchase order is approved. It is not development: they do not write the report, though they are the first to find out when it runs slowly. And on SAP HANA the classic database administrator's job has largely merged into the same person.

What does a Basis consultant do day to day?

A Basis consultant keeps every system in the landscape available, patched, connected and fast enough, and moves each change safely along the route to production. The day splits between planned work and whatever the monitoring raised overnight.

• Installations, patches and upgrades — new systems, support packages, kernel updates, release upgrades, and the database underneath, today usually SAP HANA. Planned months ahead, executed in a weekend window.
• The transport landscape — every configuration change and every line of custom code travels a defined route to production. Basis owns that route: its sequence, its conflicts and its emergency exceptions.
• Performance and monitoring — when the month-end close runs slow, the call reaches Basis first, whoever caused it. The craft is working backwards from a symptom through jobs, memory, locks and the database.
• Availability and recovery — backups, high availability, restore drills, and the confidence that a system can be brought back.
• Access and connections — accounts, single sign-on, the links between systems, printing. Invisible when right, urgent when wrong.

Functional and technical consultants shape what the system does; Basis decides whether it does anything at all.

What is the three-tier architecture Basis looks after?

Most SAP applications run as three cooperating tiers, usually on separate hosts, and S/4HANA kept that design from the older Business Suite. Basis owns the lower two and supports the first.

On a small system the application and the database can share a host. Larger systems separate them and grow by adding application server instances, which is why the next section goes inside one of those instances.

Inside one system: work processes, services, memory

An SAP system is not a single program. Requests arrive at a dispatcher and are handed to work processes of fixed types — dialog for interactive steps, background for scheduled jobs, update for the asynchronous second half of a posting, enqueue for the lock table, spool for output — and a surprising share of incidents are one of those types being exhausted while the others sit idle.

Central services sit beside the application instances: the message server that distributes logons across them, and the enqueue server that owns the lock table for the whole system. Those two are the single point of failure the high-availability design exists for, which is why a cluster and a replicated enqueue instance are the standard shape of a production landscape rather than an optional extra. Memory is the other permanent subject: with the database in memory, a report that reads a hundred million rows into a session is everybody's problem at once.

What is an SAP system landscape?

A system landscape is the set of connected SAP systems a change travels through on its way to the people doing business, classically three tiers, so that every change proves itself twice before it reaches them. Basis people think in landscapes, not single systems.

Development

Where configuration and code are created, and where every change is captured in a transport request.

Quality assurance

Where the change meets realistic data and the rest of the landscape, and where a bad transport is supposed to be caught.

Production

Where the business works. Nothing is built here — everything arrives through the route, in the order it was released.

Around those sit sandbox systems, training copies, and the refreshes that pull production data back down so testing stays honest. During a conversion or a rollout the landscape temporarily doubles.

Sequence is the discipline that carries all of it. One system in the landscape is the transport domain controller; routes are defined from there, and imports are queued in release order because a later request often contains the correction to an earlier one. Import out of order and an object silently reverts to an older version — the classic Monday mystery, and the reason emergency transports are the most argued-about thing in the job.

Which transactions does Basis work run on?

Basis work runs on a small set of transactions that exist in both SAP ERP (ECC) and S/4HANA; Basis is the part of SAP where the classic transaction codes have not been replaced by Fiori apps.

Beyond the system itself, the Maintenance Planner produces the stack file the update tool consumes, and the operations tooling — Solution Manager on older landscapes, SAP Cloud ALM on newer ones — raises alerts and delivers the EarlyWatch Alert report nobody reads until an audit. The transport domain itself is configured in STMS, as SAP's own documentation on the transport domain describes.

How do upgrades and conversions run?

On two tools, rehearsed three times. The Software Provisioning Manager (SWPM) installs and copies systems; the Software Update Manager (SUM) performs release upgrades, support-package stacks and database migrations. SUM's Database Migration Option (DMO) can move a system to a new database and upgrade it in a single downtime, which is why so many conversions were done that way rather than as two projects. DMO moves the database; the business data is the data migration stream's job, and the two seats sit beside each other on a conversion.

What makes an upgrade long is rarely the tool. It is the adjustment of whatever a previous generation modified: SAP objects changed in place have to be reconciled release by release, and custom code checked against what the new release removed. A conversion to S/4HANA adds the simplification checks — data model changes the business must decide on before the technical work can start. Downtime-optimised variants trade preparation effort for shorter outages; whether that is worth it is a business conversation, not a Basis one (what S/4HANA changed).

The whole exercise is rehearsed: a first run on a sandbox produces the real duration, a second on a production copy produces the runbook, and only the third is the one people are told about.

What are SAP Basis services?

SAP Basis services are the technical administration of SAP systems delivered as a service rather than by the company's own team. Support services take tickets against a service level, managed services run the infrastructure and technical operations outright, and project Basis, which providers sell as SAP Basis consulting services, is hired for a single upgrade or migration. The work is the same in every shape; what changes is who carries it and how it is measured.

The support shape is where most careers start. A Basis support service runs on the incident, problem and change cycle: an incident is restored, a problem is what recurs and is traced to a cause, and a change is the corrective work scheduled through a maintenance window. L2 support handles the known — a job restart, a lock cleared — and L3 handles what needs the system understood, which is where the AMS career turns into a Basis one.

The managed shape moved most in the last few years. Under RISE with SAP, private edition, SAP runs the technical operations of the S/4HANA system itself — infrastructure, operating system, database, backups and patching — and the customer's remaining responsibilities are written into a roles-and-responsibilities matrix. That document settles who may restart an instance at two in the morning and who approves a maintenance window; a seat has grown out of holding the provider to it (what the bundles contain).

Is SAP Basis still needed in the cloud?

Yes — the work moves rather than disappears, and the calendar keeps it busy: as of October 2026, the maintenance strategy SAP publishes ends mainstream maintenance for SAP ERP 6.0 (ECC) on 31 December 2027, so every remaining ECC landscape is an upgrade, conversion or decommissioning project with a Basis team inside it. Once a landscape is managed, landscape design, transport governance and performance ownership stay on the customer's side. The shorter release cadence of cloud systems makes regression testing and transport hygiene more important, not less, as the re-platforming wave keeps proving. What changed is the mix: less server-room work, more automation, more provider management, and more platform work around SAP BTP, the platform beside the core.

What is SAP Cloud ALM, and does it replace Solution Manager?

SAP Cloud ALM is SAP's cloud tool for application lifecycle management. It runs an implementation (tasks, requirements, tests, deployments) and then monitors the landscape in operation. SAP positions it as the tool to move to from SAP Solution Manager. As of October 2026, mainstream maintenance for SAP Solution Manager 7.2 ends on 31 December 2027. Customers who buy extended maintenance for Business Suite 7 keep Solution Manager until the end of 2030 at no extra cost, but only for a named scope: requirements, project and process management, the test suite, change control management, IT service management and landscape management.

SAP recommends that all customers move to SAP Cloud ALM before the end of 2027. It needs no separate licence: usage rights come with SAP cloud subscriptions and with SAP Enterprise Support. SAP Focused Run follows its own calendar and stays in mainstream maintenance beyond 2027. For a Basis team the move is a project of its own. Change control and monitoring have to be set up again in the new tool before the old system is retired.

What Basis is not asked to do

• Design the role concept. Basis operates user administration and often builds roles in smaller shops, but authorization design is its own discipline with its own arguments (what that role involves), and scoring access for risk belongs to what SAP GRC covers.
• Own the network, storage or hypervisor. Those are separate teams, and half of a Basis person's escalations are conversations with them.
• Decide business downtime. Basis states what an outage costs in hours; the business decides whether to take it.
• Fix the code that caused the problem. Finding that a custom report is responsible is Basis work; changing it is not.

Which SAP certifications fit a Basis consultant?

As of October 2026, SAP Learning lists three certifications that sit closest to Basis work. The certification for S/4HANA conversion and SAP system upgrade verifies the skills to perform a technical conversion and an upgrade, the project side of the job (its exact title is in the certifications guide). SAP Certified - Security Administrator covers the core knowledge of SAP system security and authorizations. SAP Certified - SAP BTP Administrator assesses the ability to manage and administer SAP BTP environments, the platform work that Basis teams increasingly inherit. None of the three replaces having run a landscape. An employer asks first which systems you operated, which upgrades you carried and what you did when one of them failed.

How do you get into Basis, and where does it lead?

Most people get into Basis from system, database or infrastructure administration, or from a support team's technical queue: the instincts transfer and only the vocabulary is new (switching in from another background). Because the questions in an SAP Basis interview probe the security boundary early, the SAP security interview questions are worth reading too. Many landscapes are run by one or two Basis people, so breadth arrives fast and on-call is normal. The career then leads to security and authorizations, migration and database specialism, platform and integration work, or a technical lead's seat owning landscape design and the release calendar.