When do I manually submit row and column flattening for tree versions?
Row Flattening and Column Flattening for tree versions must be manually submitted in the following scenarios.
-
A new tree or tree version is defined
-
If the tree or tree version has any change made to it that would alter the flattened hierarchy data. For example, adding, moving, and duplicating members. Basically, anything that impacts the flattened hierarchy data.
-
If Data Relationship Management (DRM) is used with Oracle General Ledger, after running the Load Account Values and Hierarchies process from the Scheduled Process work area to load chart of accounts reference data from DRM to General Ledger.
-
When range based hierarchy assignments are supported, if new values are added that are within the account range assigned to the hierarchy.
Note: In this case, try submitting the flattening programs using the Online Mode first. If the newly inserted child account value does not appear to be included in the flattened hierarchy data, then the flattening program has to be submitted using the Force Flattening Mode, instead of Online Flattening. An issue with the incremental flattening programs can prevent them from picking up this type of hierarchy change, so full flattening can be required.