Oracle FCC for Beginners: Understanding Dimensions
When I first started working with Oracle Financial Consolidation and Close (FCC), I found that understanding the dimensions was one of the most important steps in getting comfortable with the application.
At first, it is easy to focus on loading data, running consolidation, and checking reports. But when the numbers do not appear as expected, it helps to understand how FCC organizes data and what happens to it during the consolidation process.
In this blog, I want to explain some of the core FCC dimensions in simple terms, based on what I have learned while working with the application.
What Is FCC?
Oracle Financial Consolidation and Close (FCC) is a cloud-based solution used to consolidate financial data from multiple entities and support the financial close process.
It helps organizations manage tasks such as:
- Financial consolidation
- Currency translation
- Intercompany eliminations
- Consolidation adjustments
- Financial reporting
In simple terms, FCC takes financial data from different entities, processes it according to the application configuration and consolidation rules, and helps produce consolidated financial results.
Why Do Dimensions Matter in FCC?
One thing that took me some time to understand was that a financial value in FCC is not identified by the account alone.
The value is associated with a combination of dimensions. These dimensions provide the context needed to understand where the data belongs, what period it relates to, where it came from, and how it is processed.
For example, when reviewing a value in Smart View, you may need to consider the Account, Entity, Scenario, Year, Period, Currency, Data Source, Movement, and Consolidation dimensions.
If a value is missing or different from what you expected, checking the relevant dimension members is a useful place to start troubleshooting.
Let’s look at some of the key dimensions.
1. Account Dimension
The Account dimension represents the financial accounts used in the application, such as cash, accounts receivable, revenue, and expenses.
Apart from identifying the account, its properties also influence how FCC processes the data.
For example, account properties can affect currency translation and how the account is treated in financial reporting.
When troubleshooting an account, it is worth checking not only the account member but also its properties and the relevant dimension intersections.
2. Entity Dimension
The Entity dimension represents the organizational structure of the company.
It can include individual legal entities, subsidiaries, and parent entities.
For example, imagine a company has three entities:
- Entity A
- Entity B
- Parent Entity
Entity A and Entity B may maintain their own financial data, while Parent Entity consolidates their results.
The Entity dimension helps define this structure and determines how data is organized along the consolidation hierarchy.
When reviewing results, it is important to distinguish between data at an individual entity level and results calculated at a parent level.
3. Movement Dimension
The Movement dimension was one of the dimensions I found particularly important to understand.
It captures details about changes in account balances. FCC provides seeded Movement members for opening balances, closing balances, movements, and foreign exchange-related calculations.
For example, a balance sheet account may have an opening balance, movements during the period, and a closing balance.
The Movement dimension helps represent these details instead of treating the balance as a single unexplained figure.
It also plays a role in cash flow reporting, where movements can be classified into operating, investing, and financing activities.
One important point to remember is that not every account or transaction uses Movement in the same way. The relevant members depend on the account, the data being loaded, and the application’s configuration.
4. Data Source Dimension
The Data Source dimension helps identify where financial data comes from and provides an audit trail for different types of input and system-generated data.
Get Rithik’s stories in your inbox
Join Medium for free to get updates from this writer.
For example, depending on the application configuration, data may come from:
- Manual data entry or file-based data loads
- Data Integration
- Journal entries
- Supplemental Data
- Intercompany eliminations and other system-generated adjustments
FCC provides seeded Data Source members for these different purposes. For example, FCCS_Data Input, FCCS_Managed Data, and FCCS_Journal Input represent different types of input.
This dimension is particularly useful when investigating differences in financial results.
Suppose a value in Smart View does not match what you expected after loading data. Reviewing the Data Source dimension can help you determine whether the value comes from loaded data, a journal, or another source.
The exact members available depend on the application’s configuration and enabled features.
5. Consolidation Dimension
The Consolidation dimension helps show how financial data is represented at different stages of the consolidation process.
Some of the important seeded members include:
- FCCS_Entity Input
- FCCS_Entity Consolidation
- FCCS_Proportion
- FCCS_Contribution
- FCCS_Parent Input
Each member has a specific purpose in the consolidation process.
For example, Entity Input represents input data at an entity, while Entity Consolidation stores consolidation results for parent entities. Proportion and Contribution are used to represent relevant stages of the consolidation process.
These members are not interchangeable. Looking at the correct Consolidation member is important when validating results in Smart View.
The seeded members and their properties support the standard FCC calculations. They should not be treated as ordinary members that can be freely created, renamed, or deleted.
6. Other Dimensions Worth Knowing
The dimensions above are a useful starting point, but FCC also uses other dimensions to organize financial data.
Scenario: Identifies the type of data, such as Actual, Budget, or Forecast.
Year and Period: Identify the financial year and reporting period.
Currency: Represents the relevant currency context in a multicurrency application.
Intercompany: Identifies the intercompany partner associated with a transaction when intercompany tracking is enabled.
View: Determines how data is represented over time, such as periodic or year-to-date values.
Depending on the application’s requirements and configuration, FCC can also include Multi-GAAP and custom dimensions.
Understanding how these dimensions work together makes it easier to navigate data forms, Smart View, and reports.
Common Mistakes When Starting with FCC
When learning FCC, it is easy to overlook some of these details.
A few things worth checking are:
- Movement: Assuming every account uses the same Movement member.
- Data Source: Treating loaded data and journal data as if they have the same source.
- Consolidation: Checking only Entity Input when the value needs to be reviewed after consolidation.
- Entity: Expecting parent-level results to be available without considering the consolidation process.
- Dimension intersections: Comparing values that belong to different periods, currencies, or dimension members.
These are good starting points when trying to understand why a number in FCC looks different from what you expected.
Final Thoughts
For me, understanding the dimensions is an important part of learning FCC. It provides a clearer picture of how data is organized and how to investigate results when something does not look right.
You do not need to understand every advanced feature at the beginning. Start with the main dimensions, explore how they appear in Smart View, and observe how the values change after data loading and consolidation.
Once you become comfortable with these basics, it becomes much easier to explore more advanced topics such as currency translation, intercompany eliminations, journals, and consolidation rules.
If you are new to FCC, my suggestion is to spend some time understanding the dimensions before moving on to more complex configurations. That foundation will be useful throughout your work with the application.
