SAP HANA 2.0 SPS05 – Installation and Administration — Lesson 1: SAP HANA Architecture, Sizing Inputs, Installation Planning, and Prerequisites

Learning Objectives

• Explain how SAP HANA Architecture, Sizing Inputs, Installation Planning, and Prerequisites supports reliable SAP HANA administration.
• Complete the workflow and produce a reviewable HANA installation-readiness workbook.
• Evaluate the condition where a host passes basic checks but lacks storage throughput required by the target workload and select a supported response.

Detailed Topics

• SAP HANA architecture: business purpose, responsible roles, and SAP objects that establish the operating scope.
• installation sizing inputs: configuration choices, master-data dependencies, and determination logic shaping the result.
• host prerequisites: transaction flow, status behavior, integration effects, and reviewable operational evidence.
• landscape planning: control points, exception paths, testing needs, and release criteria protecting the outcome.

Instructor Demonstration

The instructor traces SAP HANA architecture, installation sizing inputs, host prerequisites, landscape planning through the scenario, explaining navigation, decisions, dependencies, system responses, and the evidence retained in HANA installation-readiness workbook. The walkthrough also investigates the condition where a host passes basic checks but lacks storage throughput required by the target workload.

Hands-On Exercise

Complete a controlled activity covering SAP HANA architecture, installation sizing inputs, host prerequisites, landscape planning and preserve the result in HANA installation-readiness workbook.

1. Confirm the business objective, organizational scope, roles, source data, and expected SAP result.
2. Execute the workflow in sequence while capturing settings, transactions, messages, and observations.
3. Introduce the stated exception and isolate the earliest divergence from the expected behavior.
4. Correct or contain the issue, retest the affected path, and record the accountable owner.

Scenario Analysis

• Which SAP object, rule, record, or process step most strongly influences SAP HANA Architecture, Sizing Inputs, Installation Planning, and Prerequisites?
• What evidence separates configuration, data, authorization, integration, and timing causes in this scenario?
• How should the HANA installation-readiness workbook 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 host passes basic checks but lacks storage throughput required by the target workload” as unconfirmed until settings, documents, logs, reports, and focused retesting support the cause.

Validation Checklist

• Required roles, structures, data, settings, and dependencies for SAP HANA Architecture, Sizing Inputs, Installation Planning, and Prerequisites are present.
• The HANA installation-readiness workbook 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 SAP HANA Architecture, Sizing Inputs, Installation Planning, and Prerequisites, explain the resulting SAP behavior, and defend the outcome through HANA installation-readiness workbook.