(Glue-2408) (Deprecated) ODP Fetchers

Owned by SNP
Aug 20, 2024
2 min read

According to the SAP Note 3255746, SAP prohibits the use of ODP API for 3rd party applications.  Therefore. SNP Glue will not support the ODP API anymore.

Please note that SNP Glue does not rely solely on the ODP framework and provides various ways to access SAP data and CDC using the SAP-certified functionality.

The SNP Glue technology is independent of any third-party APIs and is self-contained, making it resilient to future third-party changes.

ODP Fetchers use an ODP queue as their data source. For data reading they provide multiple Extraction Modes. They also support the filtering of selected data.

Prerequisites

  • You can use ODP Fetchers only if the Operational Data Provisioning (ODP) Framework is installed on the SAP system. This became available from NetWeaver 7.30 (in the context of BW: NetWeaver 7.40). (SAP Note).
  • Ensure that the additional SNP Glue transport with ODP Fetcher based on the ODP framework is installed on the system.
  • ODP source data extraction can be verified by running a report RODPS_REPL_TEST in SE38, entering the object name + respective data category, and executing a test data extract display.

Creating ODP Fetchers

Perform the steps provided under Creating Fetcher Object and select ODP Fetcher from the Component implementation drop-down menu in step 7.

Activating ODP Fetchers

After creation, the object is in the saved state.

The following information is mandatory before the activation:

  • ODP Queue
    • Name of the ODP queue for the data read.
    • F4 help is available, filtered using context.
    • Double clicking the ODP queue opens the monitor delta queues function (transaction ODQMON) with the respective queue and subscriber.
  • ODP Context
    • Name of the ODP Context - also known as a Provider the monitor delta queues function (transaction ODQMON).
    • Default value: SAPI (DataSources/Extractors).
  • Subscriber name
    • Name of the ODQ subscriber.
    • Default value: SNP GLUE.
  • Subscriber process
    • Name of the subscriber process.
    • Default value: SNP_PROCESS.
  • Execution mode
    • Mode of the execution. Can also be changed in the extraction process execution screen. For ODP replication the Serial Extraction using ODQ (for all Extraction modes) and Direct Extraction without ODQ (for Full Load Extraction Mode) are supported.

the following information is optional before the activation:

  • Selection
    • Checkbox for each field of the ODP queue that allows you to mark the field as relevant for selection before the extraction.

Extraction Modes

ODP Fetchers provide multiple extraction (replication) modes: 

  • Full Load
  • Delta Load
  • Delta Init
  • Recovery of Previous Deltas


Keep in mind that delta function is handled by ODP Queue, not by SNP Glue does not store any delta pointers, but can reset the delta for a given ODP queue (e.g. when running delta Initialization with or without a data transfer).  

Hierarchy data sources is not supported using ODP fetcher but for now there is ABAP fetcher that can be used in this case. 

Full Load 

All data from the source is extracted and transferred to the target. 

Delta Load

Data from the source is read according to the delta value. If no subscriber with a provided subscription is connected to the source ODP (transaction ODQMON), the extraction process perform a Full Load and Delta Init.

Delta Init

Only the delta value will be initialized. No data is transferred.

Recovery of Previous Deltas

This mode is useful when the last delta extraction failed and must be repeated.

Every time the Delta Load is executed, a check is verifying whether the last delta run finished successfully. If not, the delta mode is automatically switched to Recovery of Previous Deltas. This prevents potential data loss due to ODQ delta logic.