How To Fix J-835 - Portfolio hierarchy & was deleted successfully

SAP Error Message - Details

• Message type: E = Error

• Message class: J- -

• Message number: 835

• Message text: Portfolio hierarchy & was deleted successfully

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message J-835 - Portfolio hierarchy & was deleted successfully ?

  The SAP error message J-835 indicates that a portfolio hierarchy has been deleted successfully. This message is not necessarily an error but rather an informational message that confirms the deletion of a portfolio hierarchy in the system. 
  Cause:
  The message is triggered when a user or a process attempts to delete a portfolio hierarchy in SAP, and the system successfully completes the deletion. This can occur during various operations, such as:
  
  Manual deletion by a user through the SAP GUI.
  Automated processes or batch jobs that include deletion of portfolio hierarchies.
  Data cleanup activities where obsolete or unused hierarchies are removed.
  
  Solution:
  Since J-835 is an informational message indicating successful deletion, there is typically no action required unless the deletion was unintended. If the deletion was not intended, you may need to:
  
  Restore the Deleted Hierarchy: If you have a backup or if the hierarchy can be recreated, you may need to restore it manually.
  Check Dependencies: Ensure that no critical processes or reports depend on the deleted hierarchy. If they do, you may need to adjust those processes accordingly.
  Review Deletion Logs: If you need to understand why the hierarchy was deleted, check the change logs or audit trails in SAP to see who initiated the deletion and why.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing portfolio hierarchies, such as CJ20N (Project Builder) or CJH1 (Hierarchy Management).
  Authorization: Ensure that users have the appropriate authorizations to delete hierarchies to prevent accidental deletions.
  Documentation: Review SAP documentation or help files related to portfolio management for best practices on managing hierarchies.
  Support: If you encounter issues or need further assistance, consider reaching out to your SAP support team or consulting SAP Notes for specific guidance related to your version of SAP.
  
  If you have specific scenarios or additional context regarding the error message, please provide that for more tailored assistance.