RSLPO_CHECK - Logical Partitioning: Consistency Checks
 The following messages are stored in message class RSLPO_CHECK: Logical Partitioning: Consistency Checks.
It is part of development package RSLPO_CHECK in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "Logical Partitioning: Consistency Checks".
 It is part of development package RSLPO_CHECK in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "Logical Partitioning: Consistency Checks".
| Message Nr ▲ | Message Text | 
|---|---|
| 010 | Check successful | 
| 090 | SPOs cannot be created as Business Content | 
| 099 | Internal error: &1 &2 &3 &4 | 
| 100 | Semantically partitioned object (version): &1 | 
| 101 | Partitioning Criteria | 
| 102 | Components | 
| 103 | Semantically partitioned object &1 | 
| 104 | General Properties | 
| 105 | Partitions | 
| 110 | Criteria overlap with criteria of partition &1 | 
| 200 | Partition &1 | 
| 201 | Basis Components | 
| 211 | Component &1: ID of component is not same as target value &2 | 
| 212 | Component &1: Partition IDPART = &2 is not same as target value &2 | 
| 213 | Component &1: TLOGO type &2 not permitted for InfoProvider | 
| 214 | Component &1: TLOGO type &2 not permitted for transformations | 
| 215 | Component &1: Role ROLE = &2 is not the same as target value &3 | 
| 216 | Characteristic &1: Characteristic is not part of the object key | 
| 217 | Database partitioning cannot be combined with semantic criteria | 
| 250 | Partition contents data | 
| 251 | Partitioning criteria changed | 
| 252 | Partition deleted | 
| 253 | Transfer of data to partition &1 required | 
| 254 | Partial deletion of partition data required | 
| 255 | WARNING: This deletes all the data from the partition | 
| 256 | Database partitioning activated or deactivated | 
| 257 | Criteria for database partitioning changed | 
| 259 | Partition deleted | 
| 300 | Dimension &1 | 
| 301 | Criterion &1: SIGN = &2 not permitted | 
| 302 | Criterion &1: OPT = &2 not permitted | 
| 303 | Only one interval or several single values permitted for each dimension | 
| 310 | Only one interval or several single values permitted for each dimension | 
| 400 | Checking component &1: | 
| 410 | Criterion &1: SIGN = &2 not permitted | 
| 411 | Criterion &1: OPT = &2 not permitted | 
| 412 | Characteristic &1: Interval [&2, &3]: From value larger than To value | 
| 500 | Component &1 | 
| 511 | Reference structure &1 | 
| 521 | Component &1 &2: Property &3 is not supported | 
| 522 | Component &1 &2: Property &3: Value &4 is not permitted | 
| 600 | *** 600 - 699: Reserved for Class CL_RSLPO_TEST_METADATA *** | 
| 601 | Components cannot be assigned to an SPO | 
| 602 | Component &1 &2: Ambiguous assignment (for example to SPO &3) found | 
| 603 | Component &1 &2: Master Provider &3 &4 not found | 
| 610 | SPO &1 | 
| 611 | Table &1: Component &2 &3 (&4) refers to SPO that is already deleted | 
| 612 | Table &1: Not supported D version found | 
| 620 | Table RSLPO: Missing data record for M version | 
| 621 | Table RSLPO: Missing data record for A version | 
| 622 | Table RSLPO: Values '&1' and '&2' for field &3 not unique | 
| 623 | Table RSLPO: A version has unreliable values | 
| 630 | Table RSLPOCOMP: Referenced partition &1 (&2) does not exist | 
| 631 | Table RSLPOCOMP: Missing data record for component &1 (&2) | 
| 632 | Table RSLPOCOMP: Comparison of component &1 (&2 &3): Record to delete | 
| 633 | Table RSLPOCOMP: Comparison of component &1 (&2 &3): Missing data record | 
| 640 | Table &1: Cannot determine TLOGO type and name of master provider | 
| 641 | Table &1: Component &2 &3 (&4) does not refer to SPO | 
| 642 | Table &1: Component &2 &3 (&4) does not refer to master provider | 
| 650 | Table RSLPOPARTRANGE: Referenced partition &1 (&2) does not exist | 
| 651 | Table RSLPOCOMPTEXT: Referenced component &1 (&2) does not exist | 
| 652 | Table RSLPOCOMPPROP: Referenced component &1 (&2) does not exist | 
| 690 | Table &1: Value '&2' for field &3 is incorrect | 
| 699 | Inconsistency '&1' found (&2, &3, &4) |