S/4 HANA – BW/4HANA Integration through ODP – ABAP CDS views as Data Provisioning
Overview:
SAP has provided multiple approaches to integrate S/4 HANA with standalone BW4HANA/BW. Here we are going to see how data from S/4 HANA can be extracted to BW4HANA through ODP-ABAP CDS views. This document will provide step by step technical guidance to integrate the S4HANA with standalone BW system through ODP – ABAP CDS views as extraction method.
| Extraction Method | BW Version | S/4 HANA Version |
| ODP ABAP CDS Views | BW4 HANA | 1511 FPS02 |
Follow the below steps to develop the model
Step 1: Check the connection (ODP – ABAP CDS Views) is established between the source system and BW4HANA.
Step 2: Once the connection is established open your BW Modeling perspective in Eclipse/HANA studio and follow the mentioned process.
Go to the required application component in BW Modeling perspective and then replicate the ABAP CDS Views under the required application component. Replicated CDS views will act as data sources for BW4HANA for extraction purpose. Here we are using Billing CDS view (ISDBILLGDOCITEM) for illustration purpose.
Step 3: Select the required Data source name which is generated based on the CDS views replication (step 2) as per your business requirements.
Replication job will be created and you can check this job in T-code SM37.
Step 4: Create the Dataflow by dragging the CDS views from the left pane.
Step 5: Use the required modeling objects which is required for the business requirement. Here for illustration we are taking ADSO as staging layer. Drag and drop the modeling object from the right pane.
Step 6: Right click in the transformation icon and create the transformation which will navigate to the RSA1 and mapping for the source and target field are proposed. If you need any logic implementation then the same can be implemented in start, rule level or end routine as required.
Follow the step 6 for DTP creation as well.
Step 7: Run the DTP load.
Step 8: Loaded data can be visible in the active table of the DSO.
Step 9: Create a Composite Provider by adding the created ADSO.
Step 10: Create a Bex Query in the eclipse.
Maintain the general properties which are required for the query.
If any filters are required add in the Filters tab.
BeX level local/global CKF’s and RKF’s can be created by Right click in the key figure.
Step 11: Query Output:
Nice Blog Muruga. Thanks for sharing.....
Very Good Document on new capabilities of BW. Thanks for sharing.
Good one boss!! Keep it flowing.
Helps a lot in clearing out some of the concepts around data integration.
Good one Muruga.. Keep posting , learnt couple of new things from this blog.
It is very informative blog and help the developers to have readily available series of activities to build a model
Thanks everyone for going through my blog and for your comments.
Nice blog Muruga! Its imperative to have such blogs to help shed light on new methods and step by step process.
Keep it coming !
Very nice blog Muruga... Keep it up...
Nice blog and great thought provoker!… What are the thoughts around use of CDS Views like ISDBILLGDOCITEM versus exposing 2LIS_13_VDXXX extractors for ODP? I assume the CDS Views will perform faster but is the direction to cover all logic of the LIS extractors into S/4 CDS Views?
Thanks for going through my blog. To answer your question existing LO extractors are going to be replaced by CDS views and SAP road-map for future data extraction is based on CDS views only not the typical extractors. CDS view based extractions are much faster compared to typical extractors, my view is both logics will be same but I didn't deep dive and compare in that aspect. Will test and update the blog, thanks for raising this question.
Note: As of now CDS views are not capable to handle delta which is possible in typical LO extractors.
Thanks Muruga for this informative Blog. As you said, LO extractors are going to be replaced by CDS Views. I have couple of questions regarding this.
1.Does that mean all the extractors which we find in LBWE, will be available as CDS extractors as standard business content in embedded analytics of S/4 HANA?
2.How about accessing these views directly at runtime with Open ODS and not replicating them in ADSO on daily basis. Is realtime access available?
3. Can we extend the CDS views based extractors the way we used to enhance standard LO extractors in ABAP?
Best Regards,
Gaurav
Best Regards,
Gaurav
Hi Muruga,
Due to using ODP-framework, it doesn't make sence to use PSA in the staging any longer. However : when I create the DTP (and there I need to use the 'full load' mechanism so that ODP becomes available as datasource-framework) and load, everything seems to go well in the DTP-load-monitor, but the package doesn't show up in the ADSO. Any idea if such is "works as designed" ?
Tx,
Mark.
Hi Mark,
Why do you need to use FULL we tried with DELTA for ODP based extraction and it is able to pick only the delta changes so need to use FULL.
Are you referring that your request (package) is not available or data set is missing in ADSO? Can you help me to understand your question?
Thanks,
Muruga
Hi Muruga,
There was apparently still a bug in the system (solved by a patch), which solved the problem I was facing.
Kind regards,
Mark.
Hi Muruga,
Thank you so much. This is very informative.
Questions about options of accessing SAP S/4 HANA data:
1. The delta pull into the ADSO object in BW/4 HANA system
Is this pull using the embedded BW in S/4 Hana system or via the SLT replication server?
2. SAP BW/Hana system's Data provisioning
Can we use one of adapters to create a virtual table to access S/4 Hana system's CDS view?
Thanks.
Hi Bruce,
Sorry for delayed response,
The delta pull into the ADSO object in BW/4 HANA system: This is based on ODP hence you don't need SLT replication server or Embedded BW.
SAP BW/Hana system’s Data provisioning: I have tried Virtual table based CDS views but i would suggest to use ODP based extraction rather than Virtual table reason being there is no necessity to develop Virtual table. SAP provided the source system connectivity for ABAP CDS views.
Hope this helps you.
Hi Muruga,
What all type of CDS views are exposed to BW, is it that any view which has "Analytics.dataExtraction.enabled: true" can be a source to BW.
Regards,
Mayank
VDM type is composite, data category is Cube and data extraction annotation should be enabled as true.
Hi Muruga,
Thanks for your share.In STEP 2 , i can't find required application component in BW Modeling such as, you mentioned [SD-Bill].The attach photo is all application component after connect source system ,i open the folder still can't find what as you say.
What should i do to extract data from S/4 to bw/4hana? AS your last blog ,you detailed the list uising LO ,how about S/4 ?by CDS way?Hoping for your reply,thanks a lot!
Hi Duan,
Sorry for the delayed response, replicate the complete hierarchy and also check whether the info area is installed. May I know what version of BW/4HANA and BI content SP level?
If you have SAP standard data source which is whitelisted by SAP then we are good to use those extractors incase your standard extractor is not whitelisted and if you are going with custom development then I would suggest to use ABAP CDS view for extraction purpose.
Whitelisted means SAP has released list of extractors which will work in S/4HANA, always we have to check the list w.r.t. extractor.
Hope this clarifies your questions.
Thanks,
Hi,
Are these CDS extractors applicable for any BW version on any DB, and not only HANA?
BW 7.3 and above only supports CDS extractors?
Hi,
CDS extractors can be accessed in BW only through ABAP CDS view source system. Version should be above BW7.3 and on HANA (don't see the option in lower versions).