Technology Blog Posts by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Datasphere - BW ODP Delta via Replication Flow

Martin_Kuma
Contributor
‎2024 Jun 23 1:31 PM
0 Kudos
2,842

Loading Delta data using ODP from BW.

I have had an issue on my own here: I was misslead by the clasification of the ODQ Objects in the ODP Container. The clasification is set to table and a table (as such) has no delta posibitlity. In the ODP Container are real ODQ Objects, which can be subscribed to.

 

Use Case
For example, we have a HCPR and are unable to use the BW/4H Model Transfer option (we may have a 7.5 system for example).

ODP does not support delta for HCPR, so we need to connect the underlying ADSOs directly. ODP Delta works only for ADSOs with Change Log.

 

Steps
#1 Analyze the BW Provider. Check for delta capability

Analyze the source composite provider. If a join is used, analyze the conditions as we need to build them in DSP as well. All underlying ADSOs must have the Change Log activated:

Kuma_0-1719145539663.png

Kuma_1-1719145539665.png

 

#2 Create Replication flow(s). DSP Local tables can be auto-generated.

Replication flow will automatically load all initial and delta data for all subscribed ODQs. Depends on your architecture, create one flow for each ADSO or one flow for HCPR, InfoArea, etc. ODQ Sources can be combined in one flow. Depends on the costs you are willing to take. 

 

Replication Flow loads data from ODQ Source(s) to DSP local table(s).

Type: Replication Flow

Uses:

  • ODQ Source(s)
  • DSP local table (can be auto-generated!)

Settings: The only important setting is the Load Type: Initial and Delta. After executed, the flow remains in the status running and checks for new data.  

Kuma_2-1719145539666.png

The ABAP connection is sufficient for ODP:

Kuma_3-1719145539668.png

After choosing the container, also choose the ODQ Objects and subscribe to them.

Kuma_4-1719145539670.png

 

Kuma_5-1719145539674.png

It is possible to choose a more global Container, rather then Info Area. However if there is a lot of objects, the reading / fetching will get complicated and can lead to error messages.

 

Local table for all extracted data.

Type: Local Table

Semantic Usage: Relational Dataset

Key: Wizard will propose a table 1:1 to the source

 

Monitoring

Flow is real-time triggered by the ODP subscription. Monitoring is done via DIM -> Flows. 

Kuma_6-1719145539676.png

Kuma_7-1719145539678.png

 

#3 Create a View(s) and consume the BW data in DSP

This depends on your architecture. I prefer to create private-like views for each ADSO and rebuild the HCPR join in a reuse-like view.