SAP ECATT_CLASS_EXISTS Function Module for









ECATT_CLASS_EXISTS is a standard ecatt class exists 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 ecatt class exists FM, simply by entering the name ECATT_CLASS_EXISTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: ECATT_REMOTE_EXECUTE
Program Name: SAPLECATT_REMOTE_EXECUTE
Main Program: SAPLECATT_REMOTE_EXECUTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ECATT_CLASS_EXISTS 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 'ECATT_CLASS_EXISTS'"
EXPORTING
IM_TYPENAME = "Object Type Name
* IM_COMPONENT = "Full Component Name
* IM_STATIC = ' ' "
* IM_CONSTANT = ' ' "

IMPORTING
EX_EXISTS = "'X' Class Exists, ' ' Class Does Not Exist
EX_IS_REDEFINED = "
EX_COMP_EXISTS = "
EX_COMP_IS_STATIC = "
EX_COMP_IS_CONST = "
EX_COMP_TYPE = "Type of Component 'M' Method, 'A' Attribute
EX_ATTR_READ_ONLY = "
EX_IS_INTERFACE = "
EX_IS_INHERITED = "
EX_ALIAS_FOR = "

EXCEPTIONS
ERROR_SEARCHING_TYPE = 1
.



IMPORTING Parameters details for ECATT_CLASS_EXISTS

IM_TYPENAME - Object Type Name

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

IM_COMPONENT - Full Component Name

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

IM_STATIC -

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_CONSTANT -

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ECATT_CLASS_EXISTS

EX_EXISTS - 'X' Class Exists, SPACE Class Does Not Exist

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

EX_IS_REDEFINED -

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

EX_COMP_EXISTS -

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

EX_COMP_IS_STATIC -

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

EX_COMP_IS_CONST -

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

EX_COMP_TYPE - Type of Component 'M' Method, 'A' Attribute

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

EX_ATTR_READ_ONLY -

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

EX_IS_INTERFACE -

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

EX_IS_INHERITED -

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

EX_ALIAS_FOR -

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

EXCEPTIONS details

ERROR_SEARCHING_TYPE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ECATT_CLASS_EXISTS 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_ex_exists  TYPE CHAR1, "   
lv_im_typename  TYPE SEOCLSNAME, "   
lv_error_searching_type  TYPE SEOCLSNAME, "   
lv_ex_is_redefined  TYPE CHAR1, "   
lv_im_component  TYPE SEOCPDNAME, "   
lv_ex_comp_exists  TYPE CHAR1, "   
lv_im_static  TYPE CHAR1, "   SPACE
lv_ex_comp_is_static  TYPE CHAR1, "   
lv_im_constant  TYPE CHAR1, "   SPACE
lv_ex_comp_is_const  TYPE CHAR1, "   
lv_ex_comp_type  TYPE CHAR1, "   
lv_ex_attr_read_only  TYPE CHAR1, "   
lv_ex_is_interface  TYPE CHAR1, "   
lv_ex_is_inherited  TYPE CHAR1, "   
lv_ex_alias_for  TYPE CHAR1. "   

  CALL FUNCTION 'ECATT_CLASS_EXISTS'  "
    EXPORTING
         IM_TYPENAME = lv_im_typename
         IM_COMPONENT = lv_im_component
         IM_STATIC = lv_im_static
         IM_CONSTANT = lv_im_constant
    IMPORTING
         EX_EXISTS = lv_ex_exists
         EX_IS_REDEFINED = lv_ex_is_redefined
         EX_COMP_EXISTS = lv_ex_comp_exists
         EX_COMP_IS_STATIC = lv_ex_comp_is_static
         EX_COMP_IS_CONST = lv_ex_comp_is_const
         EX_COMP_TYPE = lv_ex_comp_type
         EX_ATTR_READ_ONLY = lv_ex_attr_read_only
         EX_IS_INTERFACE = lv_ex_is_interface
         EX_IS_INHERITED = lv_ex_is_inherited
         EX_ALIAS_FOR = lv_ex_alias_for
    EXCEPTIONS
        ERROR_SEARCHING_TYPE = 1
. " ECATT_CLASS_EXISTS




ABAP code using 7.40 inline data declarations to call FM ECATT_CLASS_EXISTS

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.

 
 
 
 
 
 
DATA(ld_im_static) = ' '.
 
 
DATA(ld_im_constant) = ' '.
 
 
 
 
 
 
 


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!