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