SAP RSDU_CUBE_PRE_ACTIVATION_E_TDA Function Module for Exit for Infocube before mass activation starts
RSDU_CUBE_PRE_ACTIVATION_E_TDA is a standard rsdu cube pre activation e tda 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 for Infocube before mass activation starts 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 cube pre activation e tda FM, simply by entering the name RSDU_CUBE_PRE_ACTIVATION_E_TDA into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_CUBE_ADA
Program Name: SAPLRSDU_CUBE_ADA
Main Program: SAPLRSDU_CUBE_ADA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RSDU_CUBE_PRE_ACTIVATION_E_TDA 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_CUBE_PRE_ACTIVATION_E_TDA'"Exit for Infocube before mass activation starts.
EXPORTING
I_S_CUBE = "InfoCube Name
I_T_DIME = "Dimensions Table
I_T_CUBE_IOBJ = "List of InfoObjects in InfoCube
I_T_DIME_IOBJ = "Table: Dimensions - InfoObjects
I_T_IC_VAL_IOBJ = "List of InfoObjects in the Non-Cumulative Validity Table
I_MODIFIED_DIM = "Has dimension changed?
CHANGING
C_T_MSG = "BW: Table with Messages (Application Log)
C_PROCESSED = "Has the function something done?
EXCEPTIONS
INFOCUBE_ERROR = 1 INHERITED_ERROR = 2
IMPORTING Parameters details for RSDU_CUBE_PRE_ACTIVATION_E_TDA
I_S_CUBE - InfoCube Name
Data type: RSD_S_CUBEOptional: No
Call by Reference: Yes
I_T_DIME - Dimensions Table
Data type: RSD_T_DIMEOptional: No
Call by Reference: Yes
I_T_CUBE_IOBJ - List of InfoObjects in InfoCube
Data type: RSD_T_CUBE_IOBJOptional: No
Call by Reference: Yes
I_T_DIME_IOBJ - Table: Dimensions - InfoObjects
Data type: RSD_T_DIME_IOBJOptional: No
Call by Reference: Yes
I_T_IC_VAL_IOBJ - List of InfoObjects in the Non-Cumulative Validity Table
Data type: RSD_T_IC_VAL_IOBJOptional: No
Call by Reference: Yes
I_MODIFIED_DIM - Has dimension changed?
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RSDU_CUBE_PRE_ACTIVATION_E_TDA
C_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: Yes
C_PROCESSED - Has the function something done?
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
INFOCUBE_ERROR -
Data type:Optional: No
Call by Reference: Yes
INHERITED_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSDU_CUBE_PRE_ACTIVATION_E_TDA 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_c_t_msg | TYPE RS_T_MSG, " | |||
lv_i_s_cube | TYPE RSD_S_CUBE, " | |||
lv_infocube_error | TYPE RSD_S_CUBE, " | |||
lv_i_t_dime | TYPE RSD_T_DIME, " | |||
lv_c_processed | TYPE RS_BOOL, " | |||
lv_inherited_error | TYPE RS_BOOL, " | |||
lv_i_t_cube_iobj | TYPE RSD_T_CUBE_IOBJ, " | |||
lv_i_t_dime_iobj | TYPE RSD_T_DIME_IOBJ, " | |||
lv_i_t_ic_val_iobj | TYPE RSD_T_IC_VAL_IOBJ, " | |||
lv_i_modified_dim | TYPE RS_BOOL. " |
  CALL FUNCTION 'RSDU_CUBE_PRE_ACTIVATION_E_TDA' "Exit for Infocube before mass activation starts |
EXPORTING | ||
I_S_CUBE | = lv_i_s_cube | |
I_T_DIME | = lv_i_t_dime | |
I_T_CUBE_IOBJ | = lv_i_t_cube_iobj | |
I_T_DIME_IOBJ | = lv_i_t_dime_iobj | |
I_T_IC_VAL_IOBJ | = lv_i_t_ic_val_iobj | |
I_MODIFIED_DIM | = lv_i_modified_dim | |
CHANGING | ||
C_T_MSG | = lv_c_t_msg | |
C_PROCESSED | = lv_c_processed | |
EXCEPTIONS | ||
INFOCUBE_ERROR = 1 | ||
INHERITED_ERROR = 2 | ||
. " RSDU_CUBE_PRE_ACTIVATION_E_TDA |
ABAP code using 7.40 inline data declarations to call FM RSDU_CUBE_PRE_ACTIVATION_E_TDA
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