Skip to main content

19.12 Enterprise BDC Architecture

1. Target state​

 SAP APPLICATIONS       NON-SAP / CLOUD
        |                      |
        +----------+-----------+
                   |
          Business Data Cloud
                   |
      +------------+-------------+
      |                          |
 SAP Datasphere              BW / BW Bridge
      |                          |
 semantics + products       modernization path
      |
 +----+-----------------------------+
 |                                  |
Analytics / SAC              BDC Connect
 |                                  |
AI / applications        external platforms

2. Domain architecture​

Use domain ownership for:

  • customer,
  • finance,
  • procurement,
  • supply chain,
  • workforce.

Use shared enterprise semantics only where common definitions are truly required.

3. Data product architecture​

Every strategic domain should expose a small number of high-value products rather than hundreds of uncontrolled tables.

4. Platform operating model​

Establish:

  • architecture board,
  • data product council,
  • security governance,
  • platform engineering,
  • operations,
  • FinOps,
  • domain stewardship.

5. Migration architecture​

Run the old and new worlds in parallel where business risk requires it.

Measure:

  • reconciliation,
  • performance,
  • freshness,
  • consumer acceptance,
  • operating cost.

6. Enterprise architect exercise​

Design BDC for:

  • S/4HANA,
  • BW/4HANA,
  • HANA Cloud,
  • Datasphere,
  • SAC,
  • SAP Databricks,
  • Redshift,
  • S3,
  • SaaS systems.

Document every boundary and every data-copy decision.