Hierarchy
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDIC (Package) ABAP Dictionary
Basic Data
Data Element | CLASSSPO |
Short Description | Object class for lock objects |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DYNPCHOICE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | Lock obj. |
Medium | 18 | Lock objects |
Long | 18 | Lock objects |
Heading | 0 |
Documentation
Definition
A lock object is a virtual link of several SAP tables which is used to synchronize simultaneous access by two users to the same set of data (SAP lock concept).
Locks are requested and released in the programming of online transactions by calling certain function modules which are automatically generated from the definition of the lock objects. These lock objects must be explicitly created in the ABAP Dictionary.
To set locks, you must perform the following steps:
- You must define a lock object in the ABAP Dictionary. The name of the lock object should begin with E.
- The function modules for requesting and releasing locks which are created automatically when the lock object is activated must be linked to the programming of the relevant online transactions.
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
History
Last changed by/on | SAP | 19950209 |
SAP Release Created in |