Which approach should be used (XSC vs XSA) when using HANA Native and BW4HANA on the same instance?

[KonradZaleski]

I know that there are bunch of question regarding XSC and XSA, but for me it is still quite confusing when to migrate to XSA.

As per SAP statement: SAP HANA Extended Application Services classic model (XS classic) and SAP HANA Repository are deprecated as of SAP HANA 2.0 SPS 02.

In our scenario in the same instance we have HANA views which are consumed directly by users (as native views or exposed to BW through Composite Providers) and reporting on BW4HANA objects. We can easily combine Native HANA Views with BW4 objects and take benefits from mixed scenario.

In such a setup should we migrate HANA views to XSA? I know that now it's possible to consume XSA views by BW objects (Composite providers, Open ODs etc.) but it's not possible to generate XSA views from BW objects.

Now I have some concerns for following scenarios:

• consuming XSC views (generated from BW objects) by XSA views
• mapping input parameters from XSA views to BW Composite providers
• using XSA views as data sources in Transformations

We are using HANA Views both for reporting and as data sources for BW transformations. Views generated from BW objects are used for mixed scenarios.

Could you please advise in which case migration to XSA is reasonable?

[lbreddemann]

michael.eaton3 if you are interested in a simpler way to build apps on top of HANA then make sure to have a look at Werner’s blog posts that I referenced in my answer.

Werner has released a whole new app container, that allows to build data driven apps with minimal code and even less boilerplate rain-dance around it.