Sunday, 17 May 2026

Significance of Supplemental Data Manager – Additional Help for Finance Users

 Supplemental Data

Supplemental Data means accounting supplemental records. The detailed information utmost required for accounting but is outside the scope of typical accounting, like postings in general ledger, etc. Data sitting in these records is typically additional required information which helps management and analysts perform their jobs.


                            

Using the right systems for supplemental data collection and management can gain greater control and visibility into additional information, in comparison to using manual and spreadsheet-based financial processes.

Supplementary Information May Include:

• Accounting information

• Non-accounting information

Accounting Information

• An example of supplementary information is an expanded table containing the details for line items in the financials.

• Supplementary information system is valuable for any company, allowing them to provide important additional information—such as “roll forward” reports, debt roll forwards, fixed asset roll forwards, and equity roll forwards, which are necessary to support financial statements.

Non-Accounting Information

• An employee in charge of accounts receivable might keep a supplementary record with notes about customer demeanor, personality, and ability to pay future invoices. This extra information helps the employee perform their job by giving additional warnings about controls or customers which might need additional attention.

Methods to Collect Supplemental Data

There can be two methods to collect supplemental data. Supplemental data can be collected in single source system where master data is stored or in separate systems.

                                                    

Collection of Data in Single Source System

Supplemental data can be stored in single source system where master data is stored

For example: In any ERP system (e.g., PeopleSoft or JD Edwards, etc.) or any of Oracle EPM Cloud Close suites.

