How To Fix 5P390 - E: Only 36 nodes from the same hierarchy level can be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: 5P - Error Messages for Schema, Pers.Calc.Rule and Feature Checks

• Message number: 390

• Message text: E: Only 36 nodes from the same hierarchy level can be saved

What causes this issue?

One hierarchy level has more than 36 entries. Internal technical
reasons currently prevent more than 36 entries from being saved for the
same hierarchy level in the feature tree.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Reduce your return lines/program marker lines to 36 entries.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5P390 - E: Only 36 nodes from the same hierarchy level can be saved ?

  The SAP error message 5P390 E: Only 36 nodes from the same hierarchy level can be saved typically occurs when you are trying to save a hierarchy in a structure (like a cost center hierarchy, profit center hierarchy, or similar) that exceeds the limit of 36 nodes at the same hierarchy level. This is a restriction in SAP to ensure performance and manageability of hierarchies.
  Cause:
  The error is triggered when you attempt to save a hierarchy that has more than 36 nodes (or elements) at the same level. This can happen during the creation or modification of hierarchies in various SAP modules, such as Controlling (CO) or Financial Accounting (FI).
  Solution:
  To resolve this error, you can consider the following approaches:
  
  
  Reorganize the Hierarchy:
  
  Review the hierarchy structure you are trying to save. If you have more than 36 nodes at the same level, consider reorganizing the hierarchy. You may need to create sub-levels or group some nodes together to reduce the number of nodes at the same level.
  
  
  
  Split the Hierarchy:
  
  If the hierarchy is too complex, consider splitting it into multiple hierarchies. This way, you can keep the number of nodes at each level within the allowed limit.
  
  
  
  Check for Duplicates:
  
  Ensure that there are no duplicate nodes at the same level that might be contributing to the count exceeding 36.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidelines on hierarchy structures and limitations.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue through the above methods, consider reaching out to SAP support for further assistance. They may provide insights specific to your SAP version or configuration.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any updates or patches related to this error. Sometimes, SAP releases notes that provide additional guidance or solutions for specific issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes (like OKEQ for cost center hierarchy) that you might be using when encountering this error.
  Best Practices: Follow best practices for designing hierarchies in SAP to avoid hitting such limits in the future.
  
  By following these steps, you should be able to address the error and successfully save your hierarchy in SAP.