Softenant guide / SAP BW/BI
This guide focuses on the modelling choices that turn operational data into a trusted analytical structure.
What this topic solves
SAP BW modeling connects business measures and characteristics at a defined level of detail so report totals can be interpreted correctly.
Core objects and terminology
The central building blocks for this area are InfoObjects, ADSOs, CompositeProviders, key figures, characteristics, keys and semantic layers.
- InfoObjects
- ADSOs
- CompositeProviders
- key figures
- characteristics
- keys and semantic layers
How the process works
Source data is staged, harmonised in persistent objects, combined for reporting and exposed with a business-friendly model.
Scenario to practise
A report joins data successfully but totals are duplicated because the model grain is unclear.
Integration and business impact
BW models integrate source data from finance, sales, procurement and other business systems.
Worked example: a valid join produces the wrong total
Take a fictional sales item with an amount of one hundred and a product identifier. If that product matches two rows in a lookup, the joined result can contain two copies of the sales amount. Summing those rows gives two hundred even though the original sale was one hundred. A technically successful join therefore does not prove that a reporting model is correct.
Start by writing the grain: what does one row represent in each source? For example, a sales-item row differs from a product-language text row or a product-validity interval. List the intended key fields and check whether the lookup is unique for the business context. Language, validity dates and multiple source systems are possible reasons that a product identifier alone is insufficient.
Compare record counts and measure totals before and after the join. Inspect duplicate keys rather than hiding the discrepancy with a distinct operation or an arbitrary aggregation. Record which relationship is intended and why the selected key supports it. Tool and object options depend on the BW release, so confirm the environment before reproducing an example. Continue with the data-extraction and transformation guide to trace where the records originated. SAP’s BW/4HANA data-flow overview provides the wider model context.
Hands-on learning plan
Design a tiny sales model, define its grain, select its key fields and explain where aggregation becomes safe.
Related SAP BW/BI guides
Use these supporting articles to build a connected learning path:
- SAP BW Data Extraction: DataSources, Transformations and DTPs
- SAP BW/4HANA vs SAP BW on HANA: Architecture and Feature Comparison
- SAP BW Reporting: Queries, Variables and Analysis for Microsoft Office
- SAP BW Process Chains: Scheduling, Monitoring and Error Resolution
Build practical SAP capability
For guided exercises, process-based learning and interview preparation, explore SAP BW/BI Training in Vizag.