Skip to main content

Assessment & Discovery

1. Build the estate inventory​

Capture at least:

  • source systems and owners
  • BW systems, InfoProviders, queries, process chains
  • Datasphere spaces and objects
  • connections and integration methods
  • data volumes and growth
  • load frequency and latency
  • business-critical reports
  • security and data-access rules
  • SLAs and batch windows
  • dependencies and consumers
  • custom code and unsupported patterns
  • retention and archival requirements

2. Score migration candidates​

A useful scoring model is:

Priority = Business Value × Migration Readiness × Risk Reduction

Then separately score complexity, data volume, semantic complexity, dependency count, and operational criticality.

High-value, low-dependency workloads make good pilots. Mission-critical, highly coupled workloads usually belong in later waves.

3. Dependency graph​

Do not assess an object in isolation. Trace:

Source → acquisition → persistence → transformation → semantic model → analytical model → consumer

A report that looks simple may depend on dozens of upstream objects.

4. Readiness gates​

Before migration, require:

  • source ownership confirmed
  • target pattern selected
  • supported conversion path verified
  • security model mapped
  • reconciliation rules defined
  • rollback decision documented
  • operational owner assigned

SAP provides a Readiness Check for SAP Datasphere, SAP BW bridge to assess important implications when converting SAP BW 7.x or SAP BW/4HANA estates.

5. Deliverable​

The assessment should end with a heat map, dependency graph, candidate waves, risks, and a target-state decision—not merely an inventory spreadsheet.