SAP ABAP Message Class RSO_CTC (Message class for CTC related messages)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW (Application Component) SAP Business Information Warehouse
⤷ BW_CORE_TOOLS (Package) Tools from BW_CORE (not part of LEAN BW)
⤷ BW (Application Component) SAP Business Information Warehouse
⤷ BW_CORE_TOOLS (Package) Tools from BW_CORE (not part of LEAN BW)
Attributes
Message class | RSO_CTC | |
Short Description | Message class for CTC related messages | |
Changed On | 20140121 | |
Last Changed At | 101803 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Could not activate technical content | Space: object requires documentation | |
2 | 001 | Technical content activation still running | The short text describes the object sufficiently | |
3 | 002 | Technical content activated | The short text describes the object sufficiently | |
4 | 003 | DataSources of source system &1 replicated | The short text describes the object sufficiently | |
5 | 004 | DataSources of source system &1 not replicated | Space: object requires documentation | |
6 | 005 | Could not check for technical content activation | Space: object requires documentation | |
7 | 006 | Could not activate & | The short text describes the object sufficiently | |
8 | 007 | Check for Admin Cockpit installation | Space: object requires documentation | |
9 | 008 | Check for DataSource replication | Space: object requires documentation | |
10 | 009 | Check for J2EE Engine availability | Space: object requires documentation | |
11 | 010 | Check for activation of personalization content | Space: object requires documentation | |
12 | 011 | Check for status of technical content | Space: object requires documentation | |
13 | 012 | RFC destination in table RSODADMIN_INT is empty | Space: object requires documentation | |
14 | 013 | RFC destination entered is invalid | The short text describes the object sufficiently | |
15 | 014 | TREX server is down | The short text describes the object sufficiently | |
16 | 015 | TREX server is up | The short text describes the object sufficiently | |
17 | 016 | Initial indexing not started yet | The short text describes the object sufficiently | |
18 | 017 | Initial indexing in progress | The short text describes the object sufficiently | |
19 | 018 | Initial indexing completed | The short text describes the object sufficiently | |
20 | 019 | The short text describes the object sufficiently | ||
21 | 020 | Check for TREX status and indexing. | Space: object requires documentation | |
22 | 021 | Check for collection of content objects | The short text describes the object sufficiently | |
23 | 022 | Check for activation of all the objects for role | The short text describes the object sufficiently | |
24 | 023 | Check for replication of DataSource | The short text describes the object sufficiently | |
25 | 024 | Check for connection of the virtual provider | The short text describes the object sufficiently | |
26 | 025 | Could not complete operation, since logical system not found | The short text describes the object sufficiently | |
27 | 026 | J2EE Engine set up successfully | The short text describes the object sufficiently | |
28 | 027 | Could not contact IGS | Space: object requires documentation | |
29 | 028 | IGS set up successfully | The short text describes the object sufficiently | |
30 | 029 | Error modifying table &1 | The short text describes the object sufficiently | |
31 | 030 | Check for Internet Graphic Service | Space: object requires documentation | |
32 | 031 | Virtual providers of Admin Cockpit connected to source system &1 | The short text describes the object sufficiently | |
33 | 032 | Logical system &1 found | The short text describes the object sufficiently | |
34 | 033 | Could not find logical system &1 | The short text describes the object sufficiently | |
35 | 034 | Client is not a BW client. Set client: &1 | The short text describes the object sufficiently | |
36 | 035 | No entry named "BW" found in column "customizid" in table RSADMINA | The short text describes the object sufficiently | |
37 | 036 | Client not available in table T000 | The short text describes the object sufficiently | |
38 | 037 | Problem accessing ICF services 'Check SICF' 'SICF:TRA' | The short text describes the object sufficiently | |
39 | 038 | ICF service &1 active | The short text describes the object sufficiently | |
40 | 039 | ICF service &1 not active | Space: object requires documentation | |
41 | 040 | Database table RSADMINA has entry with customizid = BW | The short text describes the object sufficiently | |
42 | 041 | Debug user is correct | The short text describes the object sufficiently | |
43 | 042 | Debug user should be empty | The short text describes the object sufficiently | |
44 | 043 | Connection to TREX RFC destination is not available | The short text describes the object sufficiently | |
45 | 044 | Connection to TREX RFC destination is available | The short text describes the object sufficiently | |
46 | 045 | Standard transport system is in test mode (off) | The short text describes the object sufficiently | |
47 | 046 | Standard transport system is not in test mode | Space: object requires documentation | |
48 | 047 | No ALEREMOTE user found | The short text describes the object sufficiently | |
49 | 048 | Client is incorrect. | The short text describes the object sufficiently | |
50 | 049 | Check for BW system client ID | Space: object requires documentation | |
51 | 050 | Check for ICF services | Space: object requires documentation | |
52 | 051 | No entry found for logical system | Space: object requires documentation | |
53 | 052 | User &1 exists for client | The short text describes the object sufficiently | |
54 | 053 | User ALEREMOTE is not locked | The short text describes the object sufficiently | |
55 | 054 | User ALEREMOTE is locked | The short text describes the object sufficiently | |
56 | 055 | User ALEREMOTE does not exist for client &1 | The short text describes the object sufficiently | |
57 | 056 | User ALEREMOTE has profile S_BI-WHM_RFC | The short text describes the object sufficiently | |
58 | 057 | User ALEREMOTE does not have profile S_BI-WHM_RFC | Space: object requires documentation | |
59 | 058 | Add profile in SU01- SU01:TRA | The short text describes the object sufficiently | |
60 | 059 | User ALEREMOTE has profile S_BI-WX_RFC | The short text describes the object sufficiently | |
61 | 060 | User ALEREMOTE does not have profile S_BI-WX_RFC | Space: object requires documentation | |
62 | 061 | User ALEREMOTE has role SAP_RO_BCTRA | The short text describes the object sufficiently | |
63 | 062 | User ALEREMOTE does not have role SAP_RO_BCTRA | Space: object requires documentation | |
64 | 063 | Add role in SU01 - SU01:TRA | The short text describes the object sufficiently | |
65 | 064 | Check for table setting | Space: object requires documentation | |
66 | 065 | Check for user information | Space: object requires documentation | |
67 | 066 | Logical system details exist | The short text describes the object sufficiently | |
68 | 067 | Client is correct | The short text describes the object sufficiently | |
69 | 068 | Database table RSADMINS has no entry with customizid = BW | The short text describes the object sufficiently | |
70 | 069 | Database table RSADMINS has entry with customizid = BW | The short text describes the object sufficiently | |
71 | 070 | Check for standard BI jobs | Space: object requires documentation | |
72 | 071 | Job &1 is not running | Space: object requires documentation | |
73 | 072 | Job &1 is running correctly | The short text describes the object sufficiently | |
74 | 073 | Job &1 is running more than once | Space: object requires documentation | |
75 | 074 | Role &1 - &2 &3 --> &4 | Space: object requires documentation | |
76 | 075 | Error retrieving BW client | The short text describes the object sufficiently | |
77 | 076 | Check for generation of role and user synchronization | Space: object requires documentation | |
78 | 079 | Error assigning logon user as &1 to Myself RFC destination | The short text describes the object sufficiently | |
79 | 080 | DTP not available for Datasource &1 Source System &2 | The short text describes the object sufficiently | |
80 | 081 | Process chain &1 cannot be copied | The short text describes the object sufficiently | |
81 | 083 | Required Input fields are not filled | The short text describes the object sufficiently | |
82 | 084 | Object &1 of Type &2 is not assigned to Request/Package | The short text describes the object sufficiently | |
83 | 085 | Object &1 of Type &2 is not active | The short text describes the object sufficiently | |
84 | 086 | BW Objects listed in "Details" could not be assigned to Transport Request | The short text describes the object sufficiently | |
85 | 087 | Object &1 is not available in Active Version | The short text describes the object sufficiently | |
86 | 088 | The short text describes the object sufficiently | ||
87 | 089 | BW Objects listed in "Details" are not available in 'A' version | The short text describes the object sufficiently | |
88 | 090 | Error in creation of ALV List | The short text describes the object sufficiently | |
89 | 091 | BW System &1 is being disconnected from Source System &2 | The short text describes the object sufficiently | |
90 | 092 | BW System &1 is successfully disconnected from Source System &2 | The short text describes the object sufficiently | |
91 | 093 | User &1 has insufficient authorizations to perform BW system refresh | Space: object requires documentation | |
92 | 094 | The short text describes the object sufficiently | ||
93 | 095 | BIA Indexes are not present. This step is not required. | The short text describes the object sufficiently | |
94 | 096 | Error during clean up of BIA Index information. Refer log for details. | The short text describes the object sufficiently | |
95 | 097 | BIA Index information is successfully cleaned up. | The short text describes the object sufficiently | |
96 | 098 | Missing authorizations. Authorization Object: S_TREX_ADM , Activity: 02 | The short text describes the object sufficiently | |
97 | 099 | Host name of BI Enqueue server is successfully adjusted in TA RSPLSE | The short text describes the object sufficiently | |
98 | 100 | Correct host was successfully updated to BW RFC Destinations | The short text describes the object sufficiently | |
99 | 101 | Generation flag is successfully reset for DSO activation programs | The short text describes the object sufficiently | |
100 | 102 | No BW Source Systems connected. Step is not required. | The short text describes the object sufficiently | |
101 | 103 | Connection to Source System &1 successfully restored | The short text describes the object sufficiently | |
102 | 104 | Source system connection &1 will be deleted in BW | The short text describes the object sufficiently | |
103 | 105 | Source system connection &1 successully deleted in BW | The short text describes the object sufficiently | |
104 | 106 | Source System connection &1 will be restored | The short text describes the object sufficiently | |
105 | 107 | Source System &1 will be retained, no need to delete connection | The short text describes the object sufficiently | |
106 | 108 | Source system &2 will be remotely disconnected from BW &1 | The short text describes the object sufficiently | |
107 | 109 | Source system &2 successfully disconnected from BW &1 | The short text describes the object sufficiently | |
108 | 110 | Check not possible before BDLS-Task was executed | The short text describes the object sufficiently | |
109 | 115 | Step is not required as this is a Non-BW system | The short text describes the object sufficiently | |
110 | 116 | Structure &1 is not active; activate DataSource &2 at some time | The short text describes the object sufficiently | |
111 | 117 | Activation failure of structure &1 of DataSource &2 | The short text describes the object sufficiently | |
112 | 118 | Target structure &1 of DS &2 already exists with different fields | The short text describes the object sufficiently | |
113 | 119 | Transfer Structure &1 does not exist | The short text describes the object sufficiently | |
114 | 120 | Error when updating delta queues in source system &1 from BW | The short text describes the object sufficiently | |
115 | 121 | Delta queues in source system &1 successfully updated from BW | The short text describes the object sufficiently | |
116 | 124 | Source system &1 is still connected to receiver system &2 | Space: object requires documentation | |
117 | 125 | Source system &1 will be remotely re-connected to BW | The short text describes the object sufficiently | |
118 | 126 | Source system &1 is still connected to BW system &2 | Space: object requires documentation | |
119 | 127 | BDLS task has wrong mapping for system &1; it must be a BW source system | Space: object requires documentation | |
120 | 128 | &1 mapped in UI of BDLS task is not a valid BW source system | The short text describes the object sufficiently | |
121 | 129 | BDLS UI contains mappings to logical system &1. Remove this mapping. | Space: object requires documentation | |
122 | 132 | Corrections of note &1 is missing in system &2 | Space: object requires documentation | |
123 | 133 | Corrections of note &1 is missing in &2 system; implement this note | The short text describes the object sufficiently | |
124 | 134 | You have to perform this task manually for &1 according to note &2 | Space: object requires documentation | |
125 | 201 | Error retrieving logical system name of this BW system | The short text describes the object sufficiently | |
126 | 202 | Enter new logical system name for clone of this BW system | The short text describes the object sufficiently | |
127 | 203 | Request &1 not completed successfully. Monitor this request (Tx RSRQ) | The short text describes the object sufficiently | |
128 | 204 | Delta Queues successfully cloned for the selected source systems | The short text describes the object sufficiently | |
129 | 205 | Request delta for &1 (&2) before synchronization of delta queues | The short text describes the object sufficiently | |
130 | 206 | Check not possible before delta queues have been cloned | The short text describes the object sufficiently | |
131 | 208 | Automatically reset last attempt to clone delta queues in &1 for &2 | The short text describes the object sufficiently | |
132 | 209 | Previous logical system name &1 does not equal current name &2 | The short text describes the object sufficiently | |
133 | 210 | Updating ALE ports successfully done | The short text describes the object sufficiently | |
134 | 211 | Error updating ALE port of Source System &1 | The short text describes the object sufficiently | |
135 | 212 | Successfully activated ALE partner of Source System &1 | The short text describes the object sufficiently | |
136 | 213 | Predecessor task &1 not found in the tasklist | The short text describes the object sufficiently | |
137 | 214 | No entry in BDLS task found for logsys &1 | The short text describes the object sufficiently | |
138 | 215 | No RFC destination found for source system (logsys) &1 | The short text describes the object sufficiently | |
139 | 216 | This task is not compatible with task &1 | The short text describes the object sufficiently | |
140 | 217 | No BW client found: task (&1) can only be executed in a BW system | The short text describes the object sufficiently | |
141 | 218 | RFC Destination &1 has errors | The short text describes the object sufficiently | |
142 | 219 | Function module &1 missing in BW source system &2 | The short text describes the object sufficiently | |
143 | 220 | Preparation successful | The short text describes the object sufficiently | |
144 | 221 | Source system &2: Delta Queue contains much data (&1 blocks) | The short text describes the object sufficiently | |
145 | 222 | &1&2&3&4 | The short text describes the object sufficiently | |
146 | 223 | DataSource &2(&3): Delta Queue contains much data (&1 blocks) | The short text describes the object sufficiently | |
147 | 224 | Activating Transfer Rule &1 &2... | The short text describes the object sufficiently | |
148 | 225 | Activating DataSource &1 &2... | The short text describes the object sufficiently | |
149 | 226 | No action required as the RFC destination is already updated | The short text describes the object sufficiently | |
150 | 227 | RDA daemons and process chains could not be stopped | The short text describes the object sufficiently | |
151 | 228 | RDA daemons and process chains stopped successfully | The short text describes the object sufficiently | |
152 | 229 | RDA daemon could not close open delta requests | Space: object requires documentation | |
153 | 230 | The function &1 must be called within the BW client | The short text describes the object sufficiently | |
154 | 231 | No destination into BW client found (table RSADMINA, field TPBWMANDTRFC) | The short text describes the object sufficiently | |
155 | 232 | RDA daemons and process chains have been started successfully | The short text describes the object sufficiently | |
156 | 233 | RDA daemons and process chains could not be re-started | The short text describes the object sufficiently | |
157 | 234 | RDA daemons and process chains re-started successfully | The short text describes the object sufficiently | |
158 | 235 | &1 Process Chains have been re-scheduled | The short text describes the object sufficiently | |
159 | 236 | &1 RDA Daemons have been re-started | The short text describes the object sufficiently | |
160 | 237 | &1 Process Chain Start Processes have been de-scheduled | The short text describes the object sufficiently | |
161 | 238 | &1 RDA Infopackages have been suspended | The short text describes the object sufficiently | |
162 | 239 | &1 Process Chains are still active | The short text describes the object sufficiently | |
163 | 240 | &1 RDA InfoPackages are still active | The short text describes the object sufficiently | |
164 | 241 | &1 RDA requests are still open | The short text describes the object sufficiently | |
165 | 242 | Background job &1 &2 could not be started | The short text describes the object sufficiently | |
166 | 243 | Background job &1 &2 not found | The short text describes the object sufficiently | |
167 | 244 | Joblog of background job &1 &2 not found | The short text describes the object sufficiently | |
168 | 245 | Check activation status of DataSource &1(&2) | The short text describes the object sufficiently | |
169 | 246 | Check activation status of Transfer Rules, 3.x DataSource &1(&2) | The short text describes the object sufficiently | |
170 | 247 | No source systems have been selected | The short text describes the object sufficiently | |
171 | 248 | Logsys &1 not considered | The short text describes the object sufficiently | |
172 | 249 | BWA not present | The short text describes the object sufficiently | |
173 | 250 | Delta for DataSource &1 (&2) will have to be re-initialized in &3 | Space: object requires documentation | |
174 | 251 | &1 RDA daemons could not be re-scheduled (see BW transaction RSRDA) | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 711 |