SAP RM_RHS_TRANSLATE Function Module for RM: Übersetzung von Risikohierarchien
RM_RHS_TRANSLATE is a standard rm rhs translate 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: Übersetzung von Risikohierarchien 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 rhs translate FM, simply by entering the name RM_RHS_TRANSLATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMRR
Program Name: SAPLRMRR
Main Program: SAPLRMRR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_RHS_TRANSLATE 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_RHS_TRANSLATE'"RM: Übersetzung von Risikohierarchien.
EXPORTING
SOURCE_LANGU = "Quellsprache
TARGET_LANGU = "Zielsprache
EXCEPTIONS
CANCELED_BY_USER = 1
IMPORTING Parameters details for RM_RHS_TRANSLATE
SOURCE_LANGU - Quellsprache
Data type: LWRKOBJ-SOURCELANGOptional: No
Call by Reference: No ( called with pass by value option)
TARGET_LANGU - Zielsprache
Data type: LWRKOBJ-TARGETLANGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELED_BY_USER - Vorgang auf Benutzerwunsch abgebrochen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_RHS_TRANSLATE 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_source_langu | TYPE LWRKOBJ-SOURCELANG, " | |||
| lv_canceled_by_user | TYPE LWRKOBJ, " | |||
| lv_target_langu | TYPE LWRKOBJ-TARGETLANG. " |
|   CALL FUNCTION 'RM_RHS_TRANSLATE' "RM: Übersetzung von Risikohierarchien |
| EXPORTING | ||
| SOURCE_LANGU | = lv_source_langu | |
| TARGET_LANGU | = lv_target_langu | |
| EXCEPTIONS | ||
| CANCELED_BY_USER = 1 | ||
| . " RM_RHS_TRANSLATE | ||
ABAP code using 7.40 inline data declarations to call FM RM_RHS_TRANSLATE
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 SOURCELANG FROM LWRKOBJ INTO @DATA(ld_source_langu). | ||||
| "SELECT single TARGETLANG FROM LWRKOBJ INTO @DATA(ld_target_langu). | ||||
Search for further information about these or an SAP related objects