Overview
Providing a significant number of new features is an important goal of release upgrades to deliver innovations to our customers and partners.
An upgrade is intended as a “no event” for customers and partners. For example, only compatible changes of released objects (APIs) will be delivered. But we recommend performing a test of the custom-built productive apps in a test environment for the new release. The complexity of the technical dependencies between the custom-built apps and the underlying environment cannot be tested isolated, only including the ABAP environment on SAP side. Therefore, we offer you to upgrade selected systems 15 days in advance to test the applications prior to the planned standard-upgrade.
Purpose
This option enables a customer or partner to test their already developed applications on top of the new release a couple of days before the standard-upgrade. With SAP BTP ABAP Environment, we follow the approach of keeping released objects stable and provide all enhancements in a compatible fashion. But early testing is an additional measure to ensure appropriate software quality and might be used to detect unforeseen regressions. However, this option is not intended to test new features or to consume new features earlier.
Approach
The standard-upgrade of all systems to release 2108 is planned for August 21/22.
A customer or partner can nominate one or more already existing systems for the pre-upgrade. A nominated system will be upgraded on August 6 within a planned downtime from 8:00 to 16:00 CEST.
We recommend nominating a non-development system, for example, a test system. The nomination of a development system is technically also possible, but fixes or other changes must not be imported into another system with a lower release. The nomination of a productive system doesn’t make sense because the purpose of the pre-upgrade is the re-test of the existing application before the productive system gets the new release.
According to the explained approach, this offer is only relevant for customers or partners having at least two systems.
There might be situations where a correction of custom-objects needs to be deployed. Such corrections are possible if the development / correction system is on the older release and is imported into the pre-upgraded system with the higher release.
Except potential fixes, the pre-upgrade is based on the same version as the standard-upgrade. In both cases, release 2108 HFC 2 will be used.
Costs
This offering is optional and free of any additional charges.
Planned New Features
All the planned new features are published on the What’s New for SAP Business Technology Platform. This list gives you an overview about potential areas for re-testing. But the purpose of the pre-upgrade is not to consume these features before the standard-upgrade, because the documentation on help.sap.com will be delivered later before the standard-upgrade and it would also not be possible to transport code of such an adoption, because subsequent systems are not yet on the new release during the pre-upgrade phase.
Independent of the upgrades of the SAP BTP ABAP Environment, we recommend developing automated tests for the custom-built apps to detect regressions early on and without manual effort for re-testing. Such automated tests are perfectly suited to be executed in the pre-upgrade test phase.
Time Schedule
The following figure summarizes the general approach
No comments:
Post a Comment