CM_EHFND_CNTNT_SRVC -
The following messages are stored in message class CM_EHFND_CNTNT_SRVC: .
It is part of development package EHFND_CONTENT_SERVICE_INTEG in software component EHS-SUS-CI. This development package consists of objects that can be grouped under "Integration to Content Service".
It is part of development package EHFND_CONTENT_SERVICE_INTEG in software component EHS-SUS-CI. This development package consists of objects that can be grouped under "Integration to Content Service".
Message Nr ▲ | Message Text |
|---|---|
| 001 | HTTP connection to content service could not be established. |
| 002 | Creation of OAuth client failed. |
| 003 | No outbound connection found in communication arrangement &1. |
| 004 | Failed to create OData v4 client. |
| 005 | Sending of HTTP request to the content service failed. |
| 006 | No RFC destination maintained for content service |
| 007 | Filename of json file &1 is invalid and couldn't be resolved. |
| 008 | ZIP file couldn't be loaded. |
| 009 | Couldn't read file &1 of ZIP file because the ZIP file is corrupt. |
| 010 | Couldn't delete file &1 of ZIP file. |
| 011 | File &1 is invalid and can't be processed. |
| 012 | Requested MIME file doesn't exist. |
| 013 | File upload failed with error code &1. |
| 014 | Connection parameter (destination) not available for HTTP destination &1 |
| 015 | HTTP destination &1 doesn't exist |
| 016 | No authorization to access the HTTP destination &1 |
| 017 | HTTP/HTTPS communication not available for HTTP destination &1 |
| 018 | Unknown error while creating an HTTP client with HTTP destination &1 |
| 019 | ZIP file &1 is invalid |
| 020 | Graphic binary &1 isn't listed in JSON file &2 |
| 021 | JSON file &1 contains graphic binary &2 which is missing in ZIP file &3 |
| 022 | Graphic binary &1 doesn't exist |
| 023 | Graphic binary with file name &1 already exists. |
| 024 | Graphic binary with UUID &1 already exists. |
| 025 | Graphic collection file &1 doesn't exist |