Oracle FCCS ships with the modern Reports framework as its strategic reporting surface — cloud-native, drag-and-drop, no client installation required. Financial Reporting (FR) Studio required a Windows client, ran on a separate server tier, and Oracle has confirmed it is being retired. New implementations should not build on FR Studio. The exam tests the Reports framework exclusively.
If an exam question describes a "drag-and-drop report designer embedded in FCCS cloud" — that is the Reports framework. If it mentions a Windows client download or a standalone BI reporting server — that is the legacy FR Studio. Expect the exam to include FR Studio as a distractor against the correct Reports framework answer.
The Consolidation dimension POV determines which stage of the consolidation engine's output a report is reading. Setting it incorrectly is the most common source of "my report doesn't match the signed accounts" support calls.
A report set to FCCS_Entity Input for DeutschWerk shows 100% of the raw trial balance — even though DeutschWerk is 80% owned and has IC eliminations applied. The numbers look plausible but are wrong for group reporting. Always confirm the Consolidation dimension member is FCCS_Contribution before distributing any external report. This is the single most common cause of restatements from FCCS implementations.
Entities accounted for under the equity method — AsiaLink (50% JV) and NovaTech (30%) — do not contribute individual revenue, expense, asset, or liability lines to the consolidated group statements. In the group P&L they appear as a single line: "Share of income from associates and JVs." A report showing AsiaLink's revenue line in the group P&L means either the entity is incorrectly configured as Full consolidation, or the Consolidation POV is set to FCCS_Entity Input which bypasses the engine's equity method logic.
The equity pickup line ("Share of income") that appears in the group P&L is a non-cash item — it represents GlobalMerge's share of AsiaLink's earnings, not cash received. In the Cash Flow statement, this line must be reversed out from Operating Activities (added back as a non-cash deduction from net income).
When AsiaLink actually distributes a cash dividend, GlobalMerge receives real cash. That inflow appears as a cash inflow under Investing Activities in FCCS_DividendsReceived. The net effect: equity pickup disappears from Operating Activities, actual cash appears in Investing Activities. This matches IAS 7 treatment precisely and FCCS handles it automatically via the FCCS_CashFlow Movement hierarchy.
Data Forms are browser-based grid interfaces for structured manual data entry. They sit alongside Data Integration — not as a replacement for it, but as the tool for controlled human-authored adjustments that don't belong in the ERP-to-FCCS pipeline. While Hall 3 handles bulk trial balance loading from SAP and Oracle Financials, Data Forms handle the judgement layer: a controller correcting a misclassification, a finance team posting a supplemental disclosure schedule, or a group CFO entering a management-only adjustment.
Forms enforce dimension security. The DeutschWerk Controller, scoped to DeutschWerk only, opens a Data Form and sees only DeutschWerk's accounts — BritEdge and AsiaLink rows simply do not appear. Forms can also include validation rules that prevent obviously incorrect entries from reaching the cube — a controller cannot accidentally post to a locked period or enter a value outside a defined tolerance range.
Manual form entry writes to FCCS_Data Input. Not FCCS_Managed Data. Not FCCS_Journal Input. This is its own separate data source partition in the Data Source dimension.
A Replace-mode Data Integration reload of the same entity/period combination does not touch FCCS_Data Input. The controller's manual reclassification survives the reload completely intact. Both data sources coexist and are read together by the consolidation engine.
After form submission, the entity moves to Impacted (status 6). Consolidation must be rerun to incorporate the manually entered data into consolidated results. This is correct expected behaviour, not an error.
Oracle Smart View for Office is an add-in that connects Microsoft Excel, Word, and PowerPoint directly to FCCS (and other EPM cloud applications). It gives Finance teams live access to FCCS data in their preferred working environment — no browser navigation, no report regeneration. Pull a DeutschWerk P&L into Excel, pivot across periods and scenarios, double-click to drill down, and submit corrections without leaving the spreadsheet.
Smart View is not a Data Integration replacement. It is an analysis, review, and controlled entry tool — suited for individual entity review, ad-hoc drill-through during close, and targeted manual adjustments. Bulk trial balance loading — 10,000 rows of GL data from SAP — belongs in Hall 3 (Data Management / EPM Automate) where mapping rules, transformation logic, and governance controls exist. Submitting bulk data through Smart View bypasses all of that and is slow, error-prone, and inappropriate for production close cycles.
Smart View retrieval is read-only by default. When a user explicitly submits data from a Smart View grid (Submit Data action), it writes to FCCS_Data Input — the same data source partition as Data Form manual entry. A Replace-mode DI reload does not clear FCCS_Data Input entries made via Smart View, just as it doesn't clear Data Form entries. Both are protected from bulk reload operations by design.
Smart View cannot and should not replace Data Integration for bulk trial balance loading. Bulk loading = Data Integration (Hall 3) → FCCS_Managed Data. Ad-hoc entry and analysis = Smart View → FCCS_Data Input. The exam tests this boundary explicitly in multiple question variants.
The consolidation engine reads all three sources together at every consolidation run. The group P&L figure for DeutschWerk Revenue = FCCS_Managed Data (SAP trial balance) + FCCS_Data Input (€15,000 freight reclassification) + FCCS_Journal Input (any journal entries). Reports can expose the Data Source dimension as a column axis to show the full breakdown — essential for audit trail reviews.
| Line Item | Actual USD | Budget USD | Variance | Var % |
|---|---|---|---|---|
| Revenue — BritEdge Ltd (GBP 100%) | 1,875,000 | 1,800,000 | 75,000 | 4.2% |
| Revenue — DeutschWerk GmbH (EUR 80%) | 1,455,000 | 1,500,000 | (45,000) | -3.0% |
| IC Revenue elimination (DW→BE) | (547,000) | (520,000) | (27,000) | -5.2% |
| Total External Revenue | 2,783,000 | 2,780,000 | 3,000 | 0.1% |
| Cost of Sales — BritEdge | (1,020,000) | (990,000) | (30,000) | -3.0% |
| Cost of Sales — DeutschWerk | (792,000) | (810,000) | 18,000 | 2.2% |
| Unrealised profit elimination (inventory) | (30,000) | — | (30,000) | n/m |
| Gross Profit | 941,000 | 980,000 | (39,000) | -4.0% |
| Share of income — AsiaLink Pte (50% JV equity method) | 48,000 | 45,000 | 3,000 | 6.7% |
| Share of income — NovaTech Inc (30% equity method) | 21,000 | 18,000 | 3,000 | 16.7% |
| Operating Profit / PBT | 789,000 | 802,000 | (13,000) | -1.6% |
DeutschWerk Revenue ($1,455,000) reflects the SAP trial balance ($1,440,000 from FCCS_Managed Data) plus the €15,000 Data Form reclassification ($15,000 from FCCS_Data Input). AsiaLink and NovaTech appear as single equity-pickup lines — no revenue, no costs, no assets or liabilities in the group statements. The unrealised profit elimination ($30,000) came from the Enterprise Journal in Hall 6 (FCCS_Journal Input).
A standard FCCS report shows the aggregated total. An audit trail report exposes the Data Source dimension as a column axis, showing the breakdown across all three lanes side by side. This is the primary tool for Finance Controllers and auditors who need to understand the composition of any consolidated figure — and for proving that a DI reload did not overwrite a manual adjustment.
| Account | FCCS_Managed Data | FCCS_Data Input | FCCS_Journal Input | Total |
|---|---|---|---|---|
| Revenue | 1,440,000 | 15,000 | — | 1,455,000 |
| OtherExpenses | (65,000) | 15,000 | — | (50,000) |
| CostOfSales | (660,000) | (15,000) | — | (675,000) |
| FCCS_Inventory (BS) | 480,000 | — | (30,000) | 450,000 |
| FCCS_ICSales | 500,000 | — | — | 500,000 |
The FCCS_Data Input column makes the DeutschWerk Controller's reclassification fully traceable. The FCCS_Journal Input column shows the unrealised profit elimination from Hall 6. The FCCS_Managed Data column is the unmodified SAP extract. Total is the consolidated figure that appears in external reports.
Row axis typically holds Account dimension members — a defined range like all P&L accounts, or a specific sub-set such as ReclassificationAccounts. The form designer can restrict which accounts are visible and editable, hiding system accounts that should not receive manual input.
Column axis holds Period members (Jan, Feb, Mar, Q1) or Scenario members (Actual vs Budget in a comparison form). Columns can be set read-only for prior locked periods and editable only for the current open period.
Page axis holds the dimensions that define the form's fixed context — Entity, Scenario, Year. These do not scroll; they define what the entire form is about. A form with Entity on the page axis, scoped to DeutschWerk, shows only DeutschWerk data regardless of which user opens it. Dimension security then further restricts which users can even see that form.
Below is a mockup of the DeutschWerk Q1 Actual reclassification form as the controller sees it — page axis locked, Account on rows, Q1 on columns, with the freight reclassification already entered:
| Account | Jan | Feb | Q1 (editable) | YTD |
|---|---|---|---|---|
| Revenue | 480,000 | 510,000 | 15,000 | 1,455,000 |
| CostOfSales | (198,000) | (221,000) | (15,000) | (675,000) |
| OtherExpenses | (18,000) | (21,000) | — | (50,000) |
| FCCS_OperatingProfit | 264,000 | 268,000 | ✦ calc | 730,000 |
Smart Push is configured at the form level by the Service Administrator. When triggered, it takes the value entered at a parent entity and distributes it proportionally down to its child entities. Direction is always parent → children — never upward. A typical use case: the Group Finance Manager enters a Q2 group revenue target of $12m at the GlobalMerge level, triggers Smart Push, and FCCS distributes $4.5m to BritEdge, $3.6m to DeutschWerk, and so on based on the configured weighting. Smart Push writes to FCCS_Data Input on all child entities it touches.
Ad-Hoc Analysis is a free-form query builder. You connect to an FCCS application, place dimensions on rows and columns however you want, double-click any member to drill down one level, and use the Smart View toolbar to pivot, zoom in/out, and switch POV. The output is a live-connected Excel grid that refreshes from FCCS on demand. Ideal for period-end review, variance investigation, and unstructured exploration where you don't know in advance which accounts matter.
Function Grids use EPM functions — primarily HsGetValue(connection, POV_string) — embedded directly in Excel cells to retrieve specific FCCS data point values. The workbook layout is fixed by the designer; the data refreshes but the structure does not change. Used for structured management reporting packs and board templates where the CFO's preferred layout must be preserved exactly. HsGetValue requires an explicit POV string: HsGetValue("FCCS","S#Actual;Y#FY2025;P#Q1;E#DeutschWerk;A#Revenue;C1#USD;C2#FCCS_Contribution").
| Capability | Ad-Hoc Analysis | Function Grids (HsGetValue) |
|---|---|---|
| Layout | Flexible, drag dimensions freely | Fixed by designer, cannot be moved |
| Best for | Exploration, variance investigation, drill-through | Management packs, board templates, fixed reports |
| Refresh method | Smart View Refresh button | Standard Excel Refresh or HsRefreshAll |
| Drill-through | ✓ Right-click any cell | Limited — context-dependent |
| Submission | ✓ Submit Data writes to FCCS_Data Input | ✓ Submit Data writes to FCCS_Data Input |
| Learning curve | Low — intuitive drag-and-drop | Higher — requires EPM function syntax |
Below is a Smart View mockup showing the Group Finance Manager's ad-hoc session — DeutschWerk Q1 Actual P&L pulled at FCCS_Contribution, with FCCS_Inventory highlighted as the drill-through target:
| Account | Q1 Actual | Q1 Budget | Variance |
|---|---|---|---|
| Revenue | 1,455,000 | 1,500,000 | (45,000) |
| CostOfSales | (675,000) | (720,000) | 45,000 |
| OtherExpenses | (50,000) | (55,000) | 5,000 |
| FCCS_GrossProfit | 730,000 | 725,000 | 5,000 |
| FCCS_Inventory | 450,000 ↗ | 480,000 | (30,000) |
Right-clicking the FCCS_Inventory cell (marked ↗) and selecting Drill-Through reveals the three data source contributions: FCCS_Managed Data = $480,000 (SAP balance), FCCS_Journal Input = -$30,000 (the unrealised profit elimination Enterprise Journal from Hall 6, with the approver name and timestamp visible). FCCS_Data Input = $0 for this account. Total = $450,000. The Finance Manager can click through to the journal to see the full entry detail and the supporting BritEdge inventory schedule.
The DeutschWerk Controller opens Smart View and sets the POV bar to what they intend to be Actual / Q1 / FY2025 — but accidentally leaves the Scenario set to Budget from a prior session. They enter the €15,000 freight reclassification and click Submit Data.
FCCS accepts the submission without error. The data is written to FCCS_Data Input for DeutschWerk / Budget / Q1 / FY2025. The controller's intended Actual scenario is completely untouched. No warning is raised. No error log entry appears. The submission was syntactically valid — it just went to the wrong Scenario member.
The consequence: The Q1 Actual consolidation runs without the reclassification. Budget figures are corrupted by an unexpected adjustment. The controller cannot understand why their Actual figures don't reflect the change. The audit trail report shows the FCCS_Data Input lane is empty for Actual — but has an unexpected entry under Budget.
The exam tests whether you understand that FCCS will accept a submission to any valid Scenario member that the user has write access to — even if it is not the intended one. No error is raised. No warning appears. The only way to detect this is to check the Data Source audit trail report and verify which Scenario the FCCS_Data Input entry landed in.
The fix: always verify the full POV bar — every dimension — before any Smart View submission or Data Form save. A mismatched Scenario is the most common wrong-POV error because it is easy to carry over from a prior session.
A Data Form with Scenario on the page axis can present the same risk if the page axis selector is not locked by the form designer. Best practice: lock the Scenario and Year on the page axis in Data Forms used for close-cycle entry. The controller should not be able to accidentally navigate to Budget or Forecast when the form is intended for Actual data entry only.
When AsiaLink distributes a Q1 cash dividend and GlobalMerge receives SGD cash, two Cash Flow movements happen simultaneously: FCCS_ShareOfAssociateIncome in Operating Activities is reversed out as a non-cash deduction (the equity pickup is P&L income but not cash). FCCS_DividendsReceived in Investing Activities is a positive cash inflow — the actual SGD cash GlobalMerge received, translated to USD at the relevant rate. Net effect matches IAS 7: equity pickup disappears from Operating; real cash appears in Investing.
It is Day 4 of the GlobalMerge 5-day close. All four entities are Consolidated (status 2) for Actual Q1 FY2025. Three activities run in parallel: DeutschWerk Controller needs to post a manual reclassification; the Group Finance Manager is reviewing consolidated figures in Smart View; and the CFO has requested the Q1 board pack with entity-level burst outputs.
FCCS sandbox · Reports framework enabled · All four entities Consolidated (2) Actual Q1 FY2025 · DeutschWerk Controller: DeutschWerk-only Entity dimension security, Actual write + Budget read Scenario security · Group Finance Manager: all-entity access, all scenarios · Smart View connected to FCCS in Excel.
The DeutschWerk Controller identifies that €15,000 of freight costs were incorrectly classified as OtherExpenses in the SAP extract loaded on Day 1. The correct account is CostOfSales. This is too small to justify a full DI reload but must be corrected before consolidation sign-off. She opens the DeutschWerk Data Form.
- 01Navigate to Data Forms → DeutschWerk Q1 Actual form. Account on rows, Q1 Period on columns. Page axis is locked: Entity = DeutschWerk, Scenario = Actual, Year = FY2025. The controller sees only DeutschWerk rows — dimension security prevents any other entity appearing.
- 02Enter the reclassification. OtherExpenses row → Q1 column: enter
−15,000(reducing OtherExpenses). CostOfSales row → Q1 column: enter+15,000(increasing CostOfSales). The form's validation rule verifies the net change = 0 before allowing save. - 03Click Save & Submit. FCCS writes both entries to
FCCS_Data Inputfor DeutschWerk / Q1 / Actual. The SAP trial balance inFCCS_Managed Datais completely untouched. Both data sources now coexist for DeutschWerk. - 04Observe entity status change. Navigate to Consolidation → System Check. DeutschWerk flips from Consolidated (2) to Impacted (6). The form submission changed entity data — Consolidation must rerun. This is correct expected behaviour, not a problem.
- 05Rerun Consolidation for DeutschWerk. Action: Consolidate → Actual / Q1 / FY2025. After completion, status returns to Consolidated (2). The €15,000 reclassification flows through the consolidation engine (translation → proportion 80% → elimination → contribution) into the group P&L.
- 06DI reload test — confirm FCCS_Data Input is protected. The data team reruns the DeutschWerk data load rule in Replace mode with a minor correction to the SAP extract. After the reload completes, open the Data Source audit trail report. Confirm: FCCS_Managed Data updated to new values. FCCS_Data Input still shows the €15,000 reclassification — completely untouched by the Replace mode reload.
This protection is by design. In a real close cycle, the ERP may send multiple corrected trial balance files during the close window. FCCS_Data Input entries — whether from Data Forms or Smart View submissions — must survive all of them. The Finance Controller's reclassification is not an ERP-sourced adjustment; it is a human judgement that should not be overwritten by any automated data pipeline.
The Group Finance Manager has received an alert that DeutschWerk's Q1 FCCS_Inventory balance is lower than expected. She opens Smart View in Excel to investigate without leaving her spreadsheet environment.
- 01Connect Smart View to FCCS. In Excel → Smart View ribbon → Panel → Connect → select the GlobalMerge FCCS connection URL. Authenticate. The Smart View POV bar appears at the top of the worksheet.
- 02Set the POV bar — verify every dimension. Entity = DeutschWerk · Scenario = Actual (confirm — not Budget) · Year = FY2025 · Period = Q1 · Consolidation = FCCS_Contribution (not Entity Input) · Currency = USD. The wrong Scenario or wrong Consolidation member would give misleading results.
- 03Pull the ad-hoc P&L grid. Select Ad-Hoc Analysis. Place Account dimension on rows, Period on columns (Jan, Feb, Q1, YTD). Refresh. DeutschWerk's full P&L appears, translated to USD, with all eliminations applied. FCCS_Inventory shows $450,000 — lower than the $480,000 SAP balance she expected.
- 04Drill-through on FCCS_Inventory. Right-click the Q1 FCCS_Inventory cell → Drill-Through → Source Data. The drill-through view opens, showing the Data Source breakdown: FCCS_Managed Data = $480,000, FCCS_Data Input = $0, FCCS_Journal Input = −$30,000. Total = $450,000.
- 05Navigate to the journal entry. Click the FCCS_Journal Input row to expand the journal detail. The drill-through shows the Enterprise Journal from Hall 6 — journal reference, approver (Group Finance Manager), approval timestamp, and the attached BritEdge inventory schedule confirming the unrealised profit amount. The Finance Manager confirms this is the expected elimination and closes the investigation.
- 06Smart View read-only confirmation. Confirm no Submit Data action was triggered — the investigation was read-only throughout. The FCCS cube is unchanged. No entity status was affected.
If the Finance Manager had found an error and entered a correction value directly in a Smart View grid cell, clicking Submit Data would write the entry to FCCS_Data Input — identical to a Data Form entry. DeutschWerk would move from Consolidated (2) to Impacted (6). Consolidation must rerun. The submission would appear in the Data Source audit trail under FCCS_Data Input, alongside the Data Form reclassification from Exercise 1.
- 01Reports → Books → New Book. Name: GlobalMerge_Q1_BoardPack_FY2025. Add three reports in order: (1) Consolidated P&L Actual vs Budget · (2) Consolidated Balance Sheet · (3) Cash Flow Statement. Set Book-level POV: Entity = GlobalMerge, Consolidation = FCCS_Contribution, Q1, FY2025, Currency = USD.
- 02Generate as PDF and verify content. Confirm: DeutschWerk Revenue reflects the €15,000 Data Form reclassification. AsiaLink and NovaTech appear as single equity-pickup lines in the P&L. Cash Flow shows AsiaLink dividends under Investing Activities. The unrealised profit elimination appears in COGS.
- 03Configure the entity-level Bursting definition. Name: Q1_EntityPL_Burst_FY2025. Report: entity P&L template with parameterised Entity POV. Burst dimension: Entity. Members: BritEdge, DeutschWerk, AsiaLink, NovaTech. Map each member to the relevant controller's EPM inbox. Format: PDF.
- 04Run the Bursting job and verify security enforcement. After completion, check DeutschWerk Controller's inbox — confirm only the DeutschWerk PDF is present. BritEdge, AsiaLink, and NovaTech outputs were silently excluded by dimension security. Group Finance Manager's inbox contains all four entity outputs. No errors in the job log.
The exam reliably tests: Reports framework features vs FR Studio (sunset), Consolidation dimension POV traps, Bursting security, the three data source lanes (especially what Replace mode can and cannot clear), Smart View submission destination, the wrong Scenario POV silent failure, and Smart Push direction. The data source separation questions have appeared in multiple exam variants.
FCCS_Data Input. Data Integration Replace mode operates exclusively on FCCS_Managed Data. These are separate data source partitions. Replace mode has no access to and no effect on FCCS_Data Input. The manual reclassification is fully protected. Both data sources coexist after the reload and are both read by the consolidation engine when it next runs.FCCS_Data Input — the same partition as Data Form entries. Smart View retrieval is read-only by default; the Submit Data action explicitly triggers the write-back. Once submitted, the entry is protected from Replace-mode DI reloads, just like Data Form entries. Data Form entry and Smart View submission are the same data stream — both write to FCCS_Data Input.FCCS_Managed Data only. Both FCCS_Data Input (Data Forms and Smart View submissions) and FCCS_Journal Input (approved journals) are separate data source partitions that Replace mode cannot access or modify. All three data sources coexist after the reload — the consolidation engine reads all of them together at the next consolidation run.FCCS_Data Input rather than FCCS_Managed Data — meaning Replace mode reloads would not clear it. Bulk trial balance data belongs in FCCS_Managed Data via the proper Data Integration pipeline.