DSP01: Introduction to SAP Datasphere — Lesson 3: Business Builder, Semantic Models, Analytic Models, and Consumption

Learning Objectives

• Explain how Business Builder, Semantic Models, Analytic Models, and Consumption supports governed SAP Datasphere analytics.
• Complete the workflow and produce a reviewable semantic model and consumption register.
• Evaluate the condition where a business measure is aggregated differently across two consuming reports and select a supported response.

Detailed Topics

• Business Builder: business purpose, responsible roles, and SAP objects that establish the operating scope.
• semantic entities: configuration choices, master-data dependencies, and determination logic shaping the result.
• analytic models: transaction flow, status behavior, integration effects, and reviewable operational evidence.
• consumption interfaces: control points, exception paths, testing needs, and release criteria protecting the outcome.

Instructor Demonstration

The guided walkthrough connects Business Builder, semantic entities, analytic models, consumption interfaces to the intended business outcome and control evidence. Learners see the expected SAP behavior, what belongs in semantic model and consumption register, and how to respond when a business measure is aggregated differently across two consuming reports.

Hands-On Exercise

Complete a controlled activity covering Business Builder, semantic entities, analytic models, consumption interfaces and preserve the result in semantic model and consumption register.

1. Define the expected business outcome and the SAP objects that should produce it.
2. Perform the lesson scenario, retaining before-and-after evidence for every material decision.
3. Test the exception without altering unrelated settings or data, then explain the first failure point.
4. Apply proportionate remediation and complete a focused regression check before approval.

Scenario Analysis

• Which SAP object, rule, record, or process step most strongly influences Business Builder, Semantic Models, Analytic Models, and Consumption?
• What evidence separates configuration, data, authorization, integration, and timing causes in this scenario?
• How should the semantic model and consumption register be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected behavior differs from the observed result. Review process sequence, relevant data, configuration, authorization, integration, and timing as separate hypotheses. Treat “a business measure is aggregated differently across two consuming reports” as unconfirmed until settings, documents, logs, reports, and focused retesting support the cause.

Validation Checklist

• Required roles, structures, data, settings, and dependencies for Business Builder, Semantic Models, Analytic Models, and Consumption are present.
• The semantic model and consumption register links each conclusion to objective and reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, monitoring, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Business Builder, Semantic Models, Analytic Models, and Consumption, explain the resulting SAP behavior, and defend the outcome through semantic model and consumption register.