Starting from August 2021, we are able to process “Dense Sparse Optimization” (DSO), which is basically changing the dense dimension from Account to Period and Movement.

 

Initially, the account was the only dense dimension in a Financial Consolidation and Close application. You may run into certain performance challenges, including taking a long time to run a business rule, retrieve data via Smart View, etc. Setting Period and Movement as dense dimensions can increase the block density, reduce application size, and improve performance.

 

With this new patch, you can,

1. Select on the option to make Period and Movement as dense dimensions, when creating a new application
2. Migrate an existing application from Account dense dimension to Period and Movement dense dimensions.

Please note:

• This only works for Hybrid applications.
• Once we make the change, we cannot quickly change it back to Account as dense. We will have to restore the application from a backup.

Once you change the period and movement as dense dimensions, double check the following items.

• Business rules, member formulas
• Solve order.
  • Account: The solve order of the existing parent account members is automatically set to 58. Make sure to set the Solve Order to 58 for any new Parent Account members that are added.
  • Movement: All Parent Movement members must be Dynamic Calc. Remove the Solve Orders for any of the members that you have previously set.
  • Data Source: Remove the Solve Orders for any of the members that you have previously set.
• Data Export jobs. Update the data export jobs and use Period and Movement as dense.
• Data Source dimension. The following members are no longer used for consolidation.
  • FCCS_RateOverride (Parent member: FCCS_SystemTypes)
  • FCCS_AmountOverride (Parent member: FCCS_SystemTypes)
  • FCCS_PCON (Parent member: FCCS_SystemTypes)

 

According to Oracle, they have tested for multiple applications, there are the sample results.

 

Now, let’s go through the process of making an existing application from Account dense dimension to Period and Movement dense dimensions.

By default, we can tell that the account is the only dense dimension.

 

From the application overview, Actions, we will be able to select Make Period and Movement Dense.

 

When we select it, it will prompt the following window. We will have to make sure we understand the process and the impact. Most importantly, we’d better take a full backup of the application.

 

Check all the boxes to continue.

 

Also, if it starts the migration within 12 hours of AMW, we have to update the AMW time.

 

After that, it will start validating the process.

 

Once the validation is done, we are ready to Launch the process.

 

We can download the “PeriodMovementDenseMigrationSummary.log” file.

 

Launch the process, it will prompt the warning message.

 

Now the process has started.

 

It is enabling features.

 

In the end, it tells us the application is successfully migrated to have Period and Movement as Dense dimensions.

 

Re-sign in the application, we see the Period and Movement dimensions have been updated to dense.

 

From the job log, we can tell the following jobs have been run during the converting process.

 

Check the Make Period and Movement Dense job.

 

We can download the log file and check the details.

PeriodMovementDenseMigration_1630792274938.log

 

Hope this post gives you some ideas of Dense Sparse Optimization in an FCC application.