HA450 – SAP HANA 2.0 SPS06 – Application Development for SAP HANA® — Lesson 2: Persistence, Calculation Views, and SQLScript Services

Learning Objectives

• Explain how Persistence, Calculation Views, and SQLScript Services supports deployable HANA applications.
• Complete the workflow and produce a reviewable persistence and database-service evidence pack.
• Evaluate the condition where a procedure reads the wrong container because a cross-container grant is incomplete and select a supported response.

Detailed Topics

• CDS persistence artifacts: settings, dependencies, and derivation rules that control the selected process behavior.
• HDI containers: integration touchpoints and downstream effects that must remain aligned with business intent.
• Calculation view integration: authorization, governance, and change controls required to protect the configuration outcome.
• SQLScript procedures: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

Using the stated scenario, the instructor demonstrates CDS persistence artifacts, HDI containers, Calculation view integration, SQLScript procedures. Particular attention is given to object relationships, field or status behavior, integration effects, and how persistence and database-service evidence pack supports review. The demonstration deliberately introduces the exception where a procedure reads the wrong container because a cross-container grant is incomplete.

Hands-On Exercise

Complete a controlled activity covering CDS persistence artifacts, HDI containers, Calculation view integration, SQLScript procedures and preserve the final result in persistence and database-service evidence pack.

1. Set the scope, roles, evidence requirements, and success conditions for the practical case.
2. Run the process or configuration steps and annotate the resulting records, statuses, and integration effects.
3. Challenge the result using the stated exception and distinguish symptom, cause, and downstream consequence.
4. Finalize the deliverable with correction evidence, approvals, escalation criteria, and measurable next actions.

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 persistence and database-service 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 procedure reads the wrong container because a cross-container grant is incomplete” 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 Persistence, Calculation Views, and SQLScript Services are present.
• The persistence and database-service 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 Persistence, Calculation Views, and SQLScript Services, explain the resulting SAP behavior, and defend the outcome through persistence and database-service evidence pack.