An ODP (Operational Data Provisioning)-enabled data source is a data extraction mechanism that uses the ODP framework to allow the transfer of data between systems. It leverages the ODP infrastructure to manage the data extraction process efficiently, ensuring that data is consistently and reliably transferred from the source system to the target system.
To consume S4HANA data to SAP Datasphere via ODP, we need a datasource that is ODP enabled, either we can use some standard datasources like (e.g. 2LIS_11_VAHDR - Sales Document Header Data, 2LIS_11_VAITM - Sales Document Item Data) or we can also create a custom datasource either by using a view or table or some custom CDS view.
In order to view the datasources, enter the RSA6 t-code, a hierarchical structure will come.
Over there go through the appropriate modules to find any required standard datasources available and check whether the appropriate datasource is ODP enabled or not (if it is mentioned as a green tick ✅, it is an ODP enabled datasource, if it is represented as a red cross mark ❌, it is not an ODP enabled datasource)
To find the no. of data records and the data in ALV grid or List in the appropriate datasource click on datasource and press execute icon
then in the Extractor checker page click on Start Extraction.
A popup will appear representing the no. of records and then below the screen there will be two options to view the data (ALV Grid, List)
If you want to find the source of the standard datasource, just go to the RSA2 tcode, In the database repository screen, enter the datasource and click on display to view the details and sources of the appropriate datasources.
Now if the required datasource is not ODP enabled, you can enable it by going to the tcode SE38 and Enter RODPS_OS_EXPOSE and then just execute. After Executing, Enter the appropriate datasource which is to be ODP enabled in the Release datasource page. Once you enter the datasource and release the datasource, the datasource becomes ODP enabled and it can be now consumed in SAP datasphere. We can check the release status in the Display Releases section.
Now let's Extract this data to datasphere. Log on to Datasphere and then make sure the tenant is connected to the appropriate S4 system.
Go to the databuilder section and click on “Import Remote tables”
then click on the appropriate connection in the popup
In the next step click on extractors and click on SAPI and then under that choose the appropriate datasource.
In the next step review the datasource and click on import and deploy. Now the remote table is imported into the datasphere.
No comments:
Post a Comment