SAP HRIQ_READ_RM_LTXT Function Module for CM: Read Text for Rule Module
HRIQ_READ_RM_LTXT is a standard hriq read rm ltxt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CM: Read Text for Rule Module 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 hriq read rm ltxt FM, simply by entering the name HRIQ_READ_RM_LTXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00RULE
Program Name: SAPLHRPIQ00RULE
Main Program: SAPLHRPIQ00RULE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQ_READ_RM_LTXT 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 'HRIQ_READ_RM_LTXT'"CM: Read Text for Rule Module.
EXPORTING
I_RMID = "Rule Module
* I_LANGU = SY-LANGU "Language Key
IMPORTING
ET_TEXT = "Rule Module Description
IMPORTING Parameters details for HRIQ_READ_RM_LTXT
I_RMID - Rule Module
Data type: PIQRULEMODULEOptional: No
Call by Reference: Yes
I_LANGU - Language Key
Data type: SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HRIQ_READ_RM_LTXT
ET_TEXT - Rule Module Description
Data type: PIQRULEMODLTTL_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRIQ_READ_RM_LTXT 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_rmid | TYPE PIQRULEMODULE, " | |||
| lv_et_text | TYPE PIQRULEMODLTTL_T, " | |||
| lv_i_langu | TYPE SPRAS. " SY-LANGU |
|   CALL FUNCTION 'HRIQ_READ_RM_LTXT' "CM: Read Text for Rule Module |
| EXPORTING | ||
| I_RMID | = lv_i_rmid | |
| I_LANGU | = lv_i_langu | |
| IMPORTING | ||
| ET_TEXT | = lv_et_text | |
| . " HRIQ_READ_RM_LTXT | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_READ_RM_LTXT
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_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects