FMHIE - Budget Hierarchies
The following messages are stored in message class FMHIE: Budget Hierarchies.
It is part of development package FMBMA_E in software component PSM-FM-BCS-BU. This development package consists of objects that can be grouped under "Budgeting Rules, BCS".
It is part of development package FMBMA_E in software component PSM-FM-BCS-BU. This development package consists of objects that can be grouped under "Budgeting Rules, BCS".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Hierarchy node &1 (ID &2) does not exist |
| 002 | Inconsistent customizing for account assignment element &1 |
| 003 | Constant element &1 is not assigned to any hierarchy |
| 004 | Budget structure &1 is not multi-level for FM area &2 |
| 005 | No header entries exist for hierarchy ID &1 |
| 006 | Deletion of read-only entries is not allowed |
| 007 | Hierarchy ID &1 does not exist |
| 008 | Funds center is not multi-level |
| 009 | Commitment item is not multi-level |
| 010 | Fund is not multi-level |
| 011 | Functional area is not multi-level |
| 012 | Funded program is not multi-level |
| 013 | No hierarchy ID selected |
| 014 | Sequence is not consistent |
| 015 | Enter a valid value for the hierarchy ID |
| 016 | Hierarchy ID &1 already exists |
| 017 | Hierarchy ID was deleted |
| 018 | Hierarchy ID was not changed |
| 019 | Function not allowed - errors found |
| 020 | Hierarchy ID has been saved |
| 021 | Address already assigned to the hierarchy ID |
| 022 | Constant element &1&2 already assigned to a different hierarchy ID &3 |
| 023 | No hierarchy ID can be maintained for FM area &1 and structure &2 |
| 024 | No budget structure selected |
| 025 | Overlapping with existing nodes of the hierarchy &1 |
| 026 | No node selected |
| 027 | No fund selected |
| 028 | No funds center selected |
| 029 | No commitment item selected |
| 030 | No functional area selected |
| 031 | No funded program selected |
| 032 | Node not found |
| 033 | No hierarchy variant for funds center selected |
| 034 | No hierarchy variant for commitment item selected |
| 035 | There is no &1 maintained in the hierarchy variant &2 |
| 036 | Selected hierarchy is empty, change your entries for restriction |
| 037 | You cannot delete hierarchy ID &1 because it is not empty |
| 038 | Operation cancelled |
| 039 | Enter a hierarchy ID |
| 040 | Target hierarchy is not empty, change your entries for target |
| 041 | No group for &1 selected |
| 042 | No source budget structure selected |
| 043 | More than one source address is reassigned to target address &1&2 |
| 044 | Source year is later than target year |
| 045 | This transaction does not support multi-level BS &1 in FM area &2 |
| 046 | Combination of FM area &1 and fiscal year &2 not allowed |
| 047 | Enter a source hierarchy ID |
| 048 | Enter a target hierarchy ID |
| 049 | The superior hierarchy node is statistical |
| 050 | &1 is not multi-level in budget structure &2 within FM area &3 |
| 051 | Error in sequence of account assignment elements |
| 052 | The constant budget address element of the hierarchy ID has been deleted |
| 053 | No constant budget address element assigned to the hierarchy ID |
| 054 | Commitment item &1/&2 is not allowed for budgeting and posting |
| 055 | Select at least one node |
| 056 | &1 node &2 does not found |
| 057 | Too much data (&1 nodes) to be loaded at one time (maximum &2 nodes) |
| 058 | Empty &3 in address &1&2 is not allowed |
| 059 | Paste is impossible |
| 060 | Hierarchy is not active |
| 061 | No node exists in the hierarchy |
| 062 | No node exists in distribution receiver hierarchy |
| 063 | Hierarchy tree cannot be generated |
| 064 | Constant element &1&2 has already been assigned to hierarchy ID &3 |
| 065 | FMAA &1&2 does not exist in any hierarchy of bdgt structure &3 in FY &4 |
| 066 | FMAA role customizing changed for FM area &1 and budget structure &2 |
| 067 | The selected node is already a top node |
| 070 | Selection leads to multiple identical nodes |
| 071 | Selection not allowed |
| 072 | No budget period selected |
| 073 | Role of fund is not consistent with role of budget period |
| 074 | Budget period is not multi-level |
| 075 | Warning occurred(&1 warnings), see details in error log |
| 076 | Field &1 is not multi-level |
| 077 | No value selected for the field &1 |
| 078 | No target budget structure selected |
| 100 | FMAA element &1 has not hierarchy role "constant" and cannot be used |
| 101 | FMAA element &1 has not hierarchy role "multi-level" and cannot be used |
| 102 | FMAA element &2 has not hierarchy role "not relevant" and cannot be used |
| 103 | Superior hierarchy node has a different commitment item category |
| 104 | Superior hierarchy node is postable |
| 105 | Whole hierarchy ID &1 will be locked |
| 106 | FMAA &1&2 already exists in the hierarchy |
| 107 | FMAA &1&2 does not exist in the hierarchy for hierarchy ID &3 |
| 108 | FMAA &1&2 already exists in the database for hierarchy ID &3 |
| 109 | Subordinate data of the node &1&2 has to be read from database |
| 110 | Superior data of the node &1&2 has to be read from database |
| 111 | Only an end node can be deleted |
| 112 | FM account assignment &1&2 cannot be budgeted in budget category &3 |
| 113 | Missing hierarchy role definition for budget structure &1 |
| 114 | Commitment item subtree in &1 is not consistent |
| 115 | Commitment item subtree in &1 is not allowed for budgeting or posting |
| 116 | No multi-level roles defined for budget structure &1 |
| 117 | Define at least one multi-level role for budget structure &1 |
| 118 | No hierarchy exists |
| 119 | Hierarchy ID &1 cannot be created because hierarchy ID &2 exists |
| 120 | No budget category defined for FM area &1 |
| 121 | Sibling data of the node &1&2 has to be read from database |
| 125 | Multi-level budget structure &2 is not activated in FM area &1 |
| 130 | Address &1 does not exist in budget address list |
| 131 | Address &1 does not exist in posting address list |
| 132 | Commitment item in subtree &1 is not valid |
| 164 | No authorization for hierarchy ID &1 activity &2 authrization group &3 |
| 200 | Only one sender line can be used for distribution process |
| 201 | You are only allowed to distribute to the next hierarchy level |
| 202 | Transfer allowed only if the addresses have a common parent |
| 203 | Transfers only allowed between top nodes |
| 204 | The FMAA you entered is not the top node in the hierarchy |
| 205 | Distribution lines cannot be created as distribution is not active |
| 206 | Transfer not allowed, only distribution process may be used |
| 207 | Only one fiscal year can be used for distribution process |
| 208 | Only one year of cash effectivity can be used for distribution process |
| 209 | Only one budget category can be used for distribution process |
| 210 | Distribution not allowed |
| 211 | No details exist |
| 212 | Reduce Distribution not allowed |
| 215 | Distribution receiver should match relevant distribution sender |
| 216 | Document types with rollup not permitted for this application |
| 217 | Document types with rollup not permitted for this application |
| 218 | Document type &1 not permitted for the selected update mode |
| 220 | The subordinates of the address &1 will also be moved |
| 222 | No inconsistency check for multi-level budget structure |
| 300 | Specified group &1 is empty |
| 301 | Specified entry node &1 does not exist in group &2 |
| 302 | Non-leaf group &1 in specified group &2 must contain exactly one item |
| 303 | No matching functional area found |
| 304 | Fill all entries for sequence of account assignments |
| 305 | Fill the entry for &1 &2 |
| 306 | Enter a group value for the field &1 |
| 307 | Enter a variant value for the field &1 |
| 310 | FM area is empty for commitment item hierarchy, variant &1 |
| 311 | FM area &1 not found for commitment item hierarchy, variant &2 |
| 312 | Wrong fiscal year &1 for commitment item hierarchy, variant &2 |
| 313 | Specified commitment item &1 not found in commitment item variant &2 |
| 314 | Error occurred for &1 hierarchy by variant &2 |
| 315 | Read &1 list error: FM area &2, fiscal year &3 |
| 320 | Budget structure &1 and &2 must have same multi-level FMAA elements |
| 321 | No address maintained for the selected node |
| 330 | No hierarchy nodes selected according to the restriction on hierarchy |
| 400 | Reserved for Export / Import Multi Level Budget Structure |
| 401 | Number of data of hierarchy IDs (record type A): &1 |
| 402 | Number of data of constant elements for hierarchy ID (record type B): &1 |
| 403 | Number of data of multi-level nodes (record type C): &1 |
| 404 | Number of data of relations for multi-level nodes (record type D): &1 |
| 405 | Number of hierarchy IDs created : &1 |
| 406 | Number of constant budget address elements created : &1 |
| 407 | Number of multi-level nodes created : &1 |
| 408 | Number of hierarchy IDs updated : &1 |
| 409 | Number of lines transfered : &1 |
| 410 | All multi-level nodes have been deleted for hierarchy ID &1 |
| 411 | Multi-level nodes already exist for hierarchy ID &1. Import not possible |
| 412 | File has been signed |
| 413 | Envelope error in &1 |
| 414 | Contents of the file incorrect. Check if file is signed |
| 415 | No data found for FM area &1, year &2, budget cat. &3 Budget structure &4 |
| 416 | File verified |
| 417 | File developed and verified |
| 418 | File enveloped |
| 419 | Sign error in &1 |
| 420 | No customizing defined for Digital Signature |
| 421 | Application data exists for hierarchy ID &1. Import of data not possible |
| 422 | Inconsistent import data: no multi-level nodes defined for ID &1 |
| 423 | Process has been canceled during password verification |
| 424 | Inconsistent hierarchy data: invalid multi-level nodes for ID &1 |
| 425 | Inconsistent hierarchy data: duplicate multi-level nodes for ID &1 |
| 426 | No authorization for Envelope |
| 427 | No authorization for Develop |
| 428 | Test run started |
| 429 | Update run started |
| 430 | Inconsistent hierarchy data: invalid next sibling definition for ID &1 |
| 431 | Application data exists for hierarchy ID &1. Deletion not possible |
| 432 | Constant budget address element does not exist |
| 433 | Application data exists for multi-level node. Deletion not possible |
| 434 | Deletion not possible for multi-level node |
| 435 | Multi-level node becomes leaf node when its subordinate nodes are deleted |
| 436 | Hierarchy ID &1 used for budget structure. Deletion not possible |
| 437 | Multi-level node used for budget structure. Deletion not possible |
| 438 | Inconsistent hierarchy data: invalid next sibling definition for ID &1 |
| 439 | Multi-level node does not exist |
| 440 | Multi-level node &3&4 already exists |
| 441 | Multi-level node already exists with differing hierarchy relationship |
| 442 | No valid parent for new multi-level node |
| 443 | No valid next sibling for new multi-level node |
| 444 | Multi-level node is no longer a leaf node after subordinate nodes added |
| 800 | Hierarchy inconsistency: class &1, method &2 |
| 801 | Error calling method &2 of class &1 |
| 802 | Inconsistent hierarchy of FMAA element &1 |
| 803 | Message exists, see details in the application log |
| 804 | You must save the deletion before inserting a new root node |
| 805 | No application log handler exists |
| 806 | No message in error log |
| 807 | Add node to column tree failed: Function Module &1, Subroutine &2 |
| 808 | Use 'Insert Node Manually' to start processing an empty hierarchy |
| 809 | Access object &1 does not exist in group &2 |
| 810 | &1&2&3&4 |
| 811 | The combination of BA def.rule and PA def.rule is not allowed |
| 812 | Parent node doesn't exist |
| 813 | Selected BA or PA definition rule is not allowed |
| 814 | Distribution path broken in document &1 |
| 815 | Budget address is not a root node (document &1) |
| 816 | No master data selected for FMAA element &1 |