Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TE - Market Risk Management
Message number: 562
Message text: Risk hierarchy &: Node & marked as end node
The node is not a bottomw node, but has nonetheless been marked as one.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
TE562
- Risk hierarchy &: Node & marked as end node ?The SAP error message TE562 indicates that a node in a risk hierarchy is marked as an end node, which means that it cannot have any child nodes. This error typically arises in the context of SAP GRC (Governance, Risk, and Compliance) when you are trying to create or modify a risk hierarchy.
Cause:
- End Node Definition: The node you are trying to modify or add children to is defined as an end node in the risk hierarchy. End nodes are terminal nodes that do not allow further subdivisions or child nodes.
- Hierarchy Structure: The structure of the risk hierarchy may not be correctly defined, leading to attempts to add child nodes to an end node.
Solution:
- Check Node Properties: Review the properties of the node in question. Ensure that it is not set as an end node if you intend to add child nodes. You may need to change its classification or create a new node that is not an end node.
- Modify Hierarchy: If the node must remain an end node, consider restructuring your hierarchy. You may need to create a new parent node that can accommodate the child nodes you want to add.
- Consult Documentation: Refer to SAP GRC documentation or help resources for guidance on managing risk hierarchies and understanding node classifications.
- System Configuration: If you believe the configuration is incorrect, consult with your SAP Basis or GRC administrator to ensure that the hierarchy settings are correctly configured.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TE561
Risk hierarchy &, bottom node &: Wrong level
What causes this issue? The level of the node is not exactly one level above the subsequent node or one level below the previous node.System Response...
TE560
Risk hierarchy &, bottom node &: Wrong node category
What causes this issue? The node is a bottom node, but has the node type 'LEAF'.System Response The system issues an error message and wil...
TE563
Risk hierarchy &, node &: predecessor node does not exist
What causes this issue? The node listed as the previous node doesn't exist in the hierarchy.System Response The system issues an error message ...
TE564
Risk hierarchy &, node &: Wrong node category (category &)
What causes this issue? The node must be labelled as 'NODE' if it is under the top-most level, and 'ROOT' if it is on the top-mos...
Click on this link to search all SAP messages.