How To Fix 1E146 - Account &1 cannot be closed on &2 because it is still in the hierarchy

1E146 - Overview

• Message type: E = Error

• Message class: 1E - BCA: Account

• Message number: 146

• Message text: Account &1 cannot be closed on &2 because it is still in the hierarchy

What causes this issue?

Since the account is still in a hierarchy, you cannot close it.

How to fix this error?

To remove the account from the hierarchy and close it, proceed as
follows:
Set the <LS>Valid To</> date of the hierarchy to the last (or next)
account balancing date by choosing <LS>Hierarchy -> Change Interval.
</>Make a note of the original <LS>Valid To</> date of the hierarchy.
Create a new hierarchy. Use the hierarchy that you changed above as the
copy template.
<LS>Valid From: </>One day after the new <LS>Valid To</> date of the
changed hierarchy.
<LS>Valid To: </>Old <LS>Valid To</> date of the original hierarchy.
In the hierarchy, delete the related account that is to be closed.
Now you can enter the account closure date and close the account.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1E146 - Account &1 cannot be closed on &2 because it is still in the hierarchy ?

  The SAP error message 1E146 indicates that an account cannot be closed because it is still part of a hierarchy. This typically occurs in the context of financial accounting, where accounts are organized in a hierarchical structure for reporting and analysis purposes.
  
  Cause:
  The error arises when you attempt to close an account (e.g., during a fiscal year-end closing process) that is still linked to a higher-level account in the hierarchy. This means that the account is still active and cannot be closed until it is removed from the hierarchy.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Account Hierarchy:
  
  Navigate to the account hierarchy in your SAP system.
  Identify the account that is causing the issue (as indicated by the error message).
  
  
  
  Remove from Hierarchy:
  
  If the account is part of a higher-level structure, you will need to remove it from the hierarchy.
  This can typically be done in the account master data or hierarchy maintenance