Analytics Trends


Operational Data Provisioning - SAP BW 7.4 on SAP HANA

Posted 7/18/14

In this post we'll discuss a few recent developments in the SAP HANA space, including new features available in the recent versions of SAP BW on SAP HANA. My objective here is not to write a How-To Document (there are way too many how-to docs available from SAP), but rather to start a discussion. While there are many new features/functionalities introduced with the latest version, there is one in particular that I found very interesting. That feature is Operational Data Provisions (ODP)

What is ODP and how is it going to change the way SAP BW modeling is done today, specifically in the area of extraction/data staging? Reading through some of the SAP presentations on SAP BW 7.4 and the online help documents, I have discovered that the ODP is not a new concept. It was actually available prior to SAP BW 7.4.  So, does that mean the application of ODP has been broadened with the latest version? SAP BI Data Services (DS) had the option of using Operational Data Provisioning for consuming data from an ECC source. What’s new in 7.4 is that now it supports SAP BW as a Provider (i.e. Source) and as a Consumer (i.e. target).

Basically there are three layers (1) A Provider, (2) Operational Data Provisioning (with Operational Delta Queue) and (3) a Consumer. It is a unified technology for data provisioning and consumption with benefits such as

  • Extract once deploy many architectures for sources
  • Unified Configuration and monitoring
  • Highly Efficient Compression that enables data compression rate up to 90%
  • Intelligent parallelization options in high volume scenarios

Moreover, it supports trigger based table replication to SAP BW with SLT. A new source system type “ODP-SLT” is now available for “SLT Real-Time push in operational Delta Queue (ODQ)” and “Direct Update to SAP BW InfoProviders”. The benefits include:

  • simplified data flow
  • flexible recovery options
  • consumption of ODQ by multiple subscribers
  • reduced data latency  
  • PSA becoming optional

Now that becomes even more interesting. This is certainly going to help in many ways and change the way we have been doing data modeling in SAP BW. I am waiting to get an opportunity to use/implement these new concepts in a real life scenario and share my experiences with you all.

I look forward to your response/comments to keep the discussion going.

Add Comment
Shreyash Tambe
Can anyone tell me about benefits of ODP? eg.
1. flexible recovery options
2. reduced data latency
Posted on 6/29/17 1:42 AM.
rahul kevin
Hi Buddy,
Very cool to see your post come up when I was searching this topic!

we are planning to migrate the <a href="">HANA DB</a>
from On-prem to Azure .
how ever on Azure we are going to choose RHEL 7.
Source HANA is having the OS as SUSE 11.
please confirm the correct method for the same . so that we should plan accordingly.
Backup restore or export import.

Appreciate your effort for making such useful blogs and helping the community.
Posted on 3/23/18 11:39 PM.
Radhey radhey
Hi There,

Nice tutorial! Let's keep our fingers crossed that this works. I would like to put this all to rest.

I have written a stored procedure with tables from schema - "DEV" in my source hana system and the same tables are under a different schema "QAL" in target hana system. <a href="">SAP HANA training USA </a>
I have to transport this stored procedure, how will this work?
For Ex :
I have written below statement in Stored procedure in Source HANA system:
select * from "DEV"."MARA"
However, in Target it has to become "QAL"."MARA" after transport.
Schema Mapping will not help in this scenario, Please help.

Excellent tutorials - very easy to understand with all the details. I hope you will continue to provide more such tutorials.

Thanks a heaps
Posted on 5/30/18 11:26 PM in reply to rahul kevin.
Ratna sri
<a href="">SAP HANA TRAINING in Hyderabad</a>
Posted on 9/6/18 6:50 AM.
Ratna sri
Posted on 9/6/18 6:51 AM.

Contact Us

character(s) remaining