India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
SAP Cloud FinOps: HANA Commitments, Non-Prod Schedules, Storage Tiers
SAP Cloud FinOps is the practice of managing the cloud cost of SAP landscapes per system and environment, using levers specific to SAP: HANA instance commitments, non-production start and stop schedules, storage tiers per HANA volume, memory rightsizing, data tiering and OS licensing. NTSPL builds SID-level cost visibility and applies these levers without breaking SAP operations.
Delivered on
In scope
Why Generic Cloud Savings Levers Do Not Fit HANA
SAP is often the single largest line on an Indian enterprise's cloud bill, and the generic FinOps playbook does not fit it. HANA cannot be autoscaled or moved to spot capacity. Non-production systems cannot be stopped at random because background jobs, RFC destinations and transports expect them up. Certified memory-optimized shapes come in large steps, so an extra 200 GB of growth can force a much bigger instance. And many teams pay pay-as-you-go rates for production HANA a year after go-live because nobody owned the commitment decision.
NTSPL runs SAP FinOps per SID. Every resource is tagged with system ID, tier and cost centre so finance sees what PRD, QAS and DEV of each system cost. We then apply SAP-safe levers in order: commitments on steady HANA and app servers, start and stop schedules agreed with Basis and project teams, storage tier changes validated against HANA KPIs, and memory relief through NSE and archiving before any instance upsize.
Cost Signals That Point to SAP-Specific FinOps Work
Signals you need SAP Cloud FinOps
- SAP runs on pay-as-you-go pricing for more than three months after go-live.
- Non-production SAP systems run 24x7 while being used fewer than 60 hours a week.
- Finance cannot see the monthly cloud cost of each SAP system and environment.
- Basis has requested a larger certified HANA instance because used memory is above 80 percent.
- The board wants a comparison of current SAP IaaS run cost with a RISE with SAP subscription offer.
When to choose something else
- The cloud bill is mostly non-SAP workloads; an estate-wide cloud cost assessment gives better returns first.
- SAP is not yet on cloud and the question is a five-year TCO against on-prem refresh; that is a cloud TCO and business case.
- SAP runs under RISE with SAP, where infrastructure is in the subscription; cost work then focuses on contract sizing at renewal.
SAP Cost Levers NTSPL Manages
SID-level cost allocation
Tags for SID, tier, environment and cost centre on every SAP resource, with shared costs such as networks and backups split by agreed rules.
Commitments for steady SAP capacity
Reservations, savings plans or committed use discounts for production HANA, DR HANA and steady app servers, timed with planned resizes.
Non-production schedules
Start and stop schedules for sandbox, development, quality and training systems, coordinated with Basis for job and RFC dependencies.
Storage and backup tiering
HANA volume tiers validated against throughput needs, snapshot and backup retention tuning, and archive storage classes.
Memory and licensing levers
HANA memory rightsizing using NSE and archiving, OS subscription model choice, and a RISE versus IaaS cost view at renewal points.
SID-Level Cost Model from Tags to Monthly SAP Cost Review
SID-Level SAP Cost Model from Tags to Monthly Review
Billing data is enriched with SAP tags and HANA usage metrics, turned into cost per SID and environment, and checked against commitment coverage and schedules. Recommendations go to a monthly SAP cost review with Basis and finance.
Select any component
SID-Level SAP Cost Model from Tags to Monthly Review: click any of its 9 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
Commitment, Scheduling and Licensing Options per Cloud for SAP
On AWS, production HANA usually suits Reserved Instances or EC2 Instance Savings Plans, non-production uses Instance Scheduler with Basis-approved calendars, and gp2 volumes are moved to gp3 where HANA KPIs allow.
On Azure, M-series reservations cover production HANA, Start/Stop VMs v2 schedules non-production, and Azure Hybrid Benefit can apply existing RHEL or SLES subscriptions to SAP VMs.
On Google Cloud, resource-based committed use discounts cover M-series HANA, instance schedules stop non-production, and Hyperdisk throughput can be tuned down for quieter tiers.
SAP Cost Decisions with Break-Even Thresholds
Commitment term and timing
Commit production HANA for three years only after two clean month-end closes and a growth review, since a forced upsize mid-term may strand the commitment. Use one-year terms or flexible savings plans for app servers and DR. Target 80 to 90 percent commitment coverage for steady SAP capacity, leaving project and test systems on demand.
Non-production schedules
Typical schedules run development and quality 12 hours on working days and stop at weekends, cutting runtime by 60 to 65 percent. Keep sandbox off unless requested. Before stopping, Basis must confirm background jobs, RFC destinations and interface partners for that SID. Provide an override path for test cycles, approved within an hour.
Upsize or relieve memory
When HANA used memory passes 80 percent, compare the cost of the next certified size over the remaining term with the effort of NSE and archiving. In most cases, relieving 15 to 30 percent of memory through tiering is cheaper. Upsize only when growth is structural, such as a new plant or company code.
RISE with SAP or IaaS at renewal
Compare like for like: IaaS cost per SID including DR, backup, monitoring, Basis operations and OS licences, against the RISE subscription for equivalent FUE and tier. Include the cost of tasks that remain yours under RISE. The decision usually turns on Basis staffing and how much control you need over patch timing.
SAP FinOps Rollout over Eight Weeks
Tagging and cost baseline
Apply SID, tier and cost centre tags and publish the first cost per SID and environment.
Quick wins
Stop idle systems, remove orphaned disks and snapshots, and move storage where HANA KPIs allow.
Non-production schedules
Agree calendars with Basis and project leads, then automate start and stop with override handling.
Commitment plan
Model coverage, term and timing against growth and resize plans, then purchase with finance approval.
Monthly review cadence
Start the monthly SAP cost review with realized savings, exceptions and upcoming decisions.
What you receive
SAP Unit Cost and Coverage Measures
| KPI | Typical target |
|---|---|
| SAP resources with complete SID and cost centre tags | At least 98 percent |
| Commitment coverage of steady SAP capacity | 80 to 90 percent |
| Non-production runtime reduction | 55 to 65 percent of always-on hours |
| Realized SAP infrastructure saving in first 6 months | Typically 25 to 40 percent |
Savings Moves That Can Break SAP Operations
| Risk | How NTSPL prevents it |
|---|---|
| A stopped non-production system breaks a test cycle or interface | Schedules are agreed per SID with Basis and project leads, dependencies are checked, and override requests are handled within an hour. |
| A three-year commitment is stranded by an upsize or move | Commitments are timed after growth reviews, and flexible instruments are used where resize is likely within 18 months. |
| Storage downgrade slows HANA commits | Every HANA storage change is preceded by HCMT on the new configuration and checked during the next month-end. |
Reserved instances or savings plans for SAP HANA on cloud?
For production HANA that will stay on one instance family and size for three years, reservations or resource-based commitments usually give the deepest discount and apply cleanly to memory-optimized shapes. Flexible savings plans or spend-based commitments cost a little more but survive family or size changes, which suits application servers and systems likely to be resized after an S/4HANA conversion or acquisition. NTSPL typically reserves production and DR HANA once growth is understood, and covers application servers with flexible plans, keeping project systems on demand.
Key facts: SAP Cloud FinOps
SAP Cloud FinOps in Practice
2 SAP Cloud FinOps scenarios, from Spirits distiller and Sugar, plus related platform case studies.
Spirits distiller cuts SAP AWS bill 34 percent without touching production sizing
Sugar mill group matches SAP capacity to the crushing season on Azure
Auto-ancillary maker converts ECC to S/4HANA on AWS inside a 48-hour downtime window
API manufacturer moves a GxP-validated SAP landscape to Azure without re-validation delays
SAP Cloud FinOps: Frequently Asked Questions
How much can SAP FinOps save?
For landscapes that have run on cloud for six months or more without SAP-specific cost work, 25 to 40 percent of SAP infrastructure cost is a common outcome, mostly from commitments and non-production schedules. Savings are reported as realized in the bill, not projected.
What does an SAP FinOps engagement cost?
The initial rollout usually takes 20 to 30 consultant-days over eight weeks, followed by a monthly review as a managed service. Some clients prefer a fee linked partly to realized savings; NTSPL can structure either.
Can we stop SAP non-production every night?
Usually yes for development and quality, with agreed calendars. Some systems must stay up for overnight jobs, interface tests or offshore teams. Basis confirms each SID's dependencies before scheduling.
How are SAP costs shown to Indian finance teams?
We present cost per SID and environment in INR, mapped to cost centres and profit centres used in SAP controlling, so the CFO can see SAP IT cost by business unit. GST on cloud invoices is handled in the same report.
Does Azure Hybrid Benefit apply to SAP on Linux?
Azure Hybrid Benefit for Linux lets eligible RHEL and SLES subscriptions be applied to Azure VMs, which can reduce cost when you already hold enterprise subscriptions. NTSPL checks eligibility and support terms before switching.
Should we move to RISE with SAP to cut cost?
Not automatically. RISE bundles infrastructure, Basis operations and licences into one subscription, so compare it with your full IaaS run cost including operations staff. NTSPL builds a like-for-like comparison at renewal points.