SAP ABAP Message Class SHMA (Shared Objects: Management Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-TOO (Application Component) Workbench Tools: Editors, Painters, Modelers
⤷
SHARED_OBJECTS (Package) Shared Objects: Basis Components
⤷
⤷
Attributes
| Message class | SHMA | |
| Short Description | Shared Objects: Management Messages | |
| Changed On | 20110908 | |
| Last Changed At | 153032 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Operation was cancelled | Space: object requires documentation | ||
| 2 | The area attributes were not changed | Space: object requires documentation | ||
| 3 | Access to area class is not possible | Space: object requires documentation | ||
| 4 | The name of an area class should begin with CL_ or /.../CL_ | Space: object requires documentation | ||
| 5 | Syntax error in area class &1: &2, line &3, include &4 | Space: object requires documentation | ||
| 6 | Area class & is consistent | Space: object requires documentation | ||
| 7 | Specify the implementing class. | Space: object requires documentation | ||
| 8 | Specify a root data class. | Space: object requires documentation | ||
| 9 | Instances of the class &1 cannot be created in the shared memory. | Space: object requires documentation | ||
| 10 | The constructor class &1 must implement the interface &2 | Space: object requires documentation | ||
| 11 | Root data class must not be the area class | The short text describes the object sufficiently | ||
| 12 | Specify an area class. | Space: object requires documentation | ||
| 13 | The area class & does not exist. | Space: object requires documentation | ||
| 14 | & is not a valid area class (does not inherit from CL_SHM_AREA). | Space: object requires documentation | ||
| 15 | The Class & already exists. | Space: object requires documentation | ||
| 16 | Error when reading the attributes of the class &. | Space: object requires documentation | ||
| 17 | The class & does not exist | Space: object requires documentation | ||
| 18 | The class & does not exist actively. | Space: object requires documentation | ||
| 19 | Area attribute & has an invalid value &. | Space: object requires documentation | ||
| 20 | Any number of versions is allowed without specification. | Space: object requires documentation | ||
| 21 | Synchronization is only possible for transactional areas. | Space: object requires documentation | ||
| 22 | The area attribute & does not exist. | Space: object requires documentation | ||
| 23 | Value is deleted when selecting 'No Limit'. | Space: object requires documentation | ||
| 24 | Enter a value or select 'No Limit'. | Space: object requires documentation | ||
| 25 | Only one of the two times can be different from zero. | The short text describes the object sufficiently | ||
| 26 | The attributes were saved. | Space: object requires documentation | ||
| 27 | The attributes were deleted. | Space: object requires documentation | ||
| 28 | The area & was created. | Space: object requires documentation | ||
| 29 | The area & was changed. | Space: object requires documentation | ||
| 30 | The area class &1 was copied to &2. | Space: object requires documentation | ||
| 31 | Error when reading &1 of the reference class &2. | Space: object requires documentation | ||
| 32 | The area class cannot be created; error code &. | Space: object requires documentation | ||
| 33 | The method implementations cannot be created; error code &. | Space: object requires documentation | ||
| 34 | The transport request &1 was created. | Space: object requires documentation | ||
| 35 | Change the entry for the area class and the attributes | Space: object requires documentation | ||
| 36 | Change the object directory entry in transaction SHMA | Space: object requires documentation | ||
| 37 | Global class &1 already existed with original in &2 | Space: object requires documentation | ||
| 38 | Class &1 exists with original in &2 (no area class) | Space: object requires documentation | ||
| 39 | Area properties for &1 already exist with original system &2 | Space: object requires documentation | ||
| 40 | Inconsistent global TADIR entries (package) exist for area &1 | Space: object requires documentation | ||
| 41 | Inconsistent global TADIR entries (original) exist for area &1 | Space: object requires documentation | ||
| 42 | Instance &1 in client &2 is already maintained in line &3 of the list. | Space: object requires documentation | ||
| 43 | &1 new instances of &2 were copied from the preassignment. | The short text describes the object sufficiently | ||
| 44 | Autostart is possible for specific clients only. | Space: object requires documentation | ||
| 45 | The preassignment was copied to client &. | The short text describes the object sufficiently | ||
| 46 | The preassignment was copied. | The short text describes the object sufficiently | ||
| 47 | Incorrect call of function module/method &. | Space: object requires documentation | ||
| 48 | The Generation Version &1 Is Not Current (&2). | Space: object requires documentation | ||
| 49 | Autostart is only possible for binding to the application server. | Space: object requires documentation | ||
| 50 | The automatic structuring should be active for displacement. | Space: object requires documentation | ||
| 51 | The area is not configured for automatic structuring. | Space: object requires documentation | ||
| 52 | Entry is only possible for automatic area structuring. | Space: object requires documentation | ||
| 53 | The root data class does not implement IF_SERIALIZABLE_OBJECT. | Space: object requires documentation | ||
| 54 | A version cannot be larger than the whole area. | Space: object requires documentation | ||
| 55 | An explicit specification is only possible for active versioning. | Space: object requires documentation | ||
| 56 | The number cannot be 1 for active versioning. | Space: object requires documentation | ||
| 57 | You must maintain the list of instance names first. | Space: object requires documentation | ||
| 58 | The area is configured for automatic structuring. | Space: object requires documentation | ||
| 59 | This change invalidates all active area instances and locks | The short text describes the object sufficiently | ||
| 60 | An area with this kind of binding must be client dependent | The short text describes the object sufficiently | ||
| 61 | The area attributes for area &1 are missing in table &2. | Space: object requires documentation |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in | 630 |