SAP RSDGDB_AFTER_DB_MODIFICATION Function Module for (Infocube) Post Work after activation

Search SAP Function Modules

RSDGDB_AFTER_DB_MODIFICATION is a standard rsdgdb after db modification SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for (Infocube) Post Work after 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 rsdgdb after db modification FM, simply by entering the name RSDGDB_AFTER_DB_MODIFICATION into the relevant SAP transaction such as SE37 or SE38.

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

Function RSDGDB_AFTER_DB_MODIFICATION 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 'RSDGDB_AFTER_DB_MODIFICATION'"(Infocube) Post Work after activation
  EXPORTING
   I_INFOCUBE =  "InfoCube
*  I_MODIFIED_DIM = RS_C_TRUE "Cube-dimensionality has been changed
*  I_PROC_INDEX_FOR_E = RS_C_TRUE "Flag: Process index for E-table
*  I_PROC_INDEX_FOR_F = RS_C_TRUE "Flag: Process index for F-table
*  I_S_CUBE_A =  "Active rsdcube entry

 IMPORTING
   E_SUBRC =  "Return Code
   E_T_MSG =  "Table with Messages

CHANGING
*  C_S_CUBE =  "InfoCube field bar

.

IMPORTING Parameters details for RSDGDB_AFTER_DB_MODIFICATION

I_INFOCUBE - InfoCube

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

I_MODIFIED_DIM - Cube-dimensionality has been changed

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: Yes

I_PROC_INDEX_FOR_E - Flag: Process index for E-table

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: Yes

I_PROC_INDEX_FOR_F - Flag: Process index for F-table

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: Yes

I_S_CUBE_A - Active rsdcube entry

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

EXPORTING Parameters details for RSDGDB_AFTER_DB_MODIFICATION

E_SUBRC - Return Code

Data type: SYSUBRC
Optional: No
Call by Reference: Yes

E_T_MSG - Table with Messages

Data type: RS_T_MSG
Optional: No
Call by Reference: Yes

CHANGING Parameters details for RSDGDB_AFTER_DB_MODIFICATION

C_S_CUBE - InfoCube field bar

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

Copy and paste ABAP code example for RSDGDB_AFTER_DB_MODIFICATION 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.

ABAP code using 7.40 inline data declarations to call FM RSDGDB_AFTER_DB_MODIFICATION

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