DBPROC_PROXY - Nachrichten f�r DB Prozedur Proxies
The following messages are stored in message class DBPROC_PROXY: Nachrichten f�r DB Prozedur Proxies.
It is part of development package SDDBPROC_PROXY in software component BC-DWB-DIC. This development package consists of objects that can be grouped under "Back-End Functions for Database Procedure Proxy".
It is part of development package SDDBPROC_PROXY in software component BC-DWB-DIC. This development package consists of objects that can be grouped under "Back-End Functions for Database Procedure Proxy".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error |
| 001 | Internal error: data is not consistent |
| 002 | This function is not available on a system without an SAP HANA database |
| 003 | Not an SAP HANA DB system; runtime objects will not be created |
| 004 | Not an SAP HANA DB system; proxy will be activated without type checks |
| 005 | Internal error: & |
| 010 | No connection to database: connection & unknown |
| 011 | No connection to database: connection & SQL code & SQL message & |
| 012 | SQL error: code & message & |
| 013 | DBI error; see developer trace |
| 014 | Error while closing database connection: SQL code & SQL message & |
| 015 | Database procedure & & does not exist in the catalog |
| 016 | Table type & & does not exist in the catalog |
| 017 | Procedure name is empty |
| 018 | ABAP name is empty |
| 019 | & is protected and cannot be used as parameter name |
| 020 | Parameter name & is too long as ABAP identifier and has been truncated |
| 021 | Parameter name & is not a valid ABAP identifier |
| 022 | Parameter name & is not unique within the procedure |
| 023 | Component name & is too long as ABAP identified and has been truncated |
| 024 | Component name & is not a valid ABAP identifier |
| 025 | Component name & is not unique within parameter & |
| 026 | Name for DB procedure proxy is empty |
| 027 | Name for DB procedure proxy is too long (maximum 30 characters) |
| 028 | Name for DB procedure proxy contains invalid characters |
| 030 | & is not a valid proxy name |
| 031 | Incorrect version (&) for proxy & |
| 032 | & is not a valid proxy (incorrect source format) |
| 033 | Proxy & does not exist in version & |
| 034 | & is not a valid interface pool name |
| 035 | Interface pool & already exists |
| 036 | Interface pool & could not be deleted (rc = &) |
| 037 | Proxy & (version &) could not be deleted |
| 038 | Catalog entry for proxy & could not be written |
| 039 | Interface pool & does not exist |
| 040 | Database type & (&,&) cannot be mapped onto ABAP type |
| 041 | Interface pool & contains syntax errors |
| 042 | Interface pool & could not be created |
| 043 | No authorization for changing interface pool & |
| 044 | Error while activating interface pool & |
| 045 | Interface pool contains syntax error: & & & & |
| 046 | ABAP type could not be determined |
| 047 | Interface pool & could not be deleted |
| 048 | Proxy & already exists |
| 049 | Proxy & does not exist |
| 050 | Proxy & does not match current database procedure & & |
| 051 | Interface pool & cannot be entered in transport request & |
| 052 | Error while saving DB procedure proxy & |
| 053 | Error while reading DB procedure proxy & (source format invalid) |
| 054 | Error while writing the DB procedure proxy & (conversion error) |
| 055 | Transfer tables could not be deleted |
| 056 | Read-only procedures must have an output parameter |
| 057 | INOUT parameters are not supported (&) |
| 058 | Invalid order of parameters (see long text) |
| 060 | Invalid target version: & |
| 061 | Error occurred during activation |
| 062 | Internal error during activation (&) |
| 063 | Warnings occurred during activation |
| 070 | Short text for DB procedure proxy & is empty |
| 071 | Short text for DB procedure proxy & is too long (max. 60 characters) |
| 080 | & is not an active DDIC data element |
| 081 | DDIC data element & does not match parameter & |
| 082 | DDIC data element & does not match component & of parameter & |
| 083 | & is not an active DDIC structure or table |
| 084 | DDIC structure or table & does not match parameter & |
| 085 | DDIC object & has a different number of components than parameter & |
| 086 | Component & from DDIC object & does not match column & of parameter & |
| 099 | Checks successful |
| 100 | Interface pool & was deleted |
| 101 | Proxy & (version &) was deleted |
| 102 | Proxy & (version &) was saved |
| 103 | Interface pool & was created active |
| 104 | Interface pool & was created inactive |
| 105 | Catalog entry for proxy & was written |
| 106 | Catalog entry for proxy & was deleted |
| 107 | Transfer tables were created |
| 108 | Version validation was activated |
| 109 | Version validation could not be deactivated |
| 110 | Proxy & is inconsistent and must therefore be re-activated |
| 111 | Transfer table created: & |
| 112 | Transfer table deleted: & |
| 114 | Database procedures cannot be called without parameters |
| 120 | Error while setting lock for proxy & |
| 121 | Error while generating a UUID |
| 122 | Error while setting lock for interface & |
| 123 | Error while generating interface & |
| 124 | API can only delete generated proxies using the API |
| 125 | Parameter & does not exist in proxy & |
| 126 | Type description does not match parameter & for proxy & |
| 127 | Type "&" cannot be used for database procedure proxies |
| 128 | Name & is not allowed for an interface pool |
| 129 | Input help could not be found |
| 130 | Transfer table could not be created: & |
| 131 | Version validation could not be activated |
| 132 | Version validation was deactivated |