AEB software and involved components are continuously changing and being developed further. This article summarizes the relevant, up-to-date information.
Active and passive maintenance, end of maintenance, follow-up releases, and rollout phase
The terms used in the graphical release planning are briefly explained here.
Release in active maintenance - Current release
Necessary functional adjustments will be implemented. Reported or internally found malfunctions will be patched as part of the active maintenance by means of monthly standard service packs or quarterly feature packs (February, May, July, November). AEB will provide the necessary information.
For on-premise installations, it is the obligation of the customer to install the service packs/releases provided by AEB and keep them up to date. If the customer does not comply with this obligation, it will not be able to use the services and support according to the General Terms and Conditions for Support.
Release in passive maintenance
Malfunctions, if reported, will be corrected. In justified and exceptional cases, standard service packs will be provided. It is recommended to schedule a release change.
New standard service packs will not be made available anymore. A release change should be carried out.
A new version is available and replaces the current release. A release change should be carried out.
Migration phases from one release to the next are flagged as rollout phases. The rollout phase includes the migration phase supported by AEB, during which migration projects should be implemented.
- MSSQL Server As a Service under Azure currently in evaluation
- SAP S/4HANA® released
- Oracle 19 driver released for Business Services (Engines)
- Oracle database 19 released
- MS SQL Server 2019 released
- Windows 2019 Server released
- Microsoft Edge (Chromium) released
End of support for operating environments and third-party software
- End of support for Internet Explorer as from 2022
- AEB products and Java
- MSSQL Server 2008 RS Service Pack 2
AEB will no longer support the Microsoft SQL Server 2008 database as from May 1, 2021.
Old versions of operating systems, Oracle databases, and MS SQL servers are only supported as long as they are still supported by the manufacturer. For SAP® releases the following regulation applies.
Supported Releases of SAP® solutions
In principle, the AEB Plug-Ins for SAP® require an SAP® ERP release (see SAP® release and maintenance strategy) which is part of the "Mainstream Maintenance" or "Extended Maintenance" of the supplier. Upon expiration of the "Extended Maintenance", i.e. when the “Customer-Specific Maintenance” is started, maintenance of products from the Plug-Ins is ceased in regards to the discontinued SAP® ERP release and S/4HANA release.
Therefore, active and passive maintenance of the products from the AEB Plug-Ins for the SAP® ERP ECC 6.0 will end of 2027.
When you are using SAP S/4HANA®, only the current version of the AEB plug-ins for SAP® is supported. Only on-premise releases of SAP S/4HANA® with status 2020 or higher are actively maintained. The maintenance for the respective S/4HANA® release ends 5 years after the first release.
Therefore, as from the May 2021 service pack, make sure to always download the transport of the corresponding SAP® version. The transports are shown accordingly in the Download Portal.
Current system requirements
For the current requirements of your AEB application, please refer to the product-specific AEB Cloud System Requirements or On-Premise Installation System Requirements. The system requirements are available after login in the Download Portal.