17.11 Enterprise BW Modernization Architecture

1. Reference architecture

                    SAP SOURCES
                         |
             +-----------+-----------+
             |                       |
        Native SAP              Existing BW
       integration               landscape
             |                       |
             v                       v
      Datasphere native         BW/4HANA
             |                       |
             |                  migration /
             |                  coexistence
             |                       |
             +-----------+-----------+
                         |
                     BW bridge
                         |
                         v
                   Datasphere
                         |
             +-----------+-----------+
             |                       |
       Enterprise semantics     Data products
             |                       |
             +-----------+-----------+
                         |
                  SAC / consumers

2. Platform decision matrix

Situation	Starting decision
Existing BW investment is critical	Preserve and modernize selectively
BW-style extraction is essential in cloud	Evaluate BW bridge
New cloud-native use case	Evaluate native Datasphere first
Existing BW query has many consumers	Prefer controlled reuse/migration
Historical layer adds no value	Simplify
Regulatory workload	Prioritize controlled parallel run

3. Avoid the "lift everything" strategy

A migration that copies every object into BW bridge and then copies everything into Datasphere may reproduce technical debt.

Modernization should classify:

• preserve,
• migrate,
• redesign,
• consolidate,
• retire.

4. Data product boundary

Datasphere should expose governed enterprise data products rather than simply expose every migrated BW object.

A migrated object is an implementation asset.

A data product is a consumer-oriented contract.

5. Operating model

A mature organization separates:

Platform team

• tenant,
• connectivity,
• runtime,
• security foundation.

Data engineering team

• acquisition,
• transformations,
• orchestration,
• monitoring.

Domain team

• semantics,
• quality,
• business rules,
• data products.

Governance team

• policies,
• classification,
• ownership,
• standards.

6. Architecture decision record

Every major migration decision should capture:

• current state,
• target state,
• capability retained,
• capability redesigned,
• migration method,
• risk,
• cost,
• performance,
• rollback,
• retirement date.

7. Capstone

Design modernization for:

• 3 BW/4HANA systems,
• 6 S/4HANA systems,
• 20 domains,
• 10,000 consumers,
• global finance reporting,
• near-real-time operations,
• historical analytics.

Your answer must explicitly state:

• what remains BW/4HANA,
• what enters BW bridge,
• what becomes native Datasphere,
• how data products are exposed,
• how migration waves work,
• how coexistence ends.