EPM Assistants in Financial Consolidation and Close

Financial Consolidation and Close provides EPM assistants to perform administrative and operational tasks.

The assistants are available as importable agents that integrate with Fusion AI Studio, enabling a chat-based experience. They are exclusively available to Fusion customers and are not supported for EPM customers without Fusion Cloud subscriptions. For information about setting up EPM Assistants see How to Use EPM Assistants with AI Agent Studio in Getting Started Guide for Administrators.

EPM Assistants

  • Calculation Assistant to Create Configurable Consolidation Rules for Administrators

    Helps Service Administrators create Configurable Consolidation rules with rulesets, or add new rules to an existing ruleset. By providing a guided framework, the Calculation Agent Assistant reduces the complexity and time involved in setting up Configurable Consolidation rules.

  • Consolidation Performance Diagnostic Assistant for Administrators

    Service Administrators can run the diagnostic assistant to automatically identify deviations from standard configurations, proactively highlighting potential application corruptions or misconfigurations. It suggests actionable next steps based on consolidation job analytics.

The assistants are packaged as a downloadable ZIP file on the Downloads page. Extracting the ZIP file provides access to the following assistant definition files.

  • For Calculation Assistant to Create Configurable Consolidation Rules for Administrators:

    FCCS_CONFIG_CONSOL_RULE_AGENT.json

    For Consolidation Performance Diagnostic Assistant for Administrators:

  • FCCS_DIAGNOSIS_AGENT,json —This .json file needs to be imported under the Agent Teams section. It imports the Diagnosis Agent, which contains the agent configuration.

    FCCS_DIAGNOSIS_AGENT_APP.json —This .json file needs to be imported under the Apps section. It imports the interactive UI App that is used to access and interact with the Diagnosis Agent.

    Both files are required for the complete setup. The first file imports the agent itself, while the second file imports the user interface through which the agent can be used.