Skip to main content

17.3 BW Modeling Concepts

1. Core BW concepts​

BW bridge retains important BW modeling concepts.

Common objects include:

  • InfoObjects,
  • DataStore Objects,
  • CompositeProviders,
  • DataSources,
  • transformations,
  • Data Transfer Processes,
  • process chains,
  • queries and related metadata.

The exact supported object set depends on the BW bridge release.

2. Data flow​

Source
  |
DataSource
  |
Transformation
  |
DTP
  |
ADSO / target
  |
CompositeProvider
  |
Query / consumer

The data flow describes both design-time relationships and runtime processing.

3. Persistent versus transient modeling​

BW documentation distinguishes persistent objects from transient data-flow representations.

A persistent object exists in the repository and can participate in multiple data flows.

A transient representation helps visualize or design relationships without necessarily becoming a persistent runtime object.

4. Why this matters to architects​

The distinction helps separate:

  • logical architecture,
  • physical implementation,
  • runtime processing,
  • reusable metadata.

5. BW bridge and LSA++​

For learners coming from BW/4HANA, LSA++ remains useful as an architectural reasoning framework.

But do not force every Datasphere design into a historical BW layer pattern.

Ask whether a layer provides:

  • reuse,
  • governance,
  • performance isolation,
  • semantic stability,
  • operational value.

If not, the layer may be unnecessary.

Exercise​

Take an existing LSA++ flow:

Source → ADSO → CompositeProvider → Query.

Explain which capabilities are needed in the modern target and whether each layer should be preserved, replaced or removed.