HA250 – Database Migration Using DMO – SAP HANA 2.0 SPS07 — Lesson 2: SUM Preparation, Target HANA, and Preprocessing

Learning Objectives

• Explain how SUM Preparation, Target HANA, and Preprocessing supports controlled DMO migration.
• Complete the workflow and produce a reviewable SUM preprocessing evidence pack.
• Evaluate the condition where a preprocessing check passes while a required target database parameter remains unsuitable and select a supported response.

Detailed Topics

• SUM extraction and configuration: settings, dependencies, and derivation rules that control the selected process behavior.
• Target database connectivity: integration touchpoints and downstream effects that must remain aligned with business intent.
• Prechecks and simplification findings: authorization, governance, and change controls required to protect the configuration outcome.
• Shadow system preparation: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

The instructor models an end-to-end decision path covering SUM extraction and configuration, Target database connectivity, Prechecks and simplification findings, Shadow system preparation. Navigation, documents, configuration influences, authorization boundaries, and retained evidence are connected to SUM preprocessing evidence pack, including a controlled test where a preprocessing check passes while a required target database parameter remains unsuitable.

Hands-On Exercise

Complete a controlled activity covering SUM extraction and configuration, Target database connectivity, Prechecks and simplification findings, Shadow system preparation and preserve the final result in SUM preprocessing evidence pack.

1. Confirm the business objective, organizational scope, required roles, source data, and expected SAP result.
2. Execute the workflow in sequence while recording settings, transactions, documents, messages, and observations.
3. Introduce the stated exception and isolate the earliest point where observed behavior differs from expectation.
4. Correct or contain the issue, retest the outcome, and document ownership, evidence, and follow-up.

Scenario Analysis

• Which SAP object, rule, master record, or process step most strongly influences the observed result?
• What evidence distinguishes a configuration problem from data, authorization, integration, or timing causes?
• How should the SUM preprocessing evidence pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected SAP behavior differs from the observed result. Review process sequence, master data, organizational assignments, configuration, authorization, integration, and timing separately. Treat “a preprocessing check passes while a required target database parameter remains unsuitable” as a testable hypothesis until settings, documents, logs, reports, and retest outcomes confirm the cause.

Validation Checklist

• Required structures, master data, roles, settings, and dependencies for SUM Preparation, Target HANA, and Preprocessing are present.
• The SUM preprocessing evidence pack connects each conclusion to objective, reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, documentation, monitoring, and operational handover are complete.

Lesson Outcome

Learners can apply SUM Preparation, Target HANA, and Preprocessing, explain the resulting SAP behavior, and defend the outcome through SUM preprocessing evidence pack.