Scenario: consolidation is running slow. Instead of starting with a long manual checklist, the FCCS Consolidation Assistant can bring metric anomalies and application recommendations into one guided conversation, then help the administrator decide what can be resolved automatically and what still requires technical review.

1. What the Consolidation Assistant is designed to do

1

Diagnose performance

Bring metric anomalies and application recommendations into a guided investigation focused on consolidation performance.

2

Review system health

See findings, supporting evidence, and suggested next steps instead of reviewing individual diagnostics in isolation.

3

Act on supported findings

Use an Action ID for supported fixes. Findings without an Action ID remain manual administrator work.

Scope: The feature is built for Service Administrators. It helps direct the investigation, but the findings still require technical review before production changes are accepted.

2. GenAI inside FCCS — but be precise about “Agent”

Oracle classifies the built-in Consolidation Assistant shown here as a Generative AI capability. It supports diagnosis and guided actions directly inside FCCS.

Oracle also offers EPM Assistants for Fusion AI Agent Studio. Those are separate diagnostic agents with a different deployment path and should not be confused with the built-in Consolidation Assistant.

Important distinction: The documented setup for this built-in assistant starts with enabling Generative AI in FCCS; it is not the same deployment model as Fusion AI Agent Studio.

3. Prerequisites and setup

The source walkthrough lists three prerequisites: EPM Enterprise subscription, Hybrid mode, and Service Administrator access.

1

Enable Generative AI

Go to Application → Settings → Enable AI → Generative AI → Save.

2

Open Consolidation Assistant

Use a prompt or one of the available instruction templates.

3

Start with a simple question

For example: “consolidation is running slow”.

4

Refresh the evidence

Choose Yes when the assistant asks whether it should rescan for the latest recommendations.

FCCS Consolidation Assistant menu showing resolve, rollback, diagnose consolidation and system health diagnostic options
Example Consolidation Assistant menu from the supplied FCCS application screenshot.

4. Reading the diagnosis: one run can surface multiple findings

In the supplied application example, the assistant returns four findings. Two have Action IDs and two require manual follow-up.

FCCS Consolidation Assistant diagnosis results showing four findings and Action IDs R11 and R12
Supplied application example. Findings and Action IDs are environment-specific.
R11

Yearly Consolidation

Suggested for multi-period consolidation performance.

R12

Custom dimension optimization

Consolidation and Translation settings are identified for optimization.

Also flagged: a Restructure Cube job and findings in two calculation rules. In the example, only R11 and R12 have an Action ID.

5. Resolve and rollback: supported fixes stay under administrator control

For findings with an Action ID, the assistant can propose a supported action. The administrator reviews the proposed change and confirms whether to proceed.

Illustrative commands from the example
resolve R11 resolve R12  rollback R11

Resolve applies a supported action after administrator confirmation. Rollback reverses a resolution previously performed by the assistant. Always use the Action ID from the current diagnosis.

Control point: The commands above are illustrative. The supplied screenshots do not show execution, and the administrator should review the proposed action before confirming it.

6. No Action ID? Move to Recommendations for manual follow-up

The assistant does not automatically fix every performance finding. When there is no Action ID, the next step is to open the full recommendation, inspect the affected artifact, test the change, and compare results.

FCCS Applications Recommendations page with performance findings including insertion rules and Restructure Cube
Applications → Recommendations example used for deeper manual investigation.

The supplied example flags two insertion rules:

FCCS_20_Final Calculations_LocalCurrency
FCCS_10_After Opening Balance Carry Forward_LocalCurrency
Manual workflow: Open the full finding → inspect the rule → test the proposed change → compare consolidation time and financial results. A Restructure Cube job is also recommended in this example.

7. The EPMXpert approach: turn findings into tested improvements

  • Refresh the evidence.
    Run a rescan before reviewing the diagnosis so the assistant is working with the latest recommendations.
  • Understand the impact.
    Separate supported fixes with Action IDs from changes that still require manual analysis.
  • Validate the outcome.
    Compare consolidation time and financial results after the change. A recommendation alone does not prove a speed improvement.
Bottom line: The Consolidation Assistant can significantly shorten the path from “consolidation is slow” to a focused technical investigation. Its value is not that it removes administrator judgment — it organizes the evidence, identifies supported actions, and makes the next step clearer.

8. Oracle documentation referenced in the source walkthrough

  1. AI Features for FCCS
  2. Working with Consolidation Assistant
  3. Resolving Issues and Rollback
  4. Consolidation Assistant Examples
  5. EPM Assistants for FCCS
  6. EPM Assistants and AI Agent Studio

Source walkthrough states that the Oracle documentation was checked October 5, 2026. Findings, Action IDs, and recommendations are environment-specific.