SAP DB6_PM_DB6CSTRC_PROG_CONT Function Module for DB6: Get Summary for Cumulative SQL Trace
DB6_PM_DB6CSTRC_PROG_CONT is a standard db6 pm db6cstrc prog cont SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB6: Get Summary for Cumulative SQL Trace processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for db6 pm db6cstrc prog cont FM, simply by entering the name DB6_PM_DB6CSTRC_PROG_CONT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDB6CSTRACE
Program Name: SAPLSDB6CSTRACE
Main Program: SAPLSDB6CSTRACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DB6_PM_DB6CSTRC_PROG_CONT pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'DB6_PM_DB6CSTRC_PROG_CONT'"DB6: Get Summary for Cumulative SQL Trace.
EXPORTING
STMT_STR_LEN = "Length of SQL Statement
STMT_STR = "First 200 Characters of the Statement Text
TABLENAME = "Name of the First Table in the SQL Statement
OPTLEVEL = "Database Optimization Level
* CONNECTION = "Logical name for a database connection
TABLES
ABAP = "DB6: abap prog for cumulative sql trace
EXCEPTIONS
NO_HISTORY_FOUND = 1 ADBC_ERROR = 2 C_CALL_FAILED = 3 SYSTEM_ERROR = 4
IMPORTING Parameters details for DB6_PM_DB6CSTRC_PROG_CONT
STMT_STR_LEN - Length of SQL Statement
Data type: DB6CSTRACE-STMT_LENOptional: No
Call by Reference: No ( called with pass by value option)
STMT_STR - First 200 Characters of the Statement Text
Data type: DB6CSTRACE-STMT_SUBSTOptional: No
Call by Reference: No ( called with pass by value option)
TABLENAME - Name of the First Table in the SQL Statement
Data type: DB6CSTRACE-TABLENAMEOptional: No
Call by Reference: No ( called with pass by value option)
OPTLEVEL - Database Optimization Level
Data type: DB6CSTRACE-OPTLEVELOptional: No
Call by Reference: No ( called with pass by value option)
CONNECTION - Logical name for a database connection
Data type: DBCON-CON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DB6_PM_DB6CSTRC_PROG_CONT
ABAP - DB6: abap prog for cumulative sql trace
Data type: DB6CSTABPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_HISTORY_FOUND - required history records could not be read
Data type:Optional: No
Call by Reference: Yes
ADBC_ERROR -
Data type:Optional: No
Call by Reference: Yes
C_CALL_FAILED -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DB6_PM_DB6CSTRC_PROG_CONT Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lt_abap | TYPE STANDARD TABLE OF DB6CSTABP, " | |||
| lv_stmt_str_len | TYPE DB6CSTRACE-STMT_LEN, " | |||
| lv_no_history_found | TYPE DB6CSTRACE, " | |||
| lv_stmt_str | TYPE DB6CSTRACE-STMT_SUBST, " | |||
| lv_adbc_error | TYPE DB6CSTRACE, " | |||
| lv_tablename | TYPE DB6CSTRACE-TABLENAME, " | |||
| lv_c_call_failed | TYPE DB6CSTRACE, " | |||
| lv_optlevel | TYPE DB6CSTRACE-OPTLEVEL, " | |||
| lv_system_error | TYPE DB6CSTRACE, " | |||
| lv_connection | TYPE DBCON-CON_NAME. " |
|   CALL FUNCTION 'DB6_PM_DB6CSTRC_PROG_CONT' "DB6: Get Summary for Cumulative SQL Trace |
| EXPORTING | ||
| STMT_STR_LEN | = lv_stmt_str_len | |
| STMT_STR | = lv_stmt_str | |
| TABLENAME | = lv_tablename | |
| OPTLEVEL | = lv_optlevel | |
| CONNECTION | = lv_connection | |
| TABLES | ||
| ABAP | = lt_abap | |
| EXCEPTIONS | ||
| NO_HISTORY_FOUND = 1 | ||
| ADBC_ERROR = 2 | ||
| C_CALL_FAILED = 3 | ||
| SYSTEM_ERROR = 4 | ||
| . " DB6_PM_DB6CSTRC_PROG_CONT | ||
ABAP code using 7.40 inline data declarations to call FM DB6_PM_DB6CSTRC_PROG_CONT
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single STMT_LEN FROM DB6CSTRACE INTO @DATA(ld_stmt_str_len). | ||||
| "SELECT single STMT_SUBST FROM DB6CSTRACE INTO @DATA(ld_stmt_str). | ||||
| "SELECT single TABLENAME FROM DB6CSTRACE INTO @DATA(ld_tablename). | ||||
| "SELECT single OPTLEVEL FROM DB6CSTRACE INTO @DATA(ld_optlevel). | ||||
| "SELECT single CON_NAME FROM DBCON INTO @DATA(ld_connection). | ||||
Search for further information about these or an SAP related objects