ABAP® Programming for SAP HANA® – HA400 — Lesson 3: AMDP, CDS-Based Logic, and Database Procedures

Learning Objectives

• Explain how AMDP, CDS-Based Logic, and Database Procedures supports efficient ABAP execution.
• Complete the workflow and produce a reviewable code-pushdown implementation evidence pack.
• Evaluate the condition where an AMDP procedure returns correct data but bypasses an expected authorization restriction and select a supported response.

Detailed Topics

• AMDP method structure: settings, dependencies, and derivation rules that control the selected process behavior.
• SQLScript implementation: integration touchpoints and downstream effects that must remain aligned with business intent.
• CDS table functions: authorization, governance, and change controls required to protect the configuration outcome.
• Exception and authorization considerations: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

The instructor traces AMDP method structure, SQLScript implementation, CDS table functions, Exception and authorization considerations through the course scenario, explaining navigation, decision logic, dependencies, system messages, and the evidence retained in code-pushdown implementation evidence pack. The walkthrough also shows how to investigate the condition where an AMDP procedure returns correct data but bypasses an expected authorization restriction.

Hands-On Exercise

Complete a controlled activity covering AMDP method structure, SQLScript implementation, CDS table functions, Exception and authorization considerations and preserve the final result in code-pushdown implementation 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 code-pushdown implementation 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 “an AMDP procedure returns correct data but bypasses an expected authorization restriction” 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 AMDP, CDS-Based Logic, and Database Procedures are present.
• The code-pushdown implementation 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 AMDP, CDS-Based Logic, and Database Procedures, explain the resulting SAP behavior, and defend the outcome through code-pushdown implementation evidence pack.