SADT_RESOURCE - Resource messages
The following messages are stored in message class SADT_RESOURCE: Resource messages.
It is part of development package SADT_REST in software component BC-DWB-AIE. This development package consists of objects that can be grouped under "REST Framework".
It is part of development package SADT_REST in software component BC-DWB-AIE. This development package consists of objects that can be grouped under "REST Framework".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Resource &1 &2 does already exist. |
| 002 | Resource &1 &2 does not exist. |
| 003 | No authorization to access the resource &1 &2. |
| 004 | Resource &1 &2 could not be successfully saved. |
| 005 | Resource &1 &2 could not be successfully deleted. |
| 006 | Resource &1 &2 could not be successfully created. |
| 007 | Resource &1 &2: wrong input data for processing |
| 008 | Resource &1 does not support the method &2 |
| 009 | Resource message format contains errors: &1 |
| 010 | Resource controller does not support method &1 |
| 011 | Version &1 not supported by resource controller |
| 012 | For object &1 &2 could not be created a transport request. |
| 013 | Resource &1 &2: error related to Change and Transport System. |
| 014 | The resource id &1 could not be found. |
| 015 | Object(s) could not be inserted into transport request &1. |
| 016 | No mapping found for resource controller &1. |
| 017 | Parameter &1 could not be found. |
| 018 | Resource &1 &2 is locked. |
| 019 | Resource &1 &2 could not be successfully activated. |
| 020 | Resource &1 &2 cannot be checked. |
| 021 | The data, which is returned by the resource controller, is invalid. |
| 022 | Resource &1 &2 could not be successfully activated. Reason: &3 |
| 023 | Resource &1 &2 could not be successfully updated. |
| 024 | Resource &1 &2 contains errors. |
| 025 | Resource &1 &2 contains errors: &3 |
| 026 | Resource &1 &2 is not locked (invalid lock handle: &3) |
| 027 | Resource &1 &2 is not locked. |
| 028 | Resource &1 &2 could not be successfully read. |
| 029 | Resource &1 &2 could not be locked. |
| 030 | The editor does not support enhanced objects (use SAP GUI instead) |
| 031 | Service message format contains errors: &1 |
| 032 | Resource &1 &2 is not locked in a transport request |
| 033 | Resource &1 &2 could not be updated: eTag &3 does not match eTag &4 sent |
| 034 | Request could not be understood by the server due to malformed syntax: &1 |
| 036 | Editing not supported for objects modified with Modification Assistant |
| 037 | The message content is not acceptable |
| 038 | The text contains characters [&1] which cannot be converted |
| 039 | Unsupported Media Type |
| 040 | Request could not be processed due to syntax error in &1 |
| 041 | Precondition failed |
| 042 | Request was well formed but contained semantic errors |
| 043 | Client ETag &1 does not match the object ETag &2 in the server |
| 044 | The message content is not acceptable. Accepted content types: &1&2&3&4 |
| 045 | Unsupported Media Type. Supported Media Types: &1&2&3&4 |
| 046 | The If-Match header value does not match the server-side ETag for &1 &2 |
| 047 | Message content type is not declared. Accepted content types: &1&2&3&4 |
| 050 | Operation is not allowed |