SAP HELP_REQUEST_FOR_PR_OTYPE Function Module for
HELP_REQUEST_FOR_PR_OTYPE is a standard help request for pr otype 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 help request for pr otype FM, simply by entering the name HELP_REQUEST_FOR_PR_OTYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVH
Program Name: SAPLGJVH
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HELP_REQUEST_FOR_PR_OTYPE 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 'HELP_REQUEST_FOR_PR_OTYPE'".
EXPORTING
BUKRS = "
IMPORTING
SELECT_VALUE = "
IMPORTING Parameters details for HELP_REQUEST_FOR_PR_OTYPE
BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HELP_REQUEST_FOR_PR_OTYPE
SELECT_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HELP_REQUEST_FOR_PR_OTYPE 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_bukrs | TYPE T001-BUKRS, " | |||
| lv_select_value | TYPE T001. " |
|   CALL FUNCTION 'HELP_REQUEST_FOR_PR_OTYPE' " |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| IMPORTING | ||
| SELECT_VALUE | = lv_select_value | |
| . " HELP_REQUEST_FOR_PR_OTYPE | ||
ABAP code using 7.40 inline data declarations to call FM HELP_REQUEST_FOR_PR_OTYPE
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 BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
Search for further information about these or an SAP related objects