Kontakt

Ansicht
Dokumentation

RS_AMDP_COVERAGE_TRACE - Prototype: Coverage Trace for AMDP Calls

RS_AMDP_COVERAGE_TRACE - Prototype: Coverage Trace for AMDP Calls

TXBHW - Original Tax Base Amount in Local Currency   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program controls Coverage 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 Coverage 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
  • ...

As Coverage trace might have a strong influence on statement runtimes, it should be used carefully, and not in productive environments, and not in scenarios with processing of large amounts of data.

Caution

  • This program is 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, avoid to use this program in a productive system.
  • If you need to use it in a productive system, you should verify before in a test system with equal or at least similar HANA and ABAP software version, whether
  • enabling the Coverage trace causes unexpected side-effects on the ABAP application

  • tracing does not slow down the application too much (avoid timeout issues)

  • trace filter possibilities fit to the application scenario to meet tracing restrictions (see below).

  • If necessary, additional filter measures have to be taken to avoid concurrent calls, e.g. using dedicated application users, application servers for the trace, or limiting internal application parallelization.
  • 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

While it is possible in general, please avoid to trace concurrent calls to procedures with Coverage trace active, as this might cause high load on the database.

Coverage trace can be controlled only for ABAP->HANA procedure calls, including all nested calls inside the called HANA procedure, i.e. there is no filter for those nested calls.

Currently, the Coverage run for SQLSCRIPT uses the debug version of the script for execution and each AMDP start creates a new context, so each time a new debug version is prepared and executed. This can result in high overhead, depending on the executed AMDP scenario.

For further restrictions of this trace, please consult the HANA documentation for Coverage trace.

This prototype is built to be used via SAPGUI only.

Integration

Prerequisites

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

Features

Control of Coverage trace for AMDP calls:

  • Activation of Coverage trace: Activation info is managed via the ABAP server only, i.e. there is no global Coverage trace activation on the database, but for each traced AMDP call a new Coverage context is opened on the current HANA connection, the procedure call is executed, the trace is extracted and stored, and then the Coverage context is closed again.
  • 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 Coverage trace.
  • Overview over Trace Activations and Removal of Obsolete Activations

Maintenance of stored Coverage trace entries

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

Selection

Standard Variants

Output

Activities

Example






BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 5317 Date: 20240601 Time: 103507     sap01-206 ( 68 ms )