SAP ABAP Message Class SVMCRT_LOCKING (VMC Locking)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-VMC (Application Component) Virtual Machine Container
⤷
SVMCRT (Package) VM Container Runtime
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-VMC (Application Component) Virtual Machine Container⤷
SVMCRT (Package) VM Container Runtime 
Attributes
| Message class |  |
SVMCRT_LOCKING |
| Short Description |  |
VMC Locking |
| Changed On |  |
20130531 |
| Last Changed At |  |
091623 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Implementation class "&1" could not be found | The short text describes the object sufficiently | |
| 2 | 001 |
Class "&1" could not be instantiated | The short text describes the object sufficiently | |
| 3 | 002 |
Class "&1" could not be accessed | The short text describes the object sufficiently | |
| 4 | 003 |
Cannot be remove the locks for user "&1" | The short text describes the object sufficiently | |
| 5 | 004 |
Cannot create the user of the lock | The short text describes the object sufficiently | |
| 6 | 005 |
Cannot lock [&1, &2, &3, &4], being used by others | The short text describes the object sufficiently | |
| 7 | 006 |
Cannot lock [&1, &2, &3, &4], still being used | The short text describes the object sufficiently | |
| 8 | 007 |
Cannot lock [&1, &2, &3, &4], still partially being used | The short text describes the object sufficiently | |
| 9 | 008 |
Cannot lock at least one of &1 (&2); being used by other users | The short text describes the object sufficiently | |
| 10 | 009 |
Cannot lock at least one of &1 (&2); still in use | The short text describes the object sufficiently | |
| 11 | 010 |
Cannot lock at least one of &1 (&2); partially in use | The short text describes the object sufficiently | |
| 12 | 011 |
Cannot lock [&1, &2, &3, &4], reason: &5 (ret. = &6) | The short text describes the object sufficiently | |
| 13 | 012 |
Cannot lock at least one of &1 (&2); reason: &3 (ret. = &4) | The short text describes the object sufficiently | |
| 14 | 013 |
Cannot unlock [&1, &2, &3, &4], reason: &5 (ret. = &6) | The short text describes the object sufficiently | |
| 15 | 014 |
Cannot unlock at least one of &1 (&2); reason: &3 (ret. = &4) | The short text describes the object sufficiently | |
| 16 | 015 |
Cannot cancel all cumulative locks [&1, &2, &3, &4] | The short text describes the object sufficiently | |
| 17 | 016 |
Problem: &4 (return code = &5) | The short text describes the object sufficiently | |
| 18 | 017 |
Cannot cancel all cumulative locks for at least one of &1 (&2) | The short text describes the object sufficiently | |
| 19 | 018 |
Problem: &2 (return code = &3) | The short text describes the object sufficiently | |
| 20 | 019 |
Cannot unlock everything for &1; reason: &2 (return code = &3) | The short text describes the object sufficiently | |
| 21 | 020 |
List for &1 / &2 is not available; reason: &3 (return code = &4) | The short text describes the object sufficiently | |
| 22 | 021 |
Cannot create unique lock owner; reason: &1 (return code = &2) | The short text describes the object sufficiently | |
| 23 | 022 |
Namespace "&1" with description "&2" cannot be resolved | The short text describes the object sufficiently | |
| 24 | 023 |
Namespace "&1" is reserved for description "&3" | The short text describes the object sufficiently | |
| 25 | 024 |
Namespace "&1" cannot be resolved due to an error | The short text describes the object sufficiently | |
| 26 | 025 |
No connection to lock server | The short text describes the object sufficiently | |
| 27 | 026 |
Cannot determine the lock owner | The short text describes the object sufficiently | |
| 28 | 027 |
The implementation "&1" is not available | The short text describes the object sufficiently | |
| 29 | 028 |
The namespace "&1" cannot be deleted due to an error | The short text describes the object sufficiently | |
| 30 | 029 |
The namespace "&1" has not been registered | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 710 |
