General properties of ABAP Classes / Interfaces
Every day you create or change ABAP class in class builder. When you activate your change, have you noticed a series of objects with several “=” in the middle part of each?
Technically speaking, an ABAP class consists of several parts. In order to figure them out, I just create a simple class with the following source code:
CLASS zcl_abap_class DEFINITION
PUBLIC FINAL CREATE PUBLIC .
PUBLIC SECTION.
DATA public_attribure TYPE i .
TYPES:BEGIN OF ty_global,
name TYPE string,
score TYPE i,
END OF ty_global.
METHODS public .
protected section.
data PROTECTED_ATTRIBUTE type I .
methods PROTECTED .
PRIVATE SECTION.
DATA private_attribute TYPE i .
METHODS private .
ENDCLASS.
CLASS ZCL_ABAP_CLASS IMPLEMENTATION.
METHOD private.
ENDMETHOD.
method PROTECTED.
endmethod.
METHOD public.
ENDMETHOD.
ENDCLASS.
I have also generated a local test class for it via SE80. After activation, look into corresponding entry in TRDIR.
The object name under column NAME could be opened via SE38. Take CCAU for example:
So CCAU contains the source code of local test class implementation:
Here below is the list of each part and its meaning:
Part Name | Part meaning |
---|---|
CCAU | contains the source code of local test class implementation |
CCDEF | Class-Relevant Local Definitions, contains the definitions of local classes inside the public class |
CCIMP | It contains the implementation for those local classes which definitions are stored in the Definitions-Include |
CCMAC | contains the macros of the public class |
CI | source code of private section |
CO | source code of protected section |
CU | source code of public section |
CP | open it in SE38, it will automatically navigate to class builder |
CT | open it in SE38, it will automatically navigate to class builder |
CMXXX | source code of each method |
The constant of part name is defined in type group SEOP:
If you need to get the part name of a given class via ABAP code, you can use utility class CL_OO_CLASSNAME_SERVICE. There are corresponding getter method for each kind of part defined.
For example, if you need to get the part name of all methods of class CL_CRM_BOL_CORE, just set breakpoint in method CL_OO_CLASSNAME_SERVICE =>GET_ALL_METHOD_INCLUDES, and open the class CL_CRM_BOL_CORE in SE24, and click “Source Code-Based” button:
Here you can find the name class part for each method are populated with one incremental step in hexadecimal.
Hi,
I always wondered what are those funny things. Now i know 🙂
Really good thought. Appreciated your efforts. Good to know more things in detailed. 🙂
Regards,
Krishna Chaitanya.
Good. Few of the details where known, but really good to bring out it as blog.
Nice one dear.....
Regards,
Dadarao
Thanks for sharing usefull info......
Hi Jerry,
Nice collection. Good job!
I found the current blog title ("General properties of ABAP Classes / Interfaces") slightly misleading. Something like "Subobjects of ABAP Classes / Interfaces" or similar would describe your blog better.
Cheers,
Peter
Hi Jerry,
Thank you very much. Very useful content.
Regards,
Raghu B
Very well explained. Thank you for sharing.
We have some old orphaned entrys of deleted classes in the TRDIR-Table. Exists any Report to reorganize this entrys?
Regards
Siegfried
Simply entering the following OK code, pressing enter, and chosing the class pool button afterwards shows the same ...
B.t.w., those "parts" are called include programs 😉
Nice hidden feature, didn't know it before. It's quite useful!
Show_Clif(fhanger) 🙂
Hello Horst,
Never know this hidden feature till today. Thanks a lot for sharing!
Best regards,
Jerry
"Show_clif" -> Very New Learning!!! - Thanks Horst Keller!!! 🙂
& Thanks Jerry Wang for another Interesting Analysis and Blog! 😀
Cheers,
Kripa Rangachari.
Is there any plan to replace the classical ABAP editor to the new one in show_clif?
Thanks,
Peter
Useful Content..
A class is used to specify the form of an object and it combines data representation and methods for manipulating that data into one neat package. The data and functions within a class are called members of the class.
ABAP Objects makes this possible by using interfaces. Interfaces are independent structures that you can implement in a class to extend the scope of that class. The class-specific scope of a class is defined by its components and visibility sections.
Thank You Very Much…Jerry WangÂ
 
Very useful information , Thanks for sharing this 🙂
In REPOSRC table we find another part name for classes like CL, CA, and CS.
Besides that, there can be found multiple more endings.
Can somebody explain them?
And some reports without any ending (see screenshot below).