ECATT_ODATA_TST - eCATT OData Testing - Nachrichten
The following messages are stored in message class ECATT_ODATA_TST: eCATT OData Testing - Nachrichten.
It is part of development package SECATT_ODATA_APL in software component BC-TWB-TST-ECA. This development package consists of objects that can be grouped under "eCATT - OData Core".
It is part of development package SECATT_ODATA_APL in software component BC-TWB-TST-ECA. This development package consists of objects that can be grouped under "eCATT - OData Core".
Message Nr ▲ | Message Text |
---|---|
000 | Error in eCATT OData Control |
001 | Functionality is not implemented |
008 | No valid addressing method specified (&1) |
009 | Could not determine host or port for local communication |
010 | No HTTP destination to generate HTTP client |
011 | Error while generating HTTP client: &1&2&3&4 |
012 | Connection parameter (destination &1) not available |
013 | HTTP destination &1 not found |
014 | You are not authorized to use HTTP destination &1 |
015 | HTTP/HTTPS communication is not available / is deactivated |
016 | Internal error (dest:&1 URL:&2) |
017 | Connection parameter (host or service) not available (URL:&1) |
018 | No service URL for generation of HTTP client |
019 | Error during initialization of eCATT OData Service Client: no URI |
020 | Error: Service URL is initial for SET_URL |
021 | Error: HTTP client not initialized (method:&1) |
022 | Error: REST client not initialized (request method: &1) |
023 | Destination &1 not suitable for HTTP(S) (DestTyp: &2) |
024 | Error while using HTTP destination &1 |
025 | Error while accessing metadata: &1&2&3&4 |
026 | Error during metadata access: EntityContainer &1 not found |
027 | Error during metadata access: EntitySet &1 not found |
028 | Error during metadata access: EntityType not found |
029 | Error while generating HTTP client: &1&2&3&4 |
040 | Error: eCATT OData Client not initialized |
041 | Error: Metadata does not exist |
049 | HTTP method &1 is not supported. |
050 | Error in HTTP &1: &2&3&4 |
051 | Error while retrieving: &1&2&3&4 |
052 | Error while querying metadata document: &1&2&3&4 |
054 | Error in batch request: &1&2&3&4 |
055 | Error while inserting: &1&2&3&4 |
056 | Error during delete: &1&2&3&4 |
057 | Error during update: &1&2&3&4 |
058 | Error with operation &1: &2&3&4 |
059 | Error: Import parameter &1 was not specified for function &2 |
060 | Key for set &1 is not specified fully |
061 | Number for &TOP must be greater than 0 |
062 | Number for &SKIP must be positive |
063 | Index for set must be positive |
064 | Specify exactly one criterion (index or key) |
065 | Error while generating entity data: &1&2&3 |
066 | Error before service call while creating request: &1&2&3 |
071 | Error during REST operation &1: &2&3&4 |
072 | Error during postprocessing REST operation &1: &2&3&4 |
073 | Response does not contain an ETag (operation &1: &2) |
074 | Error accessing entity container &1 (entity set &2): &3&4 |
075 | You are not authorized to start the SAP Gateway Client (/IWFND/GW_CLIENT) |
076 | Content type &1 is not supported. |
090 | Transaction /IWFND/GW_CLIENT does not exist in this system |
091 | You are not authorized to execute transaction /IWFND/GW_CLIENT |
110 | Error while accessing test data: &1&2&3&4 |
111 | Error while generating test data: &1&2&3&4 |
112 | Error while generating test data (TDC:&1(&2)) |
113 | Error while generating test data container &1(&2): &3&4 |
114 | Test data container &1(&2) generated |
115 | Test data container &1(&2) filled; transferred entities: &3 |
116 | &1: GET_ENTITYSET disabled |
127 | URL does not contain service name: &1 |
130 | Error while processing a batch request: &1&2&3&4 |
131 | Service response could not be transferred in ABAP data (&1, &2) |
132 | HTTP header in batch section contains no "Content-Type: .. boundary". |
133 | Section with ID &1 of the $batch request not found. |
134 | Section with the ID &2 in change set &1 of the batch request not found. |
135 | Section with the ID &1 is not a change set. |
136 | HTTP header in batch section does not contain a "Content-Type". |
137 | HTTP header in batch section does not contain a "Content-Length". |