SAP RFC_GET_FUNCTION_INTERFACE_P Function Module for
RFC_GET_FUNCTION_INTERFACE_P is a standard rfc get function interface p 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 rfc get function interface p FM, simply by entering the name RFC_GET_FUNCTION_INTERFACE_P into the relevant SAP transaction such as SE37 or SE38.
Function Group: RFC1
Program Name: SAPLRFC1
Main Program: SAPLRFC1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RFC_GET_FUNCTION_INTERFACE_P 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 'RFC_GET_FUNCTION_INTERFACE_P'".
EXPORTING
FUNCNAME = "Name of function module
* LANGUAGE = SY-LANGU "Language for parameter texts
* NONE_UNICODE_LENGTH = ' ' "
TABLES
PARAMS_P = "Parameter of function module
* RESUMABLE_EXCEPTIONS = "
EXCEPTIONS
FU_NOT_FOUND = 1 NAMETAB_FAULT = 2
IMPORTING Parameters details for RFC_GET_FUNCTION_INTERFACE_P
FUNCNAME - Name of function module
Data type: TFDIR-FUNCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
LANGUAGE - Language for parameter texts
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
NONE_UNICODE_LENGTH -
Data type: FNKEYDefault: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RFC_GET_FUNCTION_INTERFACE_P
PARAMS_P - Parameter of function module
Data type: RFC_FINT_POptional: No
Call by Reference: No ( called with pass by value option)
RESUMABLE_EXCEPTIONS -
Data type: RSEXCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FU_NOT_FOUND - Function module not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAMETAB_FAULT - Error in opening/editing the NAMETAB
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RFC_GET_FUNCTION_INTERFACE_P 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_funcname | TYPE TFDIR-FUNCNAME, " | |||
| lt_params_p | TYPE STANDARD TABLE OF RFC_FINT_P, " | |||
| lv_fu_not_found | TYPE RFC_FINT_P, " | |||
| lv_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_nametab_fault | TYPE SY, " | |||
| lt_resumable_exceptions | TYPE STANDARD TABLE OF RSEXC, " | |||
| lv_none_unicode_length | TYPE FNKEY. " SPACE |
|   CALL FUNCTION 'RFC_GET_FUNCTION_INTERFACE_P' " |
| EXPORTING | ||
| FUNCNAME | = lv_funcname | |
| LANGUAGE | = lv_language | |
| NONE_UNICODE_LENGTH | = lv_none_unicode_length | |
| TABLES | ||
| PARAMS_P | = lt_params_p | |
| RESUMABLE_EXCEPTIONS | = lt_resumable_exceptions | |
| EXCEPTIONS | ||
| FU_NOT_FOUND = 1 | ||
| NAMETAB_FAULT = 2 | ||
| . " RFC_GET_FUNCTION_INTERFACE_P | ||
ABAP code using 7.40 inline data declarations to call FM RFC_GET_FUNCTION_INTERFACE_P
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 FUNCNAME FROM TFDIR INTO @DATA(ld_funcname). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| DATA(ld_none_unicode_length) | = ' '. | |||
Search for further information about these or an SAP related objects