📊 Accessing FX Rates in the Consol Cube (FCC) — Explained

One common question in Oracle FCC is:

Can we view FX rates in the Consol Cube, or are they only stored in the Rates Cube? If yes, what is the correct POV to view them?

Let’s break this down clearly.

Yes — FX rates can be viewed in the Consol Cube.

However, it’s important to understand the architecture:

• Rates Cube → Primary storage of exchange rates
• Consol Cube → Stores rates after they are processed and transferred via system rules

So, while the Rates Cube is the source, the Consol Cube does hold FX rates.

How to Access FX Rates in FCC

FX Rates in FCC can be accessed in two ways:

• Via a Data Form (Web Interface)

• Via Oracle Smart View (Excel Add-in)

Both methods require the correct Point of View (POV) and form configuration to display exchange rate data accurately. The sections below detail how to design and configure the Data Form targeting the Consol cube.

🧩 Data Form Design — Consol Cube

Creating the Data Form

To build this form in the FCC web interface, navigate to Data > Create Form. Set up the POV, Row, Column, and Page dimensions as defined in the tables above. Once you have configured the layout, enable the Show Currency option (highlighted below) to display the default entity currency alongside the exchange rate data in the form.

▶️ Running the Data Form

Once the form is saved and opened, it will display the FX Rates (Average Rate and Ending Rate) held in the Consol cube for each entity, broken down by period across the fiscal year. The screenshot below shows the form output for Scenario: Actual, Year: FY21.

🔎 Validating FX Rates

After viewing the exchange rates in the Consol cube, the next step is to verify that the rates match what is stored in the Rates cube

If you compare the Rates between the Rates and Consol cube for example EUR Avg & EOM Rate matches exactly in both cubes.

Jan :1.50000/2.00000

Feb :1.70000/2.200000

🔄 What Happens When You Save FX Rates?

When FX Rate data is saved in a form targeting the Rates cube, FCC automatically triggers two seeded post-process rules that compute and push rates to the Consol cube.

Form_PostProcess_Rate

Form_PostProcess_SDMCurrencyRates

✅ What These Rules Do:

Compute exchange rates

Transfer rates from Rates Cube → Consol Cube

Use Case: Troubleshooting Translation Issues

These data forms are extremely useful for diagnosing currency translation issues. A common scenario is when you run consolidation or translation and notice that certain entities are not being translated, even though FX Rates appear to have been loaded correctly.

The root cause in such cases is often one of the following:

• The FX Rates were cleared from the Consol cube.

• The rates were not moved from the Rates cube to the Consol cube (i.e., the post-process rules did not execute successfully).

By using the Consol cube data form (Figure 2) alongside the Rates cube form (Figure 3), you can quickly determine whether rates are present in both cubes for the affected currency and period, and take corrective action accordingly.

Important: FCCS_No Data Source — Handle With Care

FCC_No Data Source is a reserved system member in the Data Source dimension. It stores system-level values, including currency rates, in the Consol cube.

Warning: Do not use FCCS_No Data Source as a target for manual data inputs. If you clear data for this member, or copy data from one scenario to another while including FCCS_No Data Source in the selection, there is a risk that the FX Rates stored under this member will be wiped — causing translation failures during consolidation.

Best practices to follow:

• Never use FCCS_No Data Source as a target for manual data loads.

• When copying data between scenarios, explicitly exclude FCCS_No Data Source from the copy scope.

• When clearing data, always review the member scope carefully to ensure system-level rate data is not inadvertently removed.

🧠 Final Thoughts

This approach helps with FX rate validation, translation troubleshooting, and understanding data movement between cubes.

A dedicated Data Form for viewing FX rates in the Consol Cube can significantly reduce debugging time during close cycles.