Skip to main content

16.3 ODP & ODQ

1. What ODP solves​

Operational Data Provisioning provides infrastructure for extraction and replication from SAP and ABAP-based applications.

SAP documentation describes ODP providers such as:

  • service API DataSources,
  • ABAP CDS views,
  • SLT,
  • SAP BW and BW/4HANA.

For delta procedures, source changes can be handled through the Operational Delta Queue, commonly abbreviated ODQ.

2. Mental model​

ABAP source
   |
   +--> extractor / CDS / supported provider
   |
   v
ODP infrastructure
   |
   v
Operational Delta Queue
   |
   +--> subscriber / consumer
   |
   v
Target processing

The exact runtime path depends on source type and integration technology.

3. Initial versus delta​

Initial load​

Establishes the target baseline.

Delta​

Transfers changes after the baseline.

Architecturally:

Initial:
Source state ---------> Target baseline

Delta:
Source changes -------> Delta mechanism -------> Target changes

4. Why delta is harder​

A delta design must answer:

  • what identifies a change,
  • how deletions are represented,
  • how ordering is preserved,
  • how failures are recovered,
  • how subscriptions are maintained,
  • how reinitialization works,
  • how duplicates are handled.

Never say "it supports delta" without understanding those semantics.

5. ODP versus ODQ​

ODP is the provisioning framework.

ODQ is the operational delta queue mechanism used in relevant ODP scenarios.

Do not use the terms interchangeably.

6. Subscriber thinking​

Delta mechanisms are not simply files sitting in a folder.

A consumer subscribes to a source-provisioning contract and consumes packages according to the supported protocol.

This is why lifecycle and recovery matter.

7. Delta failure scenario​

Suppose a target load fails after some packages were processed.

A robust design determines:

  1. what was committed,
  2. what remains available,
  3. whether the next run can resume,
  4. whether a reinitialization is required,
  5. how reconciliation proves completeness.

Architect exercise​

Draw the lifecycle of an ODP-based initial plus delta load from S/4HANA to Datasphere.

Include:

  • source,
  • provider,
  • delta queue,
  • subscriber,
  • target,
  • restart,
  • reconciliation.