SAP ABAP Message Class RSCV (Analysis of BW objects (InfoCubes...))
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-BEX-ET (Application Component) End User Technology
⤷
RSR (Package) BW: General reporting processor
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-BEX-ET (Application Component) End User Technology⤷
RSR (Package) BW: General reporting processor 
Attributes
| Message class |  |
RSCV |
| Short Description |  |
Analysis of BW objects (InfoCubes...) |
| Changed On |  |
20140121 |
| Last Changed At |  |
101748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
------------------------------------------------------------------------- | Space: object requires documentation | |
| 2 | 001 |
& & & | Space: object requires documentation | |
| 3 | 009 |
Generation no longer possible. Start the transaction again | Space: object requires documentation | |
| 4 | 010 |
Without errors and warnings | Space: object requires documentation | |
| 5 | 011 |
Disallowed entry for function module | Space: object requires documentation | |
| 6 | 012 |
Other eror & & & & | Space: object requires documentation | |
| 7 | 013 |
No results available. | Space: object requires documentation | |
| 8 | 014 |
No long text exists for message no. & in class & | Space: object requires documentation | |
| 9 | 015 |
Message &1 in class &2 of type &3 not found in language &4 | Space: object requires documentation | |
| 10 | 016 |
Please select a function module | Space: object requires documentation | |
| 11 | 017 |
No initialized languages found | Space: object requires documentation | |
| 12 | 018 |
System language for installed languages not found | Space: object requires documentation | |
| 13 | 020 |
InfoCube & was not found. | Space: object requires documentation | |
| 14 | 021 |
Error when reading the InfoCatalog of InfoCube &. | Space: object requires documentation | |
| 15 | 022 |
InfoObject & was not found in the InfoCube & | Space: object requires documentation | |
| 16 | 023 |
Table names could not be determined from InfoObject &. | Space: object requires documentation | |
| 17 | 024 |
Invalid entry & InfoCube &. | Space: object requires documentation | |
| 18 | 025 |
First select an InfoCube | Space: object requires documentation | |
| 19 | 026 |
The data dictionary could not be read for the InfoCube & | Space: object requires documentation | |
| 20 | 028 |
Checking InfoCube & with function &. | Space: object requires documentation | |
| 21 | 029 |
Checking & produced no errors or warnings. | Space: object requires documentation | |
| 22 | 030 |
Manual table maintenance (SE16) was switched on for & | Space: object requires documentation | |
| 23 | 040 |
Documentation for function module not available in language &1 | Space: object requires documentation | |
| 24 | 050 |
Time characteristic &1 cannot be derived | Space: object requires documentation | |
| 25 | 051 |
Time characteristic &1 is checked against time characteristic &2 | Space: object requires documentation | |
| 26 | 052 |
Start of check | The short text describes the object sufficiently | |
| 27 | 053 |
Record with the DIMID &1 contains non-compatible time characteristics | Space: object requires documentation | |
| 28 | 054 |
Time characteristic &1 value &2 does not fit with time char &3 val &4 | Space: object requires documentation | |
| 29 | 055 |
End of check. &1 data records have errors | The short text describes the object sufficiently | |
| 30 | 056 |
Consistency of time dimension of InfoCube &1 | Space: object requires documentation | |
| 31 | 057 |
InfoCube &1 has no time dimension, or FISCVARNT is missing | The short text describes the object sufficiently | |
| 32 | 058 |
InfoCube &1 does not exist or is not active | The short text describes the object sufficiently | |
| 33 | 059 |
The following checks were carried out: | The short text describes the object sufficiently | |
| 34 | 060 |
InfoCube &1 was marked as a Cube with a consistent time dimension | Space: object requires documentation | |
| 35 | 061 |
InfoCube &1 was marked as a Cube with an inconsistent time dimension | Space: object requires documentation | |
| 36 | 062 |
Table &1 contains &2 data records with an incorrect partition column | The short text describes the object sufficiently | |
| 37 | 063 |
Table &1 contains no records with an incorrect partitioning column | The short text describes the object sufficiently | |
| 38 | 064 |
Test of partitioning column of InfoCube &1 | Space: object requires documentation | |
| 39 | 065 |
Aggregates were deactivated. You must reconstruct them | Space: object requires documentation | |
| 40 | 066 |
Aggregates could not be automatically deactivated | Space: object requires documentation | |
| 41 | 067 |
Correcting table &1 | The short text describes the object sufficiently | |
| 42 | 068 |
Processing &1 different DIMIDs (dimension keys) | Space: object requires documentation | |
| 43 | 069 |
This DIMID is used by &1 records of the fact tables | The short text describes the object sufficiently | |
| 44 | 070 |
This DIMID is no longer used in the fact table | The short text describes the object sufficiently | |
| 45 | 071 |
Time dimension entries not being used are to be removed | The short text describes the object sufficiently | |
| 46 | 072 |
Time dimension entries not being used were successfully removed | The short text describes the object sufficiently | |
| 47 | 073 |
Error when removing entries not being used | Space: object requires documentation | |
| 48 | 074 |
Time dimension entries not being used removed from &1 | The short text describes the object sufficiently | |
| 49 | 075 |
Error when reading metadata for InfoCube &1 | The short text describes the object sufficiently | |
| 50 | 076 |
InfoCube &1 is not partitioned. Test not carried out | The short text describes the object sufficiently | |
| 51 | 077 |
Metadata inconsistency in InfoCube &1. Test not carried out | The short text describes the object sufficiently | |
| 52 | 078 |
InfoCube &1 does not contain a time dimension. Test not carried out | The short text describes the object sufficiently | |
| 53 | 079 |
An SQL error occured in the data repair. Process not ended | The short text describes the object sufficiently | |
| 54 | 080 |
Total of &1 records repaired in table &2 | The short text describes the object sufficiently | |
| 55 | 081 |
Changes were committed | The short text describes the object sufficiently | |
| 56 | 082 |
Consistency of time dimension of all InfoCubes | Space: object requires documentation | |
| 57 | 083 |
No master data found for characteristic of test described subsequently | Space: object requires documentation | |
| 58 | 084 |
Fiscal year period is too large | Space: object requires documentation | |
| 59 | 085 |
Error when deriving or determining fiscal year period | Space: object requires documentation | |
| 60 | 086 |
Correction not necessary for InfoCube &1 | The short text describes the object sufficiently | |
| 61 | 087 |
The partitioning column for InfoCube &1 is repaired | The short text describes the object sufficiently | |
| 62 | 088 |
The following table contains suggested corrections | Space: object requires documentation | |
| 63 | 089 |
Execute suggested repairs in the time dimension table | The short text describes the object sufficiently | |
| 64 | 090 |
Errors occurred while changing dimension table. Changes rolled back | The short text describes the object sufficiently | |
| 65 | 091 |
The modified records were successfully written into the table | The short text describes the object sufficiently | |
| 66 | 092 |
Additional &1 data records contain errors | The short text describes the object sufficiently | |
| 67 | 093 |
Data records with a different fiscal variant already exist | The short text describes the object sufficiently | |
| 68 | 094 |
Data records exist for one fiscal variant only | The short text describes the object sufficiently | |
| 69 | 095 |
Fiscal variant can be subsequently set to a fixed value | The short text describes the object sufficiently | |
| 70 | 096 |
Fiscal variant is not specified | The short text describes the object sufficiently | |
| 71 | 097 |
Time characteristics are inconsistent | The short text describes the object sufficiently | |
| 72 | 098 |
Only partial time characteristics. Check not possible | The short text describes the object sufficiently | |
| 73 | 099 |
Cannot check partial time characteristics due to missing year | The short text describes the object sufficiently | |
| 74 | 106 |
DATAFL for SID &1 in SID table &2 not set | Space: object requires documentation | |
| 75 | 107 |
Checking of dimension '&1' (&2) produced errors or warnings | Space: object requires documentation | |
| 76 | 108 |
No errors: Dimension '&1' characteristic '&2' | Space: object requires documentation | |
| 77 | 109 |
Checking dimension '&1' characteristic '&2' | Space: object requires documentation | |
| 78 | 110 |
Module RSDG_CUBE_CHECK established an error in InfoCube & | Space: object requires documentation | |
| 79 | 111 |
Type of incorrect InfoObject is '&'. | Space: object requires documentation | |
| 80 | 112 |
The error affects InfoObject '&' | Space: object requires documentation | |
| 81 | 113 |
Referenced InfoObject '&' is incorrect. | Space: object requires documentation | |
| 82 | 114 |
Dimension '&' is incorrect | Space: object requires documentation | |
| 83 | 115 |
Number of errors: & | Space: object requires documentation | |
| 84 | 116 |
Checking InfoCube & with & without errors and warnings. | Space: object requires documentation | |
| 85 | 117 |
Check of the database indices could not be generated | Space: object requires documentation | |
| 86 | 118 |
Database index & is of type & | Space: object requires documentation | |
| 87 | 119 |
A BITMAP index for index &, field &2 (cat. &3) improves response times | Space: object requires documentation | |
| 88 | 120 |
One or more SIDs for the InfoObject are incorrect | Space: object requires documentation | |
| 89 | 121 |
No errors in the SID table for InfoObject &. | Space: object requires documentation | |
| 90 | 122 |
SID table does not exist for InfoObject &. | Space: object requires documentation | |
| 91 | 123 |
Master data table & does not exist for InfoObject &. | Space: object requires documentation | |
| 92 | 124 |
Dimension table & does not have any entries for version & | Space: object requires documentation | |
| 93 | 125 |
Default entry SID=0 missing in SID table &, InfoObject & | Space: object requires documentation | |
| 94 | 126 |
More than one SID = 0 in entry in SID table &, InfoObject & | Space: object requires documentation | |
| 95 | 127 |
In row &4 of table &1, the value '&3' has the SIF = 0, InfoObject &2 | Space: object requires documentation | |
| 96 | 128 |
SID table & has no entries. | Space: object requires documentation | |
| 97 | 129 |
Master data table & has no entries for version &. | Space: object requires documentation | |
| 98 | 130 |
Entry &1 in SID table of char. &2 is missing in master data table &3 | Space: object requires documentation | |
| 99 | 131 |
Entry & in master data table does not have an SID. | Space: object requires documentation | |
| 100 | 132 |
SID=0 Entry &1 in &2 also contained in master data &3 of InfoObject &4. | Space: object requires documentation | |
| 101 | 133 |
Checking SID for InfoObject & InfoCube & tables: & and & | Space: object requires documentation | |
| 102 | 134 |
Entry & in SID table & without CHCKFL although data is present in &. | Space: object requires documentation | |
| 103 | 135 |
Master data table & exists for InfoObject & but NOVALFL = 'X'. | Space: object requires documentation | |
| 104 | 136 |
Checking of MID table & produced warnings. | Space: object requires documentation | |
| 105 | 137 |
Checking of SID table & produced errors. | Space: object requires documentation | |
| 106 | 138 |
Field name could not be read for InfoObject & (CHABSNM &). | Space: object requires documentation | |
| 107 | 139 |
SIF & of InfoObject & appears several times, but must be unique | Space: object requires documentation | |
| 108 | 140 |
Dimension table '&' (techn. name &) does not exist for InfoCube & | Space: object requires documentation | |
| 109 | 141 |
Checking dimension no. &, '&' (techn. name &, table &) | Space: object requires documentation | |
| 110 | 142 |
No error in dimension no. &, '&' (techn. name &, table &) | Space: object requires documentation | |
| 111 | 143 |
Entry & in master data table & is missing in SID table & (InfoObject &) | Space: object requires documentation | |
| 112 | 144 |
Entry &1 in dimension table &2 is missing in SID table &3 | Space: object requires documentation | |
| 113 | 145 |
ID & of dimension & of the fact table is missing in dimension table & | Space: object requires documentation | |
| 114 | 146 |
ID 0 of dimension & of the fact table is missing in dimension table & | Space: object requires documentation | |
| 115 | 147 |
Entry & in table & cannot be derived from table & | Space: object requires documentation | |
| 116 | 148 |
Entry & in table & is not compatible with table & | Space: object requires documentation | |
| 117 | 149 |
Check of fact table / dimension &1 produced errors or warnings | Space: object requires documentation | |
| 118 | 150 |
No hierarchy exists for InfoObject & | Space: object requires documentation | |
| 119 | 151 |
No hierarchy data exists for InfoObject & in table & | Space: object requires documentation | |
| 120 | 152 |
Hierarchy &3 (SIF &1) for InfoObject &2 has obsolete version ' ' | Space: object requires documentation | |
| 121 | 153 |
No data for hierarchy &4 (SIF &1) version &2 in table &3 | Space: object requires documentation | |
| 122 | 154 |
Checking hierarchy &3 (SIF &1) version &2 | Space: object requires documentation | |
| 123 | 155 |
Hierarchies from InfoObject & o.k. | Space: object requires documentation | |
| 124 | 156 |
ROOTSID & is missing in inclusion table of hierarchy & version & | Space: object requires documentation | |
| 125 | 157 |
ROOTSID & jumps to & and not to & | Space: object requires documentation | |
| 126 | 158 |
RESTLEAF & has & as PRED & and not & | Space: object requires documentation | |
| 127 | 159 |
Hierarchy node has FACTOR = &, but the value must be 1 | Space: object requires documentation | |
| 128 | 160 |
Hierarchy screen & has SUM(FACTOR)=&, but the value must be 1 | Space: object requires documentation | |
| 129 | 161 |
Hierarchy screen & of type RESTLEAF is not unique | Space: object requires documentation | |
| 130 | 162 |
Hierarchy node & of type RESTNODE is not unique | Space: object requires documentation | |
| 131 | 163 |
Hierarchy leaf & is missing in the SID table | Space: object requires documentation | |
| 132 | 164 |
Hierarchy sheet & with SID & does not have INCFL flag in the SID table | Space: object requires documentation | |
| 133 | 165 |
Predecessor & of node & (LISTNO &) is not contained in the hierarchy | Space: object requires documentation | |
| 134 | 166 |
InfoCube & does not contain any InfoObjects with hierarchies | Space: object requires documentation | |
| 135 | 167 |
Hierarchy &2 (SIF &1) is defective. | Space: object requires documentation | |
| 136 | 170 |
Checks navigation attribute & (tables & and &) | Space: object requires documentation | |
| 137 | 171 |
Table & does not exist | Space: object requires documentation | |
| 138 | 172 |
There are no records in table & for records &, & | Space: object requires documentation | |
| 139 | 173 |
The check of navigation attribute & produced errors | Space: object requires documentation | |
| 140 | 174 |
The check of navigation attribute & produced warnings | Space: object requires documentation | |
| 141 | 175 |
Navigation attribute & without errors and warnings | Space: object requires documentation | |
| 142 | 176 |
No navigation attributes available | Space: object requires documentation | |
| 143 | 177 |
Master data of navigation attribute &1 in InfoCube &2 is incorrect. | Space: object requires documentation | |
| 144 | 180 |
Record with initial unit dimension (&) does not have initial key figures | Space: object requires documentation | |
| 145 | 181 |
Checking the units of InfoCube & produced errors | Space: object requires documentation | |
| 146 | 182 |
Checking the units of InfoCube & produced warnings | Space: object requires documentation | |
| 147 | 183 |
Checking the units of InfoCube & without errors and warnings | Space: object requires documentation | |
| 148 | 184 |
InfoCube & does not contain a dimension | Space: object requires documentation | |
| 149 | 189 |
No information from database system &1 contained for InfoCube &1 | Space: object requires documentation | |
| 150 | 190 |
The number of indices of InfoCube &1 is incorrect | Space: object requires documentation | |
| 151 | 191 |
Star transformation is not switched on | Space: object requires documentation | |
| 152 | 192 |
Merge area for bitmaps is too small (& < & MByte) | Space: object requires documentation | |
| 153 | 193 |
'Create' area for bitmaps is too small (& < & MByte) | Space: object requires documentation | |
| 154 | 194 |
Index &1, field &2 (status &3) is invalid | Space: object requires documentation | |
| 155 | 195 |
InfoCube &1 indices are correctly set | Space: object requires documentation | |
| 156 | 196 |
Database parameters for star transformation and bitmap indices o.k. | Space: object requires documentation | |
| 157 | 197 |
Index &1, field &2 is of type &3 | Space: object requires documentation | |
| 158 | 198 |
The indices of InfoCube &1 are incorrectly set | Space: object requires documentation | |
| 159 | 200 |
Unique ID for program generation could not be created | Space: object requires documentation | |
| 160 | 201 |
Deletion of generated program & refused (authorization ?) | Space: object requires documentation | |
| 161 | 202 |
Error when deleting generated program &. | Space: object requires documentation | |
| 162 | 203 |
Template & not found when generating | Space: object requires documentation | |
| 163 | 204 |
Syntax error in template class & | Space: object requires documentation | |
| 164 | 205 |
Syntax error in generated program & (row &, message: &) | Space: object requires documentation | |
| 165 | 206 |
Program generated for InfoObject & | Space: object requires documentation | |
| 166 | 207 |
Invalid program class & | Space: object requires documentation | |
| 167 | 208 |
Unique program ID & invalid | Space: object requires documentation | |
| 168 | 209 |
Generation not possible due to external lock & | Space: object requires documentation | |
| 169 | 210 |
InfoObject &1: System error when generating &2 | Space: object requires documentation | |
| 170 | 211 |
Internal error function module RSS_PROGRAM_GENERATE | Space: object requires documentation | |
| 171 | 212 |
Error in row & | Space: object requires documentation | |
| 172 | 213 |
Generation of utility routines for characteristic & ... | Space: object requires documentation | |
| 173 | 220 |
Fact table &1 has not yet been analyzed | Space: object requires documentation | |
| 174 | 221 |
Fact table &1 was last analyzed &2 days ago | Space: object requires documentation | |
| 175 | 222 |
Dimension table &1 has never been analyzed | Space: object requires documentation | |
| 176 | 223 |
Dimension table &1 was last analyzed &2 days ago | Space: object requires documentation | |
| 177 | 224 |
Index &1 has never been analyzed | Space: object requires documentation | |
| 178 | 225 |
Index &1 was last analyzed &2 days ago | Space: object requires documentation | |
| 179 | 226 |
DB Statistics fact-, dimension table and indices are o.k. | Space: object requires documentation | |
| 180 | 227 |
DB statistics for InfoCube &1 must be recreated | Space: object requires documentation | |
| 181 | 228 |
DB statistics for InfoCube &1, table &2 must be recreated | Space: object requires documentation | |
| 182 | 229 |
Table &1 has &2 entries. Size corresponds to &3% of the InfoCube | Space: object requires documentation | |
| 183 | 230 |
Line item dimension &1 is not checked | Space: object requires documentation | |
| 184 | 250 |
An entry is missing in table RSMDATASTATE for InfoCube &1 | Space: object requires documentation | |
| 185 | 251 |
Condition &2 is not fulfilled for InfoCube &1 | Space: object requires documentation | |
| 186 | 252 |
RSMDATASTATE blank, although InfoCube &1 &2 contains trans. data records | Space: object requires documentation | |
| 187 | 253 |
Internal error when checking InfoCube &1 (RSDU_DATA_EXISTS_INFOCUBE) | Space: object requires documentation | |
| 188 | 254 |
Entry in RSMDATASTATE is initial although there is data in InfoCube &1 | Space: object requires documentation | |
| 189 | 260 |
Master data of characteristic &1 is consistent | Space: object requires documentation | |
| 190 | 261 |
The initial entry in the master data of characteristic &1 is missing | Space: object requires documentation | |
| 191 | 262 |
&1 Entries exist several times in master data of &1 | Space: object requires documentation | |
| 192 | 263 |
Master data of &1 has &2 overlapping entries in version '&3' | Space: object requires documentation | |
| 193 | 264 |
Master data of &1 display &2 gaps in version '&3' | Space: object requires documentation | |
| 194 | 265 |
Invalid record with version '&2', changed='&3' for &1 found | Space: object requires documentation | |
| 195 | 266 |
The master data cannot be checked for InfoObject &1 | Space: object requires documentation | |
| 196 | 267 |
Following errors occurred during master data check for char. &1: | Space: object requires documentation | |
| 197 | 270 |
No queries avaialble for InfoCube &1 | Space: object requires documentation | |
| 198 | 271 |
Query "&2" could not be found for InfoCube &1 | Space: object requires documentation | |
| 199 | 272 |
Errors occurred when loading query "&2" of InfoCube &1 | Space: object requires documentation | |
| 200 | 273 |
Query "&2" of InfoCube &1 could not be generated | Space: object requires documentation | |
| 201 | 274 |
Generation of query "&2" of InfoCube &1 produced the following errors | Space: object requires documentation | |
| 202 | 275 |
Queries of InfoCube &1 are all correct | Space: object requires documentation | |
| 203 | 276 |
Analyzing query &1 | Space: object requires documentation | |
| 204 | 277 |
Query &1 was generated without errors | Space: object requires documentation | |
| 205 | 278 |
The name (COMPID) for the query is blank (COMPUID &1, GENUNIID &2) | Space: object requires documentation | |
| 206 | 300 |
Check &1 (&2) successfully started in the background | Space: object requires documentation | |
| 207 | 301 |
Check &1 (&2) successfully started in the background (&3) | Space: object requires documentation | |
| 208 | 320 |
Checking the time-dependent master data produced no errors | Space: object requires documentation | |
| 209 | 321 |
Checking the time-dependent master data produced warnings | Space: object requires documentation | |
| 210 | 322 |
Checking the time-dependent master data produced errors or warnings | Space: object requires documentation | |
| 211 | 323 |
InfoCube &1 has no InfoObjects with time-dependent master data | Space: object requires documentation | |
| 212 | 330 |
InfoCube &1 has no InfoObjects with master data | Space: object requires documentation | |
| 213 | 331 |
Check of master data &1 &2 produced neither errors nor warnings | Space: object requires documentation | |
| 214 | 332 |
Check of master data &1 &2 produced warnings | Space: object requires documentation | |
| 215 | 333 |
Check of master data &1 &2 produced errors or warnings | Space: object requires documentation | |
| 216 | 334 |
Check of master data InfoObject &1, table &2 | Space: object requires documentation | |
| 217 | 335 |
Master data '&1' in table &2 (char. &3) contains disallowed characters | Space: object requires documentation | |
| 218 | 336 |
Master data of char. &1 (table &2) contain characters not permitted | Space: object requires documentation | |
| 219 | 337 |
Master data '&1' in table &2 (characteristic &3) contains small letters | Space: object requires documentation | |
| 220 | 338 |
Reconstruction of aggregates and hierarchies started in the background | Space: object requires documentation | |
| 221 | 339 |
Program 'RSR_ERROR_REPORT' could not be deleted | Space: object requires documentation | |
| 222 | 340 |
Aggregate &1 could not be filled | Space: object requires documentation | |
| 223 | 341 |
Node '&1' for hierarchy &2 (characteristic &3) contains small letters | Space: object requires documentation | |
| 224 | 342 |
Node '&1' for hierarchy &2 (char. &3) contains non-permitted characters | Space: object requires documentation | |
| 225 | 343 |
Check hierarchies for InfoObject &1 | Space: object requires documentation | |
| 226 | 344 |
Hierarchy '&1' for InfoObjects &2 could not be activated | Space: object requires documentation | |
| 227 | 345 |
Status of number range for characteristic &1 is &2 too small | Space: object requires documentation | |
| 228 | 346 |
Status of number range for characteristic &1 is correct | Space: object requires documentation | |
| 229 | 347 |
Number range object for characteristic &2 does not exist | Space: object requires documentation | |
| 230 | 348 |
The number range interval for characteristic &1 does not exist | Space: object requires documentation | |
| 231 | 350 |
Entry &1 in table &2 is invalid | Space: object requires documentation | |
| 232 | 355 |
Status of number range &1 for dimension &2 is &3 too small | Space: object requires documentation | |
| 233 | 356 |
The status of number range &1 for dimension &2 is correct | Space: object requires documentation | |
| 234 | 357 |
Number range object &1 for dimension &2 is missing | Space: object requires documentation | |
| 235 | 360 |
PSA table &1 is not partitioned in database | Space: object requires documentation | |
| 236 | 361 |
PSA table &1 ; request &2 partition &3, packages are in partition &4 | Space: object requires documentation | |
| 237 | 362 |
Inconsistency: High value for table &1: &2 ; PARTNO value in RSTSODS: &3 | Space: object requires documentation | |
| 238 | 400 |
Available repairs have been successfully carried out (see results) | Space: object requires documentation | |
| 239 | 401 |
No repairs were necessary | Space: object requires documentation | |
| 240 | 402 |
No repairs were carried out | Space: object requires documentation | |
| 241 | 403 |
A repair could not be successfully be carried out | Space: object requires documentation | |
| 242 | 404 |
Repair for Message &1 (Object &2) Failed | Space: object requires documentation | |
| 243 | 405 |
Repair for Message &1 (Object &2) Carried Out Successfully | Space: object requires documentation | |
| 244 | 410 |
Multiple SIF &1 of InfoObject &2 is generated with a number range | Space: object requires documentation | |
| 245 | 411 |
Multiple SIF &1 of InfoObject &2 is generated with an Exit module | Space: object requires documentation | |
| 246 | 412 |
Multiple SIF &1 of InfoObject &2 is generated in an unknown way | Space: object requires documentation | |
| 247 | 440 |
InfoObject &1 references basic InfoObject &2 | Space: object requires documentation | |
| 248 | 441 |
Characteristic value with SID &1 of InfoObject &2 not being used | Space: object requires documentation | |
| 249 | 442 |
InfoObject &1 is a navigation attribute | Space: object requires documentation | |
| 250 | 500 |
Table &1 is analyzed | Space: object requires documentation | |
| 251 | 501 |
Table &1 can be ignored | Space: object requires documentation | |
| 252 | 502 |
The number of secondary indexes for InfoCube &1 is correct | Space: object requires documentation | |
| 253 | 503 |
The fact table of InfoCube &1 is missing &2 secondary indexes | Space: object requires documentation | |
| 254 | 504 |
Index &1 type is OK (type &2) | Space: object requires documentation | |
| 255 | 505 |
Index &1 type is &2. Type &3 was expected | Space: object requires documentation | |
| 256 | 506 |
Index &1 is &2 | Space: object requires documentation | |
| 257 | 507 |
Index &1 is &2. &3 was expected | Space: object requires documentation | |
| 258 | 508 |
Read Note 401242 when analyzing index problems | Space: object requires documentation | |
| 259 | 509 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 260 | 510 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 261 | 511 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 262 | 512 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 263 | 513 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 264 | 514 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 265 | 515 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 266 | 516 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 267 | 517 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 268 | 518 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 269 | 519 |
--- reserved for DB-independent messages | Space: object requires documentation | |
| 270 | 520 |
ORACLE: Table &1 has not yet been analyzed | Space: object requires documentation | |
| 271 | 521 |
ORACLE: Statistics information for table &1 may be obsolete | Space: object requires documentation | |
| 272 | 522 |
ORACLE: Check in progress; statistics in table &1 are current | Space: object requires documentation | |
| 273 | 523 |
ORACLE: The status of index &1 is OK | Space: object requires documentation | |
| 274 | 524 |
ORACLE: The status of index &1 is &2 | Space: object requires documentation | |
| 275 | 525 |
ORACLE: Index &1 has possibly degenerated | Space: object requires documentation | |
| 276 | 526 |
ORACLE: No degenerated indexes were found for InfoCube &1. | Space: object requires documentation | |
| 277 | 527 |
ORACLE: Parameter &1 is set to value &2 (recommended value is &3) | Space: object requires documentation | |
| 278 | 528 |
Current recommendations for Oracle parameters are in SAP Note 830576 | Space: object requires documentation | |
| 279 | 529 |
Existence of catalog synonyms (SAP Notes 519448, 565416) is checked | Space: object requires documentation | |
| 280 | 530 |
ORACLE: Synonym &1 exists | Space: object requires documentation | |
| 281 | 531 |
ORACLE: Synonym &1 does not exist. See SAP Notes 519448, 565416 | Space: object requires documentation | |
| 282 | 532 |
Existence of catalog indexes (SAP Note 519407) is checked | Space: object requires documentation | |
| 283 | 533 |
ORACLE: Catalog index &1 exists | Space: object requires documentation | |
| 284 | 534 |
ORACLE: Catalog index &1 does not exist. See SAP Note 519407 | Space: object requires documentation | |
| 285 | 535 |
Existence of catalog statistics (SAP Note 558746) is checked | Space: object requires documentation | |
| 286 | 536 |
ORACLE: Catalog statistics are missing. Refer to SAP Note 558746 | Space: object requires documentation | |
| 287 | 537 |
ORACLE: Obsolete database version: &1 | Space: object requires documentation | |
| 288 | 538 |
ORACLE: | Space: object requires documentation | |
| 289 | 539 |
ORACLE: | Space: object requires documentation | |
| 290 | 540 |
INFORMIX: No 'Update statistics' has been carried out yet for table & | Space: object requires documentation | |
| 291 | 541 |
INFORMIX: Database statistics for table &1 are current (Threshold: &2 %) | Space: object requires documentation | |
| 292 | 542 |
INFORMIX: Database statistics for table &1 are obsolete (Threshold: &2 %) | Space: object requires documentation | |
| 293 | 543 |
INFORMIX: The status of index &1 is OK | Space: object requires documentation | |
| 294 | 544 |
INFORMIX: The status of index &1 is 'not active' (disabled) | Space: object requires documentation | |
| 295 | 545 |
INFORMIX: The type for index &1 is OK: Detached from the Basis table | Space: object requires documentation | |
| 296 | 546 |
INFORMIX: The type for index &1 is OK: Fragmented acc. to Basis table | Space: object requires documentation | |
| 297 | 547 |
INFORMIX: Index &1 does not have the expected type: 'Detached Index' | Space: object requires documentation | |
| 298 | 548 |
INFORMIX: Index &1 does not have the expected type: (Fragmented Strategy) | Space: object requires documentation | |
| 299 | 549 |
INFORMIX: The type for index &1 is not known | Space: object requires documentation | |
| 300 | 550 |
INFORMIX: ONCONFIG Parameter &1 equals &2 (recommended value is &3) | Space: object requires documentation | |
| 301 | 551 |
INFORMIX: Environment variable &1 equals &2 (recommended value is &3) | Space: object requires documentation | |
| 302 | 554 |
INFORMIX: Database Statistics for Table and Not Current (Indices) | Space: object requires documentation | |
| 303 | 555 |
INFORMIX: | Space: object requires documentation | |
| 304 | 556 |
INFORMIX: | Space: object requires documentation | |
| 305 | 557 |
INFORMIX: | Space: object requires documentation | |
| 306 | 558 |
INFORMIX: | Space: object requires documentation | |
| 307 | 559 |
INFORMIX: | Space: object requires documentation | |
| 308 | 560 |
SQL SERVER: Empty | Space: object requires documentation | |
| 309 | 561 |
SQL SERVER: Status OK | Space: object requires documentation | |
| 310 | 562 |
SQL SERVER: Index status OK | Space: object requires documentation | |
| 311 | 563 |
SQL SERVER: Status Wrong | Space: object requires documentation | |
| 312 | 564 |
SQL SERVER: The status of index &1 is OK | Space: object requires documentation | |
| 313 | 565 |
SQL SERVER: The status of the index &1 is &2 | Space: object requires documentation | |
| 314 | 566 |
SQL SERVER: Not used | Space: object requires documentation | |
| 315 | 567 |
SQL SERVER: Not used | Space: object requires documentation | |
| 316 | 568 |
SQL SERVER: Not used | Space: object requires documentation | |
| 317 | 569 |
SQL SERVER: Not used | Space: object requires documentation | |
| 318 | 570 |
SQL SERVER: Not used | Space: object requires documentation | |
| 319 | 571 |
SQL SERVER: Not used | Space: object requires documentation | |
| 320 | 572 |
SQL SERVER: Not used | Space: object requires documentation | |
| 321 | 573 |
SQL SERVER: Not used | Space: object requires documentation | |
| 322 | 574 |
SQL SERVER: Not used | Space: object requires documentation | |
| 323 | 575 |
SQL SERVER: Not used | Space: object requires documentation | |
| 324 | 576 |
SQL SERVER: Not used | Space: object requires documentation | |
| 325 | 577 |
SQL SERVER: Not used | Space: object requires documentation | |
| 326 | 578 |
SQL SERVER: Not used | Space: object requires documentation | |
| 327 | 579 |
SQL SERVER: Not used | Space: object requires documentation | |
| 328 | 580 |
DB2/UDB: Table &1 has not yet been analyzed | Space: object requires documentation | |
| 329 | 581 |
DB2/UDB: Statistics for table &1 were generated &2 days ago, max. &3 OK | Space: object requires documentation | |
| 330 | 582 |
DB2/UDB: Statistics for table &1 were generated &2 days ago | Space: object requires documentation | |
| 331 | 583 |
DB2/UDB: Index &1 created correctly | Space: object requires documentation | |
| 332 | 584 |
DB2/UDB: Index &1 is missing or is not correct in the ABAP dictionary | Space: object requires documentation | |
| 333 | 585 |
DB2/UDB: Stored procedures are not currently supported | Space: object requires documentation | |
| 334 | 586 |
DB2/UDB: The representative primary index&1 is OK | Space: object requires documentation | |
| 335 | 587 |
DB2/UDB: The representative primary index &1 is missing or is not correct | Space: object requires documentation | |
| 336 | 588 |
DB2/UDB: The representative primary index &1 is not unique. | Space: object requires documentation | |
| 337 | 589 |
DB2/UDB: Index &1 is not a clustering index | Space: object requires documentation | |
| 338 | 590 |
DB2/UDB: Partitioning key for table &1 is missing or incorrect. | Space: object requires documentation | |
| 339 | 591 |
DB2/UDB: Partitioning key for table &1 is correct. | Space: object requires documentation | |
| 340 | 592 |
DB2/UDB: Clustering of table &1 is not correct | Space: object requires documentation | |
| 341 | 593 |
DB2/UDB: Clustering of table &1 is not correct | Space: object requires documentation | |
| 342 | 594 |
DB2/UDB: The MDC columns of table &1 are not correct | Space: object requires documentation | |
| 343 | 595 |
DB2/UDB: The index &1 is missing from the database | Space: object requires documentation | |
| 344 | 596 |
DB2/UDB: | Space: object requires documentation | |
| 345 | 597 |
DB2/UDB: | Space: object requires documentation | |
| 346 | 598 |
DB2/UDB: | Space: object requires documentation | |
| 347 | 599 |
DB2/UDB: | Space: object requires documentation | |
| 348 | 600 |
DB2-z/OS: Table &1 has not yet been analyzed | Space: object requires documentation | |
| 349 | 601 |
DB2-z/OS: Statistics for table &1 were generated &2 days ago, max. &3 OK | Space: object requires documentation | |
| 350 | 602 |
DB2-z/OS: Statistics for table &1 were generated &2 days ago | Space: object requires documentation | |
| 351 | 603 |
DB2-z/OS: Index &1 is OK | Space: object requires documentation | |
| 352 | 604 |
DB2-z/OS: Index &1 is &2 | Space: object requires documentation | |
| 353 | 605 |
DB2-z/OS: Stored procedures are not currently supported | Space: object requires documentation | |
| 354 | 606 |
DB2-z/OS: Triggers are not currently supported | Space: object requires documentation | |
| 355 | 607 |
DB2-z/OS: Index &1 is in REBUILD PENDING mode | Space: object requires documentation | |
| 356 | 608 |
DB2-z/OS: Status of index &1 cannot be determined (rfcoscol?) | Space: object requires documentation | |
| 357 | 609 |
DB2/390: | Space: object requires documentation | |
| 358 | 610 |
DB2/390: | Space: object requires documentation | |
| 359 | 611 |
DB2-z/OS: No entry in RTS table for table &1 | Space: object requires documentation | |
| 360 | 612 |
DB2-z/OS: &2 % of data changed in table &1 | Space: object requires documentation | |
| 361 | 613 |
DB2-z/OS: Statistics from &1 are no longer up-to-date (&2) | Space: object requires documentation | |
| 362 | 614 |
DB2-z/OS: No entry in TABLESPACESTATS for table &1 partition &2 | Space: object requires documentation | |
| 363 | 615 |
DB2-z/OS: &3 % of data has changed in partition &2 from &1 | Space: object requires documentation | |
| 364 | 616 |
DB2-z/OS: Statistics from partition &2 from &1 are not up-to-date (&3) | Space: object requires documentation | |
| 365 | 617 |
DB2/390: | Space: object requires documentation | |
| 366 | 618 |
DB2/390: | Space: object requires documentation | |
| 367 | 619 |
DB2/390: | Space: object requires documentation | |
| 368 | 620 |
--- Beginning DB2/400 Messages --- | Space: object requires documentation | |
| 369 | 621 |
Index &1 exists, but index &2 was expected | Space: object requires documentation | |
| 370 | 622 |
DB2/400: | Space: object requires documentation | |
| 371 | 623 |
The status of index &1 is ok | Space: object requires documentation | |
| 372 | 624 |
DB2/400: The status of index &1 is &2 | Space: object requires documentation | |
| 373 | 625 |
DB2/400: The type of index &1 is okay (type &2). | Space: object requires documentation | |
| 374 | 626 |
DB2/400: The type of index &1 is &2. Type &3 was however expected | Space: object requires documentation | |
| 375 | 627 |
DB2/400: Parameter &1 is set to value &2 (recommended value is &3) | Space: object requires documentation | |
| 376 | 628 |
DB2/400: The index &1 is &2 | Space: object requires documentation | |
| 377 | 629 |
DB2/400: The index &1 is &2, but &3 was expected | Space: object requires documentation | |
| 378 | 630 |
Fact table for InfoCube &1 contains additional indexes | Space: object requires documentation | |
| 379 | 631 |
Index &1 does not belong to the standard indexes | Space: object requires documentation | |
| 380 | 632 |
Index &1 does not exist in the data dictionary | Space: object requires documentation | |
| 381 | 633 |
Index &1 does not exist in the database | Space: object requires documentation | |
| 382 | 634 |
The number of secondary indexes for InfoCube &1 is incorrect | Space: object requires documentation | |
| 383 | 635 |
&2 indexes are missing in the DDIC from the fact table of InfoCube &1 | Space: object requires documentation | |
| 384 | 636 |
&2 indexes are missing in the database from the fact table of InfoCube &1 | Space: object requires documentation | |
| 385 | 637 |
DB2/400: The indexes were successfully converted | Space: object requires documentation | |
| 386 | 638 |
DB2/400: Indexes from fact tables are missing | Space: object requires documentation | |
| 387 | 639 |
DB2/400: | Space: object requires documentation | |
| 388 | 640 |
SAP DB: Table &1 has not yet been analyzed | Space: object requires documentation | |
| 389 | 641 |
SAP DB: Statistics information on table &1 is possibly obsolete | Space: object requires documentation | |
| 390 | 642 |
SAP DB: Table &1 was analyzed on &2 (sample &3 %) | Space: object requires documentation | |
| 391 | 643 |
SAP DB: Status of index &1 is OK | Space: object requires documentation | |
| 392 | 644 |
SAP DB: Status of index &1 is &2 | Space: object requires documentation | |
| 393 | 645 |
SAP DB: Type of index &1 is OK (type &2) | Space: object requires documentation | |
| 394 | 646 |
SAP DB: | Space: object requires documentation | |
| 395 | 647 |
SAP DB: | Space: object requires documentation | |
| 396 | 648 |
SAP DB: | Space: object requires documentation | |
| 397 | 649 |
SAP DB: | Space: object requires documentation | |
| 398 | 650 |
SAP DB: | Space: object requires documentation | |
| 399 | 651 |
SAP DB: | Space: object requires documentation | |
| 400 | 652 |
SAP DB: | Space: object requires documentation | |
| 401 | 653 |
SAP DB: | Space: object requires documentation | |
| 402 | 654 |
SAP DB: | Space: object requires documentation | |
| 403 | 655 |
SAP DB: | Space: object requires documentation | |
| 404 | 656 |
SAP DB: | Space: object requires documentation | |
| 405 | 657 |
SAP DB: | Space: object requires documentation | |
| 406 | 658 |
SAP DB: | Space: object requires documentation | |
| 407 | 659 |
SAP DB: | Space: object requires documentation | |
| 408 | 660 |
Sybase ASE: &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 409 | 661 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 410 | 662 |
Sybase ASE: | The short text describes the object sufficiently | |
| 411 | 663 |
Sybase ASE: The status of index &1 is OK | The short text describes the object sufficiently | |
| 412 | 664 |
Sybase ASE: Status of index &1 is &2 | Space: object requires documentation | |
| 413 | 665 |
SYB: Statistics for table &1 are up to date | The short text describes the object sufficiently | |
| 414 | 666 |
SYB: Statistics for table &1 are obsolete | The short text describes the object sufficiently | |
| 415 | 667 |
SYB: Statistics for partion &1 of table &2 are obsolete | The short text describes the object sufficiently | |
| 416 | 668 |
Sybase ASE: | The short text describes the object sufficiently | |
| 417 | 669 |
Sybase ASE: | The short text describes the object sufficiently | |
| 418 | 670 |
Sybase ASE: | The short text describes the object sufficiently | |
| 419 | 671 |
Sybase ASE: | The short text describes the object sufficiently | |
| 420 | 672 |
Sybase ASE: | The short text describes the object sufficiently | |
| 421 | 673 |
Sybase ASE: | The short text describes the object sufficiently | |
| 422 | 674 |
Sybase ASE: | The short text describes the object sufficiently | |
| 423 | 675 |
Sybase ASE: | The short text describes the object sufficiently | |
| 424 | 676 |
Sybase ASE: | The short text describes the object sufficiently | |
| 425 | 677 |
Sybase ASE: | The short text describes the object sufficiently | |
| 426 | 678 |
Sybase ASE: | The short text describes the object sufficiently | |
| 427 | 679 |
Sybase ASE: | The short text describes the object sufficiently | |
| 428 | 700 |
Dimensions for InfoCube &1 contain unused entries | Space: object requires documentation | |
| 429 | 701 |
Dimensions for InfoCube &1 contain non-multiple entries | Space: object requires documentation | |
| 430 | 800 |
*********** Partitioning *************** | The short text describes the object sufficiently | |
| 431 | 801 |
InfoCube & Is Not Partitioned | The short text describes the object sufficiently | |
| 432 | 802 |
InfoCube & is correctly partitioned | The short text describes the object sufficiently | |
| 433 | 803 |
The partitioning settings for InfoCube & are not correct | The short text describes the object sufficiently | |
| 434 | 804 |
Aggregate & is not partitioned | The short text describes the object sufficiently | |
| 435 | 805 |
Aggregate & is correctly partitioned | The short text describes the object sufficiently | |
| 436 | 806 |
The partitioning settings for aggregate & are not correct | The short text describes the object sufficiently | |
| 437 | 807 |
Table & is correctly partitioned | The short text describes the object sufficiently | |
| 438 | 808 |
Table & is not correctly partitioned | The short text describes the object sufficiently | |
| 439 | 809 |
Table & is partitioned, although it should not be | The short text describes the object sufficiently | |
| 440 | 810 |
Table & could not be found in the database | The short text describes the object sufficiently | |
| 441 | 811 |
Table & is not partitioned in the database | The short text describes the object sufficiently | |
| 442 | 812 |
Table & is partitioned in the DB although it is not in the InfoCube | The short text describes the object sufficiently | |
| 443 | 813 |
Partitioning details for table & could not be read | The short text describes the object sufficiently | |
| 444 | 814 |
Table & does not have a partitioning column | The short text describes the object sufficiently | |
| 445 | 815 |
Table & has partitioning column & | The short text describes the object sufficiently | |
| 446 | 816 |
In table &, the partitioning column is missing | The short text describes the object sufficiently | |
| 447 | 817 |
Table & has the partitioning column &, although it should be & | The short text describes the object sufficiently | |
| 448 | 818 |
Table & has the partitioning column &, although there should not be one | The short text describes the object sufficiently | |
| 449 | 819 |
Partition & from & to & is unnecessary | The short text describes the object sufficiently | |
| 450 | 820 |
The partition from & to & is missing | The short text describes the object sufficiently | |
| 451 | 821 |
The number of partitions in table & is correct | The short text describes the object sufficiently | |
| 452 | 822 |
The partitioning type is & | The short text describes the object sufficiently | |
| 453 | 823 |
The partitioning type is &. However, & was expected | The short text describes the object sufficiently | |
| 454 | 824 |
The partitioning type is &, although it should not be partitioned | The short text describes the object sufficiently | |
| 455 | 825 |
Unknown partitioning type. However, & was expected | The short text describes the object sufficiently | |
| 456 | 826 |
Unknown partitioning type, although it should not be partitioned | The short text describes the object sufficiently | |
| 457 | 827 |
The partitioning key is & | The short text describes the object sufficiently | |
| 458 | 828 |
The partitioning key is &. However, & was expected | The short text describes the object sufficiently | |
| 459 | 829 |
Table & has too many partitioning keys | The short text describes the object sufficiently | |
| 460 | 830 |
Partition & starts at & | The short text describes the object sufficiently | |
| 461 | 831 |
Partition & starts at &. However, & was expected | The short text describes the object sufficiently | |
| 462 | 832 |
Partition & goes to & | The short text describes the object sufficiently | |
| 463 | 833 |
Partition & extends to &. However, & was expected | The short text describes the object sufficiently | |
| 464 | 834 |
The partition limit & is inclusive | The short text describes the object sufficiently | |
| 465 | 835 |
The partition limit & is inclusive. It was expected to be exclusive | The short text describes the object sufficiently | |
| 466 | 836 |
The partition limit & is exclusive | The short text describes the object sufficiently | |
| 467 | 837 |
The parition limit & is exclusive. Inclusive was expected | The short text describes the object sufficiently | |
| 468 | 838 |
Partition & is correct | The short text describes the object sufficiently | |
| 469 | 839 |
Partition & is not correct | The short text describes the object sufficiently | |
| 470 | 845 |
F table of aggregate &1 is empty | The short text describes the object sufficiently | |
| 471 | 846 |
F table of aggregate &1 has over 30 partitions | The short text describes the object sufficiently | |
| 472 | 847 |
F table of aggregate &1 has over 50 partitions | The short text describes the object sufficiently | |
| 473 | 848 |
E table of aggregate &1 is well partitioned | The short text describes the object sufficiently | |
| 474 | 849 |
E table of aggregate &1 has too many partitions | The short text describes the object sufficiently | |
| 475 | 850 |
E table of aggregate &1 should be partitioned | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
