SAP R2_HELPVALUES_GET Function Module for
R2_HELPVALUES_GET is a standard r2 helpvalues get 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 r2 helpvalues get FM, simply by entering the name R2_HELPVALUES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_DRIVER_R2
Program Name: SAPLBBP_BD_DRIVER_R2
Main Program: SAPLBBP_BD_DRIVER_R2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function R2_HELPVALUES_GET 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 'R2_HELPVALUES_GET'".
EXPORTING
* OBJTYPE = ' ' "
* OBJNAME = ' ' "
METHOD = "
PARAMETER = "
* FIELD = "
* MAX_OF_ROWS = 0 "
IMPORTING
RETURN = "
TABLES
SELECTION_FOR_HELPVALUES = "
HELPVALUES = "
VALUES_FOR_FIELD = "
DESCRIPTION_FOR_HELPVALUES = "
* CONTROL_RECORD = "
IMPORTING Parameters details for R2_HELPVALUES_GET
OBJTYPE -
Data type: BAPIF4A-OBJTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJNAME -
Data type: BAPIF4A-OBJNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
METHOD -
Data type: BAPIF4A-METHODOptional: No
Call by Reference: No ( called with pass by value option)
PARAMETER -
Data type: BAPIF4A-PARAMOptional: No
Call by Reference: No ( called with pass by value option)
FIELD -
Data type: BAPIF4A-FIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
MAX_OF_ROWS -
Data type: BAPIF4A-MAX_ROWSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for R2_HELPVALUES_GET
RETURN -
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for R2_HELPVALUES_GET
SELECTION_FOR_HELPVALUES -
Data type: BAPIF4BOptional: No
Call by Reference: No ( called with pass by value option)
HELPVALUES -
Data type: BAPIF4COptional: No
Call by Reference: No ( called with pass by value option)
VALUES_FOR_FIELD -
Data type: BAPIF4DOptional: No
Call by Reference: No ( called with pass by value option)
DESCRIPTION_FOR_HELPVALUES -
Data type: BAPIF4EOptional: No
Call by Reference: No ( called with pass by value option)
CONTROL_RECORD -
Data type: BBP_CONTROL_RECORDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for R2_HELPVALUES_GET 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_return | TYPE BAPIRETURN, " | |||
| lv_objtype | TYPE BAPIF4A-OBJTYPE, " SPACE | |||
| lt_selection_for_helpvalues | TYPE STANDARD TABLE OF BAPIF4B, " | |||
| lv_objname | TYPE BAPIF4A-OBJNAME, " SPACE | |||
| lt_helpvalues | TYPE STANDARD TABLE OF BAPIF4C, " | |||
| lv_method | TYPE BAPIF4A-METHOD, " | |||
| lt_values_for_field | TYPE STANDARD TABLE OF BAPIF4D, " | |||
| lv_parameter | TYPE BAPIF4A-PARAM, " | |||
| lt_description_for_helpvalues | TYPE STANDARD TABLE OF BAPIF4E, " | |||
| lv_field | TYPE BAPIF4A-FIELD, " | |||
| lt_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, " | |||
| lv_max_of_rows | TYPE BAPIF4A-MAX_ROWS. " 0 |
|   CALL FUNCTION 'R2_HELPVALUES_GET' " |
| EXPORTING | ||
| OBJTYPE | = lv_objtype | |
| OBJNAME | = lv_objname | |
| METHOD | = lv_method | |
| PARAMETER | = lv_parameter | |
| FIELD | = lv_field | |
| MAX_OF_ROWS | = lv_max_of_rows | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| SELECTION_FOR_HELPVALUES | = lt_selection_for_helpvalues | |
| HELPVALUES | = lt_helpvalues | |
| VALUES_FOR_FIELD | = lt_values_for_field | |
| DESCRIPTION_FOR_HELPVALUES | = lt_description_for_helpvalues | |
| CONTROL_RECORD | = lt_control_record | |
| . " R2_HELPVALUES_GET | ||
ABAP code using 7.40 inline data declarations to call FM R2_HELPVALUES_GET
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 OBJTYPE FROM BAPIF4A INTO @DATA(ld_objtype). | ||||
| DATA(ld_objtype) | = ' '. | |||
| "SELECT single OBJNAME FROM BAPIF4A INTO @DATA(ld_objname). | ||||
| DATA(ld_objname) | = ' '. | |||
| "SELECT single METHOD FROM BAPIF4A INTO @DATA(ld_method). | ||||
| "SELECT single PARAM FROM BAPIF4A INTO @DATA(ld_parameter). | ||||
| "SELECT single FIELD FROM BAPIF4A INTO @DATA(ld_field). | ||||
| "SELECT single MAX_ROWS FROM BAPIF4A INTO @DATA(ld_max_of_rows). | ||||
Search for further information about these or an SAP related objects