SAP RM_SUBSCREEN_GENERATE Function Module for RM: Merkmaleingabe (Subscreen und BDT-Steuerungseinträge generieren)
RM_SUBSCREEN_GENERATE is a standard rm subscreen generate 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: Merkmaleingabe (Subscreen und BDT-Steuerungseinträge generieren) 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 subscreen generate FM, simply by entering the name RM_SUBSCREEN_GENERATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMGEN
Program Name: SAPLRMGEN
Main Program: SAPLRMGEN
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_SUBSCREEN_GENERATE 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_SUBSCREEN_GENERATE'"RM: Merkmaleingabe (Subscreen und BDT-Steuerungseinträge generieren).
EXPORTING
I_RMBID = "RM-Bereich
EXCEPTIONS
ERROR = 1 SUCCESS = 2
IMPORTING Parameters details for RM_SUBSCREEN_GENERATE
I_RMBID - RM-Bereich
Data type: JBRRMBBF-RMBIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUCCESS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_SUBSCREEN_GENERATE 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_error | TYPE STRING, " | |||
| lv_i_rmbid | TYPE JBRRMBBF-RMBID, " | |||
| lv_success | TYPE JBRRMBBF. " |
|   CALL FUNCTION 'RM_SUBSCREEN_GENERATE' "RM: Merkmaleingabe (Subscreen und BDT-Steuerungseinträge generieren) |
| EXPORTING | ||
| I_RMBID | = lv_i_rmbid | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| SUCCESS = 2 | ||
| . " RM_SUBSCREEN_GENERATE | ||
ABAP code using 7.40 inline data declarations to call FM RM_SUBSCREEN_GENERATE
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 RMBID FROM JBRRMBBF INTO @DATA(ld_i_rmbid). | ||||
Search for further information about these or an SAP related objects