Skip to Content
0

Impact on HANA reports when changing source to S/4HANA

Apr 10 at 03:31 PM

52

avatar image
Former Member

My client currently delivers their front office reports out of HANA. They have a number of SLTs to replicate data from ECC 6.0 into HANA for this purpose. They now want to upgrade ECC 6.0 to S/4HANA. What will be the impact on their Front Office reports? They want minimal impact on Front Office so they want to continue to use their HANA Front Office reports. Are SLTs still required to replicate data from S/4HANA to HANA? What other considerations do I need to consider so their Front Office HANA reports continue to work

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Renaud VAN DEN DAELE
Apr 11 at 07:21 PM
0

Hello,

I would say we are missing a bit of information, for example, you are not mentioning if the "front office" report is done on standard tables or specific tables, in ABAP or via a reporting tool such as BO BI requesting on SAP HANA DB. My understanding is that the customer is currently in side-car scenario, like the CO-PA accelerator, but it may different, which would void my answer

Assuming all data originates from ECC AND is based on standard tables replicated to SAP HANA for performance purpose AND is consumed via ABAP reporting in ECC, they would "only" need to adapt their reports to call the SAP HANA DB like they would do on the current ECC DB, and not like via a side car SAP HANA DB. The standard data model in SAP S/4HANA is different from ECC one due to the simplification, but as we are proposing so called compatibility views, there is quite a lot of chance that they can keep calling the same table names (ie BSEG) from their report (compatibility views may lead to perf issues so this will then have to be handled case by case) even if the table does not exist in reality. But in all case, if my understanding of the scenario is correct (but you need to explain what a front office report is), SLT will not be used for data originating from future SAP S/4HANA

Hope this helps.

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thanks Renaud.

The Front Office reports vary in nature. Data in HANA is modelled using HANA Studio (1.00.93) and then developed into reports using various tools. E.g.: Webi (4.1 SP6), Design Studio(1.6), Analysis for Office (2.4.1), Lumira (1.30), Crystal reports (2013). Most reports, no matter where they were developed, are consumed by end users through a Portal.

Although reports get their data from other sources, it is the impact on the data coming from ECC that I am focusing on because ECC will be upgraded to S/4HANA.

Based on your feedback, it sounds like all the data currently residing in HANA should be migrated to S/4 HANA and all the reports currently built on top of HANA (WEBI, A4O etc.) should also be migrated to run on top of S/4HANA. Is this correct?

0
Renaud VAN DEN DAELE
Apr 13 at 03:25 PM
0

Hello Michael,

I think will go a bit beyond my Knowledge regarding reporting directly on the HANA db, I am more on the SAP S/4HANA topic. However, indeed, I think that keeping an HANA DB (or maybe tenant) + SLT to replicate data which is already in the HANA DB for the sake of minimal impact cannot be a good strategy. I do not not even know if you can put SLT triggers on the to be source HANA DB. This may however be a valid strategy if the HANA db serves for EDW (that is feeding data from other sources than ECC). You may need to understand as well that while the customer will discover SAP S/4HANA and the Embedded Analytics, they may feel as well that their FO report are not useful anymore, or need to be re-created via the Embedded Analytics Framework for plenty of reasons. They will be able to consume the data from SAP S/4HANA Views via BO for example as well.

Best regards

Renaud

Share
10 |10000 characters needed characters left characters exceeded