SADT_REST - Messages for ADT REST Framework
The following messages are stored in message class SADT_REST: Messages for ADT 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".
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 |
|---|---|
| 000 | No application class found for URI: &1 |
| 001 | Please change your password using SAP GUI |
| 002 | Password is initial - please change your password using SAP GUI |
| 003 | Password has expired - please change your password using SAP GUI |
| 004 | Password check failed due to internal error |
| 005 | No data mapping found! Data name: &1 <-> Data type: &2 |
| 006 | Data is invalid and could not be converted |
| 007 | The value of &1 &2 is invalid and could not be converted |
| 008 | The value &2 of header field &1 is invalid |
| 009 | CSRF token validation failed |
| 010 | No content handler found for content type '&1' |
| 011 | No content handler found |
| 012 | No data type found in content type '&1' |
| 013 | Data type &1 does not exist |
| 014 | The user does not have the necessary development authorization |
| 015 | The filter value cannot be longer than 40 characters |
| 016 | The system does not support Eclipse based ABAP Development Tools |
| 017 | The user does not have the necessary authorization |
| 018 | Request can not be routed |
| 019 | Only operators =, CP, or CS are allowed in this BAdI |
| 020 | The action is not supported |
| 100 | No boundary in content-type header of the batch request found (Line: &1) |
| 101 | Expected batch part boundary: &2 in message body not found (Line: &1) |
| 102 | No closing boundary of the form: &2 found (Line: &1) |
| 103 | Expected request content-type: &2, but was: &1 |
| 104 | Syntax or last line of the header is invalid (Line: &1) |
| 105 | A specific header name: &2 is expected but is missing (Line: &1) |
| 106 | Wrong input data type for serialization is used |
| 107 | Invalid request, maybe lf is used instead of crlf |
| 108 | Batch part finished too early, subrequest or empty line needed (Line: &1) |
| 109 | An empty line is necessary after header section (Line: &1) |
| 110 | Expected an HTTP request line: GET/POST/PUT/DELETE (Line: &1) |
| 111 | Expected header: &3 but was: &2 (Line: &1) |
| 500 | &1&2&3&4 |
| 999 | This message is used in Unit Tests: &1 &2 &3 &4 |