ODP/ODQ Extraction in SAP BW

Introduction to ODP/ODQ Extraction in SAP BW

ODP (Operational Data Provisioning) is a data extraction framework introduced by SAP with the
release of SAP BW 7.3, and it is an enhanced and flexible data extraction mechanism that
allows data to be extracted from various SAP and non-SAP data sources into SAP BW.

ODP extraction in SAP BW provides a flexible and efficient mechanism for extracting data from
a wide range of data sources, which can help organizations to improve their data integration and
analysis capabilities.

ODP extraction is performed using a set of ODP extractors, which are designed to extract data
from specific data sources.
Overview of ODP/ODQ Extraction- Schematic
ODP/ODQ Extraction-Advantages

If you use ODP, you can load

The following are the
advantages of ODP Framework
for BW Extractors as
recommended by SAP
the data directly into the BW
InfoProviders, bypassing the
Persistent Staging Area
(PSA)layer by using a Data
Transfer Processes(DTP)
The ODP infrastructure (with
delta queues) takes over
important services such as
monitoring data requests.

The data is stored in a

• The data changes to a queue
compressed state in the delta The data is retained in the delta
can also be requested by more
queue. A delta request transfers queue for a specified time
than one subscriber (target
data records from the queue to period for recovery purposes.
system)
the subscriber (target system).
 ODP/ODQ Extraction-Scope of Work
The list of identified Datasources are consisting of different categories of extractors which are actively
loaded and used in the ECC production system.

• Business Content Datasources (Example: 0EC_PCA_3 - Profit Center: Actual Line Items)
• Business Content Datasources for Logistics Extraction- (2LIS_18_I3HDR- Service Orders)
• Generic Datasources (Example: ZLSD_DS_TRDT_LCLTXTAMT- Local Tax Calculation)
• Generated Datasources (Example: 3FI_GL_T1_SI - EVO Tax Ledger Line Items)

Identify the extractors are in scope in the ODP/ODQ Extraction

 ODP/ODQ Extraction- List of Identified Extractors
S. No App.Comp Data Source Data Source Name
1 FI-GL 3FI_GL_Z1_SI EVO Local Ledger SI - Line items
2 FI-GL 3FI_GL_Z1_TT EVO Local Ledger
3 FI-GL 3FI_GL_T1_TT EVO Tax Ledger
4 FI-GL 3FI_GL_T1_SI EVO Tax Ledger Line Items
5 CO-PA 1_CO_PA_CZ00 COPA OP CONCERN CZ00
6 CO-PA 1_CO_PA_DE02 COPA OP CONCERN DE02
7 CO-PA 1_CO_PA_LU07 COPA OP CONCERN LU07
8 EC-PCA 0EC_PCA_3 Profit Center: Actual Line Items
9 0REFX 0REFX_1 RE: Conditions (Flow Data)
10 0REFX 0REFX_13 Differing Measurements (Contract)
11 PM 2LIS_17_I3OPER Plant Maintenance Order Process
12 PM 0PM_OM_OPA_2 Maintenance Orders: Actual Costs by Means of Delta Extract.
13 0CS 2LIS_18_I3HDR Service Orders
14 0CS 2LIS_18_I3OPER Service order operation
15 0CS 2LIS_18_I0NOTIF Service Notifications
ZLSD_DS_TRDT_LCLTXTA
16 MM Local Tax Calculation
MT
ZFAP_DS_TRDT_CHNGDO
17 FI Change log Document Datasource
C01
18 FI ZFFI_INV_PAYMENT_DT Invoice Payment dates
ZFFI_DS_TRDT_FI_VCUPA
19 FI-AP BW vendorcust park doc
RKED01
ZFFI_DS_TRDT_FI_VENPA
20 FI-AP Vendor Parked Doc.
RKED01
 ODP ENABLEMENT – Business Content Datasources

For Business Content Datasources (Example: 0EC_PCA_3 - Profit Center: Actual Line Items):

• Check in ROOSATTR table in ECC system if SAP has enabled ODP mechanism for the Business
Content Extractor.
• SAP provided the list of standard extractors which are enabled for ODP/ODQ extraction in the SAP
note 2232584
 ODP ENABLEMENT For Generic Extractors

For Generic Datasources (Example: ZLSD_DS_TRDT_LCLTXTAMT- Local Tax Calculation)

• Use the program in the transaction code SE38 in ECC - RODPS_OS_EXPOSE to enable the generic
extractors for ODP/ODQ extraction

• Once executed this program for a Datasource, an entry is created in ROOSATTR table for the
Datasource
 ODP ENABLEMENT For Custom Generated Extractors
For Custom Generated Datasources (Example: 3FI_GL_T1_SI - EVO Tax Ledger Line Items)

• Use the program in the transaction code SE38 BS_ANLY_DS_RELEASE_ODP to enable the generated
extractors for ODP/ODQ extraction
• Once executed this program for a Datasource, an entry is created in ROOSATTR table for the
Datasource
 ODP Extraction- BW Activities
Steps to be performed in BW system for ODP/ODQ Extraction:

• Creation of new ODP source system and maintaining the logical system in BW system(Basis Team Activity)
• Replicate the ODP Enabled Datasources to the newly created ODP Source system.
• Create a new transformation for ODP Datasource to the first level data target copying from the existing S-
API extractor
• Create a new DTP to load the data from ODP Datasource to the first level data target.
• The ODP DTP can extract the data directly into the Data target without using a PSA as staging. This option is
enabled for all the Extractors in the scope - Directly from source system, PSA not used
• Execute the old InfoPackages to empty the Delta queues from RSA7 from old S-API extractor.
• Execute the old DTP to load the first level data targets.
• Now, Execute the ODP DTP with - No Data Transfer; Delta status in Source: Fetched. This is to ensure that
the new delta records are extracted from ODP Extractor and can be Checked in ODQMON transaction in
ECC system.
• Check the data in the first level data target to ensure the new delta records are coming from ODP/ODQ
extractor
• Changes are to be made in the process chains to incorporate the ODP DTPs for the regular data loads.
 ODP Extraction- Create ODP Source system in BW