Oracle EPM Cloud Close suite (Financial Consolidation and Close Cloud services (FCCS), Account reconciliation Cloud services (ARCS) and Tax Reporting Cloud services (TRCS) supports Consolidated data as well Supplemental data into a single system.

Benefits of Collecting Supplemental Data in Single Source System like SDM of FCCS

● It provides greater flexibility for reporting purposes

● Cost effective solution

● Administrator needs to maintain a single system

● Improved performance

                


Collection of Data in Separate Systems

Supplemental data can be stored in a separate system than the master source system. It can be MS Excel/File system/Database tables, etc.

Impacts of Maintaining Data in Multiple Systems

1. Collecting data in multiple systems can impact reporting capabilities.
2. System administrator will have to maintain multiple different systems.
3. When the master source system does not support inbuilt supplemental data collection and system admin still have to store supplemental data into master system, the size of master system will increase which might impact performance.

            

Supplemental Data Manager: An Untapped Gem of Close Consolidation

Oracle EPM cloud close consolidation suite (FCCS, ARCS and TRCS) have an inbuilt supplemental data collection tool named “Supplemental Data Manager” (SDM).

EPM cloud close consolidation suite supports consolidation, account reconciliation, and tax reporting for controllership users. Not only this, using SDM functionality of Oracle Cloud, supplemental data can be stored in EPM.
Summary/aggregated data will be available in FCCS/ARCS/TRCS whereas additional/detailed supporting information will be stored in SDM.

Supplemental Data in Financial Consolidation and Close Cloud Services (FCCS)

Oracle Financial Consolidation and Close Cloud Service (FCCS) is a suite of:

                

Oracle Supplemental Data Manager (SDM) is a platform that can be used to centralize the collection of financial, textual, and other unstructured data. It helps organizations to streamline the supplemental data collection process and introduces visibility as well as efficiency into the process.

SDM Provides a Robust Ad Hoc Data Collection Process That Supports:

• Defining the data definition process and associated data forms for data collection
• Provides a complete security mechanism on data
• Supports the ability to create calculation formula and validation criteria
• Control and monitor the data collection workflow

Examples of Use of SDM
                                
                                


How to Enable Supplemental Data Manager in FCCS

To collect supplemental data within FCCS, supplemental data collection module needs to be enabled while creating FCCS application. As shown in below screenshot of “Enable Features” while creating FCCS application, FCCS provides below options –

                

1. Enable both “Consolidation” and “Supplemental Data Collection” option to store both consolidated and supplemental data
2. Enable “Consolidation” option to store consolidated data only
3. Enable “Supplemental Data Collection” option to store supplemental data only
Note – If an FCCS application has been created without enabling the SDM, it can be enabled later as well.

Collection of Supplemental Data in FCCS – Investment Details

An organization makes a couple of investments. For each investment, the company needs to store additional information as well. Detailed information of investments will be collected as supplemental data whereas Invested amount will be part of the company's Financial Statements.

FCCS the Game Changer
Based on requirements – FCCS will keep only the aggregated invested amount for financial statements, whereas other detailed information will be kept in S    DM.
Detailed Investment information to be collected can be divided into 4 different sections –
1. General Information
2. Investment Information
3. Investment Details
4. Investment Value

    


Steps to Set Up SDM in FCCS
Below are the eight steps to set up Supplemental Data Manager in FCCS.
  


Step 1 - Study Existing Process

Study the existing user input templates to:
● Identify all attributes/parameters for which data needs to be collected?
● Is there any need to create an additional dimension or attribute?
● Any validation logic required?
● Any calculation required?
● How SDM Input Form will be organized?
● User/Team details who will input data into SDM Forms?
● How to set up the Workflow process?
● Security setup details required?

Step 2 - Create the Additional Dimension/Attributes to Record Information

In addition to FCCS inbuilt dimensions, additional dimensions can be created to store supplemental information. Each Dimension can have further members under it. Metadata will be loaded for these members.
For example, In following screenshot “Account” is a FCCS seeded dimension, whereas “Moodys Ratings” is a custom dimension to store additional information.



Below two custom dimensions will be created to store investment details.
1. ‘Moodys Rating’
2. ‘SP Rating’
Following are the members and properties for each dimension.
    


Step 3 - Define the Data Set

• A data set consists of all attributes, required to record data.
• Under Data Set, new Attributes can be created.
• It consists of Attributes from dimensions (FCCS seeded dimension or custom dimension) and Attributes created in the data set.

            

• Once the Data Set has been defined, it will be used to create SDM Forms.

As shown in below screenshot – add all Attributes under the “Investment Details”.



Step 4 - Create Form Template

Form Template is created based on ‘Data Set’ and is a reusable component. To Create a Form Template:
• Define the layout of user input forms.
• Define mapping between FCCS and SDM and using that data will flow from SDM to FCCS.
• Define instructions to be followed by the user while entering data.
• Define the Workflow process.
• Define the security setup.
• Define the Users/Team who will be responsible to input data in SDM form for specific Entity.

Create New Section under Form Template

As per requirement, there will be four sections to collect Investment details:
Under each section, there are three tabs:
1. Columns
2. Group By
3. Mapping

Columns Tab
Choose the attributes which need to be added under the ‘Investment detail’ section from “Data Set” “Investment Details”.

• Select the checkbox “Included” for all items required in “Investment Value” section out of the entire Attributes of Data Set “Investment Details”.
• Select the checkbox “View only” if any column needs to be marked as view only.
• For all columns where ‘Data Type’ is Number, you can define the ‘Total Validation POV’.
• For example - If aggregated investment amount is available in FCCS and using SDM, detailed information is getting submitted, SDM Data can be validated against the data stored in FCCS.
• A mapping needs to be defined between FCCS and SDM members for ‘Total Validation POV’.



Group By Tab

● In “Group By” page – it will show only those columns which were selected as “Included” in “Column tab”.
● Select the “Included” check box for which data needs to be sent to FCCS.
● Select the “Group By” check box against which data needs to be aggregated in SDM and sent to FCCS.
● Select the “Included” check box for which data needs to be sent to FCCS.
● Select the “Group By” check box against which data needs to be aggregated in SDM and sent to FCCS.
For example – In screenshot – SDM will aggregate data against “Investment ID” for “Current Value”, “Book value”, “Unrealized Loss”, “Market Value” and “Fair Value” columns and send from SDM to FCCS.    

    


Mapping Tab
In Mapping Tab, mapping between SDM and FCCS is defined.

To define mapping, click on POV - it will open a new window to select the specific member from each FCCS dimension.
    

As shown in the above screenshot - we can see the specific member from FCCS dimension.
As a result of this mapping - Value of “Book Value” entered by user will map to, “Investment Details” account of FCCS.

Click OK.

Click on “Save Button” to complete all tasks related to Section Tab and return to “Form Template”.
Once Section has been defined, the next import task under ‘Form Template’ is to define the workflow process for SDM forms. Go to the ‘Workflow’ tab.

Workflow Tab

Define the workflow process of SDM input form. Below are different available options.

    
● There can be multiple approval levels.
● Once, SDM form will be in Posted status – Data will be moved from SDM to FCCS.
● Based on the selected workflow option, preparer, approver, and integrator need to be defined.
● Post deployment of template, preparer, approver, and integrator who has been defined in Workflow, will be able to perform specific tasks in SDM Input form for Entities that has been defined in Workflow.

Step 5 - Open the Period for Data Collection
To start supplemental data collection process:
• Make sure the period is open for the month in which data is to be loaded.

Step 6 - Deployment the Form Template
Once the form template has been created, the next step is to deploy the template.

Step 7 - Data Submission to Input for Using workflow
Once SDM forms have been deployed, it will undergo the workflow process.
It will have three stages below:
1. Preparer
2. Approver
3. Integrator

Preparer Related Task

Once the SDM form has been assigned to the preparer, the preparer needs to enter the data and submit data to approver for approval.
For our example, there are four different tabs under “Investment details” where the preparer needs to enter data.



Enter the details and click the ‘Save’ button. Similar to this, the preparer need to enter details in all four forms.
Once all data has been entered into four different forms, the preparer needs to “Submit” control from “Preparer” to “Approver” stage.

Approver Related Task
• Once the preparer will submit the data, control will move to “Approver”.
• Approver has the option to “Approve” or “Reject” this data.
• On Rejection – control will go back to the preparer.
• On Approval – control will move to next level (i.e., Integrator).
• Once approver clicks the ‘Approve’ button, control will move to the integrator.

Integrator Related Task
• Once control moves to the integrator, the integrator can post or reject it.
• Once it has been posted, data will be moved from SDM to FCCS.

Viewing Data in FCCS
• As “Book Value” was mapped with the “Investment details” member in FCCS.
At the below member combination, data can be seen in FCCS.
• SDM data will be loaded on the “Supplemental Data” member from the “Data Source” dimension in FCCS.


Drill through from FCCS to SDM

• FCCS will hold summary data and detail data will be available in SDM.
• To see detailed data from FCCS, the drill-through option can be used.
• It is supported via Smart View and FCCS Web Forms.
• In Web Form - right click on the data cell for account “Investment Details”-> ‘C_101” and select Drill Through.
• On the next window, all four input forms will appear.


The screen of SDM below will appear where we can see all four input forms.


Step 8 - Close the Data Collection Period
Once Supplemental data has been posted, close the data collection period.
Powerful SDM Features Provided by FCCS
With the implementation of FCCS, any organization can have a centralized system to store financial data as well as the supplemental data.

Supplemental Data Manager Security
SDM provides a robust security model. While defining the SDM “Form template”, Admin needs to set up the SDM workflow.


Admin needs to define who will be the preparer, approver, and integrator for each entity for which SDM data need to be loaded.

Post deployment of Template – Only preparer, approver, and integrator who has been defined in Workflow will be able to perform specific tasks in SDM Input form for that particular Entity.

SDM allows users to define Teams instead of individual preparer, approver, and integrator. Teams specifically for supplemental data, for example, for working on supplemental data forms
can be created. You can then determine which users or teams can claim a form, and from Access, you can assign teams for workflow stages.

Based on assigned access – multiple users can enter data to their respective assigned SDM Input form at same time.

For SDM Input form – only specific users who have given access “Form Template” under “Access Tab” can view the data.

Based on dimension level security defined in FCCS, users will be able to see data for specific members in FCCS.

Data Flow from Supplemental Data Manager to FCCS
Once data has been approved and posted by the integrator, data will be moved from SDM to FCCS application.
At below combinations, data will be available in FCCS:
● “Supplemental Data” member from “Data Source” dimension
● Year, period, scenario, and entity will be picked from SDM input form.
● For other dimensions, data will be available on member-defined in the mapping session.

Data will be available on the same combination which has been defined under the “Mapping” section. For example, as per the screenshot below, data will be available on “Investment Details” Account.



Supplemental Data Management Dashboard

FCCS provides inbuilt Dashboard to monitor the progress on SDM input forms. You can monitor the business process and supplemental data information using below types of dashboards.
1. Task
2. Compliance
3. Financial dashboards


Benefit of Supplemental Data Management

A Single Interface
Both consolidated and supplemental data can be stored from a single interface of Oracle EPM Financial Consolidation and Close services (FCCS).

Flexible Reporting Capabilities
As both consolidated data and supplemental data is available at the same interface, it provides great flexibility to report both types of data.
Summary/aggregated data will be available in FCCS whereas additional/detailed supporting information will be stored in SDM.
FCCS allows drill through from FCCS to SDM to see detail-level information.

Cost Effective Solution
Storing both consolidated data and supplemental data into a single interface is a cost effective solution for any organization. Administrator needs to maintain a single system. FCCS supports SaaS architecture.

Improved Performance
Instead of maintaining information in multiple sources for consolidated data and supplemental data, having a single source reduced the end to end consolidation cycle time and improved performance.
Security
FCCS/SDM provides a robust security model. For the SDM input form, only specific users who have been assigned any task (preparer, approver, and integrator) or given access “Form Template” under “Access Tab” can view the data.
Based on dimension level security defined in FCCS, users will be able to see data for specific members in FCCS.

Easy User Interface
FCCS provides great flexibility to load supplementary data into SDM input form. Users can use Smart View (Excel), load data file (.CSV format), and use a web interface.
FCCS provides different types of Dashboards to see the status of SDM input forms.

SDM Workflow
Using workflow, it can easily track the status of any task. The administrator or power user sends email alerts to assigned users for their related data forms.

Thank you!

Oracle EPM FCCS: Financial Task Manager

Problem Statement


Manual tracking of the close process, using excel and e-mails is one of the reasons companies still experience issues in their close process from an accuracy, transparency, complexity and comprehensiveness perspective.

By standardizing and embedding controls in period-end close processes, organizations can eliminate labor-intensive, non-value adding activities and streamline decentralized and disjointed workflows that lengthen cycle times, increase the risk of control failure, and threaten the integrity of financial statements.

However, you don’t need to spend countless hours on how to close the books in Real time! 

This article will guide you through how Financial Task Manager is a pathway to Streamline and Accelerate Your Close Operations and best practices you need for a successful journey to EPM Closing and Reporting.

What is Financial Close Cycle


Financial Close Cycle indicates the number of business days required to close the books of accounts and submit finalized financial reports to the management and regulatory authorities at the end of the accounting period. It can be monthly/quarterly/yearly from the time that financial data gathering begins, until management and any regulatory authorities receive finalized financial reports.


Close challenges 


  • Inconsistent closing calendar and checklist 

  • Lack of quality data from upstream processes or ineffective data aggregation activities

  • Lack of automated close processes (e.g., high level of manual journal entries) 

  • Ineffective procedures for validating results 

  • Lack of timely hard close of periods and ability to post transactions after reporting package submission

  • Intercompany accounting – manual adjustments


Organizations are finding it difficult to track:

  • The current status of close

  • Number of open tasks?

  • Where is it stuck?

  • Is there any issue in closing the task? 

  • Who all are assigned to close tasks?

  • Is the predecessor/successor tasks followed?

  • Is any assigned employee on Leave?

  • Do they need some backup for assigned employee?

  • There is no workflow to monitor?

  • Approval mechanism in place?

  • Looking for email notification for current status?

  • Availability of backups?

Task Manager

Oracle Financial Task Manager module of FCCS is built for centralized, web-based management of period-end close activities across the extended financial close cycle.

It helps to manage all financial close cycle tasks, including ledger and sub ledger close, data loading and mapping, financial consolidation, account reconciliation, tax/treasury and internal and external reporting processes.

This includes:

  • Close Manager Components (Setup Calendar, Security, Periods, Years, Custom Attributes, Alert Types, Integrations)

  • Define Tasks for a Close Process - setup Task Types

  • Define Dashboard Views (Calendar, Task List, Gantt Chart)

  • Create / Update Templates (and validate) with repeatable close tasks

  • Setup / Update Schedule by pulling from a template

  • Workflow process


Thank you!

Created by Mohit Jain & Megha Gupta

Oracle Financial Consolidation and Close (FCCS): Transformation from a "consolidation tool" to building an AI-first "Intelligent Close" ecosystem

 Oracle Financial Consolidation and Close (FCCS) has undergone a significant transformation heading into 2026. Oracle has pivoted from simply providing a "consolidation tool" to building an AI-first "Intelligent Close" ecosystem.

Here is a breakdown of the most critical updates and shifts we need to know.

1. The Rise of the AI "Record-to-Report" Advisor

The biggest headline for 2026 is the introduction of the Record-to-Report (R2R) Assurance Advisor. This is a generative AI agent specifically designed for the consolidation process.

  • Anomaly Detection: Instead of waiting for the trial balance to fail, the AI flags exceptions (like unusual intercompany mismatches or account fluctuations) in real-time.

  • Insight Summaries: In the latest updates, IPM (Intelligent Performance Management) Insights now use GenAI to write narrative summaries of your financial results, explaining why a variance occurred rather than just stating it exists.

2. The "2.0" Standard: Sunsetting Legacy UI

Oracle has officially drawn a line in the sand regarding the user interface. As of the late 2025 and early 2026 updates:

  • Forms & Dashboards 2.0: These are now the mandatory default. They offer significantly faster rendering times and a more modern "Redwood" look.

  • De-support of Infolets: The old "Infolet" dots on the home page are being phased out in favor of the more robust Dashboard 2.0 and Infolet-style components within the new framework.

  • Legacy List Pages: The old "flat" navigation lists are gone, replaced by standardized artifact pages that make searching and filtering for forms or rules much more intuitive.

3. Advanced Governance & Security

Security updates in the 26A and 26B release cycles have focused on zero-trust architecture:

  • Cell-Level Security: FCCS now supports granular cell-level security via EPM Automate. This allows admins to restrict access to specific data intersections (e.g., "User A can see Salary data for UK, but not for the US") more easily than the old valid intersection rules.

  • OAuth 2.0 Default: Oracle is aggressively pushing users away from "Basic Auth" (username/password) for integrations. EPM Automate and REST APIs now strongly prioritize OAuth 2.0 for better security handshakes between systems.

  • Idle Timeout Changes: The default idle session timeout has been reduced (from 75 minutes down to 30 minutes) to comply with modern global security standards.

4. Integration & Performance Boosts

  • ERP to EPM "Seamless Flow": New architecture patterns for 2026 allow for direct data extraction from Oracle Fusion Cloud ERP into FCCS with minimal transformation logic. This "direct-drill" capability means you can look at a consolidated number in FCCS and drill all the way back to the sub-ledger invoice in the ERP.

  • Essbase 21c Under the Hood: Most environments have been migrated to the newer Essbase engine, which significantly improves the speed of complex "Consolidation with Logic" rules.

  • Java 17 Migration: EPM Automate has moved to Java 17, which provides better performance and stability for those running heavy local automation scripts.

Key Takeaway for Finance Teams

The "2026 version" of FCCS is less about manual data entry and more about exception management. Oracle’s goal is to reach a "Continuous Close" state where the system consolidates data as it arrives, and the human team only steps in when the AI Advisor flags a discrepancy.

Pro Tip: If your application is still using "Dashboard 1.0" or "Forms 1.0," your priority for this quarter should be a UI migration to avoid functionality breaks during the upcoming monthly updates.

Thank you!

Saturday, 9 August 2025

Introducing Business Script Language (BSL) in HFM 11.2.22: A Native Alternative to VBScript

In one of prior blog, we talked about that Microsoft’s plan to deprecate the VB scripting language and how VBScript will be retired and eliminated from future versions of Windows.

Hyperion Financial Management uses Microsoft VB Script as a scripting language for writing business logic against any application created on Financial Management System. In response to Microsoft’s deprecation of VBScript, HFM is introducing a native scripting language called as Financial Management Business Script Language (BSL) to maintain continuity.

What is BSL?

Business Script Language (BSL) uses the same syntax as VBScript, supporting most built-in VBScript functions and several key objects within a defined scope. It serves as the scripting language for writing business logic in any application built on the Financial Management System.

Here –

  • Starting with 11.2.22 release, Financial Management includes the Native Script Engine as an option to use. The default engine is still Microsoft VB Script Engine.
  • Business Script Language (BSL) is same as Microsoft VB Script language within the defined scope.
  • Starting with 11.2.22 release, user have option to switch between the VBScript engine and the new Native Script Engine.

To switch between script engines:

Parameter - ScriptEngineType:

  • 0 - Native Engine
  • 1 - Microsoft Engine (Default)

Verify if the ScriptEngineType parameter is present on the Settings page. If the parameter is missing, you must add it by executing the appropriate SQL scripts on the corresponding database.

Oracle Database

INSERT INTO XFM_PARAMETERS_DEFAULTS (Name,Type,Hidden,Validation,Description,DefaultValue) VALUES ('ScriptEngineType','1','0','','Set Native or Microsoft Script Engine','1');

INSERT INTO XFM_PARAMETERS (ParameterName, ClusterName, ServerName, ApplicationName, CategoryName, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, Value) SELECT Name, 'ALL','ALL','ALL','ALL', SYSDATE, SYSDATE, 'system', 'system', DefaultValue FROM XFM_PARAMETERS_DEFAULTS WHERE NOT EXISTS ( SELECT * FROM XFM_PARAMETERS WHERE Name = ParameterName );

SQL Server Database

INSERT INTO XFM_PARAMETERS_DEFAULTS (Name,Type,Hidden,Validation,Description,DefaultValue) VALUES ('ScriptEngineType','1','0','','Set Native or Microsoft Script Engine','1');

INSERT INTO XFM_PARAMETERS (ParameterName, ClusterName, ServerName, ApplicationName, CategoryName, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, Value) SELECT Name, 'ALL','ALL','ALL','ALL', GETDATE(), GETDATE(), 'system', 'system', DefaultValue from XFM_PARAMETERS_DEFAULTS  WHERE NOT EXISTS ( SELECT * FROM XFM_PARAMETERS WHERE Name = ParameterName );

Note

  • Ensure that no ofmserver.exe processes are running before switching the script engine.
  • After switching, launch the HFM application to proceed.
Thank you!
Created on Aug 10, 2025

Saturday, 2 August 2025

Data Integration Pipeline Extended to Account Reconciliation

From Aug 2025 monthly patch release, the Pipeline in Data Integration is now available to Account Reconciliation environments.  The Pipeline is used to orchestrate a series of routine tasks within Cloud EPM Platform as a single process.

Below is the sample example of Pipeline in ARCS where we are performing below tasks - 
  • Open the Period
  • Load Rate
  • Import Pre-mapped Balance
  • Create Reconciliation
  • Close period

Below are the sample screen shots while creating job in pipeline -



New Pipeline job types specific to Account Reconciliation include:

  • Create Reconciliation: (Reconciliation Compliance) Copies all selected profiles to a period and return success or failure status.
  • Generate Report for Account Reconciliation: Generates either a single predefined Reconciliation Compliance report, predefined Transaction Matching report or a custom report.
  • Import Attribute Values: Imports attribute values into an existing list attribute or group attribute. In Transaction Matching, only group attributes can be imported.
  • Import Balances: (Reconciliation Compliance) Imports balances data using Data Integration from a previously created integration definition and returns a success or failure status.
  • Import Pre-Mapped Balances: (Reconciliation Compliance) Imports pre-mapped balances and returns the success or failure status.
  • Import Pre-Mapped Transactions: (Transaction Matching) Imports a file of pre-mapped transactions into Transaction Matching and returns the success or failure status.
  • Import Rates: (Reconciliation Compliance) Imports rates for a particular period and rate type, and returns the success or failure status.
  • Run Auto Match: (Transaction Matching) Runs the auto match process in Transaction Matching.
  • Run Auto Alert: (Transaction Matching) Runs the auto alert process for the specified match type in Transaction Matching. This job processes the alert rules defined for the match type and then automatically creates alerts for unmatched transactions. Status of an Auto Alert job can be monitored through the Job History tab in Account Reconciliation.
  • Set Period Status:  (Reconciliation Compliance) Changes the status of a period (open, closed, pending, locked) and returns the success or failure status. 

Applied to: ARCS

Business Benefit

The Pipeline functionality allows users to conduct a sequence of Account Reconciliation focused operations such as importing balances, pre-mapped balances and transactions, rates and so on, streamlined in one location and executed then in serial or parallel mode.

Updated on: Aug 02, 2025

New consolidation setting for Translation Rules to skip the Translation in FCCS

Consolidation Setting for Translation Rules

In Aug 2025 monthly release for FCCS, a new Consolidation Setting called Skip Translation Rules if Entity Currency Equals Parent Currency is now available for multiple-currency applications. When you enable this setting, the translation-based configurable calculation (insertion) rules are skipped during the translation process for those Entities whose Base Currency property matches their Parent’s Base Currency property. The rules include:

  • FCCS_25_Before Foreign Exchange (FX) Calculations
  • FCCS_30_After Opening Balance Carry Forward
  • FCCS_40_Final_Calculations

By default, the Consolidation Setting is not enabled.

To manage consolidation settings:

  1. On the Home page, click Application, then Consolidation Settings.
  2. From the Setting Type dropdown, select the type of setting as Consolidation/Translation.



  1. To enable or disable the setting (Skip Translation Rules if Entity Currency Equals Parent Currency), use the slider icon Slider button next to the setting.
  2. To save the setting selection, click Save. When you receive the saved confirmation message, click Close.
Applied to: FCCS

Business Benefit: 

This consolidation setting enables you to decide whether to skip these calculation rules, which improves overall Consolidation performance, in addition to making the translation process more efficient.

Updated on: Aug 2, 2025 

Sunday, 29 June 2025

Future of Infolets: Plan to Discontinue Support for Infolets

Plan to Discontinue Support for Infolets

About Infolets

Infolets enable users to view and interact with high-level, essential information generated from different sources so that they can quickly assess where to direct their attention. Service Administrators create, redesign, delete, and assign permissions to infolets.

An infolet is a self-contained, interactive box-shaped container used to display information using text and charts. Infolets are interactive and use progressive disclosure to display high-level, aggregated, essential information for quick consumption at a glance, and then can be acted upon as needed. Infolets can be flipped and resized to display up to three charts or sets of values.



Future of Infolets

Starting with the October 2025 (25.10) update, Oracle will no longer support the following infolet actions:

  • Creation of new infolets
  • Copy As, which duplicates an existing infolet
  • Designating an infolet as Default and defining infolet dots on the Home page

This change applicable to Enterprise Profitability and Cost Management, FCCS, FreeForm, Planning, and TRCS.

Thank you!


Sunday, 15 June 2025

Latest Features introduced in 25.06 release of EPM Cloud

Below are the important changes in EPM Cloud release 25.06 -

Reports Changes

1. New Grid-Level Property for the Use Database Suppression Option

 The grid-level property now allows row suppression at the Oracle Essbase level. This option applies row suppression at the Oracle Essbase level instead of at the business process level, which reduces the amount of data on the business process side and eliminates the impact on query thresholds. Previously, this property was only available at the business process level in forms.

 Applies to

  • Enterprise Profitability and Cost Management
  • Financial Consolidation and Close
  • FreeForm and Planning
  • Tax Reporting

Business Benefit

This option reduces the amount of data processed at the business process level and helps eliminate impacts on query thresholds.

FCCS Changes

1. Label Change for Data Source Currency Attribute

The label of the Data Source Currency Attribute option has been changed from Entity Currency to Default Currency

The label change is displayed while selecting the attribute in the Dimension Editor, and in existing applications in which an Entity Currency Data Source member has already been created.

As shown in below screen shots from Data Source Dimension in FCCS-


If we edit the member properties of member "FCCS_Managed Data" and look for "Attribute Values", Label for "Source Currency type" property has been changed from "Entity Currency" to "Default Currency" -


 Applies to

  • Financial Consolidation and Close

Business Benefit: 

The Default Currency label more accurately reflects the currency based on the Data Source members available for use. For example, Parent Currency is the Default Currency for Parent Input.

Forms and Dashboards

1.New Standardized Artifact Page Option: Hide Empty Folders

Hide Empty Folders (available only for DashboardsDocumentsInfolets, and Data standardized artifact pages), hides folders that don't contain relevant artifacts for the current context.

Applies to: 

  • Enterprise Profitability and Cost Management
  • Financial Consolidation and Close
  • FreeForm and Planning
  • Tax Reporting

When the Hide Empty Folders toggle is off, all folders are visible in the list region of the artifact page, including empty ones. When the toggle is on, only folders containing relevant artifacts for the specific artifact page are displayed.

Standardized Interface Dashboards Page with Hide Empty Folders Option

By default, the Hide Empty Folders toggle is off, and will reset to off each time you start a new session. The state of the toggle is retained by the page during the session and is page specific. Navigating away from the page and returning preserves the toggle state until the tab is closed or the user logs out.

To view and use the Hide Empty Folders option, open one of the following standardized artifact pages in your business process:

  • Dashboards
  • Data
  • Infolets
  • Documents

Business Benefit: This feature enhances usability by allowing users to hide folders that do not contain relevant artifacts for the current context.

Account Reconciliation

1.Editing Comments Added to Reconciliations

Users can edit comments that they added if an Administrator has allowed this in the Allow Comment Editing and Deleting configuration setting. 

To edit comments in a reconciliation:

  1. From Home, select Reconciliations, then open the reconciliation you want to comment on.
  2. Click the Comments drawer.
  3. Click the action to the right of the comment that you want to delete and then select Edit.

Note that the Delete option is disabled if you don’t have the permissions required to delete the comment.

How to enable setting to edit or delete comments -

For users to be able to edit or delete their own comments, an Administrator must have allowed this in the Allow Comment Delete configuration setting under Application > Configuration > System Settings. A user who is a Preparer or Reviewer can still delete their own comments as long as the reconciliation is open and they continue to have access to the reconciliation.

The following table describes the tasks you can perform based on the status of the reconciliation and current user role:

RoleStatus: Open with PreparerStatus: Open with ReviewerStatus: Closed
Preparer

Can add comments

Can delete comments added by them or by other Preparers

Can edit comments added by them

Can add comments

Can edit or delete comments added by them

Can add comments
Reviewer

Can add comments

Can edit or delete comments added by them

Can add comments

Can edit or delete comments added by them or by other Reviewers

Can add comments
Commentator

Can add comments

Can edit or delete comments added by them

Can add comments

Can edit or delete comments added by them

Can add comments
Administrator

Can add comments

Can edit or delete any comment

Can add comments

Can edit ot delete any comment

Can add comments
Power User

Can add comments

Can delete any comment

Can add comments

Can edit or delete any comment

Can add comments
ViewerCan view commentsCan view commentsCan view comments

Business Benefit: This feature enhances the usability of reconciliation comments.

Significance of Supplemental Data Manager – Additional Help for Finance Users

 Supplemental Data “ Supplemental Data ” means accounting supplemental records. The detailed information utmost required for accounting but...