SCA_DS - Object provider
The following messages are stored in message class SCA_DS: Object provider.
It is part of development package SCA_DS_COMMON in software component BC-DWB-TOO-ATF. This development package consists of objects that can be grouped under "Commonly used objects".
It is part of development package SCA_DS_COMMON in software component BC-DWB-TOO-ATF. This development package consists of objects that can be grouped under "Commonly used objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Not authorized to access object_provider &1 |
| 001 | Object provider &1 does not exist |
| 002 | Object provider &1 has not the expected type |
| 003 | Access to object provider &1 failed |
| 004 | &1 does not exist. Please enter an existing system group |
| 005 | Please enter a valid system id |
| 006 | Object provider & has no RFC destination assigned |
| 007 | Object provider &1 already exists |
| 008 | System group &1 already exists |
| 009 | No valid generic RFC destination provided |
| 010 | No base ID provided |
| 011 | ID &1 is not valid for object provider creation |
| 012 | The current checked system's SAP_BASIS release is not supported |
| 013 | The current checked system's SAP_BASIS release is not supported |
| 050 | Insufficient authorization |
| 051 | &1&2&3 |
| 055 | Unexpected return code &2 at call of &1 |
| 056 | Remote function error: &1&2&3&4 |
| 057 | Remote call of &1: Method supported from version &2 onwards only |
| 058 | RFC destination &1 does not exist |
| 059 | Connection test for RFC destination &1 failed (see longtext) |
| 060 | A name starting with &1 is not allowed |
| 061 | Call of object provider stub: &1 |
| 062 | RFC destination &1 points to system &2, not &3 |
| 063 | System failure for RFC destination &1 |
| 064 | Communication failure for RFC destination &1 |
| 100 | Object &1 not found |
| 101 | Object &1 is restricted |
| 200 | Failure during code analysis |
| 300 | Communication failure for RFC destination &1: &2&3&4 |
| 301 | System failure for RFC destination &1: &2&3&4 |
| 302 | RFC destination &1 points to system &2, not to &3 |
| 303 | Failed to get system information for RFC destination &1: &2&3&4 |
| 304 | Ping to RFC destination &1 failed |
| 305 | RFC destination &1 not reachable |
| 306 | Failed to receive results from ping to RFC destination &1 |
| 307 | Enter RFC destination or SAP system |
| 308 | Enter RFC destination if you want to schedule check runs for &1 in &2 |