SAP ABAP Message Class SVMCRT (VMC Runtime)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-VMC (Application Component) Virtual Machine Container
⤷
SVMCRT (Package) VM Container Runtime
⤷
⤷
Attributes
| Message class | SVMCRT | |
| Short Description | VMC Runtime | |
| Changed On | 20141121 | |
| Last Changed At | 124020 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Name &1 is not compatible with 7-Bit US-ASCII | The short text describes the object sufficiently | ||
| 2 | Parameter &1 is not a valid module name | Space: object requires documentation | ||
| 3 | Module &2 is locked by user &1 | The short text describes the object sufficiently | ||
| 4 | Installation of module &1 has failed | The short text describes the object sufficiently | ||
| 5 | Module &1 has been successfully installed | The short text describes the object sufficiently | ||
| 6 | Package &1 or request/task &2 is invalid | The short text describes the object sufficiently | ||
| 7 | Internal error (error code: &1) | The short text describes the object sufficiently | ||
| 8 | Request/task &1 cannot be used | The short text describes the object sufficiently | ||
| 9 | No authorization to process Java modules | The short text describes the object sufficiently | ||
| 10 | File "&1" cannot be read | The short text describes the object sufficiently | ||
| 11 | VMC Container is not active on this application server | The short text describes the object sufficiently | ||
| 12 | File &1 could not be created on the application server | The short text describes the object sufficiently | ||
| 13 | An entry in the object repository (TADIR) could not be created | Space: object requires documentation | ||
| 14 | Module &1 successfully deleted | The short text describes the object sufficiently | ||
| 15 | Request/task &1 is invalid | The short text describes the object sufficiently | ||
| 16 | Module &1 is not available | The short text describes the object sufficiently | ||
| 17 | Configuration &1/&2 (version &3) successfully uploaded | The short text describes the object sufficiently | ||
| 18 | Configuration name &1/&2 is invalid | The short text describes the object sufficiently | ||
| 19 | No authroization to process Java configurations | The short text describes the object sufficiently | ||
| 20 | Configuration &2/&3 (Version &4) is locked by user &1 | The short text describes the object sufficiently | ||
| 21 | Upload of configuration &1/&2 (version &3) has failed | The short text describes the object sufficiently | ||
| 22 | Parameter &1 is not a valid component name | The short text describes the object sufficiently | ||
| 23 | Installation of configuration &1/&2 (&3) has failed (error &4) | The short text describes the object sufficiently | ||
| 24 | No entry could be created in TADIR for object &1 | The short text describes the object sufficiently | ||
| 25 | At least one Java object could not be included in task &1 | The short text describes the object sufficiently | ||
| 26 | Error in the change validation of the Java transport objects | The short text describes the object sufficiently | ||
| 27 | Java objects cannot be registered for the transport | The short text describes the object sufficiently | ||
| 28 | This function is not yet supported by a current kernel | Space: object requires documentation | ||
| 29 | Configuration &1/&2 (&3) for deletion not found | The short text describes the object sufficiently | ||
| 30 | VMC administration authorization required for the upload | The short text describes the object sufficiently | ||
| 31 | No deployment possible because upgrade or update is running | The short text describes the object sufficiently | ||
| 32 | Upgrade/update status could not be determined | The short text describes the object sufficiently |
History
| Last changed on/by | 20141121 | SAP | |
| SAP Release Created in | 700 |