DAAG_API - Message Class for Data Aging API

The following messages are stored in message class DAAG_API: Message Class for Data Aging API.
It is part of development package S_DAAG_API in software component BC-CCM-DAG. This development package consists of objects that can be grouped under "Interface Functions for Application and for Users".
Message Nr
Message Text
000*** Back-end - Messages ***
001SQL connection could not be established
002Data management object &1 enhances data management object &2
003Not all enhancements of data management object &1 are active
004Database &1 is not supported by data management object &2
005Report started
006Report completed
007Data aging group ID: &1
008Data management object ID: &1
009&2 Entries processed for table &1
010Runtime for data management object &1: &2 hours &3 minutes &4 seconds
011Report can only run in a background job
012Report started without valid data aging group
013Data aging run already in progress for data aging group &1
014Cannot process data management object &1
015Data management object &1 has inconsistent enhancements
016Data management object &1 contains tables with OTHERS partition
017Errors occurred while updating data records
018Run &1 stopped by user
019Stop run for &1 failed
020Data aging run &1 is not active
021Cancel of data aging run &1 failed
022No data aging runs to stop
023Update failed for STATUS_DETAILS field
024Select a run to stop
025Stop run for &1 already initiated
026Data aging run &1 already stopped
027Data management object is not provided
028Target date for undo run is not provided
029Undo run for data management object: &1
030Data management object is not active and cannot be undone
031Undo cannot be performed; object &1 is locked in data aging run &2
032Undo cannot be performed; object &1 is locked in undo run &2
033Cannot process undo run of data management object :&1
034Undo run &1 is stopped
035Undo run &1 could not be stopped
036Cannot schedule undo run
037Target date cannot be more than latest max. date &1 for object &2
038Data aging run cannot be scheduled; undo run for object &1 in progress
039Target date &1 cannot be more than latest max date &2
040Method &1 not implmented in application class &2 of data aging object &3
041Enter a data management object
042The retaining field &1 for F4 help is not in structure &2
043The structure &1 does not exist
044The structure &1 is not active
045The exporting parameter &1 of method &2 in app. class &3 can't be initial
046Data aging run or undo aging run stopped because upgrade is running
047The data aging &1 got activated during the data aging run
048The data aging group ID & already exist
049Enter the data aging group ID
050The data aging group ID & does not exist
051Select a run to view the logs
052Run ID for the aging run is &1
053The job associated with the aging run is &1
054Job count for the aging run is &1
055Aging run is executed in sequential mode
056Package size is &1
057Aging runs started for the package &1
058Aging runs ended for the package &1
059Maximum number of tasks that can be processed in parallel mode is &1
060Logon/server group is &1
061Number of objects processed in a task is &1
062Aging run is executed in parallel mode
082Run stopped; maximum runtime has expired
100No aging run exist for the data management object &
192Internal error occured during data aging run
193Cannot perform undo run; inconsistent dates
200Correction report started
201Correction report completed
202Error invoking correction interface
203Correction for object &1 started
204Correction report called
300& & & &
500Data aging update failed for some packages
Privacy Policy