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?

In an AMDP function you join two client-dependent tables but leave the client (MANDT) out of the ON condition. What result do you get?

By default, what does 'implicit client handling' do to a CDS table function, and when would you turn it off?

You add DETERMINISTIC to a scalar AMDP function expecting a speedup. When does it actually help, and when can scalar functions still hurt?

From ABAP's perspective, SQLScript is Native SQL, not Open SQL. What practical consequence does that have for a program that uses it?

AMDP procedure, CDS table function, and AMDP function — how is each one called from ABAP/Open SQL?

What single thing makes an ABAP class an 'AMDP class', and what methods does that interface add?

Per SAP's own documentation, when should you actually reach for AMDP instead of staying with Open SQL?

You give an AMDP method a RETURNING parameter and a REF TO DATA parameter, reusing your usual ABAP method style. Why won't it activate?

Your AMDP method hits an error at runtime and the whole program dumps instead of being caught. What did you forget in the signature?

What is the minimal correct method-implementation header for a read-only AMDP procedure, and which parts are optional?

In an AMDP method you write USING /BI0/PPLANT with no quotes, then quote the same table inside the SELECT. Why the inconsistency?

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?

For an AMDP procedure that may be called directly from other SQLScript, why prefer separate IT_/ET_ table parameters over one CHANGING parameter?

ABAPVARCHARMODE is 'true'. What does this return? ``` SELECT length(' ') FROM dummy; ```

Which SAP NetWeaver / SAP_BASIS releases gate the AMDP variants (procedures, table functions, AMDP functions, scalar functions)?

You activate an AMDP class on a NetWeaver system. Which SAP HANA database objects does activation create?

You must support both HANA and non-HANA databases behind one ABAP interface. How do you pick the AMDP vs Open SQL implementation at runtime?

In an ABAP Unit test you replace an AMDP method with canned data via a local subclass. Why is that even allowed to work?

One AMDP procedure needs to CALL another AMDP procedure's generated DB procedure. What two things must you get right?