Categories Uncategorized FAQ: SAP BW & Operational Data Provisioning Framework (ODP) November 26, 2015 | 32,650 Views | Former Member BW (SAP Business Warehouse) share share tweet share like 1 Follow The Operational Data Provisioning FAQ has moved! Please have a look at: https://blogs.sap.com/2017/07/20/operational-data-provisioning-odp-faq/ Alert Moderator To report this post you need to login first. 36 Replies 36 Comments You must be Logged on to comment or reply to a post. Prashanth Avula December 1, 2015 at 8:50 am Hello Marc, We are planning to leverage BW reporting out of SAP GRC system. Does ODP be applicable in this use case. since we don’t have seperate BW system, we are trying to understand if it benefits to go with ODP or with out ODP. Please suggest. thanks. like (0) Former Member Post authorDecember 2, 2015 at 10:57 am Hi Prashnath, the ODP infrastrcuture can also be used to enabled reporting scenarios in embedded BW use cases like in SAP GRC. In this cases we are exposing a DataSource with direct access on tables. My explanation in this blog is focusing on transfering data with ODP to another system. Here you find documentation for your use case: Operational Data Provisioning – Search and Operational Analytics – SAP Library Regards, Marc like (0) Prashanth Avula December 2, 2015 at 4:47 pm thank you Marc. like (0) Former Member December 14, 2015 at 12:42 pm Hi Marc, Thanks for the detailed Blod, the is very nice document on ODP, I have few questions Reg..this. I am new to this ODP Concept, in our company we have ECC6, BW on HANA, SLT connected to HANA & BODS. 1. Do I need separate installation for ODP? We have PI_BASIS— 731 SP5 2. Is there any separate configuration required for ODP? 3. As you know we have BODS & SLT, which one we have to use for data load? 4. I can replicate from SAP, when why we have to go for other option? Only for live data. 5. For live data I can do native HANA modeling right? Please share me detail steps to implement the ODP extraction from SAP, SLT, BODS. Jameel like (0) Former Member Post authorDecember 23, 2015 at 8:04 am Please find my answers according to you questions: See above I updated the prerequisites according the used release You don’t have to use any of both, but you can There are slight differences: SLT is writing into ODP, DataServices is reading out of it. So from this perspecitve you can’t compare them with each other. I would rather than think about my requirements: do I need replication and delta creation (SLT) or do I need ETL with transform functions (DataServices)…. Different requirements – different tools and approaches. Replication is not always required.. HANA modelling is a option for SQL centric modelling and an again an option depending on requirements Regards, Marc like (0) Former Member April 5, 2016 at 7:06 am Dear MARC, We are running on BW on HANAProject, as part of that we are implementing ODP enabled extractors. You would like to use the ODPdata replication API for the below datasource to replicate Data from ERP Systemusing ODP – SAP (Extractors). The below extractors are not yetreleased for ODP, please advise us how we can leverage the ODP functionalityfor the below SAP standard Data sources. SAP Extractor 2LIS_03_BF 2LIS_03_BX 2LIS_03_UM 0FI_GL_6 0FI_GL_4 0CO_OM_WBS_6 0CO_OM_CCA_10 0CO_PC_ACT_05 0CO_PC_ACT_02 0EC_PCA_1 like (0) Andreas Tenholte April 6, 2016 at 1:58 pm Hi Shaik Jameel Ahmed, all the data sources mentioned by you are already released for extraction in the ODP context. Just follow SAP Note 2232584 mentioned in bullet point ‘How can I enable standard or generic extractors using ODP?’ in Marc’s blog post above. Best regards, Andreas like (0) Sander van Willigen December 27, 2015 at 9:23 am Hi Marc, Can you please review the SAP Note given for the following question: How can I enable standard or generic extractors using ODP? See SAP Note 2235284 for more information The SAP Note refers to EHS and I think you meant a different one. Thanks in advance. Best regards, Sander like (0) Former Member Post authorJanuary 4, 2016 at 9:57 am Hi Sander, thanks for the hint, it was indeed a type which should refer to: 2232584 – Release of SAP extractors for operational data provisioning (ODP) Thanks, Marc like (0) Former Member January 6, 2016 at 10:33 pm Hello Marc, Thanks for an informative Blog. I have a QQ in my scenario I need to know the last Delta pointer of a Delta Queue for ODQ. My scenario : i) <Generic Timestamp Data Source ECC > –> ODP based extraction into BW cube w/o PSA (Target 1) ii) <Same Data source as i) in ECC > –> ODP based extraction to Virtual Provider in BW but with a filter of data only upto the Timestamp extracted in process i) Target 2. appreciate your help. Thanks, Tarun like (0) joseph yeruva February 14, 2016 at 1:25 am Hi Marc, Thanks for the updates. Apart from performance of loading, 1.what is the main difference between loading from the Operational Delta Queue (TA ODQMON) in the source system via DTP into a DSO compared to loading from BW Service API Delta Queue (TA RSA7) via InfoPackage into a PSA and then via DTP into a DSO. 2.Can we make ODP frame work for extractors realtime without SLT.? Thanks, Joseph like (0) Former Member Post authorFebruary 15, 2016 at 8:11 am Hi Joseph, regarding your questions: 1) the data transfer, data storage (compressed) and the options to easily subscribe with many targets to the same source by receiving delta independently. Last but not least ODP is our strategic interface and with the services of ODQ in source we don’t need a PSA table per default 🙂 2) ODP supports all the existing extractor capabilities, also regards RDA enablement. However it is not enabling more extractors real-time (without SLT). Regards, Marc like (0) Former Member February 15, 2016 at 8:41 am Hi Marc, Can you please let me know your recommendation. we are going to start NEW BW implementation, do you recommend use Source system ” ODP – SAP (Extractors) ” ? Rather Classical SAP API ? if you have Step by Step for one Flow , please share us. Thanks for your help. Jameel like (0) Former Member Post authorFebruary 15, 2016 at 9:02 am Yes I would absolutely recommend ODP from scratch. There is no difference for implementation, beside you just use another type of source system and enable once the extractors for ODP usage. This is documented in my blog and in sap help. Regards, Marc like (0) Former Member February 18, 2016 at 9:11 am Hi Mark, Can you please clarify, when you are saying “ Yes I would absolutely recommend ODP from scratch. There is no difference for implementation “ do you consider that the implementation of ODP requires to have SLT server int system landscape, but with Classical SAP API SLT server is not required? or I missing something in the concept? thanks, Best, Igor like (0) Former Member Post authorFebruary 18, 2016 at 9:57 am Hi Igor, there are multiple use cases for ODP usage, which we should not mix up together: ODP is a general interface for data transfer for many use cases (ERP->BW, SLT->BW, BW->BW) SLT is using ODP to replicate data into BW as additional option to bring data into BW (to use ODP, SLT is not required) I would recommend to use ODP for transfer between ERP to BW in every new data flow. SLT could be an additional tool to replicate data in real-time by also using ODP as framework. Regards, Marc like (0) Former Member February 19, 2016 at 2:31 pm Hi Marc, can i replicate real-time data from ERP to BW by ODP-SAP(Extractors) source system? can i use sap standard extractor in ODP-SLT source system? SLT support only DB tables and Views? like (0) Christophe Posson March 23, 2016 at 4:23 pm Hi Marc, Interesting information 🙂 I have a question regarding the scenario where ODP is used in between 2 BW systems. How should we proceed in this case? My initial idea was: to generate en Export DataSource for example on an InfoCube in the source BW. Expose that DS to ODP using RODPS_OS_EXPOSE replicate it in the target BW under the ODP – BW Source Systems node However, I found out that: An Export DataSource is always generated as a 3.X DataSource A 3.X datasource is not visible in RODPS_OS_EXPOSE A 3.X DataSource cannot be migrated to a 7.X DataSource So I wonder now what the preferred method of transferring data between 2 BW systems using ODP is? Thanks far any clarification! Kind regards, Christophe Posson like (0) Christophe Posson April 25, 2016 at 7:19 am No worries, Answer found thanks to email@example.com. As of BW 7.4 SP5 most of the InfoProviders are by default available as datamart interface for ODP in the BW to BW scenario. InfoCube TEST123 for example would represent itself as TEST123$F in the ODP datasource tree in the target BW. Kind regards, Christophe like (0) Former Member March 29, 2016 at 8:36 am Hi Marc, We have an ERP1->ERP2 scenario in which I have to transfer daily GL data (with some ETL) from one ECC6 system to another. We would like to leverage the powerful delta queue features of ODQMON but we do not have the use of DataServices. Is it possible for the receiving ERP2 system to be the consumer of the delta queue in ERP1? What mechanism/s could be used to achieve this? Thanks and regards, Dieter Zimmermann like (0) Former Member May 30, 2016 at 2:03 pm Hi Marc, For the point, If the extractor logic is the ‘bottle neck’ the throughput won’t change I am trying to understand the scenario where ODP queue will help in improving the issue with extractor run time for data loads that are performed daily during night by filling the ODP queue frequently, ex. more than once in a day. In a regular flow using RSA7 the data has to be loaded to PSA multiple times a day. Can you please comment? like (0) Torsten Wirth June 15, 2016 at 11:14 am Hi Marc, It would be nice if there is a scenario / how to what to do if release / EHP in source system is changing. For the old RSA7 way there are several guide which basically say clear delta queue (which means 0 in RSA7) and then proceed which release change. E.g. http://scn.sap.com/community/data-warehousing/bw/blog/2013/11/25/step-by-step-process-to-clear-extract-delta-queues-during-patchupgrade-in-ecc-system http://scn.sap.com/docs/DOC-27590 http://scn.sap.com/community/data-warehousing/bw/blog/2013/07/09/how-to-clear-the-outbound-queue-and-delta-queue But there are some DS which have safety intervalls of e.g. 2hours. That means in RSA7 you can check if there are really no records anymore. Then you have the approval that it’s safe to continue. I’m not sure how this should work in ODQMON because I don’t see records which are not extracted to BW in this monitoring transaction, do I? Second thing is that the records are kept for a customizable time period. Does this data has to be cleared before release change / EHP because structures could be changed? Furthermore it is difficult to activate content from BW because some DS are not available with ODP. That bascally means that content has to be activated for two source systems in parallel for ODP and old way to get the ones where no ODP is available at the moment. Or maybe something like prefer ODP but if this is not available use the old way. It would be nice if a total switch from RSA7 to ODP / ODQMON would be possible. Regards, Torsten like (1) Former Member August 6, 2016 at 9:00 pm Hi All, We were performing Inventory data loading to BW PRD (BI 7.4 SP15) system from ECC 6.0 and using ODP enabled data sources as below 2LIS_03_BX (Stock Initialization for Inventory Management) 2LIS_03_BF (Goods Movements from Inventory Management) 2LIS_03_UM (Revaluations) – captures revaluation data. we are using the LSA++ Architecture. ODP DataSource –> W/Optimiz ADSO –> Standard DSO (ADSO). Please advice me how to implement the Inventory model in BW, since this is compleatly different from classic approach. I have gone through the SAP Help document, it is not updated one. Inventory Management (SAP HANA-Optimized) – Supply Chain Management (SAP HANA-Optimized) – SAP Library if any one implemented with LSA++ & ODP based extraction, please help me. @Jameel like (0) Andreas Tenholte August 11, 2016 at 8:59 am Hi Jameel, the procedure when extracting inventory data via ODP is actually pretty much the same as described in the online documentation, especially on page Perform Setup: Inventory Management (SAP ERP). Problem might be that you could not find the option ‘Initial Non-Cumulative for Non-Cumulative Values’ in the DTP for your ODP data source 2LIS_03_BX. But this is a bug and can be fixed by implementing SAP Note 2353421 ‘740SP16: Minor problems in ODP DataSources’. Hope this helps… All the best, Andreas like (0) Sebastian Gesiarz July 14, 2017 at 9:43 am Hi Andreas, Mentioned note does not solve the issue. There is still no possibility to load ‘Initial status’ and update with ‘non cumm…’ for 2LIS_03_BX without PSA after note implementation. (BW 7.4 SP 14) Kind regards, Sebastian like (0) Former Member September 21, 2016 at 6:53 pm This blog is from Nov. 2015 and by that time the standard LO extractors like 2LIS_03_BF were not released for ODP and you said on the blog that we should NOT change to ODP based extraction FOR existing extractors BUT to consider ODP for all future implementations. My question is, considering that the standard extractors like 2LIS_03_BF are NOW released for ODP: -Why would we not be able or rather, not want to replace existing classical extractor for 2LIS_03_BF with ODP based extraction if we want to use it with SLT and take advantage of real-time inventory data? Is this still a limitation even though the extractor is now released for ODP? Can we not go ahead with this approach? like (0) Mohit Agrawal September 29, 2016 at 7:01 am Hi Marc, Would you please help me understanding how ODP compression works. I thought it’s going to suppress the number of rows by adding the KF for same key elements. But I see the same number of records in RSA7 and ODQ. And it still shows that data is 90% compressed. How does it actually compress? Thanks Mohit like (0) Former Member October 10, 2016 at 9:25 am Hi Marc, as the extractors are supposed to not change their behaviour will this also apply to any extensions made particularly when existing Business exits are used? That is, all RSUP_SAPI_BAPI implementation will still be accessible? As I read the archticture (see Standard documention) the extractors as such are all processed before ODP Comes into Play. Hence, I’d assume we can still leverage investigations made. Will you kindly comment? Thanks in advance. Best regards Andreas like (0) Former Member October 13, 2016 at 12:22 pm Hi Marc, I can you help to clarify following questions 1. We are going to implement new BW4HANA where source is still ECC in RDBMS, As this is a kind of landscape transformation we also want to keep live the old BW system as a keep the lights on. The question is as our source is same ECC in RDBMS for old BW system and also going to be the new BW4 system 1. How to use the ODP Data source (BW4 hana optimizes) in old BW system where we are flowing ETL? 2. Will there be option to have 2 version of data source one HANA optimized and other old extractor ? 3. If need to use the same ODP extractor for old BW which is using the RSA7 delta Q how that going to work in BW4 which is more based on ODQ ? 4. If I do any enhancement in the extractor how that going to reflect? Thanks Samit like (0) Former Member October 20, 2016 at 8:18 pm Hello Marc, We are in BW 7.5 SP3 and using ODP as the connector for Industry text and Distribution channel text, in BW while replicating the datasource getting the below error. ———————— Error while saving DataSource 0INDUSTRY_TEXT_0001 xxxCLNT060 No fields were supplied Source system xxxCLNT060: metadata upload with errors Message no. RSDS554 —————————– Any thoughts ??? like (0) Former Member January 20, 2017 at 7:12 am Hi All, Actually, one of our Customer is implementing Microsoft BI, and for that we would like to extract data from SAP ECC. We have been exploring various ways and means for this purpose. I Just wanted to confirm, can we use ODP for this purpose (without using SAP BW) ? If yes, I would like to humbly request you to guide us with detail procedure. Thanks like (0) Former Member April 3, 2017 at 4:40 pm Hello Marc and others, Can anyone help me on below questions: 1- What is the ECC version pre-requisite for enabling SLT-ODP to transfer data to BW4HANA? I couldn’t find anything specific on ECC versions whereas everwhere it says DMIS version add-on. 2- I have to implement FI_GL_4 and UC_SALES_STATS utility extractor in BW4HANA but we have existing BW version as well where currently delta queue is through RSA7. I found the blogs where it says both extractors will have problem while sending delta to 2 diff BW systems. Can anyone throw light on this? Thanks like (0) Former Member May 18, 2017 at 11:14 pm Hello Everyone, We are facing issues with creation of Source system under ODP – SAP (extratores) ( SAPI ) , got this error message Source system ECDCLNT300 already exists. How can i create the source system or how can i replicate the DS in Source to Netweaver system ? Thanks Ram like (0) Former Member May 25, 2017 at 5:25 am Thanks Nice Detailed Article.. Can you share the methods to extract data from any of SLT / ODP / ODQ by Non-SAP environment. May be with ODBC or any other NON SAP Tool. I understand Dataservice can connect with ODP (ODQ) and read data but it there is latency.. How can we have it more real time Change Data Capture data extraction from SLT / ODP / ODQ from any tool (Non SAP) to extract data outside SAP stack.. like (0) Former Member August 4, 2017 at 5:21 pm Hi Marc, We are in BW version is 7.5 SP08 and we are converting objects to move to B4H. Looks like the DataSource must be switched to BW-ODP to switch to BWH mode – the error message says “Use transfer tool in data mart”. Could you please tell me how to consume the transfer tool? Thanks, Naresh like (0) Sachin Patil December 19, 2017 at 6:01 am Hello, We have an ETL tool which uses the RFC NetWeaver SDK 7.21 for data extraction from SAP System. However we need to support the SAP BW Standard Extractors ( SAP ODP Extractors ) for data extraction from our Application. We would like to use RFC function modules from SAP ODP API’s 2.0. Below are the function modules which can be used for data extraction from ODP Extractors. RODPS_REPL_ODP_GET_SUBSCR RODPS_REPL_ODP_GET_DETAIL RODPS_REPL_ODP_READ_DIRECT_XML RODPS_REPL_ODP_OPEN RODPS_REPL_ODP_FETCH RODPS_REPL_ODP_CLOSE We might need to use some more functions as well. From the SAP Note 1931427 – ODP Data Replication API 2.0. Those RFC function modules can be used for RFC Client applications. However from one of the SAP ODP FAQ documents says that SAP ODP API’s is restricted to SAP Applications and not used by 3rd party party ETL Tools. Can we use those RFC Function modules for RFC Client application ( ETL Tool) ? If this is not way the correct way then which approach we should use for data extraction from SAP ODP Extractors ? Thank you in advance. Regards, Sachin like (0) Leave a Reply Cancel replyYou must be logged in to post a comment.