/UI2/CDM3_EXP - CDM 3 Exposure
The following messages are stored in message class /UI2/CDM3_EXP: CDM 3 Exposure.
It is part of development package /UI2/CDM3_TOOLS in software component CA-FLP-ABA. This development package consists of objects that can be grouped under "CDM Administrative Tools".
It is part of development package /UI2/CDM3_TOOLS in software component CA-FLP-ABA. This development package consists of objects that can be grouped under "CDM Administrative Tools".
Message Nr ▲ | Message Text |
---|---|
001 | &1 entity &2&3 exposed |
002 | &1 entity &2&3 exposed with warnings |
003 | &1 entity &2&3 not exposed |
004 | Configuration is invalid |
005 | Configuration is outdated |
006 | No configuration maintained |
007 | Preparing output (&1/&2) |
008 | You are not authorized to execute report & |
009 | You are not authorized to change the selected roles |
010 | You are not authorized to read the selected roles |
011 | You are not authorized to expose into repository & |
012 | Role &1 does not exist; exposure canceled |
013 | Invalid role selection; there is nothing to expose |
014 | There is no exposed content in the repository yet |
015 | Exposed content was not changed since the last publishing |
016 | An exposure process by user &1 is still running in parallel |
017 | Technical error when determining the state of the exposure process |
018 | Running in test mode |
019 | ICF Service /sap/bc/ui2/cdm3 is currently inactive |
100 | Schema validation skipped; BAdI not implemented |
101 | Schema validation completed; no errors found |
102 | Schema validation errors found; exposure canceled for &1 |
103 | &1. CDM3 schema not validated. &2 |
104 | &1 entity &2&3 has schema errors. |
105 | Correct schema errors to complete the exposure. |
106 | &1 |
107 | Error in webservice response |
108 | Missing RFC destination &1 |
109 | The exposure was canceled because of schema validation errors. |
110 | The exposure was canceled because some cached data is outdated. |
111 | The exposure was canceled because of technical issues. |
201 | Performing prechecks... |
202 | Performing prechecks (&1/&2) |
203 | Calculating CDM JSON... |
204 | Calculating CDM JSON (&1/&2) |
205 | Performing postcheck... |
206 | Performing postcheck (&1/&2) |
300 | &1 out of &2 entities exposed (including &3 exposed with warnings) |
301 | &1 out of &2 &3 entities exposed (including &4 exposed with warnings) |
302 | Performance Statistics (Total Time: &1s) |
303 | Start Time: &1 |
304 | End Time: &1 |
305 | End Memory: &1 MB |
310 | Version &1 from &2 at &3 (UTC) deleted |
311 | Automatic repository cleanup started with &1 expiration days |
312 | Automatic repository cleanup deactivated |
313 | Invalid FLP setting EXPOSURE_REPOSITORY_EXPIRATION_DAYS |
314 | No content had to be deleted |
400 | Content change notifications processed |
401 | Content change notification for ID "&1" sent with HTTP status code &2 |
402 | Creating Hash failed |
403 | RFC destination with matching host not in table /UI2/CDM3_CCNTGT |
404 | Content change notification for ID "&1" failed |
405 | Creating job for retry of content change notification failed |
406 | Creating HTTP client for RFC destination &1 failed |
407 | Creating job for exposure repository cleanup failed |
408 | Changing status failed |
409 | Reading status failed |
410 | You are not authorized to read the data |
411 | You are not authorized to change the data |
500 | Inserting access token failed |
501 | Reading access token failed |
502 | Deleting access token failed |
503 | You are not authorized to read or delete access token |
510 | Storing access token was successful |
511 | Unauthorized caller; &1 is not allowed to call the API |
601 | RFC Destination could not be determined |
602 | Invalid "&1"; allowed characters are "A-Z a-z _ -" |
603 | "&1" already exists; enter another value |
604 | "&1" must be filled |
605 | Invalid value for "&1"; define a number as value |