How To Fix FICUSTOM275 - Kontierung &1 wurde durch Verschieben d untergeordn. Knoten Blätterknoten


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FICUSTOM - Customizable Messages for Funds Management

  • Message number: 275

  • Message text: Kontierung &1 wurde durch Verschieben d untergeordn. Knoten Blätterknoten

  • Show details Hide details
  • Was verursacht dieses Problem?

    Moving or deleting a node to under a new higher-level account assignment
    can go against the rules for budget addresses that were defined for
    transaction <LS>Create/Assign Subhierarchy_ID</> (FMHIE_HIEID).
    The list for budget addresses or posting addresses can become invalid
    due to reason &V2&.
    <ZH>Reason 1: Inconsistency in Posting Address List</>
    You defined the following rules: "All Account Assignments in the
    Multi-Level BS are Valid Posting Addresses" and "Only Account
    Assignments at End Node Level in the Multi-Level BS are valid Posting
    Addresses?. Due to moving the node, inconsistencies have occurred in the
    list of posting addresses as the hitherto higher-level node &V1& has
    become an end node. Through this change, the node &V1& can now be posted
    to, but may not be able to be maintained in the posting address list.
    <ZH>Reason 2: Inconsistency in the Budget Address List</>
    You have defined the following rules: "All Accounts Assignments Except
    End Nodes are Valid Budget Addresses" and "All Accounts Assignments in
    the Multi-Level BS are Valid Posting Addresses". Due to moving the node,
    inconsistencies have occurred in the budget address list as the hitherto
    higher-level account assignment &V1& has become an end node and as such
    can no longer be a budget address, however is still entered in the list
    of budget addresses.
    <ZH>Grund 3: Inconsistency in the budget address and posting address
    list</>
    You have defined the following rules: "All Account Assignments Except
    End Nodes are Valid Budget Addresses". Moving the node has caused
    inconsistencies to occur in the budget address list as the hitherto
    higher-level account assignment &V1& has become an end node and as such
    can no longer be a budget address, but it is still in the list of budget
    addresses.
    Moving the node has caused inconsistencies to occur in the posting
    address list as the hitherto higher-level account assignment &V1& has
    become an end node. The change means the node &V1& can be posted to, but
    may not be in the list of posting addresses to be maintained.

    Systemantwort

    Processing is terminated.

    Wie behebe ich diesen Fehler?

    You can correct the error in one of the following ways:
    Delete or enhance the budget address list (transaction FMBSBO) or the
    posting address list (FMBSPO) with the account assignment &V1&.
    Change the definition rule for budget addresses or postings addresses in
    transaction <LS>Create/Assign Subhierarchy_ID </>(FMHIE_HIEID).
    Set this message to a warning, information, or ignore if you want to
    override this message in Customzing under <LS>Funds Management
    Government -> Basic Settings -> Change Message Control</>. However, when
    doing this, note that overriding the message can cause inconsistencies
    to occur in the multi-level budget structure.

    Vorgehensweise für Systemadministratoren


    Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE


Smart SAP Assistant

  • Was ist die Ursache und Lösung für den SAP Fehler FICUSTOM275 - Kontierung &1 wurde durch Verschieben d untergeordn. Knoten Blätterknoten ?




    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Zugehörige SAP-Fehlermeldungen

Klicken Sie auf die Links unten, um die folgenden verwandten Nachrichten anzuzeigen:

Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant