RSRV -
The following messages are stored in message class RSRV: .
It is part of development package RSRV in software component BW-WHM. This development package consists of objects that can be grouped under "Analysis and Repair of BW Objects".
It is part of development package RSRV in software component BW-WHM. This development package consists of objects that can be grouped under "Analysis and Repair of BW Objects".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | &1&2&3&4 |
002 | Application Log: Log not found when a message was output |
003 | Application log could not be initialized: Header inconsistent |
004 | No error found. Choose 'Display' for details |
005 | Required parameter &1 for test &2 was not defined |
006 | The selected package name is already assigned. Choose a different one. |
007 | No runtime information found for the scheduled test. Terminated. |
008 | Package &1 to be executed is not a valid test package. Terminated. |
009 | Start batch run for package: &1: &2 |
010 | Check facts and dimensions table for InfoCube &1 |
011 | Examine dimension &1 (techn. name &2) |
012 | Dimension &1 (technical name &2) is a line item dimension |
013 | Dimension table &1 does not exist for dimension &3 (technical name &2) |
014 | Fact table &1 contains a record whose dimension key is 0 |
015 | No lost dimension key found in fact table &1 |
016 | &1 dimension key missing in fact table &2 |
017 | Dimension table &1 does not contain a zero record |
018 | Dimension key &1 missing in dimension table &2 |
019 | The first &1 errors are: |
020 | No lost SIDs of characteristic &1 found in dimension table &2 |
021 | &1 SIDs of characteristic &2 missing in dimension table &3 |
022 | SID table &1 does not contain a zero record. |
023 | SID &1 of chacteristic &2 missing in SID table &3 |
024 | Check all dimensions of InfoCube &1 for consistency with SID tables |
025 | Check dimension &1 of InfoCube &2 for consistency with SID tables |
026 | Check SID table of characteristic &3 and InfoCube &1, dimension &2 |
027 | Internal error reading the system time |
028 | Package &1 does not exist. Terminated. |
029 | Package &1 does not contain any tests. Terminated. |
030 | &1 &2 is not active on the database |
031 | Manual table maintenance switched on for &1 &2 |
032 | Unknown error reading the SE16 indicator (manual table maintenance) |
033 | &1 &2 is active. Manual table maintenance is switched off. |
034 | Check &1 &2 &3 &4 |
035 | Dimension &2 is not in InfoCube &1 |
036 | Characteristic &3 is not in dimension &2 of InfoCube &1 |
037 | Invalid internal status |
038 | &2 parameters were passed instead of the required &1 parameters |
039 | RSD_CUBE_GET: InfoCube &1 was not found |
040 | RSD_CUBE_GET: Internal error reading InfoCube &1 |
041 | There are no packages stored. |
042 | From zero, there are various facts to dimension key &1 in &2 |
043 | All facts in table &2 for dimension key &1 are zero |
044 | The following fact records have a total of <> 0 invalid dimension keys: |
045 | Dimension key &1 is not used |
046 | Select tests first (Drag&Drop) and execute them |
047 | Carry out the tests first ("Execute" pushbutton) |
048 | The tests must firstly be given parameters. Expand tests. |
049 | There are key figures with aggregation <> summation in InfoCube &1 |
050 | Internal error:Elementary test does not implement interface IF_RSRV_ATOM |
051 | Internal error: No object reference available for elementary test |
052 | Internal error: Unable to ascertain the parameters of the test |
053 | &1 keys for dimension &2 are missing in the fact table &3 |
054 | No keys for dimension &2 are missing from the fact table &2 |
055 | &1 o'clock on &2: Start test run for user &3 |
056 | &1 o'clock on &2: Start repair run for user &3 |
057 | Error in &1 &2 & 3. |
058 | Settings have been saved successfully |
059 | System was unable to save the settings |
060 | Select tests or basic tests first |
061 | No value found for parameter &1 |
062 | Value &2 for parameter &1 is invalid |
063 | Internal error: Class &1 does not implement the interface IF_RSRV_ATOM |
064 | There is no dimension with the name &1 in InfoCube &2 |
065 | Application log: Search for detail info. that is no longer used |
066 | Application log: Delete detail info. that is no longer used |
067 | Values were not found for all settings parameters |
068 | Value flagged for deletion in active version. No M-version available: &1 |
069 | A and M versions of a value are available. D-flag blank for character.&1 |
070 | Check blank entries in SID and master data tables of characteristic &1 |
071 | Check if blank values of attributes in characteristic &1 are type-related |
072 | Check object version of the values in characteristic &1 |
073 | Compare sizes of P or Q and X or Y tables for characteristic &1 |
074 | Compare characteristic values in SID/P/and Q tables for characteristic &1 |
075 | Check existence of values for navigation attributes in characteristic &1 |
076 | Checks whether there are aggregates for InfoCubes that do not exist |
077 | InfoCube &1 does not exist, but there are aggregates for this |
078 | Aggregates deleted from InfoCube &1 |
079 | Application log: No detail information found for deletion |
080 | This (elementary) test has no parameters |
081 | Specify the name of an InfoCube first |
082 | There is no InfoCube with the name &1 |
083 | Characteristic &1 does not occur in InfoCube &2 |
084 | InfoCube &1 is not a BasicCube |
085 | &1 &2: Check existence of table and flag for manual table maintenance |
086 | Check foreign key relationship between &1 &2 and &3 &4 |
087 | Check master data for characteristic &1 |
088 | Display selected message |
089 | Check foreign key relationship between fact and dimension tables |
090 | You are not authorized to look at this log |
091 | Internal error: Unable to call repair method of class &1 |
092 | Check database parameter for *-schema table for InfoCube &1 |
093 | Internal error when calling function module &1 |
094 | Nothing was tested for the database you used |
095 | Nothing was repaired for the database you used |
096 | Check flags in the SID table for characteristic with master data |
097 | &1 entries with DATAFL='X' and CHKFL=' ' found |
098 | Internal error when reading description (COB_PRO) of characteristic &1 |
099 | Internal error when calling &1 with parameters &2 &3 &4 |
100 | Internal error when specifying name of master data table for &1 |
101 | "Without master data" is selected for characteristic &1 |
102 | Master data table &1 exists in the database |
103 | Master data table &1 does not exist in the database |
104 | View &1 using master data tables does not exist in the database |
105 | View &1 using master data tables does not exist in the database |
106 | Characteristic &1 does not exist |
107 | Error was corrected |
108 | Repair attempt executed. Searching again for errors |
109 | Compare number range for SID of characteristic &1 with max. SID |
110 | Adjust number range for dimension &2 of InfoCube &1 with maximum DIMID |
111 | Error during repair. Repair probably not successful |
112 | Multiple inputs in an InfoCube dimension |
113 | Database statistics of an InfoCube and its aggregates |
114 | Database indexes of an InfoCube and its aggregates |
115 | Check Hierarchy &1 for Characteristic &2 (Hierarchy Version '&3') |
116 | No aggregates for non-existent InfoCubes |
117 | Key figure units in fact tables of InfoCube &1 are blank |
118 | InfoCube &1 not found |
119 | Internal error when reading information for InfoCube &1 |
120 | InfoObject &1 is using Unit-InfoObject &2. &2 is not in InfoCube &3 |
121 | Key figure &1 has type number and therefore has no unit |
122 | Key figure &1 has type integer and therefore has no unit |
123 | Key figure &1 has type date and therefore has no unit |
124 | Key figure &1 has type time and therefore has no unit |
125 | Key figure &1 has type amount and has no unit |
126 | Key figure &1 has type quantity and the fixed unit &2 |
127 | Key figure &1 has type amount and has no currency unit |
128 | Key figure &1 has type amount and the fixed currency unit &2 |
129 | In the fact table &1, all key figure values have <> 0 units |
130 | &2 units are missing in fact table &1. The first errors are: |
131 | (Fields in the Fact Table Sequence) |
132 | InfoCube &1 has no unit dimension |
133 | In the fact table &1, all key figure values have <> 0 units |
134 | &2 units are missing from fact table &1. See details |
135 | Search hierarchy &1 from characteristic &2 (including temporary versions) |
136 | Hier. &3 (tech. name &1) for characteristic &2 has obsolete version ' ' |
137 | No data for hierarchy &4 (tech. name &1) version &2 in table &3 |
138 | Checking hierarchy &3 (tech. name &1) version &2 |
139 | ROOTSID &1 is missing in the inclusion table for hier. &2 version &3 |
140 | ROOTSID &1 refers to &2 and not to &3 |
141 | RESTLEAF & has & as PRED & and not & |
142 | The hierarchy node has FACTOR = &1, but the value must be 1. |
143 | The hierarchy leaf &1 has SUM(FACTOR)=&2, but the value must be 1. |
144 | The hierarchy leaf &1 from type RESTLEAF is not unique |
145 | The hierarchy node &1 from type RESTNODE is not unique |
146 | The hierarchy leaf &1 is missing from the SID table |
147 | The INCFL flag in SID table is missing for hierarchy leaf &1 with SID &2 |
148 | Predecessor &1 from node &2 (LISTNO &3) is not in the hierarchy |
149 | InfoCube &1 has no InfoObjects with hierarchies |
150 | Check all hierarchies from characteristic &1 |
151 | Characteristic &1 Not Found |
152 | Characteristic &1 supports no hierarchies |
153 | Characteristic &1 has no active hierarchies |
154 | Characteristic &1 Has Inactive Hierarchies |
155 | Hierarchy for the Entered Data Not Found |
156 | Characteristic &1 Exists Only in a Modified Version |
157 | Characteristic &1 Is Not a Basic Characteristic |
158 | Hierarchy with Tests or Texts for Tests Not Found |
159 | Characteristic &1 uses no number range objects for SID assignment |
160 | Hierarchy Node Text References for Characteristic &1 |
161 | Characteristic &1 Not Found |
162 | K Table for Characteristic &1 Not Found |
163 | Internal error. Contact SAP |
164 | K Table Successfully Repaired |
165 | Error When Writing a Change to the K Table |
166 | No Errors Found in the K Table &1 |
167 | No Errors Found in the K Table &1; No Changes Executed |
168 | Check Text References in K Table &1 for Characteristic &2 |
169 | &1 Incorrect Records Found in K Table &2 for Characteristic &3 |
170 | There is no characteristic with name &1 |
171 | Package Successfully Saved |
172 | Database information about InfoProvider tables |
173 | Database information about InfoProvider &1 tables |
174 | Check general database parameters |
175 | Characters not allowed in characteristic values (characteristic &1) |
176 | No description in language &3 for hierarchy &1 of characteristic &2 |
177 | This function has not been implemented yet |
178 | This test does not provide any repair options. See test description. |
179 | Dimension view &1 does not exist for dimension &3 (technical name &2) |
180 | Package &1 does not exist |
181 | Package &1 deleted |
182 | Package &1 does not exist and could not be deleted |
183 | Check for Characteristic Values from Text Table in SID Table |
184 | Check for values of characteristic &1 from text table in SID table |
185 | Consistency Between PSA Partitions and SAP Administration Information |
186 | PSA Table &1 is not partitioned (according to RSTSODS) |
187 | There are &1 PSA tables. These are now being checked |
188 | Checking PSA table &1 |
189 | PSA table &1 is not partitioned in database |
190 | PSA table &1; packages for request &2 are in several partitions |
191 | Inconsistency: High value for table &1: &2 ; PARTNO value in RSTSODS: &3 |
192 | No error found for PSA table for &1 |
193 | Table &1 is not available on the database |
194 | All field changes were revoked |
195 | 'RSDU_PARTITIONS_INFO_GET': No partitioning information available for &1 |
196 | Unknown error when calling up 'RSDU_PARTITIONS_INFO_GET' for &1 |
197 | All values in SID table for characteristic &1 are correct |
198 | There are &2 values with the wrong internal format in the SID table |
199 | The first 10 errors are: |
200 | Value in SID table &1/ correct value &2/ SID in SID table &3 |
201 | Check values of characteristic &1 for conversion exit |
202 | Value &1 is not consistent (external: &2; internal: &3) |
203 | Characteristic &1 has no conversion routine; No check necessary |
204 | Characteristic &1 not a basis characteristic (basis characteristic: &2) |
205 | Check admin. information of hierarchies for one/all characteristics |
206 | Internal error: Test &1 has type &2 instead of type 'A' |
207 | PSA table &1 does not exist |
208 | Object version '&1' is invalid. Valid versions are 'A', 'D' and 'M' |
209 | &1 is not a (time) characteristic. It is an InfoObject of type &2. |
210 | Hierarchy directories are consistent |
211 | Hierarchy directories are inconsistent. See long text |
212 | Hierarchy directories are inconsistent. See long text |
213 | Details about existence of hierarchies with inconsistent admin. data |
214 | Check existence of SIDs from dimension table in hierarchy inclusion table |
215 | &1 SIDS from table &2 missing in table &3 |
216 | An entry is missing in the reporting hierarchy administration table |
217 | Inconsistency between Reporting and Warehouse Management hierarchy admin. |
218 | Hierarchy with HIEID = &1, HIESID = &2 has no remaining nodes |
219 | Dimension table &1 exists for dimension &3 (technical name &2) |
220 | Text found with language key '&1' (<>'DE'). Please correct |
221 | &1 new tests found. Please correct |
222 | Test found with unknown type '&1' (<> 'A','T',' ') |
223 | Cannot access stat. attribute of class &1. Is this class inactive? |
224 | Class &1 has implemented type &2 but not interface &3 |
225 | Text for class &1 still begins with a '?'. Please maintain |
226 | Text for class &1 saved with language '&2' (<> 'DE') |
227 | Could not save due to errors in check. Please correct |
228 | Data successfully saved |
229 | Type for entry '&1' is '&2'. Only 'A','T',' ' are allowed |
230 | Internal error (&1) occured. Terminating. |
231 | Documentation object &1 (with ID &2) not found in language &3 |
232 | Aggregate &1 of InfoCube &2 has been checked. ParentCube was &3 |
233 | Dimension view &1 exists for dimension &3 (technical name &2) |
234 | The SID table name for characteristic &1 could not be determined |
235 | SID table &1 for characteristic &2 does not exist |
236 | Date &1 is not plausible |
237 | Hierarchy version &1 does not exist |
238 | Hierarchy &1 does not exist |
239 | Characteristic &1: No value found with invalid flag combinations |
240 | Error when reading metadata for superior characteristic &1 from &2 |
241 | Error when specifying the SID table name for (basic) characteristic &1 |
242 | Value &2 is not a valid initial value of characteristic &1 |
243 | Value &2 for characteristic &1 is too long |
244 | Value &2 for characteristic &1 begins with blank characters |
245 | Value &2 for characteristic &1 does not conform to ALPHA |
246 | Value &2 for characteristic &1 is not numeric |
247 | Value &2 for characteristic &1 is not permitted |
248 | Value &2 for characteristic &1 is not plausible |
249 | Value &2 for char. &1 is in external and not internal format |
250 | No errors found with this test |
251 | &1 is a virtual InfoProvider. This test is therefor unnecessary. |
252 | &1 is a Multi InfoProvider. This test is therefor unnecessary. |
253 | &1 is a Remote InfoProvider. This test is therefor unnecessary. |
254 | &1 is an InfoProvider of an unknown type. The test is not possible. |
255 | &1 is a BasisInfoCube |
256 | &1 is a DataStore object |
257 | &1 is an aggregate |
258 | Cube &1 has &2 dimensions; &3 dimensions are line item dimensions |
259 | Table &1 has &2 entries. Size corresponds to &3% of the InfoCube |
260 | There are no table names for &2 for DataStore object and &1 |
261 | Table &3 does not exist for &2 for DataStore object &1 |
262 | Table &3 for &2 for DataStore object &1 has &4 records |
263 | Tests without parameters were instantiated |
264 | Char. &1 (basic char. &2) has number range number &3 with object &4 |
265 | Name of number range object for char. &1 (basic char. &2) unknown |
266 | Number range object &1 has status &2 |
267 | Unused entries in dimensions of BasicCube &1 |
268 | Package &1 already exists |
269 | Master data table of basic characteristic &1 is not generated |
270 | Tests still exist which were not given parameters |
271 | &1 on &2: Test run for user &3 completed |
272 | &1 on &2: Repair run for user &3 complete |
273 | &1 is not a valid name for a dimension |
274 | Time intervals in Q table for a characteristic with time-dep. master data |
275 | Characteristic &1 is "Attribute Only" and therefore occupies no SID table |
276 | Characteristic &1 does not get its SIDs by using a number range object |
277 | Maximum DIMIDs for dimension &2 is &3; respective number range obj. &1 |
278 | InfoCube '&1' does not exist, but there are still aggregate infos for it |
279 | A test was excluded from the repair run (see long text) |
280 | '&1' is not a basic characteristic |
281 | '&1' is not a valid characteristic |
282 | Internal error: Info about (navigation) attributes is not correct |
283 | You have no authorization to deactivate aggregates: Termination |
284 | No aggregates/BWA indices affected by reconstruction of X/Y table |
285 | Aggregates/BWA indexes to be deactivated without user interaction |
286 | Aggregate &2 (&3) of Infocube &1 must be deactivated |
287 | Terminated by user: No changes made |
288 | Reconstruction of X/Y table was terminated with an error |
289 | Internal error: Metadata of aggregates with UID &1 inconsistent |
290 | Unknown error when deactivating aggregates; termination |
291 | X/Y table of characteristic &1 successfully built ('&3', '&4') |
292 | Affected aggregates were successfully deactivated |
293 | The following aggregates/BWA indexes are affected |
294 | Messages from deactivation of the affected aggregates |
295 | X/Y table from characteristic &1 reconstructed w/o user interaction |
296 | No text exists for the test, which is implemented from class &1 |
297 | Error when specifying the SID table from basic characteristic &1 |
298 | SID table &1 does not exist. Test cannot be executed |
299 | &1 is a key figure; this test only makes sense for characteristics |
300 | Aggregate &1(&2) is correct. Parent cube &3. Check mode &4. |
301 | Aggregate &1 (&2) is incorrect. Parent cube &3. Check mode &4. |
302 | Aggregate &1(&2) is correct. Check aggregate &3 |
303 | Aggregate &1(&2) is not correct. Check aggregate &3 |
304 | Internal error in class &3: Test (class &2) does not have parameter &1 |
305 | Test &1&2 intentionally cancelled execution of test run |
306 | Execution cancelled by user |
307 | Package includes inconsistent tests and can therefore not be saved |
308 | Package &1 was not deleted |
309 | Package &1 was not saved |
310 | SID values in X and Y table: Characteristic '&1' |
311 | Package &1 is overwritten |
312 | Package name &1 includes invalid characters; &2 are valid |
313 | Unknown, profound errors with instance creation in test "&1" |
314 | Initial parameter value for "&1" with instance creation of test "&2" |
315 | No value for parameter "&1" with instance creation of test "&2" |
316 | Invalid parameter value &2 for parameter "&1" with instantiation of "&3" |
317 | Parameter values are inconsistent. See details |
318 | Error &1 (return code &2) with instance creation of test "&3" |
319 | Known cancellation with instance creation of test "&1" |
320 | Test &1 &2 was cancelled due to an unknown error |
321 | Summary of test results: |
322 | &1 in Test:&2&3 |
323 | Test log corresponds to defined detail level (&): |
324 | (See also the application log in transaction RSRV for &.) |
325 | RSRV: Error of type &1 occurred. Process chain cancelled |
326 | There are no partitioned InfoCubes |
327 | Check partitioning of aggregates for one InfoCube |
328 | Error when loading namespace and name of DataStore obj &1 without prefix |
329 | Check consistency of High Cardinality flag of Characteristic |
330 | Test of partitioning column for all Basis InfoCubes |
331 | The referential integrity is checked for &1 characteristics |
332 | InfoObject &1 does not exist |
333 | High Cardinality setting for InfoObject &1 in version &2 is inconsistent |
334 | High Cardinality setting for InfoObject &1 in version &2 is consistent |
340 | Status of data in InfoCubes (&1) |
341 | For Infocube/DataStore object &1, an entry is missing in RSMDATASTATE |
342 | Entry for InfoCube/DataStore object &1 is invalid in table RSMDATASTATE |
343 | Internal error when checking InfoCube &1 (RSDU_DATA_EXISTS_INFOCUBE) |
344 | Entry in RSMDATASTATE is initial although there is data in InfoCube &1 |
345 | &1 InfoCubes examined |
350 | &1 is used as a hierarchy characteristic. No SID conversion is possible |
351 | SID table &1 converted successfully (commit performed) |
352 | SID table &1 could not be converted |
353 | Hierarchy tables for InfoObject &1 converted successfully |
354 | Hierarchy tables for InfoObject &1 could not be converted |
355 | Conversion of dimension table &1 was successful (commit performed) |
356 | Conversion of dimension table &1 not successful |
357 | SID conversion for InfoObject &1 |
358 | An error occurred in the where-used list for InfoObject &1 |
359 | SID tables for InfoObject &1 could not be read |
360 | Hierarchy tables for InfoObject &1 could not be read |
361 | InfoObject &1 has no hierarchies. No conversion will take place |
362 | The hierarchy table for InfoOject &1 could not be read |
363 | Error occurred while reading table &1. No conversion will take place |
364 | Hierarchy table (HIESID &1) was successfully converted |
365 | Conversion not necessary. Entries within interval limits |
366 | Conversion necessary. Entries below interval limits |
367 | Conversion necessary. Entries within but also under interval limits |
368 | Conversion necessary. Entries within but also over interval limits |
369 | Conversion necessary. Entries under, above, and within interval limits |
370 | Conversion necessary. Entries under and above interval limits |
371 | Conversion necessary: Entries above interval limits |
372 | Internal error occurred while converting the SID table (ASSIGN failed) |
373 | Hierarchy table (HIESID &1) converted incorrectly |
374 | No changes taken up (rollback executed) |
375 | Changes transferred (commit executed) |
376 | Information for InfoObject &1 could not be read |
377 | Information for InfoObject &1: Inpermissible parameter transfer |
378 | Error occurred reading the number range object for InfoObject &1 |
379 | Error occurred setting the status for the number range object &1 |
380 | The status of the number range object (&1) was set successfully |
381 | Converts the dimension tables of the InfoCube |
382 | InfoCube &1 |
383 | Conversion of the SID table for InfoObject &1 |
384 | The number range object was not updated (quantity <= 0) |
385 | Updating number range object &1 |
386 | Converting the hierarchy table for InfoObject &1 |
387 | An error occurred while invalidating the OLAP cache |
388 | The OLAP cache was successfully invalidated |
389 | An error occurred while reading the table header |
390 | Table &1 does not exist in the database |
391 | Dimension &1 is a line item dimension. No conversion takes place |
392 | InfoCube &1 is not a basis / aggregate cube. No conversion necessary |
393 | SID conversion for InfoObject &1 completed successfully |
394 | InfoObject &1 is used in the following InfoCubes: |
395 | InfoObject &1 is not used in any InfoCube |
396 | Error occurred reading the number range status for number range object &1 |
397 | Error occurred while updating to SID table &1. (Open SQL exception) |
398 | Do not execute any BW functions during the repair |
399 | An error occurred during dynamic reading of table &1.(Open SQL exception) |
400 | Checking the dimension tables for the InfoCube |
401 | Check dimension table &1 |
402 | Inconsistence between SID table &1 and dimension table &2 -> see details |
403 | Table &1 needs to be repaired |
404 | It is possible to repair table &1 |
405 | It is not necessary to repair table &1 |
406 | It is not possible to repair table &1 |
407 | Checking hierarchies for InfoObject &1 |
408 | It is necessary to convert the hierarchy for InfoObject &1 (&2) |
409 | Conversion not necessary. Table &1 is initial |
410 | Fill in all required entry fields (the first three) |
411 | Type &1 &2 objects are unknown. (No TADIR entries found) |
412 | Object &1 &2 &3 is unknown. (No TADIR entry found) |
413 | The entry from &1 was already taken on for &2 (&3): Text is transferred |
414 | This entry already exists |
415 | The exception was saved successfully |
416 | Find and delete old cache elements |
418 | Delete unused cache elements before &1, &2. |
419 | Element Buffer-ID &1, storage &2, server &3 deletable. |
420 | The Delete Cache Elements process is already running |
421 | Invalid date |
425 | Issue Technical Properties on Aggregates (A Version) |
426 | A long text on the status of RSMDATASTATE for InfoCube &1 is available |
427 | Aggregates (A version) from InfoCube &1 were read. See details |
428 | No aggregates ('A' versions) were found for InfoCube &1 |
430 | InfoCube &1 of type "In-Memory" only has an F-facttable |
431 | InfoCube &1 of type "In-Memory" doesn't have a (physical) time dimension |
432 | InfoCube &1 of type "In-Memory" doesn't have aggregates |
433 | InfoCube &1 of type "In-Memory" only has a P-dimension |
434 | Check not possible for InfoCube &1 of type "in-memory" |
438 | Unknown error during conversion of characteristic values |
439 | There are &1 unused nodes in the K table of characteristic &2 |
440 | All nodes from the K table of characteristic &1 are used |
445 | Check cannot be executed for characteristic &1 (type "High Cardinality") |
446 | Characteristic &1 is of type "high cardinality" and has no master data |
450 | Check hierarchy &1 of characteristic &2 (only active version) |
451 | SID value &1 has no corresponding master data in P table |
452 | Exposure of BW hierarchy &1 for characteristic &2 in SAP HANA |
453 | This check cannot be performed |
455 | Correcting dimension keys of InfoCube &1. |
456 | Error when correcting dimension keys. |
457 | Merging duplicate records in fact tables of InfoCube &1. |
458 | Error when merging duplicate records in fact tables. |
459 | Executing zero-elimination for InfoCube &1. |
460 | Error when executing zero-elimination. |
461 | Deleting unused entries from dimension table(s) of InfoCube &1. |
462 | Error when deleting unused entries from dimension table(s). |
463 | Repair large Infocubes via report &1 in batch mode (Note &2). |
464 | Size of SID table:&1 and X table:&2 of Time Characteristics: &3 Not Equal |
465 | Error in accessing of the X table: &1 of Time characteristics:&2 |
466 | Rebuild of X table:&1 of Time Characteristics:&2 was successful |
467 | Rebuild of X table:&1 of Time Characteristics:&2 failed |
468 | Size of SID table:&1 and X table:&2 of Time Characteristics: &3 Equal |
469 | Comparision of size of SID table and X table of Time Chareacteristics:&1 |
470 | Comparision of size of SID table and X table of Time Chareacteristics |
473 | ------------ Messages for documents CL_RSOD_CHECK_FOLDER ------------- |
474 | Checking the root directory - existence and assignment of all documents |
475 | Checking document class &1... |
476 | Root directory for document class &1 not found or inconsistent |
477 | Root directory for document class &1 is consistent |
478 | Repairing all root directories... |
479 | Root directory for document class &1 was created with ID &2 |
480 | Directories were added as root directories for the BW application |
481 | Document &1 (ID=&2) has the incorrect directory class &3 |
482 | Document &1 (ID=&2) directory class corrected for &3 |
483 | Document &1 (ID=&2) has the incorrect folder directory ID &3 |
484 | Document &1 (ID=&2) directory ID corrected for &3 |
486 | All documents are consistent for class &1 |
487 | Root directories and documents were successfully repaired |
488 | Document &1 &2: Name of the Query Element &3 has been replaced by GUID |
489 | Document &1 &2: Name of the Query Element &3 has to be replaced by GUID |
500 | Foreign key relationship for DataStore obj. &1 with SID tables for chars |
501 | The SID values are missing for &1 specifications for characteristic &2 |
502 | &1 is not a DataStore object, but rather has cube type &2 |
503 | Too many missing specifications for InfoObject &1 |
504 | New SID values created for DataStore &1 |
505 | No missing values found for DataStore &1 |
506 | Test package &1 can be used in transaction RSRV |
507 | Test package &1 could not be locked |
508 | Test package &1 could not be deleted |
509 | Error while saving the test package &1 in transport request |
511 | Test package &1 deleted |
530 | Check M version for aggregate definitions (&1) |
531 | &1 aggregate definitions examined |
532 | Aggregate with UID &1 includes invalid chars. These will be deleted. |
533 | There are no aggregates for InfoCube &1 with technical name &2 |
534 | There are no aggregates for InfoCube &1 with UID &2 |
535 | Check aggregate directory |
550 | Test of currency of the generated program for DataStore object &1 |
569 | Check existence of BWA index for BW tables for InfoCube &1 |
570 | Check sums of keyfigures of BWA queries of InfoCube &1 |
571 | Compare sums of keyfigures of BWA queries of InfoCube &1 with database |
572 | Compare data of keyfigures of InfoCube &1 to BWA indexes |
573 | &1 for &2 &3 is not active |
574 | Hierarchies of characteristic &1 not relevant for BWA indexing |
575 | Compare data of key figures of InfoCube &1 to BWA indexes |
576 | Check sums of key figures of BWA queries of InfoCube &1 |
577 | Check existence of BWA index for BW tables for InfoCube &1 |
578 | There is no BWA index for table &1 of InfoCube &2. |
579 | Index of table &1 of InfoCube &2 exists in BW, not in BWA |
580 | Space consumption of MDC InfoProviders in DB2 f. Linux, UNIX and Windows |
581 | &1 is a write-optimized DataStore object. The check is not supported. |
582 | Data row compression of InfoProviders in DB2 f. Linux, UNIX and Windows |
583 | Data row compression of PSA tables in DB2 f. Linux, UNIX and Windows |
600 | Multibyte/Unicode Text Analysis and repair |
601 | Multibyte/Unicode Text Analysis and repair: BEx Objects for Language &1 |
602 | Analyze table &1 field &1 with RSWAD_CHK_MULTIBYTE_TEXTTABLE. |
603 | Analysis of &1 (&2) in language &4 results in &3 errors. |
604 | Analysis of &1 (&2) in langauge &3 shows no warnings |
605 | Correted &4 entries in &1 (&2) &3. |
606 | Multibyte/Unicode Text Analysis and repair: Text tables for Language &1 |
607 | This characteristic does not contain a text table |
610 | BEx Web Template Integrity Check. |
611 | Filter criteria &1 = &2. |
612 | Analysis of Template &1 (&2) has &3 issues. |
613 | No issues found in Template &1(&2). |
614 | Checking BEx Web Template &1 (BTMP, A-Version) |
625 | Run the Support Desk tool |
626 | Activation of personalization content |
627 | DataSource replication check |
629 | Status of technical content activation |
630 | Repair mechanism for IGS availability check |
631 | Repair mechanism for Admin Cockpit installation check |
699 | This program is obsolete and should not be used any longer |
751 | Duplicate Record Check for key fields in PSA table &1 |
752 | Total number of duplicates in the PSA table: &1 |
753 | No Duplicates found in the PSA table |
754 | Details of duplicate records of key fields |
755 | Details of &1 |
756 | Details of the routines between &1 and &2 |
757 | Details of keyfigure and keyvalues between &1 and &2 |
758 | Details of group &2 &1 with Aggregation |
759 | Details of group &2 &1 with Update Method and source |
760 | PSA Duplicate Record Check |
761 | Check Key Figures with different Key Value updates of an infoprovider |
762 | Comparison of D-version and A-version Routines of an infoprovider |
763 | &1 &2 &3 &4 |
764 | Technical Check for InfoSource / Transfer rule |
800 | Check for deleted requests that are still hanging in BWA |
801 | RSRV Checks CCMS monitoring |
802 | Internal error with CCMS connection: RC &1. |
803 | & & & & |
804 | Checking for leftover Request Deletions in BWA |
805 | One or more requests of Cube &1 must be deleted from BWA |
806 | No Request Deletion leftovers found in BWA |
807 | Repair of deleted requests that are still hanging in BWA |
808 | Leftover Request(s) in BWA of cube &1 are successfully deleted |
809 | Request &1 of Cube &2 must be deleted from BWA |
810 | Request deletion in BWA is not successful in cube &1 |
811 | Check '&1' is skipped (obsolete in SAP HANA) |
825 | Entries for Partition Pruning for MultiProviders |
826 | InfoCube &1 is not a MultiProvider |
827 | Restrictions for &1 version &2 are valid |
828 | Restrictions invalid for PartProvider &1 InfoObject &2. Valid Values: |
829 | &1 |
830 | No restrictions maintained for MultiProvider &1 in version &2 |
831 | Only Versions 'A' or 'M' are allowed |
850 | Check table replicates in BW |
851 | Error when calling up &1 for characteristic &2 |
852 | Error when reading compounding information for &1 |
853 | Error when examining compounding information for &1 |
854 | Data element of characteristic &1 unknown |
855 | Table &1 is consistent |
856 | Inconsistency found, error code: &1 |
871 | Check is only valid for SAP HANA |
872 | Check is only valid for distributed landscapes |
873 | Characteristic &1 does not have replicated tables |
874 | Check table &1 |
880 | Non-compatible time characteristics found |
881 | These are used by &1 records of the fact tables |
885 | Check does not make sense for InfoObjects with master data read class |
886 | Characteristic &1 has no navigational attribute; Checks are skipped |
890 | Test for load program |
891 | Load program is up-to-date |
892 | Generated program for loading data is not available |
893 | Active generated load program not found |
894 | Load program for advanced DataStore object is being retranslated |
898 | Save Test Package first |
899 | Transaction RSRVALT is obsolete. Please use transaction RSRV instead. |
999 | This program can only run in an SAP patch or development system |