Skip to Content
Technical Articles

BW Extractors, CDS Views Extraction into Native HANA via SDI – Part II

Hi All,

In this blog we are going to cover 2nd Scenario Data Extraction from CDS views to Native HANA system via SDI

In the first blog we had covered – Data Extraction from BW Extractors to Native HANA system

Requirement – To Extract CDS Views Data from S/4HANA to Native HANA system.

Pre-requisite & ABAP Adapter settings – Already discussed in Part I of the blog.

Detail Steps

  • Create CDS view as shown below – It should have all the annotations needed for Extraction, Delta Fetch and annotation to detect deleted records.

CDS%20view%20-%20with%20required%20annotations

CDS view – with required annotations

  • Check CDS view under Remote Source – You will find it with SQL View Name, in this case ZCDSSOHDRITM$F (Note Dollar($) F stands for Data Category as Fact)

CDS%20view%20under%20remote%20source

CDS view under remote source

  • Create Flow Graph as shown below –

Final%20Flow%20Graph

Final Flow Graph

  • Flow Graph Source n Target – As discussed in Part I of the blog Source of the flow graph is Virtual Table created on top of CDS view and Target is Column Table.
  • Settings of Data Source in Flow Graph – 

Source%20-%20Virtual%20Table%20settings

Source – Virtual Table settings

Source – Delta Settings

  • Target Table setting in Flow Graph – Upsert mode

Writer%20Settings%20in%20Flow%20Graph%20-%20Upsert

Writer Settings in Flow Graph – Upsert Mode

  • Execute the Flow Graph – Once the Job is executed successfully observe the Subscriptions in ODQMON. I ran the job with delta setting but there are 2 extraction requests –  one with init without data transfer and other with full load.

ODQMON%20-%20CDS%20View

ODQMON – CDS View

Subscriptions

  • Check the number of records in source n target – It’s 1782
  • Delta test with an example – Transaction VA02
    • Sales Order Number – 1716
    • Item 10, Material –  8900103
    • Quantity – 25

SO%20-%201716

SO – 1716

  • Check the same in Native HANA table

SO%20Value%20in%20HANA%20Table

SO Value in HANA Table

 

  • Change the Sales Order – New Item 20 is added with Order Qty 45

SO%20Updated%20with%20Item%2020

SO Updated with Item 20

  • Execute the Flow Graph and check the entries in HANA Table

New%20Item%20in%20HANA%20Table

New Item in HANA Table

  • Change the Order Qty of item 20 to 110

Updated%20Order%20Qty%20of%20item%2020

Updated Order Qty of item 20

  • Check the Delta Entry in ODQMON – 2 records since Order & Item forms are the key in CDS view

Delta entry in ODQMON

  • Check the updated value in HANA Table

Updated%20order%20value

Updated order value

  • Delete the Sales Order Item 20 for the order 1716
  • Execute the Flow Graph and check the Delta Queue entry – Item 20 comes is transferred with Order Qty 0.

Deleted%20Order%20Item%20-%20comes%20with%200%20value

Deleted Order Item – comes with 0 value

  • Check the Order again in HANA Table

HANA%20table%20-%20Item%2020%20is%20updated%20with%200

HANA table – Item 20 is updated with 0

 

Conclusion – Extraction From CDS views in Native HANA works fine, except that table entries may grow with deleted records. These records can be identified easily and filtered out in the modeling views.

Mayank Jaiswal & Hemant Patidar

(Authors)

Be the first to leave a comment
You must be Logged on to comment or reply to a post.