Message Number list used by SAP ABAP Class CL_RSD_KYF (Key Figure (of a Version))
SAP ABAP Class
CL_RSD_KYF (Key Figure (of a Version)) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | BRAIN - 060 | Value '&1' (hex. '&3') of characteristic &2 contains invalid characters | ||
| 2 | R7 - 058 | Invalid entry &1 &2 &3 &4 | ||
| 3 | R7 - 618 | Fixed currency &1 does not exist in the system | ||
| 4 | R7 - 617 | Fixed unit &1 does not exist in the system | ||
| 5 | R7 - 595 | Key figure &1 must not be connected to itself | ||
| 6 | R7 - 594 | Key figure &1 is a non-cum. value: Fixed key figure is not allowed | ||
| 7 | R7 - 593 | Key figure &1: Fixed key figure &2 cannot be used | ||
| 8 | R7 - 592 | Key figure &1: Fixed key figure &2 does not (actively) exist | ||
| 9 | R7 - 580 | Key figure &1: Aggr. ref. char. changed --> Please adjust aggregates | ||
| 10 | R7 - 571 | Key figure &1: Unit &2 is exclusively an attribute | ||
| 11 | R7 - 564 | Non-cumulative value &1: &2 &3 already used in non-cumulative value &4 | ||
| 12 | R7 - 548 | Key figure &1 is used in non-cum value &2, type cannot be changed | ||
| 13 | R7 - 542 | Error while writing to database table &1 | ||
| 14 | R7 - 536 | Non-cumulative value &1: &2 &3 must be a cumulative value | ||
| 15 | R7 - 535 | Non-cumulative value &1 and NC value change &2 are inconsistent | ||
| 16 | R7 - 534 | Non-cumulative value &1: Outflow and inflow must differ | ||
| 17 | R7 - 532 | Non-cumulative value &1: Inflow &2 and outflow &3 are inconsistent | ||
| 18 | R7 - 186 | Enter either unit InfoObject or fixed currency/unit | ||
| 19 | R7 - 201 | InfoObject &1: Unit InfoOject &2 is not (actively) available | ||
| 20 | R7 - 206 | Unit InfoObject &1 has incorrect type &2 | ||
| 21 | R7 - 218 | InfoObject &1 is of incorrect system type &2 | ||
| 22 | R7 - 218 | InfoObject &1 is of incorrect system type &2 | ||
| 23 | R7 - 404 | Key figure &1: Aggregation reference char.&1 is not (actively) available | ||
| 24 | R7 - 423 | Key figure &1 is of invalid type &2 | ||
| 25 | R7 - 528 | InfoObject &1: &2 was changed from &3 to &4 | ||
| 26 | R7 - 528 | InfoObject &1: &2 was changed from &3 to &4 | ||
| 27 | R7 - 528 | InfoObject &1: &2 was changed from &3 to &4 | ||
| 28 | R7 - 529 | Non-cumulative value &1: &2 &3 is not (actively) available | ||
| 29 | R7 - 530 | Key figure &1: Rows were deleted from compounding (type &2) | ||
| 30 | R7 - 533 | Non-cumulative value &1: Aggregation of &2 &3 must sum | ||
| 31 | R7 - 482 | InfoObject &1 deactivated (status set to 'inactive') | ||
| 32 | R7B - 207 | Characteristic &2 is an attribute and not allowed in elimination | ||
| 33 | R7B - 658 | Indicator for high precision has been reset | ||
| 34 | R7B - 634 | Key figure &1: (Exception) aggreg. 'Total' not allowed for data type &2 | ||
| 35 | R7B - 631 | Key figure &1: Aggregation 'Total' selected | ||
| 36 | R7B - 630 | Key figure &1: Exception aggregation 'Sum' selected | ||
| 37 | R7B - 245 | Communication structure &1 is inconsistent and has to be reactivated | ||
| 38 | R7B - 244 | Key figure &1 is an attribute of characteristic &2, but unit &3 is not | ||
| 39 | R7B - 209 | Characteristic &2 is used twice in row &3 of the elimination | ||
| 40 | R7B - 208 | InfoObject &2 cannot be used in elimination | ||
| 41 | R7B - 206 | Characteristic &1 and &2 from elimination must have the same reference | ||
| 42 | R7B - 205 | Key figure &1: Char. &2 from elimination is not actively available | ||
| 43 | R7B - 204 | Key figure &1: Elimination is incomplete (row &2) | ||
| 44 | R7I - 018 | InfoProvider &1 is set to "inactive" upon activation |