SAP RSSM_PROCESS_ODSACTIVATE Function Module for Aktivate Data in a DSO
RSSM_PROCESS_ODSACTIVATE is a standard rssm process odsactivate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Aktivate Data in a DSO 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 rssm process odsactivate FM, simply by entering the name RSSM_PROCESS_ODSACTIVATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSSM_PROCESS
Program Name: SAPLRSSM_PROCESS
Main Program: SAPLRSSM_PROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSSM_PROCESS_ODSACTIVATE 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 'RSSM_PROCESS_ODSACTIVATE'"Aktivate Data in a DSO.
EXPORTING
I_ODSOBJECT = "InfoCube
* I_WITH_COMMIT = 'X' "Boolean
* I_LOG_ID = ' ' "Log-ID of a Process Chain Run
* I_PARENT_BATCH_ID = ' ' "Batch ID
* I_UNIQUE_MODE = ' ' "Uniqueness Setting for DSO Activation
* I_INIT_UNIQUE = ' ' "Boolean
I_JOBNAME = "Background job name
* I_NO_CONDENSE = ' ' "Do not condense Data in the Changelog during Activation Process
* I_SERIALIZE = RS_C_FALSE "Boolean
* I_T_REQUEST_SEL = "Activation of ODS M Records
* I_VARIANT = "Process Variant (Name)
* I_INSTANCE = "Process Instance (Value)
* I_DROP_CREA_SEC_IND = ' ' "Boolean
* I_CRT_ACTIVATION = ' ' "Boolean
IMPORTING
E_T_MSG = "BW: Table with Messages (Application Log)
E_ERROR = "Boolean
E_RNR = "Request ID (data package)
E_T_ODSR_RNR = "Request ID (data package)
E_T_ERROR_RNR = "
E_T_ACTIVATE_RNR = "
IMPORTING Parameters details for RSSM_PROCESS_ODSACTIVATE
I_ODSOBJECT - InfoCube
Data type: RSINFOCUBEOptional: No
Call by Reference: Yes
I_WITH_COMMIT - Boolean
Data type: RS_BOOLDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_LOG_ID - Log-ID of a Process Chain Run
Data type: RSPC_LOGIDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_PARENT_BATCH_ID - Batch ID
Data type: RSBTC_BATCH_IDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_UNIQUE_MODE - Uniqueness Setting for DSO Activation
Data type: RS_DSO_UNIQUEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_INIT_UNIQUE - Boolean
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_JOBNAME - Background job name
Data type: BTCJOBOptional: No
Call by Reference: Yes
I_NO_CONDENSE - Do not condense Data in the Changelog during Activation Process
Data type: RSODSNOCONDENSEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_SERIALIZE - Boolean
Data type: RSODSACTSERIALDefault: RS_C_FALSE
Optional: Yes
Call by Reference: Yes
I_T_REQUEST_SEL - Activation of ODS M Records
Data type: RSSM_T_REQUESTOptional: Yes
Call by Reference: Yes
I_VARIANT - Process Variant (Name)
Data type: RSPC_VARIANTOptional: Yes
Call by Reference: Yes
I_INSTANCE - Process Instance (Value)
Data type: RSPC_INSTANCEOptional: Yes
Call by Reference: Yes
I_DROP_CREA_SEC_IND - Boolean
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_CRT_ACTIVATION - Boolean
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSSM_PROCESS_ODSACTIVATE
E_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: Yes
E_ERROR - Boolean
Data type: RS_BOOLOptional: No
Call by Reference: Yes
E_RNR - Request ID (data package)
Data type: RSREQUIDOptional: No
Call by Reference: Yes
E_T_ODSR_RNR - Request ID (data package)
Data type: RSSM_T_REQUESTOptional: No
Call by Reference: Yes
E_T_ERROR_RNR -
Data type: RSSM_T_REQUESTOptional: No
Call by Reference: Yes
E_T_ACTIVATE_RNR -
Data type: RSSM_T_REQUESTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSSM_PROCESS_ODSACTIVATE 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_t_msg | TYPE RS_T_MSG, " | |||
| lv_i_odsobject | TYPE RSINFOCUBE, " | |||
| lv_i_with_commit | TYPE RS_BOOL, " 'X' | |||
| lv_i_log_id | TYPE RSPC_LOGID, " SPACE | |||
| lv_i_parent_batch_id | TYPE RSBTC_BATCH_ID, " SPACE | |||
| lv_i_unique_mode | TYPE RS_DSO_UNIQUE, " SPACE | |||
| lv_i_init_unique | TYPE RS_BOOL, " SPACE | |||
| lv_e_error | TYPE RS_BOOL, " | |||
| lv_i_jobname | TYPE BTCJOB, " | |||
| lv_e_rnr | TYPE RSREQUID, " | |||
| lv_i_no_condense | TYPE RSODSNOCONDENSE, " SPACE | |||
| lv_i_serialize | TYPE RSODSACTSERIAL, " RS_C_FALSE | |||
| lv_e_t_odsr_rnr | TYPE RSSM_T_REQUEST, " | |||
| lv_e_t_error_rnr | TYPE RSSM_T_REQUEST, " | |||
| lv_i_t_request_sel | TYPE RSSM_T_REQUEST, " | |||
| lv_i_variant | TYPE RSPC_VARIANT, " | |||
| lv_e_t_activate_rnr | TYPE RSSM_T_REQUEST, " | |||
| lv_i_instance | TYPE RSPC_INSTANCE, " | |||
| lv_i_drop_crea_sec_ind | TYPE RS_BOOL, " SPACE | |||
| lv_i_crt_activation | TYPE RS_BOOL. " SPACE |
|   CALL FUNCTION 'RSSM_PROCESS_ODSACTIVATE' "Aktivate Data in a DSO |
| EXPORTING | ||
| I_ODSOBJECT | = lv_i_odsobject | |
| I_WITH_COMMIT | = lv_i_with_commit | |
| I_LOG_ID | = lv_i_log_id | |
| I_PARENT_BATCH_ID | = lv_i_parent_batch_id | |
| I_UNIQUE_MODE | = lv_i_unique_mode | |
| I_INIT_UNIQUE | = lv_i_init_unique | |
| I_JOBNAME | = lv_i_jobname | |
| I_NO_CONDENSE | = lv_i_no_condense | |
| I_SERIALIZE | = lv_i_serialize | |
| I_T_REQUEST_SEL | = lv_i_t_request_sel | |
| I_VARIANT | = lv_i_variant | |
| I_INSTANCE | = lv_i_instance | |
| I_DROP_CREA_SEC_IND | = lv_i_drop_crea_sec_ind | |
| I_CRT_ACTIVATION | = lv_i_crt_activation | |
| IMPORTING | ||
| E_T_MSG | = lv_e_t_msg | |
| E_ERROR | = lv_e_error | |
| E_RNR | = lv_e_rnr | |
| E_T_ODSR_RNR | = lv_e_t_odsr_rnr | |
| E_T_ERROR_RNR | = lv_e_t_error_rnr | |
| E_T_ACTIVATE_RNR | = lv_e_t_activate_rnr | |
| . " RSSM_PROCESS_ODSACTIVATE | ||
ABAP code using 7.40 inline data declarations to call FM RSSM_PROCESS_ODSACTIVATE
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_i_with_commit) | = 'X'. | |||
| DATA(ld_i_log_id) | = ' '. | |||
| DATA(ld_i_parent_batch_id) | = ' '. | |||
| DATA(ld_i_unique_mode) | = ' '. | |||
| DATA(ld_i_init_unique) | = ' '. | |||
| DATA(ld_i_no_condense) | = ' '. | |||
| DATA(ld_i_serialize) | = RS_C_FALSE. | |||
| DATA(ld_i_drop_crea_sec_ind) | = ' '. | |||
| DATA(ld_i_crt_activation) | = ' '. | |||
Search for further information about these or an SAP related objects