1. Administering Financial Consolidation and Close
  2. Creating a Financial Consolidation and Close Application
  3. Enabling Enhanced Organization by Period

Enabling Enhanced Organization by Period

When you create an application, if you enable the Ownership Management feature, you can enable Enhanced Organization by Period. You can also enable Enhanced Organization by Period for an existing application if Ownership Management is already enabled.

Enhanced Organization by Period is only available for Dense/Sparse optimized (DSO) applications.

For details on this feature, see Managing Ownership.

This section lists the requirements to enable Enhanced Organization by Period, and the metadata changes that the system implements when it is enabled.

Note:

If you do not enable Enhanced Organization by Period, there is no impact to your existing application. However, if Ownership Management is enabled, then enabling Enhanced Organization by Period is recommended.

Before you enable Enhanced Organization by Period, review these sections:

  • Enhanced Organization by Period Requirements for New Applications

  • Enhanced Organization by Period Requirements for Existing Applications

  • Ownership Management Metadata Changes

Enhanced Organization by Period Requirements for New Applications

To select the Enhanced Organization by Period option for a new application:

  • You must enable the Intercompany Data and the Track Intercompany Elimination options.

    If both are enabled, the Ownership Management option is available for selection.

  • You must then select the Ownership Management option.

    If Ownership Management is selected, the Enhanced Organization by Period option is available for selection.

  • If you do not select Ownership Management or Enhanced Organization by Period during application creation, you can enable both features later if the required Intercompany settings are already enabled.

Ownership Management Requirements for Existing Applications

To enable the Ownership Management option for an existing application:

  • The Intercompany Data option must be enabled.

    If you do not have the Intercompany dimension enabled, you must re-create the application to use the Ownership Management feature.

  • The Track Intercompany Elimination option must be enabled.

    You can enable this option in an existing application if the Intercompany dimension is enabled. SeeEnabling Application Features.

  • You must enable Ownership Management before enabling Enhanced Organization by Period.
  • If you have any entities that are locked with a calc status of Impacted, then you must do the following:

    If you have customized the Data Status form and saved it with the same name, you will need to copy it to a unique name as there will be a new Data Status form with the Node Status included. Any customizations you have made will be overwritten.

After you enable a new feature in an existing application, you must reload the navigation flow.

  • On the Home page, click the down arrow next to the user name.
  • the Setting and Actions menu, click Reload Navigation Flow.

Enhanced Organization by Period Metadata Changes

When the Enhanced Organization by Period option is enabled, the system implements these changes to metadata and settings.

Account Changes

When Enhanced Organization by Period is enabled, additional seeded system Accounts will be created to support the recording of calculation status.

In addition to the existing FCCS_CSTATUS and FCCS_CSTATUS_FILTER accounts, these additional accounts will be created:

  • FCCS_NSTATUS_FILTER
  • FCCS_NSTATUS

Without Enhanced Organization by Period enabled, each instance of an entity has a single calculation status, Calc Status, that represents the calculations and data for the entire entity.

When Enhanced Organization by Period is enabled, Node Status is added.

Calc Status will then represent all calculations and data for all Consolidation dimension members in the Entity Total section of the Consolidation hierarchy (from Entity Consolidation up to Entity Total) for single currency applications. For multi-currency applications Calc Status will represent all calculations and data for all Consolidation dimension members in the Entity Total section of the Consolidation hierarchy for both Entity Currency and Parent Currency. The data stored in these Consolidation dimension members can be referred to as Common Data.

Node Status will represent all calculations and data in the remainder of the Consolidation dimension members (from Parent Input if enabled up to Contribution Total) single currency applications. For multi-currency applications, Node Status will represent all calculations and data in the remainder of the Consolidation dimension members , all in Parent Currency only. The data stored in these Consolidation dimension members can be referred to as Node Data.

Note that Common Data and Calc Status is common to all instances of a shared entity while Node Data and Node Status is specific to the Parent.Entity instance of the shared entity.

Consolidation Method Changes

When Enhanced Organization by Period is not enabled, the seeded Inactive consolidation method should not be used.

When Enhanced Organization by Period is enabled, the Inactive consolidation method is used by the system and will have a range setting:

From: =0% To: =0%

When Enhanced Organization by Period is not enabled, the Not Consolidated consolidation method will have a range setting of:

From: =>0% To: <=20%

When Enhanced Organization by Period is enabled, the Not Consolidated consolidation method will have a range setting of:

From: >0% To: <=20%

Approval Process Changes

When Enhanced Organization by Period is not enabled, multiple instances of a shared entity always share a single Process Management Approval Unit. When an Approval Unit for a shared entity is locked, all instances of the shared entity are locked.

When Enhanced Organization by Period is enabled, each instance of a shared entity will have its own separate Approval Unit. When an Approval Unit for a shared entity is locked, the Common Data for all instances of the shared entity are locked but only the Node Data of the locked instance will be locked.

Considerations when Enabling Enhanced Organization by Period for an Existing Application

When Enhanced Organization by Period is enabled, the system will make several changes to the application:

  • Change the ranges for the Not Consolidated and Inactive consolidation methods as noted above.
  • Change the range-based methods for all POV that have a 0% consolidation %, a No Data status. These will be changed from the default of Not Consolidated to Inactive, regardless of the locked / unlocked status. POV with Methods that have been overridden will not be changed.
  • POV that have a non-zero Ownership % and have been assigned the Inactive method as an override before enablement will be changed to a 0% Ownership %.
  • A copy of the Data Stauts form will be saved in the root directory (seeded location) if the Data Status form has been customized and continues to use the Data Status name. The copy will have the name Data Status_Customized. With Enhanced Organization by Period, the Data Status form will be overwritten with a new version that includes Node Status and removes any customizations. This form will be placed in the root directory.
  • Update Parent Currency translations for any non-primary instances of shared entities (Prior Period Data Update task). See Updating Prior Period Data,

    Note that the Prior Period Update task will execute custom calculations (Insertion Point Rules) as part of the process.

Before Enabling Enhanced Organization by Period for an Existing Application

  • If the application has been migrated to DSO in order to enable Enhanced Organization by Period, ensure that all DSO post-conversion steps have been completed before enabling Enhanced Organization by Period, in particular the review and updating of user created rules. A failure to update the rules for a DSO environment might render the application unusable after enabling Enhanced Organization by Period. See the Post-Conversion steps in Converting Period and Movement Dimensions to Dense Dimensions.
  • Ensure that there are no pending metadata changes for which the database has not yet been refreshed. If metadata changes have not been refreshed to the database, the Prior Period Data Update task might not update all required entities.
  • Ensure that any required re-computation of Ownership has been completed (check the Manage Ownership screen).
  • Prior Period Updates might take a long time to complete if the application has many scenarios and a large entity structure. You might wish to defer the Automatic Maintenance Window (AMW) before enabling Enhanced Organization by Period.

After Enabling Enhanced Organization by Period

  • Check the Approval Unit Synchronized status and synchronize if required. See Synchronizing Approval Unit Hierarchies.
  • Ensure that the Prior Period Data Updates task completed successfully (check the Jobs log). If this task did not update completely, initiate it from the Configure: Consolidation screen. See Updating Prior Period Data.