S/4HANA with RISE + AMS – Managing SAP RISE with AMS, What Changes and What Stays the Same?
SAP S/4HANA has redefined enterprise resource planning for businesses globally, empowering intelligent and integrated processes that drive real-time insights and operational excellence. With the rise of cloud adoption, SAP introduced RISE with SAP, a comprehensive business transformation as a service bundle designed to accelerate an organization’s journey to the Intelligent Enterprise.
However, moving to RISE with SAP is not just a technical migration it’s a transformation in how companies operate, consume support, and manage their SAP landscapes. For many enterprises, Serviços de Gestão de Aplicações (AMS) become the backbone of ongoing support managing configurations, upgrades, optimizations, and user support.
This article explores from an SAP S/4HANA expert’s lens what changes and what stays the same when managing SAP RISE with AMS.
1. What Is RISE with SAP? A Quick Recap
RISE with SAP is:
- A business transformation offering rather than solely a technical migration.
- A package that includes SAP S/4HANA Cloud (public or private edition), Business Technology Platform (BTP), and technical services such as migration tools, industry content, and analytics.
- A subscription-based model with cloud infrastructure and a single price/per invoice model.
Unlike traditional on-premise licensing, RISE shifts the economic and operational model to a cloud-centric, service-oriented approach.
2. What Is Application Management Services (AMS)?
AMS refers to a set of services that ensure your SAP solution runs smoothly. Key elements of AMS include:
- Incident resolution & user support
- Monitoring and performance optimization
- Change requests and minor enhancements
- Updates & quality assurance activities
- Root-cause analysis and remote troubleshooting
AMS ensures your SAP environment remains reliable, resilient, and aligned to business needs.
3. What Changes When Managing SAP RISE with AMS
a) Support Landscape Shifts from On-Premise to Cloud-Centric
In traditional setups, AMS teams managed:
- OS and database maintenance
- Hardware provisioning and patching
- Network infrastructure and disaster recovery tasks
With RISE, many of these responsibilities shift to SAP or hyperscaler partners (Azure, AWS, GCP). AMS teams now operate with:
- Cloud service management
- Integration oversight
- Performance and cost monitoring
A shared responsibility model where SAP owns platform-level stability.
This requires AMS providers to be fluent in cloud operations and SLAs at the infrastructure layer.
b) New Interfaces, New Integration Patterns
RISE with SAP encourages digital transformation, leading to:
- Greater usage of APIs
- Event-driven architectures on SAP BTP
- Microservices and modern extensions
AMS teams must now support broader integration requirements — both internally (with existing systems) and externally (partners, third-party applications).
c) Cloud-Driven Release & Update Cadence
Traditional ECC or on-premise S/4HANA upgrades were periodic and project-style engagements.
In RISE:
- Patches and releases can be more frequent
- Features delivered via continuous innovation cycles
AMS teams must adopt agile support processes, plan for quicker deployment windows, and ensure regression testing frameworks are cloud-ready.
d) Service-Level Priorities Evolve
In classic AMS, uptime was measured mostly at the application layer. Post-RISE:
Responsibility | Traditional On-Premise | RISE with SAP |
Infrastructure updates | AMS | SAP + Hyperscaler |
SAP stack maintenance | AMS | AMS & SAP Cloud Operations |
Database support | AMS | SAP Cloud + Managed AMS oversight |
Integration gateways | AMS | AMS |
Performance optimization | AMS | Shared with SAP |
The AMS model evolves from full ownership to orchestration, oversight, and orchestration with SAP.
e) Enhanced Use of Automation and Platform Monitoring Tools
RISE offers tools such as:
- SAP Focused Run
- SAP Solution Manager in the Cloud
- SAP Cloud ALM
AMS teams must adopt these systems as a central toolset for system monitoring, incident management, and proactive performance tracking.
4. What Stays the Same in AMS, Regardless of RISE
a) Core Support Objectives Don’t Change
Regardless of deployment model, AMS teams continue to:
Fix incidents fast
Maintain system usability
Support business processes
Enhance configurations
Enable users
The purpose remains — only the execution changes.
b) Functional Expertise Remains Critical
Regardless of RISE, AMS specialists still need deep knowledge of:
FI/CO, SD, MM, PP, WM & other functional modules
Business process alignment and optimization
Security and role management
Regulatory compliance
Technical infrastructure responsibilities may shift, but functional competency is non-negotiable.
c) Change Management Still Plays a Central Role
Business users still require:
Training
Documentation
Change advisory support
Testing during new releases
AMS teams still coordinate closely with business units to ensure process excellence.
d) Governance Models Still Matter
Transition to RISE does not eliminate the need for:
Change control boards
Release windows
KPIs and SLA monitoring
Issue prioritization frameworks
The governance discipline of AMS remains core.
5. Key Best Practices for Managing RISE with AMS
1. Redefine the AMS Contract Model
Move from traditional hourly/break-fix contracts to:
- Outcome-based SLAs
- Business process performance metrics
- Cloud cost monitoring KPIs
2. Build Cloud-Native Monitoring Capabilities
AMS teams must:
- Use cloud management dashboards
- Leverage BTP capabilities
- Enable proactive support rather than reactive only
3. Align with SAP’s Innovation Calendar
Instead of one big upgrade every few years, AMS teams should:
- Plan quarterly release management
- Validate changes with regression tests
- Engage business users early
4. Invest in Integration Expertise
With RISE, many companies integrate non-SAP apps. AMS professionals must:
- Understand API management
- Ensure secure data exchanges
- Monitor interface performance
Conclusion: A Unified Approach to AMS in the Age of RISE
Managing SAP S/4HANA in a RISE setup is not a departure from AMS best practices it’s a maturation of those practices.
The essence of support ensuring business continuity, optimizing performance, and enabling users remains at the heart of AMS. What changes are the tools, the shared responsibilities, the pace of innovations, and the cloud-centric mindset.
For organizations partnering with an AMS provider or managing AMS in-house the transition to RISE is an opportunity to overhaul support excellence making SAP operations more adaptive, resilient, and aligned to business outcomes.
English 
French 
Spanish 
Portuguese