Hello and welcome to 2023! The first blog post this year is a warning regarding the FCC (Financial Consolidation and Close cloud service) update for this month.
The 23.01 (January 2023) release somehow opened up the dense/sparse settings for the dimensions in the application. Dense and sparse (if a dimension is not dense then it's sparse) relate to how the underlying Essbase database is structured for saving data. Below, the Period and Movement dimensions are set to Dense (checkmark enabled). If your application shows only the Account as dense, see the bottom of this post.
The dense/sparse column is normally read-only (greyed out) but as you can see the column is editable. Do not make any changes to this! Untold calamities will occur - seriously, there is no telling what will work and not work. Insertion rules, for one, will have problems. Oracle has already worked through the optimal dense/sparse settings, determined the optimal setup, and built the application around them. A fix to put the setting back into read-only mode is under development.
If your application shows only the Account as dense, then consider running the migration to make Period and Movement dense. There are several benefits, the biggest being the consolidation time will be a lot quicker.
There are several steps to do. The process is not hard, but should be done in test to confirm, particularly if insertion rules exist. Here is the link for the documentation (note if two rows of text show this is one link that is wrapping on the screen).
https://docs.oracle.com/en/cloud/saas/financial-consolidation-cloud/agfcc/migrating_movement_period_dense.html
