In Oracle FCCS (Financial Consolidation and Close Service), metadata is the structural definition of your application — the dimensions, members, hierarchies, aliases, attributes, and consolidation rules that FCCS uses to know how to aggregate, eliminate, and translate data.
Unlike a general-purpose EPM cube where you build whatever dimensions you like, FCCS ships with a fixed set of eight system dimensions that map directly to consolidation concepts: Entity, Account, Scenario, Year, Period, View, ICP, and Movement. Some dimensions allow custom members; others are partially locked. Understanding which is which — and why — is a cornerstone exam topic.
Metadata is not just structure — it encodes business logic. The consolidation method (Full/Proportional/Equity), ownership percentage, elimination behaviour, and currency translation rules are all stored as member properties within the metadata.
ICP is the dimension that makes intercompany elimination possible. When an entity records a transaction with another entity in the group, it tags the balance with the partner's ICP code. FCCS then matches those paired balances and eliminates them during consolidation.
Not every account needs ICP tagging. In FCCS you set the IsICP
property on an Account member to Y or N. Only
ICP-enabled accounts can carry an ICP partner code. Typical ICP accounts:
Intercompany Receivables, Payables, Revenue from affiliates, Expenses to affiliates.
The system creates a matching ICP member for every base (leaf) entity. So for GlobalMerge Corp's structure, the ICP dimension automatically contains:
ICP_[None] is used when a transaction has no intercompany partner — i.e. it's with a third party. You must always intersect ICP-enabled accounts with either a specific partner or ICP_[None]; leaving it blank causes a data load error.
GlobalMerge Corp is the UK-based holding company. Below it sit four operating subsidiaries across different jurisdictions and ownership levels — each requiring a different consolidation treatment.
The consolidation method is stored as a member property on the Entity (PCON% = percentage consolidation). FCCS reads this property at runtime. Full = 100% of assets/liabilities + NCI elimination. Proportional = only the owned % flows through. Equity = single-line investment only; no line-by-line aggregation.
| Account Type | Examples | Translation Rate | Sign Behaviour |
|---|---|---|---|
| ASSET | Cash, Receivables, PPE | Closing Rate | Debit increases |
| LIABILITY | Payables, Debt, Provisions | Closing Rate | Credit increases |
| EQUITY | Share Capital, Retained Earnings | Historical Rate | Credit increases |
| REVENUE | Sales, Other Income | Average Rate | Credit increases |
| EXPENSE | COGS, Opex, D&A | Average Rate | Debit increases |
| FLOW | Cash Flow movements | Depends on sub-type | Net flow |
| CURRENCYRATE | USD, EUR, GBP exchange rates | N/A — stores rates | N/A |
| GROUPLABEL | Subtotal headers only | N/A — calculated | Sum of children |
FCCS supports alternate hierarchies (also called alternate rollups) within a dimension. A member can appear in multiple hierarchies simultaneously — this is called shared membership. The primary hierarchy determines the default aggregation path; alternate hierarchies enable reporting cuts such as region, product line, or legal vs. management structure.
A shared member is the same physical member appearing in two hierarchy branches. Data is stored once; the member just rolls up in two places. A duplicate member (not supported in FCCS base dimensions) would be two distinct members with the same name — FCCS does not allow this in the Entity dimension.
Beyond the legal ownership hierarchy, GlobalMerge uses two alternate rollups in the Entity dimension for management reporting:
| Property | Dimension | Values | Effect |
|---|---|---|---|
| DefaultCurrency | Entity | GBP, EUR, SGD, USD… | Sets the entity's local currency for data entry and translation |
| PCON% | Entity | 0–100 | Consolidation percentage; drives proportional aggregation |
| POWN% | Entity | 0–100 | Ownership %; used for equity pickup and NCI calculation |
| Method | Entity | Consolidate / Equity / Proportional / None | Determines which consolidation logic FCCS applies |
| IsICP | Account | Y / N | Enables intercompany partner tagging on this account |
| AccountType | Account | Asset/Liability/Equity/Revenue/Expense/Flow | Governs sign logic and default translation rate type |
| DataStorageType | All dims | Store / Dynamic Calc / Never Share | Controls whether data is physically stored or calculated on-the-fly |
| Alias | All dims | String (language tables) | Display labels in forms and reports; does not affect storage |
| Custom Attributes | Entity, Account | User-defined | Enables filtering, smart lists, and supplemental grouping |
Any time you add, edit, or delete members, hierarchies, or member properties in the Metadata screen, FCCS marks the application as needing a Metadata Refresh. Until the refresh completes, the application may show stale data or refuse to run consolidations.
Refresh is triggered from Application > Consolidation > Refresh. It rebuilds all dimension caches, rebuilds the dynamic calc script, and invalidates any stored data that is now structurally inconsistent.
A refresh does not delete existing data — but data at deleted members becomes inaccessible. Members can be disabled ("hidden") without a data-destructive refresh cycle.
The System Check (SC) runs automatically after every metadata refresh and is also available on-demand. It validates structural integrity and reports status per entity-scenario-period intersection.
If an admin adds a new Account member (e.g., IC_Revenue_AsiaLink) and runs a refresh, all entities that have already consolidated in the current period will flip from status 2 (Consolidated) to status 6 (Impacted). The admin must notify the consolidation team to re-run the consolidation process.
AsiaLink (50% JV, SGD) would additionally show 3 (Needs Translation) if any FX rates were updated as part of the metadata package refresh.
Metadata is loaded via a .csv or .xlsx file through the FCCS Metadata Editor UI, or automated via EPM Automate commands. The header row defines property columns; rows below represent individual members.
DeutschWerk has POWN% = 80 (we own 80%) but PCON% = 100 (we consolidate 100% of its balances — full consolidation method). The 20% NCI is then separately calculated and posted as an elimination. This is the key distinction: POWN governs equity and NCI calc; PCON governs how much data flows into the consolidated numbers before eliminations.
In this lab you will build the complete metadata structure for GlobalMerge Corp from scratch using the FCCS Metadata screen. You'll configure Entity members with ownership properties, tag ICP-enabled accounts, define an alternate geographic hierarchy, and observe how SC status changes after each metadata refresh cycle.
Access to an FCCS sandbox application · Service Administrator role · Navigator > Application > Consolidation open in a separate tab · GlobalMerge_Metadata_v1.csv available in your EPM Automate workspace
- 01 Navigate to Application > Overview > Dimensions and select the Entity dimension.
-
02
Click Import and upload
GlobalMerge_Metadata_v1.csv. Select Update existing members mode. - 03 After import completes, verify all four subsidiaries appear under GlobalMerge in the hierarchy pane. Confirm DefaultCurrency values: BritEdge=GBP, DeutschWerk=EUR, AsiaLink=SGD, NovaTech=USD.
- 04 Check PCON% vs POWN% for each entity. DeutschWerk should have PCON=100, POWN=80. AsiaLink should have both PCON=50, POWN=50. NovaTech should have PCON=0, POWN=30.
- 05 Click Refresh Database and wait for the job to complete. Note the timestamp.
All four entity members appear correctly. ICP dimension auto-populates with ICP_BritEdge, ICP_DeutschWerk, ICP_AsiaLink, ICP_NovaTech under ICP_Entities. SC Status for all entities in the current open period shows 6 (Impacted) — because the metadata refresh invalidated any previously consolidated data.
- 01 In the Entity dimension editor, click Add Member and create three parent-only nodes: EMEA, APAC, Americas. Set DataStorageType = Label Only (no data stored).
- 02 Create a top-level parent GeoTotal with EMEA, APAC, Americas as children.
- 03 Add shared members of BritEdge and DeutschWerk under EMEA. Right-click each entity > Add Shared Member.
- 04 Add shared members: AsiaLink under APAC, NovaTech under Americas.
- 05 Confirm that shared members show a different icon (ghost/shared indicator) in the hierarchy. Refresh database.
- 06 Open a data form and verify that the GeoTotal hierarchy is available as an alternate row/column selection.
When you run a consolidation for GlobalMerge (primary hierarchy), the data also rolls up through GeoTotal automatically because the same physical data cells underlie both hierarchy paths. No extra consolidation run is needed for the alternate hierarchy.
-
01
Navigate to the Account dimension. Locate
IntercompanyReceivablesand set IsICP = Y. Repeat forIntercompanyPayables,ICSales,ICExpenses. -
02
Confirm that
Cash,Revenue, andCOGShave IsICP = N. These should never carry intercompany partner tags. - 03 Run a metadata refresh. Navigate to Consolidation > System Check. Observe that all entities now show status 6 (Impacted).
-
04
Submit trial balance data for BritEdge (Actual, Jan-25). Set
ICSaleswith partnerICP_DeutschWerk= GBP 500,000. Submit data for DeutschWerk:ICExpenseswith partnerICP_BritEdge= EUR 580,000 (approx equal at spot rate). - 05 Run IC Matching from the task flow. If the GBP/EUR difference is within tolerance (±0.5%), status should move to 5 (Matched). Run consolidation. Status moves to 2 (Consolidated).
-
06
As an admin, add a new Account member
IC_Advisory_Feeswith IsICP=Y. Refresh metadata. Observe that BritEdge and DeutschWerk flip back to 6 (Impacted).
AsiaLink has PCON=50%. After consolidation, verify in the parent-level (GlobalMerge)
data that only 50% of AsiaLink's balances appear. Check the Contribution
member in the View dimension — it shows the entity's proportional share before
parent adjustments. Compare this with BritEdge (PCON=100%) to cement the difference.
These questions mirror the style, complexity, and trap-setting of the official Oracle FCCS Implementation Specialist examination. Each question covers metadata-related objectives. Click Reveal Answer after attempting each question.