on 07-21-2017 10:42 AM
I am struggling to understand what the recommended approach is when using SAP Data Services as a source for BW/4HANA.
In BWoH, you could simply add a source system of type 'SAP Data Services' and the loads from Data Services would end up in PSA tables in BW (BWoH).
The guidance for BW/4HANA for Data Services now shows: "Consolidation to new HANA Source System". But what does this mean? Do I connect SAP Data Services to HANA at database level, and do I create my own HANA tables as targets, which in turn are the source for further loads into BW/4HANA?
That is quite a radical break from the previous approach, and in many cases would result in a lot of re-design of BODS processes.
I also wonder what the consequences are if I only have a runtime license for BW/4HANA, as I am now creating tables which are not directly managed by BW/4HANA...
Any views on this or clarification would be much appreciated.
Jan.
Thanks for your input Dirk, much appreciated.
If you do find a way to connect DS through standard connectors it would be great if you could feed back the information here.
So far, I still haven't found a way and I have looked in many places and asked a number of people.
Same with SDI, by the way.
Just like you, I have read much documentation which suggests BW/4HANA interacts with SAP Data Services and SDI directly, but when you read further, it actually loads into HANA native tables, not BW/4HANA. Hopefully it is a statement of SAP's intend and they will enable direct loads into BW/4HANA soon.... but I won't hold my breath.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
According to this note https://launchpad.support.sap.com/#/notes/2441836, BW4/HANA 2.0 will provide write API for data service to write directly to ADSO inbound table. That doesn’t answer the question on how to orchestrate it all from PC, but it eliminates the need for HANA full use license for creating table on HANA level.
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan,
in the SAP BW 4 Hana training 462 they told us that DS is not supported anymore.
I think the general connection might not be the problem. But as a main part of the integration was managed via parameters of IPAKs, with their absence a substitute would be needed to ensure an elegant migration.
Same with me, I had everything managed via PC IPAKs and an ABAP that changes parameters.
If then storing data into a table is necessary then I assume creating tables with in the BW domain should not be a bit license issue.
As far as I understood they can be column based too. Although I am also a bit irritated since the books and documentations I read spare out this topic deliberately.
There are rumors that it works fine if you connect DS just to one other of the new standard connectors. But I think this will take some months for me to prove, since we just started.
Dirk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan,
Your understanding with the new approach is correct. HANA level is the new target for BODS.
I didn't come across with an automated migration process for converting the existing models. I don't think it's possible. So, unfortunately it's something to build from scratch.
As far as I know runtime license will not be enough but there might be exceptional cases. As you mentioned, it's better to confirm that with your account manager.
Regards,
Erdem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Julian - I'm pretty sure a Runtime license will not allow you to store data in HANA tables.
Best to check with your SAP account manager though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This approach also applies to BW systems with Runtime licensing?
Best Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Vadim, that sounds a good approach when you start new development with BODS and BW/4HANA.
That still leaves the question what to do with migration from 7.4 to BW/4HANA where there is a lot of BODS going directly into the BW application.
Hopefully there is an easy solution for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan! For the sake of argument, I'd think that in new BW4 realm we could create HANA tables to store BODS data and then build HANA calculation views on top of them to be included in composite providers. That would significantly shorten the whole ETL process going forward.
Otherwise, using PSA and ETL upstream from PSA into ADSO multiplies data.
I understand I haven't answered your question, just shared my view 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.