DBW362 – SAP BW Powered by SAP HANA – Delta from SAP BW Any DB (Classic) — Lesson 2: HANA-Optimized InfoProviders, DataStore Objects, InfoCubes, CompositeProviders, and Conversion

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing HANA-optimized BW object conversion.
• Perform and validate InfoProviders, conversion, and dependency controls using reviewable system evidence.
• Evaluate the condition where reports complete but figures differ after migration because object conversion, data-load semantics, query execution, and reconciliation scope are inconsistent and select proportionate corrective action.

Detailed Topics

• HANA-Optimized InfoProviders applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• DataStore Objects applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• InfoCubes applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• CompositeProviders applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Conversion applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a BW team moving a classic warehouse to HANA while protecting data lineage, reporting continuity, and operational schedules. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the DBW362 migration readiness, conversion, and performance workbook. It also tests the exception where reports complete but figures differ after migration because object conversion, data-load semantics, query execution, and reconciliation scope are inconsistent.

Hands-On Exercise

Complete a controlled SAP exercise covering HANA-Optimized InfoProviders, DataStore Objects, InfoCubes, CompositeProviders, and Conversion and preserve the verified result in the DBW362 migration readiness, conversion, and performance workbook.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences HANA-optimized BW object conversion.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the DBW362 migration readiness, conversion, and performance workbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “reports complete but figures differ after migration because object conversion, data-load semantics, query execution, and reconciliation scope are inconsistent” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The DBW362 migration readiness, conversion, and performance workbook connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply HANA-Optimized InfoProviders, DataStore Objects, InfoCubes, CompositeProviders, and Conversion, explain the resulting SAP behavior, and defend the outcome through the DBW362 migration readiness, conversion, and performance workbook.