SAP RSDU_DBSTATC_EXIT_DB4 Function Module for Exit Function for DBSTATC Handling Upon InfoCube Activation









RSDU_DBSTATC_EXIT_DB4 is a standard rsdu dbstatc exit db4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Exit Function for DBSTATC Handling Upon InfoCube Activation 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 dbstatc exit db4 FM, simply by entering the name RSDU_DBSTATC_EXIT_DB4 into the relevant SAP transaction such as SE37 or SE38.

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



Function RSDU_DBSTATC_EXIT_DB4 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_DBSTATC_EXIT_DB4'"Exit Function for DBSTATC Handling Upon InfoCube Activation
EXPORTING
I_INFOCUBE = "InfoCube
I_S_CUBE = "Matainformation for InfoCube

CHANGING
* C_PROCESSED = RS_C_FALSE "Boolean

EXCEPTIONS
ILLEGAL_INPUT = 1 INHERITED_ERROR = 2
.



IMPORTING Parameters details for RSDU_DBSTATC_EXIT_DB4

I_INFOCUBE - InfoCube

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

I_S_CUBE - Matainformation for InfoCube

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

CHANGING Parameters details for RSDU_DBSTATC_EXIT_DB4

C_PROCESSED - Boolean

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

EXCEPTIONS details

ILLEGAL_INPUT -

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

INHERITED_ERROR -

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

Copy and paste ABAP code example for RSDU_DBSTATC_EXIT_DB4 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_i_infocube  TYPE RSD_INFOCUBE, "   
lv_c_processed  TYPE RS_BOOL, "   RS_C_FALSE
lv_illegal_input  TYPE RS_BOOL, "   
lv_i_s_cube  TYPE RSD_S_CUBE, "   
lv_inherited_error  TYPE RSD_S_CUBE. "   

  CALL FUNCTION 'RSDU_DBSTATC_EXIT_DB4'  "Exit Function for DBSTATC Handling Upon InfoCube Activation
    EXPORTING
         I_INFOCUBE = lv_i_infocube
         I_S_CUBE = lv_i_s_cube
    CHANGING
         C_PROCESSED = lv_c_processed
    EXCEPTIONS
        ILLEGAL_INPUT = 1
        INHERITED_ERROR = 2
. " RSDU_DBSTATC_EXIT_DB4




ABAP code using 7.40 inline data declarations to call FM RSDU_DBSTATC_EXIT_DB4

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.
 
 
 
 


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!