SAP Technical Operations · SAP Basis

Keeping your SAP running shouldn't be a worry

We take over the technical operation so your team can think about the business — not about whether the system will hold up at month-end close.

Availability target
99.9%

on production landscapes under Novis administration

7×24×365Guaranteed SLAPreventive monitoring
Transition with no operational risk. The Novis Basis team takes over administration in an orderly way, with full context of your landscape before the first day of operation.
SAP Basis — what it is and why it matters

If the business runs on SAP, Basis is what keeps it running

SAP Basis is the technical layer that holds up everything else: users, transactions, integrations, reports, payroll, financial close. It's invisible when it works well. You only notice it when it fails. Administering Basis correctly isn't just about resolving incidents — it's about making sure they don't happen. That requires constant monitoring, deep technical expertise and documented processes. Not a single person who “knows how the system is put together”.

01
Business processes
Finance, procurement, payroll, production, logistics
02
SAP modules
FI, CO, MM, HR, SD, PP, WM...
03
SAP Basis
Technical administration, monitoring, users, landscapes, transports, performance
Novis
04
Database / Infrastructure
HANA, Oracle, SQL Server / on-premise, cloud, hybrid
The real operational risk

When SAP goes down, it's not just an IT problem

A technical incident that isn't resolved within hours has a direct impact on operations, finance and on IT's relationship with the business.

Manufacturing · Operations · Immediate

Production halted

Production orders can't be released. The shop floor can't operate without SAP. Every hour down has a direct, measurable cost.

Finance · Compliance · Regulatory

Financial close at risk

An outage during the close period can delay regulatory reports and jeopardize commitments to headquarters or external auditors.

People · Reputation · Urgent

Payroll unprocessed

If the payroll batch doesn't run, there's no disbursement. It's the incident with the greatest impact on labor relations and the hardest to reverse in terms of image.

Do you recognize yourself in any of these situations?

The most common risk isn't technology — it's depending on a single person who knows it

Without adequate coverage
  • Only one person in your company knows how the SAP is put together
  • When that person is away, nobody can resolve a technical incident
  • On weekends and holidays there's no one monitoring
  • The landscape documentation is outdated or doesn't exist
  • The IT team operates reactively: it acts once something has already failed
With Novis
  • A full team with multiple levels of Basis expertise
  • 7×24×365 coverage — no dependence on a single person
  • Permanent active monitoring with alerts by criticality
  • A living landscape documentation, updated in real time
  • Preventive intervention before the business notices
Service models

Not every company needs the same thing

The service model is defined by the size of the landscape, the capacity of the internal team and the business's level of criticality.

Complement
Support for the internal team

Your IT team handles the day-to-day; Novis covers extended hours, advanced specialties and projects with higher technical complexity.

  • 7×24 coverage outside the internal team's hours
  • Basis specialists for complex escalations
  • Support during maintenance windows and upgrades
  • Backup for absences or staff turnover
For IT teams with their own Basis profile
Projects
Technical support for projects

Specialized Basis capacity to support higher-impact projects: S/4HANA migrations, upgrades, implementations or landscape expansions.

  • Basis resources dedicated to the project
  • Management of DEV/QA/PRD landscapes during the project
  • Mass transports, client copies and refreshes
  • Load testing and pre-production tuning
For projects with a high Basis technical component
Daily operation

What happens every day so the business never notices

Invisible Basis operation is the one that's working well. This is what the Novis team does in the background to keep it that way.

Administration and control
  • User and authorization management
  • Transport order administration
  • Scheduling and control of batch jobs
  • Management of DEV · QA · PRD landscapes
  • Administration of printing and spool systems
  • Application of OSS notes and SAP patches
  • License and technical-user management
Monitoring and performance
  • System health monitoring 7×24
  • Alerts by criticality level (P1 · P2 · P3)
  • Workload and resource-usage analysis
  • Optimization of batch jobs and processes
  • Database tuning (HANA / Oracle)
  • System log review and dump analysis
  • Availability and service KPI reports

Every landscape is different. In the initial diagnosis we document the real state of your environment and define the operation plan specific to your systems — not a generic model applied to every client.

Transition

Giving a third party access to your production SAP requires an orderly process

It's a valid concern — and that's why we have a defined transition methodology that minimizes operational risk from day one. The Novis team doesn't start operating until it knows your environment completely.

  1. 1
    Week 1 — Diagnosis

    We get to know your landscape

    Full technical assessment: architecture, versions, integrations, critical jobs, historical incidents and documentation gaps.

  2. 2
    Weeks 2–3 — Shadowing

    We operate in parallel

    The Novis team observes and takes part in operations alongside the current team. The environment documentation is completed and knowledge is transferred.

  3. 3
    Week 4 — Handover

    We take over operation

    Access activation, integration into the Novis monitoring scheme and a first status report. The business doesn't notice the change.

  4. Ongoing operation

    Periodic visibility guaranteed

    Monthly reports on availability, incidents and the status of improvements. Your team always knows what's happening with its systems.

SAP Basis and the road to S/4HANA

Migrating to S/4HANA starts with a healthy landscape

Many companies in the region are evaluating or starting their road to S/4HANA. Basis technical capacity is critical at every stage: from evaluation to go-live. A poorly administered landscape today generates far greater costs and delays in the migration.

  • Technical readiness analysis for S/4HANA
  • Landscape preparation for conversion or greenfield
  • Basis support during the migration project
  • Administration of the new S/4HANA landscape in production
Signs your landscape needs attention before migrating
  • Batch jobs running outside the maintenance window
  • Outdated or nonexistent technical landscape documentation
  • Transports with no formal validation process between environments
  • Users with broad profiles not reviewed recently
  • No active monitoring outside office hours
  • Reactive, not preventive, technical support
Frequently asked questions

What people ask us before deciding

How long does the transition take for Novis to take over administration of our SAP?
The standard transition takes 3 to 4 weeks. We start with a week of diagnosis and technical assessment, then there's a shadowing period where the Novis team operates in parallel with the current team. The formal handover happens once the documentation is complete and the team has real context of the environment — not before.
What happens if we have a critical incident outside business hours?
The service operates 7×24×365. P1 incidents (system down or a critical business process blocked) have a response time of under 1 hour. The on-call team has access to all systems and landscape documentation — there's no escalation process that takes longer than the business can wait.
How is hiring Novis different from having an internal Basis?
An internal Basis consultant covers limited hours, has a single level of expertise and represents a continuity risk if they leave. The Novis service includes a team with 7×24 coverage, multiple levels of specialization (junior, senior, HANA specialist, BW, Netweaver), its own monitoring infrastructure and a methodology proven across dozens of active landscapes. In most cases, the total cost is lower than an equivalent internal team.
Does the service cover SAP in the cloud or only on-premise?
The service covers on-premise, cloud (AWS, GCP, Azure) and hybrid landscapes. Novis also has practice in SAP RISE and S/4HANA Cloud Extended Edition environments. The infrastructure platform doesn't change the scope of the Basis service.
What's the first step if we want to evaluate the service?
The first step is a technical diagnosis of your landscape: we review the current state, identify monitoring gaps, recurring incidents and operational risks. The result is an executive report with findings and a proposed service model tailored to your situation — with no commitment to hire.
Where do we start?

Someone has to know your SAP before they can take care of it

The first step isn't signing a contract — it's for the Novis team to understand how your landscape is today: what runs well, what's at risk and what needs immediate attention. In 5 days we deliver that diagnosis — with real findings and a proposed service model tailored to your operation.

I want to stabilize my SAP →