Skip to Content

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:

 

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. BW team BW team Nestlé Business Technology

    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?

     

    (0) 
    1. Muruga MuthuKrishnan Post author

      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.

      (0) 
  2. Mark Thienpont

    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.

     

    (0) 
    1. Muruga MuthuKrishnan Post author

      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

      (0) 

Leave a Reply