SAP RSDU_EXPLAIN_PLAN_DB2 Function Module for Derive and Present Query Processing Plan









RSDU_EXPLAIN_PLAN_DB2 is a standard rsdu explain plan db2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Derive and Present Query Processing Plan 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 rsdu explain plan db2 FM, simply by entering the name RSDU_EXPLAIN_PLAN_DB2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSDU_CORE_UTIL_DB2
Program Name: SAPLRSDU_CORE_UTIL_DB2
Main Program: SAPLRSDU_CORE_UTIL_DB2
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSDU_EXPLAIN_PLAN_DB2 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 'RSDU_EXPLAIN_PLAN_DB2'"Derive and Present Query Processing Plan
EXPORTING
* I_T_STMT = "SQL Statement in an Internal Table
* I_STMT = "SQL Statement in a String
* I_SHOW_PLAN = RS_C_FALSE "Display Execution Plan

IMPORTING
E_COSTS = "DB-Specific SQL-Error Code (OK = 0)
E_STMTSIZE = "Size of the SQL Statement in Bytes

CHANGING
* C_PROCESSED = RS_C_FALSE "Boolean

EXCEPTIONS
EXPLAIN_ERROR = 1 STATEMENT_TOO_COMPLEX = 2 NO_STATEMENT = 3 PLAN_TABLE_ERROR = 4
.



IMPORTING Parameters details for RSDU_EXPLAIN_PLAN_DB2

I_T_STMT - SQL Statement in an Internal Table

Data type: RSDU_T_ABAPSOURCE
Optional: Yes
Call by Reference: Yes

I_STMT - SQL Statement in a String

Data type: C
Optional: Yes
Call by Reference: Yes

I_SHOW_PLAN - Display Execution Plan

Data type: RS_BOOL
Default: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RSDU_EXPLAIN_PLAN_DB2

E_COSTS - DB-Specific SQL-Error Code (OK = 0)

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

E_STMTSIZE - Size of the SQL Statement in Bytes

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for RSDU_EXPLAIN_PLAN_DB2

C_PROCESSED - Boolean

Data type: RS_BOOL
Default: RS_C_FALSE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXPLAIN_ERROR - Error During EXPLAIN PLAN Call

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

STATEMENT_TOO_COMPLEX - Statement Is Too Long

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_STATEMENT - No Statement Specified

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PLAN_TABLE_ERROR - Error in PLAN_TABLE (Oracle Only)

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RSDU_EXPLAIN_PLAN_DB2 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:
lv_e_costs  TYPE I, "   
lv_i_t_stmt  TYPE RSDU_T_ABAPSOURCE, "   
lv_c_processed  TYPE RS_BOOL, "   RS_C_FALSE
lv_explain_error  TYPE RS_BOOL, "   
lv_i_stmt  TYPE C, "   
lv_e_stmtsize  TYPE I, "   
lv_statement_too_complex  TYPE I, "   
lv_i_show_plan  TYPE RS_BOOL, "   RS_C_FALSE
lv_no_statement  TYPE RS_BOOL, "   
lv_plan_table_error  TYPE RS_BOOL. "   

  CALL FUNCTION 'RSDU_EXPLAIN_PLAN_DB2'  "Derive and Present Query Processing Plan
    EXPORTING
         I_T_STMT = lv_i_t_stmt
         I_STMT = lv_i_stmt
         I_SHOW_PLAN = lv_i_show_plan
    IMPORTING
         E_COSTS = lv_e_costs
         E_STMTSIZE = lv_e_stmtsize
    CHANGING
         C_PROCESSED = lv_c_processed
    EXCEPTIONS
        EXPLAIN_ERROR = 1
        STATEMENT_TOO_COMPLEX = 2
        NO_STATEMENT = 3
        PLAN_TABLE_ERROR = 4
. " RSDU_EXPLAIN_PLAN_DB2




ABAP code using 7.40 inline data declarations to call FM RSDU_EXPLAIN_PLAN_DB2

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.

 
 
DATA(ld_c_processed) = RS_C_FALSE.
 
 
 
 
 
DATA(ld_i_show_plan) = RS_C_FALSE.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!