Kontakt

Ansicht
Dokumentation

RS_AMDP_STMT_TRACE - Prototype: Statement Trace for AMDP Calls

RS_AMDP_STMT_TRACE - Prototype: Statement Trace for AMDP Calls

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program controls SQL statement trace for AMDP calls, i.e. calls to HANA procedures managed by the AMDP framework (ABAP Managed Database Procedures) via the ABAP-Statement CALL METHOD.

It enables SQL statement tracing for procedure calls at runtime of the ABAP application, i.e. in the runtime context of the running ABAP application which may e.g. consist of

  • current content of temporary tables
  • current (uncommitted) content of persistent tables
  • current setting of environment variables
  • ...

This trace is based on information that is available in SAP HANA system view SYS.M_ACTIVE_PROCEDURES. Information is selected at the end of the top-level procedure, and stored separately, as the information will be no longer available via SYS.M_ACTIVE_PROCEDURES.

Caution

  • This program is meant for SAP internal usage only. Please do not use it unless proposed by SAP.
  • This program is in a prototype state; it may not work as expected, and there is no support for it. Additionally, it may break on changes of services used by it, and it will be removed later on without further notice. If possible, you should use the AMDP statement trace option provided in the ABAP profiler.
  • To enable trace collection, a slightly different procedure call is used that uses a different entry procedure in HANA which takes additional timestamps at procedure beginning and end, and selects the data from the system view. Therefore, procedure runtime is affected at the beginning and at the end of the top-level procedure, while everything else is not affected at all.
  • Please note that due to the different entry procedure, the first call to a specific procedure with activated trace may take longer because of additional SQL prepare steps in HANA. Subsequent calls then have the "normal" snall tracing overhead (at beginning and end of the top-level procedure).
  • As trace data volume grows fast, please do not forget to switch off trace as soon as possible, and to delete or cleanup trace data as soon as the analysis is done.

Restrictions

This prototype is built to be used via SAPGUI only.

Integration

Prerequisites

The AMDP framework is currently only available on HANA databases. The integrated SQL statement trace is a feature of the HANA database.

Features

Control of SQL statement trace for AMDP calls:

  • Activation of statement trace: Activation info (and subsequent selection of the entry procedure) is managed via the ABAP server only, i.e. there is no global trace activation on the database.
  • Predefined filter conditions:
  • ABAP application server: tracing is only controlled for the current application server where this control program is running,

  • ABAP application user calling the AMDP procedure, and

  • Pattern for procedure name(s) to be traced.

  • Deactivation of SQL statement trace.
  • Overview over Trace Activations and Removal of Obsolete Activations

Maintenance of stored SQL statement trace entries

  • Overview of SQL statement trace entries for the current ABAP application user, one entry for each traced ABAP->HANA procedure call.
  • Display of SQL statement trace
  • Deletion of selected SQL statement trace entries
  • Cleanup of all SQL statement trace entries for the current ABAP application user

Selection

Standard Variants

Output

Activities

Example






TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4346 Date: 20240601 Time: 061831     sap01-206 ( 71 ms )