Skip to main content

16.5 CDS Extraction

1. Objective​

The goal is to move from:

"I found a CDS view"

to:

"I have a supported, extraction-ready business interface."

2. End-to-end pattern​

S/4HANA CDS
     |
     | extraction-enabled
     v
SAP Datasphere connection
     |
     v
Remote source object
     |
     +--> federation
     |
     +--> replication flow
              |
              v
        local persistence

3. Implementation sequence​

  1. Identify the business object.
  2. Find the appropriate CDS view.
  3. Verify supported release status.
  4. Verify extraction capability.
  5. Validate grain and keys.
  6. Validate required delta behavior.
  7. Configure the Datasphere connection.
  8. Discover the source object.
  9. Create the required Datasphere object or replication flow.
  10. Perform an initial load.
  11. Validate row counts and business totals.
  12. Validate delta behavior.
  13. Document ownership and support.

4. Do not skip grain validation​

Suppose the business expects one row per sales order item.

If the CDS view produces multiple rows because of:

  • partner functions,
  • pricing elements,
  • schedule lines,
  • text joins,

then a successful technical load can still be logically wrong.

Always document:

Expected grain:
one row per ...

Actual source grain:
one row per ...

Transformation:
...

5. Initial-load validation​

Validate at least:

  • record count,
  • key uniqueness,
  • null keys,
  • business totals,
  • date ranges,
  • currency/unit semantics,
  • representative samples.

6. Delta validation​

Create controlled source changes:

  • insert,
  • update,
  • delete if supported.

Verify that the target receives the expected changes.

Do not validate delta using only an application screen. Reconcile source and target using deterministic checks.

7. Extraction anti-pattern​

Do not build an enterprise pipeline around an undocumented internal CDS view simply because it works today.

Prefer supported, stable, extraction-enabled interfaces.

Architect exercise​

Create a CDS extraction design for billing documents.

Include:

  • source CDS,
  • extraction mode,
  • grain,
  • initial load,
  • delta validation,
  • target,
  • monitoring,
  • reconciliation.