SAP RSAA_ROUTINE_MULTI_COPY Function Module for
RSAA_ROUTINE_MULTI_COPY is a standard rsaa routine multi copy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rsaa routine multi copy FM, simply by entering the name RSAA_ROUTINE_MULTI_COPY into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAA
Program Name: SAPLRSAA
Main Program: SAPLRSAA
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAA_ROUTINE_MULTI_COPY 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 'RSAA_ROUTINE_MULTI_COPY'".
EXPORTING
* I_T_CODEID = "
* I_ALL_LANGUAGES = ' ' "All Languages
* I_T_AROUT = "
* I_T_ARFIELDS = "
* I_T_AABAP = "Key Figures for Update Rules
* I_T_AABAPINV = "Key Figures for Update Rules
* I_T_AROUTT = "Key for Each Key Figure for Update Rules
I_OBJVERS_SOURCE = "
I_OBJVERS_DESTINATION = "
I_ACTIVE_FLAG = "
EXCEPTIONS
DATABASE_WRITE_ERROR = 1 REQUESTED_STATUS_NOT_FOUND = 2 CODEIDS_OR_TABLES_REQUIRED = 3
IMPORTING Parameters details for RSAA_ROUTINE_MULTI_COPY
I_T_CODEID -
Data type: RSAA_T_CODEIDOptional: Yes
Call by Reference: Yes
I_ALL_LANGUAGES - All Languages
Data type: RS_BOOLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T_AROUT -
Data type: RSAA_T_AROUTOptional: Yes
Call by Reference: Yes
I_T_ARFIELDS -
Data type: RSAA_T_ARFIELDSOptional: Yes
Call by Reference: Yes
I_T_AABAP - Key Figures for Update Rules
Data type: RSAA_T_AABAPOptional: Yes
Call by Reference: Yes
I_T_AABAPINV - Key Figures for Update Rules
Data type: RSAA_T_AABAPOptional: Yes
Call by Reference: Yes
I_T_AROUTT - Key for Each Key Figure for Update Rules
Data type: RSAA_T_AROUTTOptional: Yes
Call by Reference: Yes
I_OBJVERS_SOURCE -
Data type: RSAA_S_AROUT-OBJVERSOptional: No
Call by Reference: Yes
I_OBJVERS_DESTINATION -
Data type: RSAA_S_AROUT-OBJVERSOptional: No
Call by Reference: Yes
I_ACTIVE_FLAG -
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATABASE_WRITE_ERROR - Error writing to the database
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REQUESTED_STATUS_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CODEIDS_OR_TABLES_REQUIRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAA_ROUTINE_MULTI_COPY 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_t_codeid | TYPE RSAA_T_CODEID, " | |||
| lv_database_write_error | TYPE RSAA_T_CODEID, " | |||
| lv_i_all_languages | TYPE RS_BOOL, " ' ' | |||
| lv_i_t_arout | TYPE RSAA_T_AROUT, " | |||
| lv_requested_status_not_found | TYPE RSAA_T_AROUT, " | |||
| lv_i_t_arfields | TYPE RSAA_T_ARFIELDS, " | |||
| lv_codeids_or_tables_required | TYPE RSAA_T_ARFIELDS, " | |||
| lv_i_t_aabap | TYPE RSAA_T_AABAP, " | |||
| lv_i_t_aabapinv | TYPE RSAA_T_AABAP, " | |||
| lv_i_t_aroutt | TYPE RSAA_T_AROUTT, " | |||
| lv_i_objvers_source | TYPE RSAA_S_AROUT-OBJVERS, " | |||
| lv_i_objvers_destination | TYPE RSAA_S_AROUT-OBJVERS, " | |||
| lv_i_active_flag | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSAA_ROUTINE_MULTI_COPY' " |
| EXPORTING | ||
| I_T_CODEID | = lv_i_t_codeid | |
| I_ALL_LANGUAGES | = lv_i_all_languages | |
| I_T_AROUT | = lv_i_t_arout | |
| I_T_ARFIELDS | = lv_i_t_arfields | |
| I_T_AABAP | = lv_i_t_aabap | |
| I_T_AABAPINV | = lv_i_t_aabapinv | |
| I_T_AROUTT | = lv_i_t_aroutt | |
| I_OBJVERS_SOURCE | = lv_i_objvers_source | |
| I_OBJVERS_DESTINATION | = lv_i_objvers_destination | |
| I_ACTIVE_FLAG | = lv_i_active_flag | |
| EXCEPTIONS | ||
| DATABASE_WRITE_ERROR = 1 | ||
| REQUESTED_STATUS_NOT_FOUND = 2 | ||
| CODEIDS_OR_TABLES_REQUIRED = 3 | ||
| . " RSAA_ROUTINE_MULTI_COPY | ||
ABAP code using 7.40 inline data declarations to call FM RSAA_ROUTINE_MULTI_COPY
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_all_languages) | = ' '. | |||
| "SELECT single OBJVERS FROM RSAA_S_AROUT INTO @DATA(ld_i_objvers_source). | ||||
| "SELECT single OBJVERS FROM RSAA_S_AROUT INTO @DATA(ld_i_objvers_destination). | ||||
Search for further information about these or an SAP related objects