SAP ABAP Message Class FMHIE (Budget Hierarchies)
Basic Data
Hierarchy
☛
EA-PS (Software Component) SAP Enterprise Extension Public Services
⤷ PSM-FM-BCS-BU (Application Component) Budgeting
⤷ FMBMA_E (Package) Budgeting Rules, BCS
⤷ PSM-FM-BCS-BU (Application Component) Budgeting
⤷ FMBMA_E (Package) Budgeting Rules, BCS
Attributes
Message class | FMHIE | |
Short Description | Budget Hierarchies | |
Changed On | 20050409 | |
Last Changed At | 150916 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Hierarchy node &1 (ID &2) does not exist | The short text describes the object sufficiently | |
2 | 002 | Inconsistent hierarchy role of account assignment element &1 | The short text describes the object sufficiently | |
3 | 003 | Header entry (constant part for hierarchy nodes) &1 does not exist | The short text describes the object sufficiently | |
4 | 004 | Budget structure &1 is not hierarchical for FM area &2 | The short text describes the object sufficiently | |
5 | 005 | No header entries exist for the hierarchy ID &1 | The short text describes the object sufficiently | |
6 | 006 | Deletion not allowed | Space: object requires documentation | |
7 | 007 | Hierarchy ID &1 does not exist | The short text describes the object sufficiently | |
8 | 008 | Funds center is not hierarchical | The short text describes the object sufficiently | |
9 | 009 | Commitment item is not hierarchical | The short text describes the object sufficiently | |
10 | 010 | Fund is not hierarchical | The short text describes the object sufficiently | |
11 | 011 | Functional area is not hierarchical | The short text describes the object sufficiently | |
12 | 012 | Funded program is not hierarchical | The short text describes the object sufficiently | |
13 | 013 | No hierarchy ID selected | The short text describes the object sufficiently | |
14 | 014 | Sequence is not consistent | The short text describes the object sufficiently | |
15 | 015 | Enter a valid value for the hierarchy ID | The short text describes the object sufficiently | |
16 | 016 | Hierarchy ID &1 already exists | The short text describes the object sufficiently | |
17 | 017 | Hierarchy ID was deleted | The short text describes the object sufficiently | |
18 | 018 | Hierarchy ID was not changed | The short text describes the object sufficiently | |
19 | 019 | Function not allowed - errors found | The short text describes the object sufficiently | |
20 | 020 | Hierarchy ID has been saved | The short text describes the object sufficiently | |
21 | 021 | Address already assigned to the hierarchy ID | The short text describes the object sufficiently | |
22 | 022 | Address &1 already assigned to a different hierarchy ID | The short text describes the object sufficiently | |
23 | 023 | No hierarchy ID can be maintained for FM area &1 and structure &2 | Space: object requires documentation | |
24 | 024 | No budget structure selected | The short text describes the object sufficiently | |
25 | 025 | Overlapping with existing nodes of the hierarchy &1 | The short text describes the object sufficiently | |
26 | 026 | No node selected | The short text describes the object sufficiently | |
27 | 027 | No fund selected | The short text describes the object sufficiently | |
28 | 028 | No funds center selected | The short text describes the object sufficiently | |
29 | 029 | No commitment item selected | The short text describes the object sufficiently | |
30 | 030 | No functional area selected | The short text describes the object sufficiently | |
31 | 031 | No funded program selected | The short text describes the object sufficiently | |
32 | 032 | Node not found | The short text describes the object sufficiently | |
33 | 033 | No hierarchy variant for funds center selected | The short text describes the object sufficiently | |
34 | 034 | No hierarchy variant for commitment item selected | The short text describes the object sufficiently | |
35 | 035 | Hierarchy variant &1 does not exist | The short text describes the object sufficiently | |
36 | 036 | Selected hierarchy is empty, change your entries on the restriction! | The short text describes the object sufficiently | |
37 | 037 | You cannot delete hierarchy ID &1 because it is not empty | The short text describes the object sufficiently | |
38 | 100 | FMAA element &1 has not hierarchy role "constant" and cannot be used | The short text describes the object sufficiently | |
39 | 101 | FMAA element &1 has not hierarchy role "hierarchical" and cannot be used | The short text describes the object sufficiently | |
40 | 102 | FMAA element &2 has not hierarchy role "not relevant" and cannot be used | The short text describes the object sufficiently | |
41 | 103 | The superior hierarchy node has a different commitment item category | Space: object requires documentation | |
42 | 104 | The superior hierarchy node is postable | Space: object requires documentation | |
43 | 105 | The whole hierarchy ID &1 will be locked | Space: object requires documentation | |
44 | 106 | The FMAA &1&2 already exists in the hierarchy | The short text describes the object sufficiently | |
45 | 107 | The FMAA &1&2 does not exist in the hierarchy | The short text describes the object sufficiently | |
46 | 108 | The FMAA &1&2 already exists in the database for the hierarchy ID &3 | The short text describes the object sufficiently | |
47 | 109 | Subordinate data of the node &1&2 has to be read from database | Space: object requires documentation | |
48 | 110 | Superior data of the node &1&2 has to be read from database | Space: object requires documentation | |
49 | 111 | Only an end node can be deleted | The short text describes the object sufficiently | |
50 | 112 | FM account assignment &1&2 cannot be budgeted in budget category &3 | Space: object requires documentation | |
51 | 113 | Missing hierarchy role definition for budget structure &1 | Space: object requires documentation | |
52 | 200 | Only one sender line can be used for distribution process | The short text describes the object sufficiently | |
53 | 201 | You are only allowed to distribute to the next hierarchy level | The short text describes the object sufficiently | |
54 | 202 | Transfer allowed only if the addresses have a common parent | The short text describes the object sufficiently | |
55 | 203 | Only transfer in between top nodes is allowed | The short text describes the object sufficiently | |
56 | 204 | A direct entry is only allowed for a top node | The short text describes the object sufficiently | |
57 | 205 | Distribution lines cannot be created as distribution is not active | The short text describes the object sufficiently | |
58 | 206 | Transfer not allowed only distribution process may be used | The short text describes the object sufficiently | |
59 | 207 | Only one fiscal year can be used for distribution process | The short text describes the object sufficiently | |
60 | 208 | Only one year of cash effectivity can be used for distribution process | The short text describes the object sufficiently | |
61 | 209 | Only one budget category can be used for distribution process | The short text describes the object sufficiently | |
62 | 210 | In distribution sender should be superior to receiver in the hierarchy | The short text describes the object sufficiently | |
63 | 800 | Hierarchy inconsistence: Class &1, Method &2 | Space: object requires documentation | |
64 | 801 | Error calling method &2 of class &1 | The short text describes the object sufficiently | |
65 | 802 | Inconsistent hierarchy of FMAA element &1 | Space: object requires documentation | |
66 | 803 | The short text describes the object sufficiently |
History
Last changed on/by | 20050409 | SAP | |
SAP Release Created in | 600 |