Subsidiary Hierarchy Structure Modification
Please read the following license agreement to understand the consequences associated with a subsidiary hierarchy modification.
Modifying entries in the Subsidiary Hierarchy can have significant legal and financial consequences. Please be certain you are authorized to make such changes and consult with the appropriate stakeholders in your business before proceeding.
At a minimum, you should read the official documentation and review and download all documents that may be relevant to these modifications, including but not limited to Financial Statements such as the Balance Sheet, Income Statement, Trial Balance, and audited reports from prior periods on both Consolidated and Subsidiary Levels, as well as Consolidated Exchange Rates.
To ensure modifications are implemented correctly, make the modifications first in a Sandbox Environment and then thoroughly review all Financial Statements and Consolidated Exchange Rates to ensure the modifications had the anticipated consequences before deploying the modifications in a Production Environment.
The consequences of implemented modifications are outside the scope of any support made available to your organization by Oracle, and your organization is solely responsible for the effect of such modifications on your organization’s use of the product and for any costs or expenses arising from or related to such modifications, including but not limited to the cost of any required data fixes.
Areas of the product that may be affected by such modifications include but are not limited to the following:
-
Existing financial statements may be lost with no possibility of recovery
-
Subsidiaries may get inactivated
-
Consolidated/Budget Exchange Rates may be irreversibly recalculated
-
Elimination Subsidiaries may get different parent Subsidiary
-
Auto-Elimination Journals may post to the incorrect Elimination Subsidiary
-
The Include Children (Subsidiaries) option may include a different set of Subsidiaries than before
-
Granted restrictions on roles may change
-
Reporting may not provide correct results if crossing Subsidiary Hierarchy Modification change date
-
Customization and scripts utilizing Subsidiary may begin to fail
If you have questions before making such modifications, you may open a support ticket to request assistance from Oracle.
I have read, understood, and agree to the above on behalf of my organization.
The Allow Subsidiary Hierarchy to be Modified general preference enables you to modify your subsidiary hierarchy structure, as required by your company.
The following are common reasons to modify your subsidiary hierarchy:
-
You acquired a company and you must establish a new head quarter subsidiary.
-
You must change the headquarter subsidiary to another subsidiary in your hierarchy.
For example, subsidiary number two becomes the parent subsidiary.
-
You want to elevate a subsidiary in the hierarchy.
For example, subsidiary number three becomes a regional subsidiary rather than a local subsidiary.
In addition to the known product areas listed in the license agreement, check the product areas you use that a modification may impact. The license agreement appears earlier in this topic.
Required Permissions for Subsidiary Hierarchy Modification
If you are an administrator, you can set the following requirements on the Role page. Go to Setup > Users/Roles > Manage Roles > New.
|
On the Permissions subtab, click the Lists subtab. |
|
|
On the Permissions subtab, click the Setup subtab. |
|