SAP RSDU_TABLE_INIT_DB4 Function Module for initialize new tables with deleted records









RSDU_TABLE_INIT_DB4 is a standard rsdu table init 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 initialize new tables with deleted records 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 table init db4 FM, simply by entering the name RSDU_TABLE_INIT_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_TABLE_INIT_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_TABLE_INIT_DB4'"initialize new tables with deleted records
EXPORTING
* I_INFOCUBE = "InfoCube
* I_T_DIME = "Dimensions
* I_TABLNM = "Table

EXCEPTIONS
INFOCUBE_NOT_FOUND = 1 INHERITED = 2 ILLEGAL_INPUT = 3
.



IMPORTING Parameters details for RSDU_TABLE_INIT_DB4

I_INFOCUBE - InfoCube

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

I_T_DIME - Dimensions

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

I_TABLNM - Table

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

EXCEPTIONS details

INFOCUBE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INHERITED -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSDU_TABLE_INIT_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_infocube_not_found  TYPE RSD_INFOCUBE, "   
lv_i_t_dime  TYPE RSD_T_DIME, "   
lv_inherited  TYPE RSD_T_DIME, "   
lv_i_tablnm  TYPE RSD_TABLNM, "   
lv_illegal_input  TYPE RSD_TABLNM. "   

  CALL FUNCTION 'RSDU_TABLE_INIT_DB4'  "initialize new tables with deleted records
    EXPORTING
         I_INFOCUBE = lv_i_infocube
         I_T_DIME = lv_i_t_dime
         I_TABLNM = lv_i_tablnm
    EXCEPTIONS
        INFOCUBE_NOT_FOUND = 1
        INHERITED = 2
        ILLEGAL_INPUT = 3
. " RSDU_TABLE_INIT_DB4




ABAP code using 7.40 inline data declarations to call FM RSDU_TABLE_INIT_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.

 
 
 
 
 
 


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!