• Creation of new ODP source system and maintaining the logical system in BW system in RSA1(Basis Team
Activity)
 ODP Extraction- Replication of ODP Datasources

• Replication Of ODP Enabled Datasources on to ODP Source System

 ODP Extraction- BW Dataflow

• Create a new transformation for ODP Datasource to the first level data target copying from the existing
Dataflow
 ODP Extraction- BW Dataflow
Creation of ODP DTP to load the Data target from ODP Source system with the setting for data extraction as
-Directly from source system , PSA not used

•If you use ODP, you can load the data

directly into the BW InfoProviders,
bypassing the Persistent Staging Area
(PSA)layer by using a Data Transfer
Processes(DTP)
 ODP Extraction- ODQMON SETTINGS
• Once the ODP DTP is executed the Extractor entry is created in the ODQMON – QUEUES Tab
 ODP Extraction- ODQMON SETTINGS
• Once the ODP DTP is executed the Extractor entry is created in the ODQMON – Subscriptions Tab
 ODP Extraction- ODQMON SETTINGS

• Once the ODP DTP is executed the Extractor entry is created in the ODQMON – Requests Tab
 ODP Extraction- ODQMON SETTINGS

• Once the ODP DTP is executed the Extractor entry is created in the ODQMON- Units Tab
 ODP Extraction- ECC JoB Details
• In ECC system SM37 ODP Job can be identified with the search string ODQR*
 ODP Extraction- ECC JoB Details
• In ECC system SM37 ODP Job can be identified with the search string ODQR*
 ODP Extraction- Tables Involved for DATA Requests
In ECC the following are the technical tables involved

Extraction Mode Type of Load Table Involved

Extraction mode ‘C' Initialization ODQDATA_C
Extraction mode ‘F' Full ODQDATA_F
Extraction mode 'D' Delta ODQDATA
 ODP Extraction- Data LOAD to BW System
Data request loaded successfully to the BW Target
 ODP Extraction- Error handling in BW system

The following are the recommendations from SAP for Error handling in BW system for ODP
extraction
1. It is not possible to change records in ODQMON. So, in this case, extractor must send correct
records.
2. Alternatively, you can check the option of writing error records to error stack. If they can edit
the error stack and load to data target
3. In BW4HANA there is an option called DTIS (Data Transfer Intermediate Storage) where you can
change records like in PSA. But this option is only available there.
4. In BW-releases 7.40 and 7.50 DTIS is not available and will also not be down ported.
5. In connection with ODP only the option to correct the records via routines, either in source
system exits or the transformation routines on BW-side. There are no advanced options at
Datasource level for Error handling.
 ODP Extraction- Reorganization delta queues
• In ODQMON transaction of ECC system, retention period and data relevance settings can be configured
for the ODQ Data requests.
• Because of these configuration settings for recovery, the delta data can be retrieved any number of
times within this recovery period. Once recovery period is elapsed, there is no way to retrieve the delta
request from ODQMON (The default setting is 24 hours)
• There is no limit for this time period and can be increased according to the Business justification.
• For data with low relevance and with average relevance: Once this period has elapsed, the periodic
reorganization process deletes all data in the queue that has not yet been declared as retrieved
 ODP Extraction- BW Activities
The job ODQ_CLEANUP_CLIENT_100 is scheduled background by default in ECC system at 01:23:45 system
time and deletes the data according to the above parameters.
 ODP Extraction- Lessons learnt

1: Extractor with a Full Load

Data source Name: ZLSD_DS_TRDT_LCLTXTAMT
Extraction Issue faced: Full load was having filters on Company code in the existing Info packages(XXXX-YYYY). If the
ODP DTP was executed with the same filters, then there is a time out error in BW system.
Solution:
SAP recommended to maintain an entry in the table RSADMIN by running the program SAP_RSADMIN_MAINTAIN in
ECC system. Maintained the entry as RODPS_FETCH_TIMEOUT as value 30000 seconds.
 ODP Extraction- Lessons learnt
2: Job cancelled in Source System (Delta failures)

Data source Name: 3FI_GL_Z1_TT

Extraction issue faced: There is a job cancellation for BW extraction during DTP Execution in ECC system. The
cancellation of the ECC job may be due to system issues or manual intervention.
After the job cancellation when the delta DTP job is triggered again in BW system the delta load is always failing
without triggering the ECC job.
Solution:
In the ECC system transaction ODQMON select the failed request and choose the option in the toolbar - check and
correct current requests (Ctrl + F8)

After this step, delete the red request in the BW data target and execute the ODP DTP. This creates an ECC job
fetching Zero records. We need to run the DTP again to fetch the delta records to the BW system.
Executing the DTP twice to fetch the delta records is a cumbersome process in the daily process chain.
So, to avoid this execution of the DTP 2 times the following method is used in ODQMON of ECC system.

Click on the option Read Request Again (F6) in EDIT Menu bar
Delete the red request in the data target and execute the DTP once which fetches the Delta records in one GO.
 Reference & Disclaimer
➢ This study and documentation from https://help.sap.com/docs/ and my personal learning in projects .
➢ This is just a reference and pure learning document, and every project requirements and implementation can
differ.
Thank you !!

Happy learning

Srinivas GOLLAPATI