/IWPGW/TGW_TCM_MSG -
The following messages are stored in message class /IWPGW/TGW_TCM_MSG: .
It is part of development package /IWPGW/TGW_RUNTIME_TCM in software component OPU-BSC-TGW. This development package consists of objects that can be grouped under "Task Gateway TCM OData Provider Runtime".
It is part of development package /IWPGW/TGW_RUNTIME_TCM in software component OPU-BSC-TGW. This development package consists of objects that can be grouped under "Task Gateway TCM OData Provider Runtime".
Message Nr ▲ | Message Text |
---|---|
000 | Navigation property '&1' not supported for entity '&2' by task provider |
001 | Entity set '&1' not supported by task provider |
002 | POST request on URI &1 is not supported |
003 | DELETE request on URI &1 is not supported |
004 | HTTP client initialization for destination &1 failed |
005 | Return parameter expected to be a table type |
006 | Mapped field '&1' for property '&2' missing in target structure |
007 | Metadata document from destination &1 could not be read |
008 | Return parameter expected to be a structure type |
009 | Deserializing response failed |
010 | Type of result is not supported - entity or complex type expected |
011 | OData exception occurred |
012 | Serializing request entity '&1' failed |
013 | Function import '&1' is not supported |
014 | HTTP request for destination &1 with method &2 failed |
015 | Unsupported data type ID (&1) |
016 | Filter property &1 on entity &2 not supported |
100 | Creating HTTP client for destination &1 failed (RC:&2) |
101 | Reading properties of RFC destination &1 failed (RC:&2) |
102 | Retreiving CSRF token from destination &1 failed |
103 | Sending HTTP request to destination &1 failed (RC:&2) |
104 | Receiving HTTP response from destination &1 failed (RC:&2) |
105 | HTTP Error occurred - &1 - Reason: &2 |
200 | User does not have sufficient authorizations |