Using the new AMDP, the editing, activation, transport, and life cycle management of the database procedures are performed on the ABAP application server.

AMDP performs the following functions:

1. Manages SQL Scripts source code in AS ABAP
2. Integrates SQL Scripts syntax check in ABAP syntax check
3. Creates and manages stored procedure runtime objects on HDB in the ABAP AS database schema.

 

 

The implementation of ABAP Managed Database Procedures is achieved using methods of ABAP classes. Whether a method is implemented in ABAP or native code, such as SQL script, is determined in the method implementation part, and not in the method definition part of the ABAP class. However, to create an AMDP method, there are some prerequisites that must be fulfilled in the class definition part, before a method can be used as an AMDP method.

 

 

Classes that are to act as a container for AMDPs have to implement a so-called Marker interface IF_AMDP_MARKER_HDB.

 

AMDP method parameters can import, export, or change parameters. Returning parameters cannot be used. All AMDP method parameters have to be passed by value and must be of either table or scalar types and AMDP doesn’t support nested tables.

 

 

AMDP methods are identified with the syntax BY DATABASE PROCEDURE. The database system(for example, HDB) and language(for example, SQL Script) must also be specified. Optionally, the AMDP method can be marked as a READ-ONLY database procedure. It is also necessary to list all ABAP Dictionary tables, views, and other procedures used in the procedure body in the USING clause. The method body can then be implemented using native SQL Script source code. Almost the full SQL Script reference can be used in the method body, except the CE function CE_COLUMN_TABLE.

 

 

All ABAP Dictionary tables or views, and other AMDP methods that will be called in the procedure body must be declared with the USING keyword. In the procedure body, these objects are addressed without the need for the SAP<SID> prefix.

 

 AMDP can detect the following types of syntax-errors in active or inactive source code:

1. Database-independent syntax errors: parameters not passed by value, wrong parameter types, or cyclic method calls.
2. SAP-HANA -specific syntax errors: Type mapping check or wrong default values.
3. SQL scripts errors.

 

 

You use the ABAP Development Tools for full AMDP support, including the following functions:

1. Semantic code completion for the ABAP part
2. Syntax coloring for SQL script
3. Customizable shades of Native SQL code via

Window->Preferences->General->Appearance->Colors and Fonts

 

AMDP Usage

An AMDP Method is called like any ABAP method, as follows:

• AMDP methods are executed like a static method, even if they are defined as instance methods.
• When an AMDP is processed, the ABAP kernel calls the corresponding database procedure in SAP HANA.

 

AMDP makes sure that a database procedure is available at runtime:

• The database procedure is created at first use (lazy approach)
• It exists in the SAP<SID> schema
• A new version of the database procedure is created each time the source code or dependent objects change
• Obsolete versions are deleted asynchronously

 

AMDP Enhancement

 

 

To allow for the enhancement of AMDP, the following must apply:

• The software provider must create an Enhancement Spot and a Business-Add-in (BADI) Definition
• The BADI definition must be marked as AMDP BADI
• This setting makes providing a fallback class mandatory