This blog is a continuation of my previous blog on SAP Operational Data Provisioning and why its SAP’s version of an Enterprise Data Hub.
When converting extractors to ODP some common questions regarding the same are:
- Will my existing extractors be disturbed?
- Can I have my existing extractors through RSA7 and have them active in ODP to support parallel extraction to the current BW System and a
greenfield BW4/HANA system?
- Do I have to reinitialize my existing extractors with my current BW system?
Every ECC system is a mix of Standard and generic extractors and it would not be of much utility if only SAP Extractors are available for ODP extraction. SAP however provides for a way to expose existing generic extractors to ODP and this is not done by default but instead must be done selectively for each extractor.
In this document, we will look at how to make any extractor ODP enabled. SAP has not made the ODP API available to all the extractors. The list of SAP extractors available for ODP extraction can be found in the note here.
To illustrate this, let us take a delta enabled generic extractor as an example in ECC, ZBC_TRAVEL_SFLIGHT that is currently being used in the traditional BW system. Note that this extractor is not yet ODP as it is indicated by the icon in the far left . Alternatively, you can also check if the if the extractor is ODP enabled by checking if entry is present for the extractor in the table ROOSATTR.
To use this same extractor in our new BW/4HANA system, this needs to be converted to an ODP enabled extractor. This can be done using the program RODPS_OS_EXPOSE. After executing the program, give the extractor name and click on Release Datasource(s). You can also roll back an extractor release by clicking on Delete Release.
You can now see that the extractor is released for use by the ODP and is ready to be consumed in the BW/4HANA system. It is now indicated by the icon at the far left of the extractor. You can now see that an entry will be added for this extractor in the ROOSATTR table.
After replication and initialization of the delta, you can monitor this ODP based delta extraction in the T-code ODQMON in ECC source system. This ODP based extraction is basically a subscription-based service and the same extractor can be used as a source for multiple targets.
When you expose / whitelist an extractor for ODP – it does not disturb your existing RSA7 deltas and a new Delta queue is created for the ODP enabled version of the extractor. The ODP queue can be viewed using TCode ODQMON in the ECC system. Since ODP is subscription based – you can also have different delta pointers based on the service that is extracting – essentially you can have separate queues for BW4/HANA and also OData if you are using an ODATA interface.