CONSENT_MANAGEMENT - Consent Administration: General Message Class
The following messages are stored in message class CONSENT_MANAGEMENT: Consent Administration: General Message Class.
It is part of development package CONSENT_DB in software component CA-GTF-CON. This development package consists of objects that can be grouped under "Consent Administration: Database Layer".
It is part of development package CONSENT_DB in software component CA-GTF-CON. This development package consists of objects that can be grouped under "Consent Administration: Database Layer".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Source / target combination not supported for mapping: &1 -> &2 |
002 | Imported parameter is_struc doesn't contain a flat/deep structure |
003 | Imported parameter is_struc contains a table type which is not supported |
004 | Table to be modified is not supported by this data access object |
005 | &1&2&3&4 |
016 | Consents could not be saved |
017 | Form texts could not be saved |
019 | Consent Validation Messages |
032 | Consent '&1': Duplicate form text IDs |
033 | Consent '&1': Form text with ID '&2' persisted differently on database |
035 | Consent could not be found |
036 | Consents '&1' and '&2' are invalid |
045 | No source with name '&1' found |
048 | Select a row to show form texts |
049 | Select a row to show change documents |
050 | ### Internal Messages ### |
051 | Log level '&1' was changed to '&2'; choose a valid number between 1-5 |
052 | Search supports only positive values for IV_MAX_ENTRIES absolute used |
053 | Log disabled |
054 | Log enabled with log level '&1' and save enabled |
055 | Log enabled with log level '&1' and save disabled |
056 | Consent '&1': The form text '&2' was not found |
057 | Select a row to show attachments |
058 | No attachments for the selected consent record found |
100 | ### Consent Validation ### |
101 | Consent not valid &1 |
102 | Consent with ID '&1' is not valid |
103 | Consent '&1': Field '&2' must not be empty |
104 | Consent '&1': Field '&2' in combination with field '&3' must not be empty |
105 | Consent '&1': Form texts for field '&2' are not available |
106 | Consent '&1': Field '&2' is not valid |
107 | Consent '&1': Field '&2' in combination with field '&3' is not valid |
108 | Consent '&1': Field '&2' must be less than field '&3' |
109 | Consent '&1': Field '&2' must be empty when field '&3' is empty |
110 | Consent '&1': Value of field '&2' is not in a valid range |
111 | Unable to determine key field of check table '&1' for field '&2' |
112 | Consent '&1': Newer version of this consent is already available |
113 | Consent '&1': Fields '&2' and '&3' must both be filled or both empty |
114 | Consent '&1': Combination of fields '&2' and '&3' is not valid |
115 | Consent '&1': All third party fields must either be filled or empty |
116 | Consent '&1': Import consents not permitted; missing authorization |
117 | Search consents not permitted; missing authorization |
118 | Read consents not permitted; missing authorization |
119 | Import consents not permitted; missing authorization |
120 | Consent with ID '&1' already exists |
121 | Consent '&1': Combination of data subject type and ID is not valid |
122 | Consent '&1': Combination of withdrawn at, by and consent status invalid |
123 | Consent '&1': Same version of this consent is already available |
124 | Consent '&1' and origin_changed_at '&2' has newer version or duplicate |
125 | Consent '&1': Field '&2' must have leading zeros |
126 | Consent '&1': Field lifecycle_status is expired. Consent will be skipped |
127 | Consent '&1': Field lifecycle_status is blocked |
128 | Consent '&1': Contains blocked data subject |
129 | Consent '&1': No handler class found for data subject ID type '&2' |
130 | ### Consent Import Mapper ### |
131 | Consent '&1': Value '&2' of field '&3' is not processible |
132 | Consent '&1': Language code '&2' cannot be converted into SAP lang. code |
133 | Mapping started at '&1' |
134 | Mapping '&1' consent records |
135 | Mapping ended at '&1'; '&2' of '&3' consent records are valid |
136 | Consent '&1': Error occurred while locking; consent is already locked |
137 | Consent '&1': System failure occurred while locking |
138 | Consent '&1': Unknown error occurred while locking |
139 | Consent '&1': Withdrawn opt-out consent; maximum valid to set to '&2' |
140 | Consent '&1': No assignment of '&2' with corresponding '&3' and '&4' |
141 | Withdraw consents not permitted; missing authorization |
142 | Terminate consents not permitted; missing authorization |
143 | Consent '&1': Withdraw consent not permitted; missing authorization |
144 | Consent '&1': Terminate consents not permitted; missing authorization |
148 | Handler class '&1' cannot be instantiated; check implementation |
149 | Multiple implementations for interface IF_CM_BLOCKED_DATA_SUBJECT found |
150 | ### Consent Import via Service ### |
151 | The query string of source with name '&1' is incorrect |
152 | Import data cannot be read from source with name '&1' |
153 | Source with name '&1' cannot be found |
154 | Source with name '&1' is not active |
155 | No consent available to be imported within the chosen time interval |
156 | Imported data is invalid |
157 | Destination '&1' not found; check CMV_SRCE_INFO and destination |
158 | Sending the HTTP request failed |
159 | Receiving the HTTP response failed |
160 | Destination '&1' not available; check CMV_SRCE_INFO and destination |
161 | No authority for accessing destination '&1' |
162 | Destination '&1' needs to be checked |
163 | HTTP status code: &1 |
164 | Message: &1&2&3&4 |
165 | Unsuccessful service call: HTTP status code '&1' message '&2' |
200 | ### Import Messages ### |
201 | Import started with '&1' consent records at '&2' |
202 | '&1' of '&2' consent records were imported |
203 | Import finished at '&1' |
204 | Change documents will ignore insert |
205 | Import will run as a test; data will not be persisted |
206 | No consent records found |
207 | The file to import is empty |
208 | No consent records to import |
209 | Consent '&1' with ID '&2' imported successfully |
210 | File '&1' not found |
211 | Error while processing the file; see log for additional information |
212 | File '&1' exceeds the size limit of 100MB |
250 | ### Read Messages ### |
251 | Consent '&1': Read consents not permitted; missing authorization |
252 | Consent '&1' does not exist |
253 | Too many search criteria. Reduce the amount of search criteria. |
300 | ### Customizing Messages ### |
301 | Source name '&1' is invalid |
302 | No non-alphanumeric characters except for '_' allowed in the source name |
303 | Source name must not be empty |
304 | Query string is invalid |
305 | RFC destination type different from '&1' not supported; data not saved |
306 | Query string is missing |
307 | Source name '&1' does not exist |
308 | Controller with ID '&1' and type '&2' does not exist. |
309 | '&1' is invalid |
310 | Controller with name '&1' cannot be deleted; '&2' Consents exist |
311 | Assignment '&1' with type '&2' cannot be deleted, '&3' Consents exist |
312 | Assignment '&1' with type '&2' already exists with controller name '&3' |
330 | The assumed aging date for this analysis is '&1' |
331 | Number of consents: &1 |
332 | Number of consent records where the residence period is over: &1 |
333 | Statistics aggregated per ILM condition field for consents |
334 | Data Ctrl '&1', Data Subj. ID type '&2', Jurisd. '&3', count consents &4 |
335 | D.Ctrl '&1', D.S.ID type '&2', Jurisd. '&3', # consents res. per. over &4 |
400 | Consent '&1' is invalid |
401 | Schema validation started at '&1' |
402 | Schema validation ended at '&1'; '&2' of '&3' consent records are valid |
403 | Validating '&1' consent records |
404 | File '&1' cannot be opened |
405 | File '&1' cannot be read |
406 | There are too many files already opened. File '&1' cannot be opened |
407 | Pipes are not supported by the operating system |
408 | No authority to open file '&1' |
409 | No consents provided. Data content is initial. |
410 | Currently '&1' mapping is not supported; 'S4HANA' expected |
411 | BAdI impl. '&1' uses a non-flat structure; only flat ones allowed |
412 | Component with name '&1' is not flat |
413 | Conversion error occurred at component '&1' with value '&2' |
414 | Target field '&1' was not found |
415 | Parsing error occurred at offset '&1' |
416 | BAdI CM_IMPORT_MAPPING implemented multiple times for filter '&1' |
417 | Initial data found. |
418 | Deep structure detected at offset '&1'. Consent will be skipped |
419 | Rounding occurred when mapping from src field '&1' to target field '&2' |
420 | Creation of source structure descriptor failed |
421 | Component with name '&1' cannot be found at offset '&2' |
422 | Log with number '&1' saved |
423 | A field with name '&1' contains an invalid UTF-8 character(s) |
450 | Re-caculation started in &1 mode |
451 | '&1' consents to re-calculate the statuses for |
452 | Consent '&1': Could not change the statuses in database |
453 | Consent '&1': old lifecycle status is '&2', new one is '&3' |
454 | Consent '&1': old consent status is '&2', new one is '&3' |
455 | Error while initializing parallel processing |
456 | RFC error in callback routine; Message: &1 |
457 | Consent '&1': Not processed (RFC error with RC &2 and Message &3) |
458 | Starting Re-calculation of statuses in mode &1 |
459 | Parallel task created and saved log with number &1 |
460 | No data to process |
461 | No log messages from parallel tasks |
462 | No range, only option equals, only sign inclusive is allowed for UUIDs |
463 | No physical file name found for logical file name '&1' |
464 | Consent '&1': End of validity date was initial, new one is '&2' |
465 | Name '&1' must be 1 to 30 chars long and alphanumeric (including _-!.~) |
500 | ### EoP check Log messages ### |
501 | Start End of Purpose check |
502 | Checking '&1' partners |
503 | End of Purpose check completed |
504 | Business Partner with number '&1' and GUID '&2' is checked |
505 | Customer '&1' is checked |
506 | Vendor '&1' is checked |
507 | Contact Person '&1' is checked |
508 | No consent records found for partner '&1'; partner unknown |
509 | '&1' consent records found for partner '&2' |
510 | Checking consent record '&1' with ID '&2' |
511 | Consent record '&1' indicates ongoing business |
512 | End of business of consent record '&1' is '&2' |
513 | Found ILM rule group '&1' |
514 | At least one ILM ret. rule found for ILM object '&1' and consent '&2' |
515 | No ILM rule group found for ILM object '&1' and consent '&2' |
516 | No application rule variant found. Proceed with empty rule variant |
517 | Found application rule variant '&1' |
518 | Error during end of residence calc. for partner '&1' and consent '&2' |
519 | End of residence for consent record '&1' is '&2' |
520 | Purpose completed for partner '&1' and end of purpose '&2' |
521 | Purpose not completed for partner '&1' and end of purpose is '&2' |
522 | Condition field '&1' has value '&2' |
523 | Withdraw '&1' consent records as test; data is not persisted |
524 | Terminate '&1' consent records as test; data is not persisted |
525 | Consent '&1' could not be found |
526 | Withdraw consent '&1' |
527 | Terminate consent '&1' |
528 | Consent '&1' cannot be withdrawn; it is already withdrawn |
529 | Consent '&1' cannot be terminated; it is already terminated |
530 | Withdraw '&1' consent records; data is persisted |
531 | Terminate '&1' consent records; data is persisted |
532 | Withdrawal finished; '&1' of '&2' consents withdrawn |
533 | Termination finished; '&1' of '&2' consents terminated |
534 | Source Info '&1' is used in at least one consent; deletion not permitted |
535 | Deletion of Data Controller '&1' not possible |
536 | Deletion of Data Controller Assignment '&1' with type '&2' not possible |