SAP FDT_GET_CLASS_METADATA Function Module for FDT: Gets the metadata for the class









FDT_GET_CLASS_METADATA is a standard fdt get class 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 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 metadata FM, simply by entering the name FDT_GET_CLASS_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_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_METADATA'"FDT: Gets the metadata for the class
EXPORTING
IV_CLASSNAME = "Class Name

IMPORTING
ET_METHOD = "Methods of a class
ET_IMPLEMENTED_INTERFACE = "Interfaces
ET_MESSAGE = "FDT: Table type for messages
EV_DESCRIPTION = "Class description
.



IMPORTING Parameters details for FDT_GET_CLASS_METADATA

IV_CLASSNAME - Class Name

Data type: SEOCLSNAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FDT_GET_CLASS_METADATA

ET_METHOD - Methods of a class

Data type: SEO_METHODS
Optional: No
Call by Reference: No ( called with pass by value option)

ET_IMPLEMENTED_INTERFACE - Interfaces

Data type: FDT_T_CLAS_INTERFACE
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGE - FDT: Table type for messages

Data type: FDT_T_MESSAGE
Optional: No
Call by Reference: No ( called with pass by value option)

EV_DESCRIPTION - Class description

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FDT_GET_CLASS_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_method  TYPE SEO_METHODS, "   
lv_iv_classname  TYPE SEOCLSNAME, "   
lv_et_implemented_interface  TYPE FDT_T_CLAS_INTERFACE, "   
lv_et_message  TYPE FDT_T_MESSAGE, "   
lv_ev_description  TYPE STRING. "   

  CALL FUNCTION 'FDT_GET_CLASS_METADATA'  "FDT: Gets the metadata for the class
    EXPORTING
         IV_CLASSNAME = lv_iv_classname
    IMPORTING
         ET_METHOD = lv_et_method
         ET_IMPLEMENTED_INTERFACE = lv_et_implemented_interface
         ET_MESSAGE = lv_et_message
         EV_DESCRIPTION = lv_ev_description
. " FDT_GET_CLASS_METADATA




ABAP code using 7.40 inline data declarations to call FM FDT_GET_CLASS_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!