SAP RM_RC_SAVE_VERSION_IN_ONLINE Function Module for RM: SAVE der VERSION eines erweiterten Risikoträgers im ONLINE
RM_RC_SAVE_VERSION_IN_ONLINE is a standard rm rc save version in online SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: SAVE der VERSION eines erweiterten Risikoträgers im ONLINE 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 rm rc save version in online FM, simply by entering the name RM_RC_SAVE_VERSION_IN_ONLINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMY2
Program Name: SAPLRMY2
Main Program: SAPLRMY2
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_RC_SAVE_VERSION_IN_ONLINE 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 'RM_RC_SAVE_VERSION_IN_ONLINE'"RM: SAVE der VERSION eines erweiterten Risikoträgers im ONLINE.
EXPORTING
I_RIDXRT = "
* I_KOET_FIRST = "Laufzeitbeginn
* I_KOET_LAST = "Laufzeitende
CHANGING
C_DGUELTAB = "
EXCEPTIONS
CANCELLED_BY_USER = 1 WRONG_MODE = 2 ERROR_WHILE_SAVING = 3
IMPORTING Parameters details for RM_RC_SAVE_VERSION_IN_ONLINE
I_RIDXRT -
Data type: JBRDBKO-RIDXRTOptional: No
Call by Reference: No ( called with pass by value option)
I_KOET_FIRST - Laufzeitbeginn
Data type: JBRDBKOETOptional: Yes
Call by Reference: Yes
I_KOET_LAST - Laufzeitende
Data type: JBRDBKOETOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for RM_RC_SAVE_VERSION_IN_ONLINE
C_DGUELTAB -
Data type: JBRDBKO-DGUELTABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED_BY_USER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_MODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_WHILE_SAVING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_RC_SAVE_VERSION_IN_ONLINE 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_ridxrt | TYPE JBRDBKO-RIDXRT, " | |||
| lv_c_dgueltab | TYPE JBRDBKO-DGUELTAB, " | |||
| lv_cancelled_by_user | TYPE JBRDBKO, " | |||
| lv_wrong_mode | TYPE JBRDBKO, " | |||
| lv_i_koet_first | TYPE JBRDBKOET, " | |||
| lv_i_koet_last | TYPE JBRDBKOET, " | |||
| lv_error_while_saving | TYPE JBRDBKOET. " |
|   CALL FUNCTION 'RM_RC_SAVE_VERSION_IN_ONLINE' "RM: SAVE der VERSION eines erweiterten Risikoträgers im ONLINE |
| EXPORTING | ||
| I_RIDXRT | = lv_i_ridxrt | |
| I_KOET_FIRST | = lv_i_koet_first | |
| I_KOET_LAST | = lv_i_koet_last | |
| CHANGING | ||
| C_DGUELTAB | = lv_c_dgueltab | |
| EXCEPTIONS | ||
| CANCELLED_BY_USER = 1 | ||
| WRONG_MODE = 2 | ||
| ERROR_WHILE_SAVING = 3 | ||
| . " RM_RC_SAVE_VERSION_IN_ONLINE | ||
ABAP code using 7.40 inline data declarations to call FM RM_RC_SAVE_VERSION_IN_ONLINE
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.| "SELECT single RIDXRT FROM JBRDBKO INTO @DATA(ld_i_ridxrt). | ||||
| "SELECT single DGUELTAB FROM JBRDBKO INTO @DATA(ld_c_dgueltab). | ||||
Search for further information about these or an SAP related objects