SAP FDT_GET_CLASS_METHOD_METADATA Function Module for FDT: Gets the metadata for the class methods
FDT_GET_CLASS_METHOD_METADATA is a standard fdt get class method metadata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FDT: Gets the metadata for the class methods 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 fdt get class method metadata FM, simply by entering the name FDT_GET_CLASS_METHOD_METADATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDT_REMOTE_SERVICE
Program Name: SAPLFDT_REMOTE_SERVICE
Main Program: SAPLFDT_REMOTE_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FDT_GET_CLASS_METHOD_METADATA 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 'FDT_GET_CLASS_METHOD_METADATA'"FDT: Gets the metadata for the class methods.
EXPORTING
IV_CLASSNAME = "Class Name
IV_METHODNAME = "Method name
* IV_INTERFACENAME = "Interface name
IMPORTING
ET_PARAMETER = "FDT: Table Type for Class's method parameter metadata
ET_EXCEPTION = "Table of Exceptions
EV_PUBLIC = "Is the method Public
EV_STATIC = "Is the Method a static Method
ET_MESSAGE = "FDT: Table type for messages
IMPORTING Parameters details for FDT_GET_CLASS_METHOD_METADATA
IV_CLASSNAME - Class Name
Data type: SEOCLSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_METHODNAME - Method name
Data type: SEOCMPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_INTERFACENAME - Interface name
Data type: SEOITFNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FDT_GET_CLASS_METHOD_METADATA
ET_PARAMETER - FDT: Table Type for Class's method parameter metadata
Data type: FDT_T_CLS_MTD_PARAM_METADATAOptional: No
Call by Reference: No ( called with pass by value option)
ET_EXCEPTION - Table of Exceptions
Data type: SEO_EXCEPTIONSOptional: No
Call by Reference: No ( called with pass by value option)
EV_PUBLIC - Is the method Public
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_STATIC - Is the Method a static Method
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGE - FDT: Table type for messages
Data type: FDT_T_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FDT_GET_CLASS_METHOD_METADATA 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_et_parameter | TYPE FDT_T_CLS_MTD_PARAM_METADATA, " | |||
| lv_iv_classname | TYPE SEOCLSNAME, " | |||
| lv_et_exception | TYPE SEO_EXCEPTIONS, " | |||
| lv_iv_methodname | TYPE SEOCMPNAME, " | |||
| lv_ev_public | TYPE BOOLE_D, " | |||
| lv_iv_interfacename | TYPE SEOITFNAME, " | |||
| lv_ev_static | TYPE BOOLE_D, " | |||
| lv_et_message | TYPE FDT_T_MESSAGE. " |
|   CALL FUNCTION 'FDT_GET_CLASS_METHOD_METADATA' "FDT: Gets the metadata for the class methods |
| EXPORTING | ||
| IV_CLASSNAME | = lv_iv_classname | |
| IV_METHODNAME | = lv_iv_methodname | |
| IV_INTERFACENAME | = lv_iv_interfacename | |
| IMPORTING | ||
| ET_PARAMETER | = lv_et_parameter | |
| ET_EXCEPTION | = lv_et_exception | |
| EV_PUBLIC | = lv_ev_public | |
| EV_STATIC | = lv_ev_static | |
| ET_MESSAGE | = lv_et_message | |
| . " FDT_GET_CLASS_METHOD_METADATA | ||
ABAP code using 7.40 inline data declarations to call FM FDT_GET_CLASS_METHOD_METADATA
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.Search for further information about these or an SAP related objects