SAP RSDU_CONVERSION_REQUEST_INIT Function Module for Initializes a conversion request
RSDU_CONVERSION_REQUEST_INIT is a standard rsdu conversion request init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initializes a conversion request 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 conversion request init FM, simply by entering the name RSDU_CONVERSION_REQUEST_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_REPART
Program Name: SAPLRSDU_REPART
Main Program: SAPLRSDU_REPART
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDU_CONVERSION_REQUEST_INIT 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_CONVERSION_REQUEST_INIT'"Initializes a conversion request.
EXPORTING
I_CLASSNAME = "Name of conversion class
I_INFOPROV = "Name of InfoProvider
* I_NEW_PART_OBJNM = "Partitioning Time Char.
* I_NEW_PARTVL_FROM = "Lower limit (partitioning value)
* I_NEW_PARTVL_TO = "Upper Limit (Partitioning Value)
* I_MAX_PART_CNT = "Max. Number of Parititions
* I_ACT_AGGR = RS_C_FALSE "Set up all aggregates again?
* I_DB_PARAMS = "
IMPORTING
STATUS = "
EXCEPTION = "Abstract Superclass for All Global Exceptions
EXCEPTIONS
INVALID_CLASSNAME = 1 INHERITED_ERROR = 2
IMPORTING Parameters details for RSDU_CONVERSION_REQUEST_INIT
I_CLASSNAME - Name of conversion class
Data type: STRINGOptional: No
Call by Reference: Yes
I_INFOPROV - Name of InfoProvider
Data type: RSD_INFOCUBEOptional: No
Call by Reference: Yes
I_NEW_PART_OBJNM - Partitioning Time Char.
Data type: RSPARTTIMOptional: Yes
Call by Reference: Yes
I_NEW_PARTVL_FROM - Lower limit (partitioning value)
Data type: RSPARTVL_FROMOptional: Yes
Call by Reference: Yes
I_NEW_PARTVL_TO - Upper Limit (Partitioning Value)
Data type: RSPARTVL_TOOptional: Yes
Call by Reference: Yes
I_MAX_PART_CNT - Max. Number of Parititions
Data type: RSPARTMAXCNTOptional: Yes
Call by Reference: Yes
I_ACT_AGGR - Set up all aggregates again?
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: Yes
I_DB_PARAMS -
Data type: STRINGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSDU_CONVERSION_REQUEST_INIT
STATUS -
Data type: RSDU_REPART_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION - Abstract Superclass for All Global Exceptions
Data type: CX_ROOTOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_CLASSNAME - Classname invalid
Data type:Optional: No
Call by Reference: Yes
INHERITED_ERROR - Error inherited from called method
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSDU_CONVERSION_REQUEST_INIT 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_status | TYPE RSDU_REPART_STATUS, " | |||
| lv_i_classname | TYPE STRING, " | |||
| lv_invalid_classname | TYPE STRING, " | |||
| lv_exception | TYPE CX_ROOT, " | |||
| lv_i_infoprov | TYPE RSD_INFOCUBE, " | |||
| lv_inherited_error | TYPE RSD_INFOCUBE, " | |||
| lv_i_new_part_objnm | TYPE RSPARTTIM, " | |||
| lv_i_new_partvl_from | TYPE RSPARTVL_FROM, " | |||
| lv_i_new_partvl_to | TYPE RSPARTVL_TO, " | |||
| lv_i_max_part_cnt | TYPE RSPARTMAXCNT, " | |||
| lv_i_act_aggr | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_i_db_params | TYPE STRING. " |
|   CALL FUNCTION 'RSDU_CONVERSION_REQUEST_INIT' "Initializes a conversion request |
| EXPORTING | ||
| I_CLASSNAME | = lv_i_classname | |
| I_INFOPROV | = lv_i_infoprov | |
| I_NEW_PART_OBJNM | = lv_i_new_part_objnm | |
| I_NEW_PARTVL_FROM | = lv_i_new_partvl_from | |
| I_NEW_PARTVL_TO | = lv_i_new_partvl_to | |
| I_MAX_PART_CNT | = lv_i_max_part_cnt | |
| I_ACT_AGGR | = lv_i_act_aggr | |
| I_DB_PARAMS | = lv_i_db_params | |
| IMPORTING | ||
| STATUS | = lv_status | |
| EXCEPTION | = lv_exception | |
| EXCEPTIONS | ||
| INVALID_CLASSNAME = 1 | ||
| INHERITED_ERROR = 2 | ||
| . " RSDU_CONVERSION_REQUEST_INIT | ||
ABAP code using 7.40 inline data declarations to call FM RSDU_CONVERSION_REQUEST_INIT
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_act_aggr) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects