Customer key user responsibilities after go-live:
- Processing incidents from end users, attempting to resolve the issue and if not, interfacing with SAP Support
Maintaining users with access authorizations, user substitutions and monitoring business tasks
Maintaining and monitoring background jobs and communication with external systems
- Adapting the solution as needed, such as changing form templates, scope, and configuration settings
- Testing upgrades
- Training new users and provide enhancement training for existing users
Upgrades
SAP Cloud for Customer Upgrades:
- Customers are notified by email from SAP 4-6 weeks before the production tenant upgrade.
- Communications are sent to the customer’s IT contact, as maintained in the Service Control Center → Contact Details view.
- Release notes are published as What’s New in the Help Center documentation.
- The test tenant is upgraded two weeks before production upgrade.
- Upgrades should be positioned as a non-event, meaning that testing is not required.
- For the two weeks following the test tenant upgrade, remember the following:
- Change projects cannot be merged from test to production.
- Go-lives should be avoided.
- Avoid applying partner solutions via the SAP Cloud Applications Studio.
- Do not request new tenants.
- Do not request termination of tenants.
- Upgrades should be positioned as a non-event, meaning that testing is not required.
- For approximately two weeks during which test tenants are upgraded and production tenants are not, remember the following:
- Change projects cannot be merged from test to production.
- Go-lives should be avoided.
- Avoid applying SDK solutions.
- Do not request new tenants.
- Do not request termination of tenants.
- Note that all previously requested restore points are no longer available after the upgrade.