Hierarchy
⤷ BC-ABA (Application Component) ABAP Runtime Environment
⤷ SBAC (Package) Kernel Objects
Basic Data
Data Element | CLAS |
Short Description | Program class |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CLAS | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | TRCL |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Class |
Medium | 15 | Program class |
Long | 0 | |
Heading | 6 | Class |
Documentation
Definition
The class to which a program is assigned. You can create new classes. They are 4 characters long and must not contain any special characters.
Dependencies
Class names must correspond to the SAP standard. They must exist in Table RCL (program classes) or RCLT (program class names).
Supplementary Documentation - CLASSDE 0001
Use
You can maintain the assignment of data elements to Dictionary authorizations.
This means that authorization for Dictionary maintenance of individual data elements can be restricted to a specified group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSDOM 0001
Use
You can maintain the assignment of domains to Dictionary authorization groups.
This allows you to restrict authorization for Dictionary maintenance of individual domains to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSMCO 0001
Use
You can maintain the assignment of matchcode objects to Dictionary authorization groups.
This allows you to restrict authorization for Dictionary maintenance of individual matchcode objects to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSPC 0001
Use
You can maintain the assignment of pools/clusters to Dictionary authorization groups.
This allows you to restrict authorization for Dictionary maintenance of individual pools/clusters to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSPC 0002
Use
A table should be placed in a pool
- if external access to the table is not required
- if the table is accessed using the primary key
- if the table is very small
A table should not be placed in a pool
- if the table is to be processed from outside the SAP System
- if the table is to be accessed using non-key fields
- if additional indexes are required
- if a database join to other tables is required
- if it is a large table
A table should be placed in a cluster
- if it forms an object together with other tables and this object is generally processed as a complete unit
Example:
The "Order header", "Order item" and "Operations" tables form an object.
- if several records of a table form an object which is generally processed as a complete unit
Example:
Applies to tables containing documentation or text.
- if the table is intended for SAP internal use only, i.e. it is not accessed externally
A table should not be placed in a cluster
- if it is to be processed from outside the SAP System
- if it is to be selected using non-key fields
- if additional indexes are required
- if a database join to other tables is required
- if a table is to be processed separately from other tables in a cluster
Procedure
Examples
Dependencies
Supplementary Documentation - CLASSSPO 0001
Use
You can maintain the assignment of lock objects to Dictionary authorization groups.
This allows you to restrict authorization for Dictionary maintenance of individual lock objects to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSTAB 0001
Use
You can maintain the assignment of tables to Dictionary authorization groups.
This allows you to restrict authorization for Dictionary maintenance of individual tables to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSTABU 0001
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSVIEU 0001
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASSVIEW 0001
Use
You can maintain the assignment of views to view maintenance authorization groups.
This allows you to restrict authorization for table maintenance of individual views to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
Supplementary Documentation - CLASS_52B40001
Use
The form class determines the area in which the form will be used.
Examples
Form Form class
Remuneration statement CEDT
Payroll account CKTO
Payroll journal CLJN
Time statement TEDT
History
Last changed by/on | SAP | 19950209 |
SAP Release Created in | 740 |