SAP CL_GUI_ECATT_DEBUG OO Class - eCATT - Debugger Display
CL_GUI_ECATT_DEBUG is a standard SAP object class available within R/3 SAP systems depending on your version and release level. You can view/maintain the class details by entering its name into the relevant SAP transactions such as SE24, SE80 or even SE84. Below is the documentation available for class CL_GUI_ECATT_DEBUG including details of:
- Interface class implementations
- Inheritance details
- Methods defined within class ( including link to full details )
- Attributes ( including initial values )
- Class Events
Inheritance
This OO class has a superclass assigned to it, which means it will inherit its objects and methods. The superclass for CL_GUI_ECATT_DEBUG is CL_GUI_ECATT_MODULE_EDITORMethod list of CL_GUI_ECATT_DEBUG SAP class
A method is a coding block that performs a certain procedure (i.e. ABAP functionality) on an object within the overall SAP class. In simple terms if the object is an SAP database table a method could be the procedure to add a record or to delete a record. If you are new to OO in many respects, the implementation of a method is similar to a function module and can be called in a very similar way using CALL METHOD.
Instead of "CALL FUNCTION", Methods are referenced using the following syntax: CALL METHOD =>methodname EXPORTING/IMPORTING...
| Method Name | Description | Visability |
| CONSTRUCTOR | Constructor | Public |
| CALL METHOD cl_gui_ecatt_debug=>CONSTRUCTOR...more details | ||
| CREATE_SPLITTER | Create Main Splitter | Protected |
| CALL METHOD cl_gui_ecatt_debug=>CREATE_SPLITTER...more details | ||
| CREATE_UI_DEBUG_TREE | Generate Debugger Tree | Public |
| CALL METHOD cl_gui_ecatt_debug=>CREATE_UI_DEBUG_TREE...more details | ||
| FREE | Release Instances | Public |
| CALL METHOD cl_gui_ecatt_debug=>FREE...more details | ||
| SET_PARAMS_NEW | Pass New Parameters | Public |
| CALL METHOD cl_gui_ecatt_debug=>SET_PARAMS_NEW...more details | ||
CL_GUI_ECATT_DEBUG attributes
List of attributes within class CL_ABAP_CHAR_UTILITIES. These can be referenced using the following syntax CL_ABAP_CHAR_UTILITIES=>. Although depending on where you are inserting the ABAP code you do need to check if the attribute is public or private.
| Name | Level | Description | Initial Value | Type | Visability |
| CC_PARAM | Instance Attribute | Container for UI_PARAMS | LIKE CL_GUI_CONTAINER | Private | |
| CC_SPLITTER_H | Instance Attribute | Container for SPLITTER_H | LIKE CL_GUI_CONTAINER | Private | |
| CC_SPLITTER_V | Instance Attribute | Container for SPLITTER_V | LIKE CL_GUI_CUSTOM_CONTAINER | Private | |
| CC_TREE | Instance Attribute | Container for UI_DEBUG_TREE | LIKE CL_GUI_CONTAINER | Private | |
| CC_XML | Instance Attribute | Container for UI_XML | LIKE CL_GUI_CONTAINER | Private | |
| DEBUG | Instance Attribute | Debug Handling Class | LIKE CL_APL_ECATT_DEBUG | Protected | |
| SPLITTER_H | Instance Attribute | Splitter Parameter/XML Editor | LIKE CL_GUI_SPLITTER_CONTAINER | Protected | |
| SPLITTER_V | Instance Attribute | Main Splitter | LIKE CL_GUI_SPLITTER_CONTAINER | Protected | |
| UI_DEBUG_TREE | Instance Attribute | Log Display | LIKE CL_GUI_ECATT_LOG | Public |
Links to Related Class(s)
CL_GUI_E...Full list of available SAP object classes
Search for further information about these or an SAP related objects