Best Practice for Creating Reference Account Hierarchy Tree After Copy Issue (Tree Audit Error)

Environment:

-Oracle ERP Cloud

-Module : General Ledger

-Feature : Manage Account Hierarchies

Back Ground:

We're trying to create a new "reference-only" account hierarchy tree based on an existing production hierarchy.

The Purpose of this new tree is:

-To be used only for data access/reporting (GL balance, Narrative Reporting)

-Not for journal entry or transaction posting

-To group existing account values under additional parent nodes for easier access control

What We did:

1.Copied an existing active account hierarchy tree.

2.The copied tree had the same:

-Tree Name

-Tree Code

-Tree Structure Code

3.The copied tree was initially in Draft status.

4.The copied tree was deleted.