SAP HANA SQLScript · AMDP: SQLScript in ABAP

You call a generated AMDP procedure directly from SQLScript. The class declared only a CHANGING table param CT_COUNTRY, yet the procedure demands two table params. Why?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in AMDP: SQLScript in ABAP

First execution of one AMDP method generates several HANA objects. What are they — and what is the #covw view for?

Besides AMDP, ABAP can run SQLScript via ADBC, EXEC SQL, or CALL DATABASE PROCEDURE. Which do you pick for static code, dynamic code, and secondary connections?

A plain AMDP function can't be read from Open SQL. How does a CDS table function make the same logic consumable in a SELECT?

In a client-dependent CDS table function DDL, what must the first RETURNS field be, and what does implemented by method allow?

How can a CDS table function get the client and logon language without the ABAP caller passing them explicitly?

A CDS table function has no Open SQL fallback. How does the caller stay safe on a non-HANA database, and how do you silence the syntax warning?

Start learning today

Free to start — download the app or use it in your browser.