Object Types and Object Type Groups 

Use

Each repository object belongs to a certain object type. For example, the object type DYNP stands for screen, OO stands for class method and so on. Object type groups are hierarchically organized groups of repository object types, which can be processed by the Classification Toolset.

Features

Object Type Groups

Object type groups define the domain to which a characteristic can be applied. They are maintained by means of the Object Type Group Builder (transaction SOTG).

Object Types

You can use the Classification Toolset to process all main object types. Subtypes can be processed if they are implemented in the object type framework.

Main Objects

Main objects can belong to any R3TR object type or can be function modules (type FUNC). They are specified by their type and name. For example, PROG for Program, CLAS for Classes and DIAL for Dialog Modules.

Subtypes

The subobjects implemented in the Classification Toolset are usually LIMU objects, for example DYNP and CUAD.

The following subtypes are implemented in the Classification Toolset at present:

Object type	Technical name
Class Method	OO
Class Attribute	OA
Class Event	OE
Interface Method	IO
Interface Attribute	IA
User Interface	CUAD
Screen	DYNP
Secondary Index	INDX
Local Class	PL
Local Interface	PN
Local Class Method	OLD
Local Interface Method	OLN
PAI Module	PM
PBO Module	PO
Subroutine	PU
Page/Controller of a BSP Application	WAPP
Definition (Web Dynpro)	WDYD
Controller (Web Dynpro)	WDYC
View (Web Dynpro)	WDYV

There are also subtypes (like local classes) that do not correspond to any transport object. In such cases, the workbench-type descriptor (up to 3 characters long) is used.

Subobjects are specified by four components: type and name of the main object followed by type and name of the subobject.

FUNC FUNCTION_EXISTS for a function module,

CLAS CL_GUI_ALV_GRID for an ALV grid class,

CLAS CL_GUI_ALV_GRID OO SET_TABLE_FOR_FIRST_DISPLAY for a method of a class.