Another one bites the dust… The trend now seems clear. When SAP starts referring to one of its applications with the prefix “Classic” that means that the application is now being seen through the rearview mirror by its development team. At the same time, a new application is launched replacing the classic one and carrying usual prefixes like Smart, Advanced or Simplified.
The classic application is therefore, as SAP puts it, deprecated. No further development effort will be directed to it. New development and features will be directed to the new kid on the block…
This is exactly what is happening with SAP HANA Extended Application Services Classic (XSC). SAP launched its replacement with SAP HANA 1.0 SPS 11 and named it SAP HANA Extended Application Services Advanced (XSA). In SAP HANA 2.0, XSA has become the framework recommended as default by SAP for new native application development.
The catch is that with it the following components were also incorporated to the “Classic” list:
- SAP HANA extended application services, classic model
- SAP HANA Repository (XS classic)
- SAP HANA Studio (Development, Modeling, and Administration perspectives)
- SAP HANA Web-based Development Workbench (XS classic)
- User _SYS_REPO
What is the impact of such direction? Well, first the SAP HANA modeling, development and administrative perspectives will no longer be available within SAP HANA Studio These perspectives are being replaced by Web IDE (Web based Integrated Development Environment).
SAP HANA views developed with XSC are stored in the SAP HANA repository. However, to make use of them within Web IDE they first need to be migrated and store as XSA friendly-format design-time artifacts within the new SAP HANA Deployment Infrastructure (HDI) Container. SAP is making available a SAP HANA XS Advanced Migration Assistant for this purpose.
You can find more details of such enhancement and related preparation steps on SAP Note “2465027 – Deprecation of SAP HANA extended application services, classic model and SAP HANA Repository”.
The deprecated items listed on this post will continue to be supported with SAP HANA 1.0 SPS 12 and SAP HANA 2.0 but shall be removed from later versions of SAP HANA according to SAP.
Happy readings and migration planning!