SAP ABAP Message Class RSCRT (Near-To-Real-Time Messages)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-WHM-DST (Application Component) Data Staging
⤷
RSCRT (Package) (Near)-Real-Time Data Transfer into BW
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSCRT (Package) (Near)-Real-Time Data Transfer into BW 
Attributes
| Message class |  |
RSCRT |
| Short Description |  |
Near-To-Real-Time Messages |
| Changed On |  |
20140121 |
| Last Changed At |  |
101748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
******* Scheduler Messages **** Near-To-Real-Time | The short text describes the object sufficiently | |
| 2 | 001 |
There are no active INIT for DS '&1' QS '&2'; perform initializatn first | The short text describes the object sufficiently | |
| 3 | 002 |
Daemon '&1' cannot be used; use daemon '&2' | Space: object requires documentation | |
| 4 | 003 |
Stop processing planned for InfoPackage '&1' by daemon '&2' | Space: object requires documentation | |
| 5 | 004 |
Select only one daemon to stop | The short text describes the object sufficiently | |
| 6 | 005 |
Select only one InfoPackage | The short text describes the object sufficiently | |
| 7 | 006 |
Check, whether daemon '&1' is running with errors | The short text describes the object sufficiently | |
| 8 | 007 |
Select a line | The short text describes the object sufficiently | |
| 9 | 008 |
'Stop Upload' flagged for all assigned InfoPackages | Space: object requires documentation | |
| 10 | 009 |
'Stop Upload' flagged. Wait until all InfoPackage cycles have ended | The short text describes the object sufficiently | |
| 11 | 010 |
No deletion possible, because daemon is still running | The short text describes the object sufficiently | |
| 12 | 011 |
Internal error | The short text describes the object sufficiently | |
| 13 | 012 |
Daemon successfully deleted | The short text describes the object sufficiently | |
| 14 | 013 |
Daemon creation failed | The short text describes the object sufficiently | |
| 15 | 014 |
Daemon created successfully | The short text describes the object sufficiently | |
| 16 | 015 |
Status of displayed objects, processes and requests has been checked | The short text describes the object sufficiently | |
| 17 | 016 |
Daemon '&1' ended with error '&2' | The short text describes the object sufficiently | |
| 18 | 017 |
Daemon '&1' ended | Space: object requires documentation | |
| 19 | 018 |
*Start Upload' for InfoPackage flagged for next daemon run | The short text describes the object sufficiently | |
| 20 | 019 |
Batch job planned for InfoPackage and daemon. Start when batch job free | Space: object requires documentation | |
| 21 | 020 |
InfoPackage is already running | The short text describes the object sufficiently | |
| 22 | 021 |
'Start Upload' not possible here. Check the InfoPackage | The short text describes the object sufficiently | |
| 23 | 022 |
'Stop Upload' planned for InfoPackage | The short text describes the object sufficiently | |
| 24 | 023 |
InfoPackage is not running | The short text describes the object sufficiently | |
| 25 | 024 |
Cancellation planned. InfoPackage requests are set to RED | The short text describes the object sufficiently | |
| 26 | 025 |
Action failed | The short text describes the object sufficiently | |
| 27 | 026 |
InfoPackage assignment changed | The short text describes the object sufficiently | |
| 28 | 027 |
InfoPackage assigned | The short text describes the object sufficiently | |
| 29 | 028 |
Save of new description canceled | The short text describes the object sufficiently | |
| 30 | 029 |
Action terminated by the user | The short text describes the object sufficiently | |
| 31 | 030 |
Internal error when constructing the ALV tree | The short text describes the object sufficiently | |
| 32 | 031 |
Daemon saved | The short text describes the object sufficiently | |
| 33 | 032 |
Daemon successfully deleted | The short text describes the object sufficiently | |
| 34 | 033 |
Daemon is running or ist locked by another user (RSCRT_DEMONS) | The short text describes the object sufficiently | |
| 35 | 034 |
Stop the daemon first (also necessary if the job is no longer running) | The short text describes the object sufficiently | |
| 36 | 035 |
Exectn of InfoPack '&1' in daemon '&2' in line '&3' canceled w/o message | The short text describes the object sufficiently | |
| 37 | 036 |
Error calling InfoPackage maintenance | The short text describes the object sufficiently | |
| 38 | 037 |
Error calling the request monitor | The short text describes the object sufficiently | |
| 39 | 038 |
Error determining the job information. Start of daemon &1 failed | The short text describes the object sufficiently | |
| 40 | 039 |
Error writing RSCRT_DEMONS. Start of daemon &1 failed | The short text describes the object sufficiently | |
| 41 | 040 |
Daemon already stopped | The short text describes the object sufficiently | |
| 42 | 041 |
Daemon already stopped. Red light removed | The short text describes the object sufficiently | |
| 43 | 042 |
Error updating RSCRT_DEMONS. Start of daemon &1 failed | The short text describes the object sufficiently | |
| 44 | 043 |
(Near)-real-time upload in InfoPackage &1 stopped | The short text describes the object sufficiently | |
| 45 | 044 |
Near-real-time upload in InfoPackage &1 canceled | The short text describes the object sufficiently | |
| 46 | 045 |
InfoPackage &1 included in control tables for daemon &2 | The short text describes the object sufficiently | |
| 47 | 046 |
Enqueue for RSCRT_DEMON for daemon &1 failed (not started) | The short text describes the object sufficiently | |
| 48 | 047 |
Daemon '&1' complete. At least one request with errors | The short text describes the object sufficiently | |
| 49 | 048 |
Start of InfoPackage &1 from daemon &2 failed (no repeats) | The short text describes the object sufficiently | |
| 50 | 049 |
Periodic restart of daemon job failed | The short text describes the object sufficiently | |
| 51 | 050 |
Error determining InfoPackage metadata (IP &1, daemon &2) | Space: object requires documentation | |
| 52 | 051 |
Could not start upload with InfoPackage &1 | The short text describes the object sufficiently | |
| 53 | 052 |
Enqueue for RSCRT_CTRL for InfoPackage &1 failed | The short text describes the object sufficiently | |
| 54 | 053 |
Internal error - cannot find PSA request (IP &1, daemon &2) | The short text describes the object sufficiently | |
| 55 | 054 |
Error reading TIDs for confirmation of DB (IP &1, daemon &2) | The short text describes the object sufficiently | |
| 56 | 055 |
Open change log requests for closed PSA request (IP &1, daemon &2) | The short text describes the object sufficiently | |
| 57 | 056 |
Error generating a new PSA request (IP &1, daemon &2) | The short text describes the object sufficiently | |
| 58 | 057 |
No update for DataStore object '&1' | Space: object requires documentation | |
| 59 | 058 |
Internal error while updating DSO &1 (InfoPackage &2, daemon &3, req. &4) | The short text describes the object sufficiently | |
| 60 | 059 |
PSa request closed, but upload status not set to READY | The short text describes the object sufficiently | |
| 61 | 060 |
Internal error in CLOSE_CLOG_REQUESTS (InfoPackage &1, daemon &2) | The short text describes the object sufficiently | |
| 62 | 061 |
Internal error when generating objects (class &1) | The short text describes the object sufficiently | |
| 63 | 062 |
InfoPackage is already assigned to daemon &1 | The short text describes the object sufficiently | |
| 64 | 063 |
No authorization | The short text describes the object sufficiently | |
| 65 | 064 |
InfoPackage &1 planned in daemon &2. Daemon started successfully | The short text describes the object sufficiently | |
| 66 | 065 |
Error starting InfoPackage &1 in daemon &2 | The short text describes the object sufficiently | |
| 67 | 066 |
Data successfully loaded | The short text describes the object sufficiently | |
| 68 | 067 |
Data activated successfully | The short text describes the object sufficiently | |
| 69 | 068 |
&1 data records transferred into comm. structure for data dest. &2 | The short text describes the object sufficiently | |
| 70 | 069 |
End of processing of transformation for data target &1 | Space: object requires documentation | |
| 71 | 070 |
&1 records used for data destination &2 (insert/update/delete) | The short text describes the object sufficiently | |
| 72 | 071 |
Processing of data package &1 is complete | The short text describes the object sufficiently | |
| 73 | 072 |
Activation of data in DataStore object &1 failed | The short text describes the object sufficiently | |
| 74 | 073 |
Data transfer is running - process is working | The short text describes the object sufficiently | |
| 75 | 074 |
Scheduler ended, so that daemon can process the InfoPackage | The short text describes the object sufficiently | |
| 76 | 075 |
Stopping daemon processing for InfoPackage &1 - Wait | The short text describes the object sufficiently | |
| 77 | 076 |
Daemon &2 processing InfoPackages &1 - No access permitted | The short text describes the object sufficiently | |
| 78 | 077 |
Data received. Processing will be carried out | The short text describes the object sufficiently | |
| 79 | 078 |
The last delta request &1 was loaded in real-time | The short text describes the object sufficiently | |
| 80 | 079 |
The loading operation was probably canceled - investigate ST22 | The short text describes the object sufficiently | |
| 81 | 080 |
Do you want to process InfoPackage &1 further in real-time? | The short text describes the object sufficiently | |
| 82 | 081 |
System attempts to update request &1 | The short text describes the object sufficiently | |
| 83 | 082 |
Last delta request &1 was NOT loaded in 'realtime' | The short text describes the object sufficiently | |
| 84 | 083 |
Request &1 can not be updated in 'realtime' | The short text describes the object sufficiently | |
| 85 | 084 |
In realtime mode, repeat loading is NOT possible | The short text describes the object sufficiently | |
| 86 | 085 |
Check the request &1 in the monitor and in all data targets | The short text describes the object sufficiently | |
| 87 | 086 |
Execute a repeat request manually | The short text describes the object sufficiently | |
| 88 | 087 |
Delta management (and all data targets to be updated) | The short text describes the object sufficiently | |
| 89 | 088 |
must be in such a state that a delta can be | The short text describes the object sufficiently | |
| 90 | 089 |
requested so that 'realtime data acquisition' works | The short text describes the object sufficiently | |
| 91 | 090 |
Scheduled job '&1' JobCount '&2' for daemon '&3' cannot be deleted | The short text describes the object sufficiently | |
| 92 | 091 |
Meta data could not be determined for InfoPackage '&1' | The short text describes the object sufficiently | |
| 93 | 092 |
For InfoPackage '&1', no new delta request could be created | The short text describes the object sufficiently | |
| 94 | 093 |
RFC destination for source system '&1' could not be determined;error '&2' | The short text describes the object sufficiently | |
| 95 | 094 |
Error when writing PSA for request '&1' | The short text describes the object sufficiently | |
| 96 | 095 |
Error during data target update of request '&1' | The short text describes the object sufficiently | |
| 97 | 096 |
Error when closing request &3 for &1 &2 | The short text describes the object sufficiently | |
| 98 | 097 |
Error when updating request '&1' in DTA '&2' | The short text describes the object sufficiently | |
| 99 | 098 |
Cannot map transferred data for request '&1' | The short text describes the object sufficiently | |
| 100 | 099 |
Error when writing record of request '&1' to PSA | The short text describes the object sufficiently | |
| 101 | 100 |
Error when writing TIDs for request '&1' in table RSCRT_CONFIRM | The short text describes the object sufficiently | |
| 102 | 101 |
Daemon '&1' started | The short text describes the object sufficiently | |
| 103 | 102 |
Termination E3_CS for DTA '&1'; RNR '&2'; DP '&3'; record offset '&4'; | The short text describes the object sufficiently | |
| 104 | 103 |
Too many errors occurred while updating target &1 | Space: object requires documentation | |
| 105 | 104 |
Requests in target '&1' are not yet fully activated | Space: object requires documentation | |
| 106 | 105 |
Check DataStore object '&1'('&2') | The short text describes the object sufficiently | |
| 107 | 106 |
DataStore object '&1' still contains requests that are not activated | Space: object requires documentation | |
| 108 | 107 |
DataStore '&1' cannot be supplied by this InfoPackage | Space: object requires documentation | |
| 109 | 108 |
The system attempts to supply the DataStore objects in real time | Space: object requires documentation | |
| 110 | 109 |
Do you want to schedule the InfoPackage for RDA? | Space: object requires documentation | |
| 111 | 110 |
DTA '&1' does not exist in daemon Ctrl tab. - NOT updated | The short text describes the object sufficiently | |
| 112 | 111 |
A realtime data acquisition InfoPackage cannot create a repeat | Space: object requires documentation | |
| 113 | 112 |
In DataStore &1, load request &2(&3) is incorrectly activated | Space: object requires documentation | |
| 114 | 113 |
In DataStore &1, load request &2(&3) is incorrectly loaded | Space: object requires documentation | |
| 115 | 114 |
No single daemon can fulfill the selected data targets | The short text describes the object sufficiently | |
| 116 | 115 |
Data target '&1' is already being processed by daemon '&2' | The short text describes the object sufficiently | |
| 117 | 116 |
Daemon '&1' just started; see long text | Space: object requires documentation | |
| 118 | 117 |
Named DataStore objects cannot be supplied in real time | The short text describes the object sufficiently | |
| 119 | 118 |
Remove these DataStore objects from the selection | The short text describes the object sufficiently | |
| 120 | 119 |
InfoPackage '&1' for daemon '&2' is not possible - lock on rscrt_on_off | The short text describes the object sufficiently | |
| 121 | 120 |
InfoPackage '&1' not found in table RSLDPIO. Termination | The short text describes the object sufficiently | |
| 122 | 121 |
&1 &2 does not support real-time data acquisition (RDA) | The short text describes the object sufficiently | |
| 123 | 122 |
InfoPackage '&1' not found in table RSLDPCRT. Termination | The short text describes the object sufficiently | |
| 124 | 123 |
No active PSA found for DataSource '&1' and source system '&2' | The short text describes the object sufficiently | |
| 125 | 124 |
No active TS found for DataSource '&1' and source system '&2' | Space: object requires documentation | |
| 126 | 125 |
FM 'RSS_PROGRAM_GET_ID' found no entries for program '&1'. Termination | The short text describes the object sufficiently | |
| 127 | 126 |
No active communication structure found for InfoSource '&1'. Termination | The short text describes the object sufficiently | |
| 128 | 127 |
InfoPack '&1' and/or RNR '&2' in table RSCRT_CTRL are empty -> long text | Space: object requires documentation | |
| 129 | 128 |
No request found for InfoPackage '&1' and RNR '&2' in table RSSELDONE | The short text describes the object sufficiently | |
| 130 | 129 |
No request found for InfoPackage '&1' and RNR '&2' in table RSCRTDONE | The short text describes the object sufficiently | |
| 131 | 130 |
No PSA table found in internal ctrl structure; no restart | Space: object requires documentation | |
| 132 | 131 |
Generation status determination for ID '&1' and CLASS '&2': error '&3' | The short text describes the object sufficiently | |
| 133 | 132 |
No active update rules found for DS object '&1' and IS '&2'; termination | The short text describes the object sufficiently | |
| 134 | 133 |
Incorrect entry parameter when calling FM 'RSCRT_GET_METADATA_IPAK' | The short text describes the object sufficiently | |
| 135 | 134 |
No saved programs for request '&1' in table RSREQPROGS | The short text describes the object sufficiently | |
| 136 | 135 |
No request found for request RNR '&2' in table RSSELDONE; termination | The short text describes the object sufficiently | |
| 137 | 136 |
No program '&2' found for request '&1' in RSREQPROGS; termination | The short text describes the object sufficiently | |
| 138 | 137 |
Error in activation program for DataStore '&1' and source system '&2' | The short text describes the object sufficiently | |
| 139 | 138 |
Error in update program for DataStore '&1'; InfoSource '&2' and SS '&3'; | The short text describes the object sufficiently | |
| 140 | 139 |
Report '&1' not found in DB (no 'read report' possible !); | The short text describes the object sufficiently | |
| 141 | 140 |
Error when creating a new request for &1 &2 | The short text describes the object sufficiently | |
| 142 | 141 |
Error '&1' when calling FM 'RSC3_DELETE_LUWS' with dest. '&2'; | The short text describes the object sufficiently | |
| 143 | 142 |
No request found yesterday, today or tomorrow | The short text describes the object sufficiently | |
| 144 | 143 |
Select an InfoPackage, DataStore object or request | The short text describes the object sufficiently | |
| 145 | 144 |
InfoPackages have not yet been assigned to the daemon | The short text describes the object sufficiently | |
| 146 | 145 |
InfoPackage is locked | The short text describes the object sufficiently | |
| 147 | 146 |
InfoPackage & does not exist | The short text describes the object sufficiently | |
| 148 | 147 |
No log entries for object found since yesterday | The short text describes the object sufficiently | |
| 149 | 148 |
Logging ist not active | The short text describes the object sufficiently | |
| 150 | 149 |
Value '00' is not allowed as daemon; values '01' to '99' only | Space: object requires documentation | |
| 151 | 150 |
Daemon &1 does not yet exist - created during start of InfoPackage | Space: object requires documentation | |
| 152 | 151 |
Batch job completed, start daemon in new batch job | The short text describes the object sufficiently | |
| 153 | 152 |
InfoPackage start less than 1 minute ago or process change daemon | Space: object requires documentation | |
| 154 | 153 |
Change batch job of daemon (InfoPackage &1 affected) | The short text describes the object sufficiently | |
| 155 | 154 |
Termination after activation step through X_Message | The short text describes the object sufficiently | |
| 156 | 155 |
Termination - error in RSODSACTREQ | The short text describes the object sufficiently | |
| 157 | 156 |
Termination - no activation request entry found in DBOPS | The short text describes the object sufficiently | |
| 158 | 157 |
Termination - change log request was not found in RSTSODSREQUESTPG | The short text describes the object sufficiently | |
| 159 | 158 |
Termination - change log data package in RSTSODSREQUESTPG is too small | The short text describes the object sufficiently | |
| 160 | 159 |
Termination - change log data package is not found in RSODSACTREQ | The short text describes the object sufficiently | |
| 161 | 160 |
Termination - data package 0 was not found in RSODSACTREQ | The short text describes the object sufficiently | |
| 162 | 161 |
Termination - RSCRT_CTRL_CL was not deleted from template | The short text describes the object sufficiently | |
| 163 | 162 |
Termination - no CL data package entry in DBOPS at activation request | The short text describes the object sufficiently | |
| 164 | 163 |
InfoPackages for RDA cannot be used in process chains | The short text describes the object sufficiently | |
| 165 | 164 |
Demon with ID &1 does not exist | The short text describes the object sufficiently | |
| 166 | 165 |
Near real-time is running, but data has not yet been loaded for request | The short text describes the object sufficiently | |
| 167 | 166 |
There is already a real-time Ipak for DataSource & from source system & | The short text describes the object sufficiently | |
| 168 | 167 |
An InfoPackage cannot be created for DataSource & from source system & | The short text describes the object sufficiently | |
| 169 | 168 |
Error during creation of an Ipak for DataSource & from source system & | The short text describes the object sufficiently | |
| 170 | 169 |
None of the DataStore objects you selected can be updated | The short text describes the object sufficiently | |
| 171 | 170 |
Real-time InfoPackages cannot be edited in Ipak groups | The short text describes the object sufficiently | |
| 172 | 171 |
For this daemon there is no longer a background job to start in sm37 | The short text describes the object sufficiently | |
| 173 | 172 |
Lock on daemon &1 could not be set - no restart | The short text describes the object sufficiently | |
| 174 | 173 |
Daemon &1 with job &2 and count &3 successfully started immediately | The short text describes the object sufficiently | |
| 175 | 174 |
Error &1 during start of daemon &1 in Job &3 with count &4 | The short text describes the object sufficiently | |
| 176 | 175 |
Error while displaying the jobs for daemon & | The short text describes the object sufficiently | |
| 177 | 176 |
No sm37 job information is available for daemon &1 | The short text describes the object sufficiently | |
| 178 | 177 |
No InfoPackages that could be started found for this daemon | The short text describes the object sufficiently | |
| 179 | 178 |
No open PSA request found for DataSource &1 | The short text describes the object sufficiently | |
| 180 | 179 |
Logs no longer exist in table RSCRTMONDATA for '&' | The short text describes the object sufficiently | |
| 181 | 180 |
InfoPackage & cannot be maintained -> long text | Space: object requires documentation | |
| 182 | 181 |
Requests of InfoPackage &1 are also closed in process chain &2 | Space: object requires documentation | |
| 183 | 182 |
InfoPackage '&1' is not a hierarchy InfoPackage; canceled | The short text describes the object sufficiently | |
| 184 | 183 |
InfoPackage '&1': Load hierarchy '&2' (&3 of &4) | The short text describes the object sufficiently | |
| 185 | 189 |
******* Realtime Data Acquisition (new) ****** | The short text describes the object sufficiently | |
| 186 | 190 |
Table & is locked: Cancelled after attempt & | The short text describes the object sufficiently | |
| 187 | 191 |
Table & locked successfully on attempt & | The short text describes the object sufficiently | |
| 188 | 192 |
Locks removed for table & | The short text describes the object sufficiently | |
| 189 | 193 |
Cannot set locks for table & (lock mode &) | The short text describes the object sufficiently | |
| 190 | 194 |
Locks for table &: Work process &, lock mode &, duration & sec | The short text describes the object sufficiently | |
| 191 | 195 |
Cannot change table & | The short text describes the object sufficiently | |
| 192 | 200 |
******* Realtime Data Acquisition (new) ****** | The short text describes the object sufficiently | |
| 193 | 201 |
Unexpected program state (&1) | The short text describes the object sufficiently | |
| 194 | 202 |
No open PSA request found for DataSource &1 | The short text describes the object sufficiently | |
| 195 | 203 |
No open PSA data package for DataSource &1 found | The short text describes the object sufficiently | |
| 196 | 204 |
Select a request | The short text describes the object sufficiently | |
| 197 | 205 |
Upload period has to be between & and & minutes | The short text describes the object sufficiently | |
| 198 | 206 |
Error messages | The short text describes the object sufficiently | |
| 199 | 210 |
Specify a daemon | The short text describes the object sufficiently | |
| 200 | 211 |
Specify an InfoPackage | The short text describes the object sufficiently | |
| 201 | 212 |
Data package is locked | The short text describes the object sufficiently | |
| 202 | 213 |
Lock lifted | The short text describes the object sufficiently | |
| 203 | 214 |
Daemon is locked | The short text describes the object sufficiently | |
| 204 | 215 |
Not possible to assign to this daemon (status) | The short text describes the object sufficiently | |
| 205 | 216 |
Maximum runtime of daemon reached | The short text describes the object sufficiently | |
| 206 | 217 |
Moved to 'non-assigned nodes' | The short text describes the object sufficiently | |
| 207 | 218 |
Daemon & is running | The short text describes the object sufficiently | |
| 208 | 220 |
Specify an InfoPackage | The short text describes the object sufficiently | |
| 209 | 221 |
Batch job planned for InfoPackage and daemon. Start when batch job free | The short text describes the object sufficiently | |
| 210 | 222 |
No scheduling possible | The short text describes the object sufficiently | |
| 211 | 223 |
Deamon is already running or is locked by another user | The short text describes the object sufficiently | |
| 212 | 224 |
Cancellation by user | The short text describes the object sufficiently | |
| 213 | 225 |
InfoPackage currently locked by user & | The short text describes the object sufficiently | |
| 214 | 226 |
Request size smaller than 100,000 rows is not worthwhile; correct | The short text describes the object sufficiently | |
| 215 | 227 |
& is not PSA request | The short text describes the object sufficiently | |
| 216 | 228 |
Request closed | The short text describes the object sufficiently | |
| 217 | 230 |
Specify a DTP | The short text describes the object sufficiently | |
| 218 | 231 |
DTP currently locked by user & | The short text describes the object sufficiently | |
| 219 | 232 |
& is not a DTP for real-time data acquisition | The short text describes the object sufficiently | |
| 220 | 233 |
No request found | The short text describes the object sufficiently | |
| 221 | 234 |
DTP already assigned to InfoPackage | The short text describes the object sufficiently | |
| 222 | 235 |
DTP assigned to InfoPackage | The short text describes the object sufficiently | |
| 223 | 236 |
DTPs are assigned | The short text describes the object sufficiently | |
| 224 | 237 |
No active version for & | The short text describes the object sufficiently | |
| 225 | 238 |
Repair started for & | The short text describes the object sufficiently | |
| 226 | 239 |
Repair of & has not yet ended | The short text describes the object sufficiently | |
| 227 | 240 |
Batch job for repair request started; Content has to be activated | The short text describes the object sufficiently | |
| 228 | 241 |
Data package | The short text describes the object sufficiently | |
| 229 | 242 |
Data package closed at &1 | The short text describes the object sufficiently | |
| 230 | 243 |
Data package for daemon run at &1 | The short text describes the object sufficiently | |
| 231 | 244 |
No DTP request created | The short text describes the object sufficiently | |
| 232 | 245 |
You cannot start a daemon for this InfoPackage without a DTP | The short text describes the object sufficiently | |
| 233 | 246 |
Data package &1 already contains &2 records | The short text describes the object sufficiently | |
| 234 | 247 |
Request &1 alrady contains &2 records | The short text describes the object sufficiently | |
| 235 | 248 |
Setting status of InfoPackage & | The short text describes the object sufficiently | |
| 236 | 249 |
Changing assignment of InfoPackage & for daemon & | The short text describes the object sufficiently | |
| 237 | 250 |
InfoPackage & for daemon & started | The short text describes the object sufficiently | |
| 238 | 251 |
Status transfer not permitted (& -> & ) | The short text describes the object sufficiently | |
| 239 | 252 |
InfoPackage & for damon & finished | The short text describes the object sufficiently | |
| 240 | 253 |
Upload finished for InfoPackage & for daemon & | The short text describes the object sufficiently | |
| 241 | 254 |
Daemon process finished, initializing control tables | The short text describes the object sufficiently | |
| 242 | 255 |
Deleting InfoPackage & for daemon & from control table | The short text describes the object sufficiently | |
| 243 | 256 |
Status check of objects for RDA process & | The short text describes the object sufficiently | |
| 244 | 257 |
Finished closing; resetting status of InfoPackage & | The short text describes the object sufficiently | |
| 245 | 258 |
Initialization executed; Resetting status of InfoPackage & | The short text describes the object sufficiently | |
| 246 | 259 |
No real-time InfoPackage for this DataSource | The short text describes the object sufficiently | |
| 247 | 260 |
No InfoPackage is assigned to this daemon & | The short text describes the object sufficiently | |
| 248 | 261 |
Ending background process | The short text describes the object sufficiently | |
| 249 | 262 |
Daemon & inactive for & seconds | The short text describes the object sufficiently | |
| 250 | 263 |
Start of upload for InfoPackage & for daemon & | The short text describes the object sufficiently | |
| 251 | 264 |
Periodic scheduling of daemon &, with restart after maximum of & sec | The short text describes the object sufficiently | |
| 252 | 265 |
Daemon & scheduled as job &, on server & | The short text describes the object sufficiently | |
| 253 | 266 |
Request & opened, status set (& -> &) | The short text describes the object sufficiently | |
| 254 | 267 |
Data package & opened, status set (& -> &) | The short text describes the object sufficiently | |
| 255 | 268 |
Data package & closed in request &, status set ( -> &) | The short text describes the object sufficiently | |
| 256 | 269 |
Request & closed, status set (& -> &) | The short text describes the object sufficiently | |
| 257 | 270 |
& data records in data package & written to PSA, status set ( -> &) | The short text describes the object sufficiently | |
| 258 | 271 |
Data records deleted in the queue, status set (& -> &) | The short text describes the object sufficiently | |
| 259 | 272 |
Data records confirmed in the queue, status set (& -> &) | The short text describes the object sufficiently | |
| 260 | 273 |
Daemon lock for & set successfully on attempt & | The short text describes the object sufficiently | |
| 261 | 274 |
Daemon lock lifted for & | The short text describes the object sufficiently | |
| 262 | 275 |
Lock set for table & | The short text describes the object sufficiently | |
| 263 | 276 |
Lock lifted for table & | The short text describes the object sufficiently | |
| 264 | 277 |
Table & is already locked | The short text describes the object sufficiently | |
| 265 | 278 |
Not processing InfoPackage & for daemon & (status &) | The short text describes the object sufficiently | |
| 266 | 279 |
Status set (& -> &) | The short text describes the object sufficiently | |
| 267 | 280 |
InfoPackage & for daemon & is locked | The short text describes the object sufficiently | |
| 268 | 281 |
You are not allowed to set a lock for process & | The short text describes the object sufficiently | |
| 269 | 282 |
Job & with number & started | The short text describes the object sufficiently | |
| 270 | 283 |
& data records in data package & written to PSA | The short text describes the object sufficiently | |
| 271 | 284 |
Check of list of activated requests skipped | The short text describes the object sufficiently | |
| 272 | 285 |
Wrong daemon status | The short text describes the object sufficiently | |
| 273 | 286 |
Unexpected status | The short text describes the object sufficiently | |
| 274 | 287 |
Daemon is locked: Cancellation after attempt & | The short text describes the object sufficiently | |
| 275 | 288 |
Information Broadcasting: Predecessor job is still running for & | The short text describes the object sufficiently | |
| 276 | 290 |
***** Messages for Adapter ******* | The short text describes the object sufficiently | |
| 277 | 291 |
InfoPackage &: Writing TIDs | The short text describes the object sufficiently | |
| 278 | 292 |
InfoPackage &: TIDs successfully written | The short text describes the object sufficiently | |
| 279 | 293 |
InfoPackage &: Confirming TIDs | The short text describes the object sufficiently | |
| 280 | 294 |
InfoPackage &: TIDs successfully confirmed | The short text describes the object sufficiently | |
| 281 | 295 |
InfoPackage &: Deleting TIDs | The short text describes the object sufficiently | |
| 282 | 296 |
InfoPackage &: TIDs successfully deleted | The short text describes the object sufficiently | |
| 283 | 297 |
Function is no longer supported | The short text describes the object sufficiently | |
| 284 | 298 |
Functionality is not yet implemented | The short text describes the object sufficiently | |
| 285 | 299 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 286 | 301 |
&1 &2 saved as global setting for all daemons | The short text describes the object sufficiently | |
| 287 | 302 |
Real-time extr. completed successfully: DataSource &1, target system &2 | The short text describes the object sufficiently | |
| 288 | 303 |
Realtime extr. completed with errors: DataSource &1, target system &2 | The short text describes the object sufficiently | |
| 289 | 304 |
& records loaded, & records in data package & | The short text describes the object sufficiently | |
| 290 | 305 |
Load monitor: Caller & with & records | The short text describes the object sufficiently | |
| 291 | 306 |
Error during extraction: & rowa in l_t_tid, & rows in l_t_data | The short text describes the object sufficiently | |
| 292 | 307 |
Unable to confirm &1 TIDs in delta queue | The short text describes the object sufficiently | |
| 293 | 308 |
Unable to delete TIDs in delta queue | The short text describes the object sufficiently | |
| 294 | 310 |
Data package & is locked: Work proc. &, mode &, cancelled after attempt & | The short text describes the object sufficiently | |
| 295 | 311 |
Data package & locked successfully on attempt & | The short text describes the object sufficiently | |
| 296 | 312 |
Intention lock for data package & obtained on attempt & | The short text describes the object sufficiently | |
| 297 | 313 |
Cannot set intention lock for data package & | The short text describes the object sufficiently | |
| 298 | 314 |
Locks for data package &: Work process &, mode &, duration & sec | The short text describes the object sufficiently | |
| 299 | 315 |
Request & is locked: Work process &, mode &, cancelled after attempt & | The short text describes the object sufficiently | |
| 300 | 316 |
Request & locked successfully on attempt & | The short text describes the object sufficiently | |
| 301 | 317 |
Intention lock for request & obtained on attempt & | The short text describes the object sufficiently | |
| 302 | 318 |
Cannot set intention lock for request & | The short text describes the object sufficiently | |
| 303 | 319 |
Locks for request &: Work process &, mode &, duration & sec | The short text describes the object sufficiently | |
| 304 | 322 |
Closing request &1 for object &2... | The short text describes the object sufficiently | |
| 305 | 323 |
Request &1 closed | The short text describes the object sufficiently | |
| 306 | 324 |
&1 is not the current request; &2 is the current request | The short text describes the object sufficiently | |
| 307 | 325 |
Data in InfoObject &1 activated in &2 seconds | The short text describes the object sufficiently | |
| 308 | 326 |
Cannot activate data in InfoObject &1 | The short text describes the object sufficiently | |
| 309 | 327 |
Subsequent process chain &1 assigned | The short text describes the object sufficiently | |
| 310 | 328 |
Subsequent process &1 started for DTP &2 (log ID &3) | The short text describes the object sufficiently | |
| 311 | 329 |
Cannot start subsequent process chain &1 for DTP &2 (log ID &3) | The short text describes the object sufficiently | |
| 312 | 331 |
Execution of DTP &1 (data target &2) started | The short text describes the object sufficiently | |
| 313 | 332 |
Execution of DTP &1 (data target &2) ended | The short text describes the object sufficiently | |
| 314 | 333 |
DTP request &1 has RDA status &2 and contains &3 data package(s) | The short text describes the object sufficiently | |
| 315 | 335 |
Close request &2 for InfoPackage &1 for each process chain (selected) | The short text describes the object sufficiently | |
| 316 | 336 |
Close request &2 for InfoPackage &1 for each process chain (read) | The short text describes the object sufficiently | |
| 317 | 340 |
RDA daemon not started; completed delta requests not in target | Space: object requires documentation | |
| 318 | 341 |
Could not start RDA daemon; completed delta requests not activated | Space: object requires documentation | |
| 319 | 342 |
Could not start RDA daemon; requests are deleted in DataStore object | Space: object requires documentation | |
| 320 | 345 |
There is no active PUSH InfoPackage for DataSource &1(&2) | Space: object requires documentation | |
| 321 | 346 |
First create an RDA InfoPackage for DataSource &1(&2) | Space: object requires documentation | |
| 322 | 347 |
Daemon &2 may not be assigned to DataSource &1 | Space: object requires documentation | |
| 323 | 348 |
Cannot assign daemon &2 to data transfer process &1 | Space: object requires documentation | |
| 324 | 350 |
&1 error occurred while executing InfoPackage &2 with daemon &3 | The short text describes the object sufficiently | |
| 325 | 351 |
Daemon &3 executed InfoPackage &2 unsuccessfully for &1 seconds | The short text describes the object sufficiently | |
| 326 | 355 |
Information broadcasting activated for &1 (batch ID: &2) | The short text describes the object sufficiently | |
| 327 | 360 |
Assignment of &1 deleted | The short text describes the object sufficiently | |
| 328 | 361 |
Assignment of &1 created | The short text describes the object sufficiently | |
| 329 | 362 |
Could not delete assignment of &1 | The short text describes the object sufficiently | |
| 330 | 363 |
Could not create assignment of &1 | The short text describes the object sufficiently | |
| 331 | 364 |
Background job terminated; RDA status changed (&1 -> &2) | Space: object requires documentation | |
| 332 | 370 |
Select a daemon | Space: object requires documentation | |
| 333 | 371 |
Select a DataSource, InfoPackage or DTP | The short text describes the object sufficiently | |
| 334 | 372 |
Select a daemon, DataSource or InfoPackage | The short text describes the object sufficiently | |
| 335 | 373 |
Select a data transfer process (DTP) | The short text describes the object sufficiently | |
| 336 | 374 |
Select an InfoPackage, DTP or request | The short text describes the object sufficiently | |
| 337 | 375 |
RDA object &1 has unknown status &2 | The short text describes the object sufficiently | |
| 338 | 377 |
Background job terminated for unknown reason | The short text describes the object sufficiently | |
| 339 | 378 |
Request &1 has status red (error) | The short text describes the object sufficiently | |
| 340 | 379 |
Repair process chain cannot be uniquely defined for &1 | Space: object requires documentation | |
| 341 | 380 |
Repair process chain &1 saved | The short text describes the object sufficiently | |
| 342 | 381 |
There is already a repair process chain for &1 | Space: object requires documentation | |
| 343 | 382 |
There is no repair process chain yet for &1 | Space: object requires documentation | |
| 344 | 383 |
Repair process chain &1 for &2 started (log ID &3) | The short text describes the object sufficiently | |
| 345 | 384 |
Could not start repair process chain &1 for &2 (log ID &3) | The short text describes the object sufficiently | |
| 346 | 385 |
DTP &1 of DataSource &2 for InfoProvider &3 is not assigned | Space: object requires documentation | |
| 347 | 386 |
DTP &1 of DataSource &2 for InfoProvider &3 has no active version | Space: object requires documentation | |
| 348 | 387 |
DTP &1 of DataSource &2 for InfoProvider &3 has no instance | Space: object requires documentation | |
| 349 | 388 |
Background job &1 terminates continuously since an hour | Space: object requires documentation | |
| 350 | 389 |
Daemon &1 terminated correctly during server shutdown | The short text describes the object sufficiently | |
| 351 | 392 |
Request &1 cannot be closed (status not yellow) | The short text describes the object sufficiently | |
| 352 | 393 |
Request &1 marked to be closed | Space: object requires documentation | |
| 353 | 394 |
Request &1 being closed by assigned daemon | The short text describes the object sufficiently | |
| 354 | 395 |
Could not mark request &1 for closing | The short text describes the object sufficiently | |
| 355 | 396 |
Could not close request &1 | The short text describes the object sufficiently | |
| 356 | 399 |
Error of &1 in RDA start was reset | The short text describes the object sufficiently | |
| 357 | 401 |
Deleted inconsistent entry with key &1 &2 from table &3 | The short text describes the object sufficiently | |
| 358 | 402 |
Inserted missing entry with key &1 &2 into table &3 | The short text describes the object sufficiently | |
| 359 | 403 |
Updated RDA thresholds with key &1 &2 in table &3 | The short text describes the object sufficiently | |
| 360 | 404 |
Updated RDA status for &1 &2 in table &3 | The short text describes the object sufficiently | |
| 361 | 405 |
RDA is currently loading data into DSO &. Activation not possible. | The short text describes the object sufficiently | |
| 362 | 406 |
RDA load process &1 started (RDA status &2 -> &3) | The short text describes the object sufficiently | |
| 363 | 407 |
RDA load process &1 stopped (RDA status &2 -> &3) | The short text describes the object sufficiently | |
| 364 | 408 |
RDA load process &1 closing (RDA status &2 -> &3) | The short text describes the object sufficiently | |
| 365 | 409 |
RDA load process &1 has already executed data package &3 (&2) | The short text describes the object sufficiently | |
| 366 | 410 |
End task &1 because task &2 is scheduled or running | The short text describes the object sufficiently | |
| 367 | 411 |
New data package &2 available for RDA request &1 | The short text describes the object sufficiently | |
| 368 | 412 |
Updated RDA runtime info with key &1 &2 in table &3 | The short text describes the object sufficiently | |
| 369 | 414 |
Inconsistent notification; data package &3 (&2) for RDA process &1 | The short text describes the object sufficiently | |
| 370 | 420 |
Operation &1 started for &2 &3 at &4 | The short text describes the object sufficiently | |
| 371 | 421 |
Operation &1 finished for &2 &3 after &4 seconds | The short text describes the object sufficiently | |
| 372 | 422 |
Operation &1 failed for &2 &3 after &4 seconds | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 400 |
