Data Reloads/Data Maintenance - ability to reload current financial year/current month only

Rob Toogood

My organisation requires a full reload of the GL functional area once a month on the last day of the month to ensure Analytics Currency (GBP) is present on all transactions. Some business users post GL Journals with future accounting dates to non-GBP Ledgers (EUR, USD, etc).

If you have an accounting date of 30/11/2025 and post that today, when this is picked up by FDI, the Analytics currency will populate as Null (due to no FX rate for the accounting date). As a result, a full reload of the GL on the last day of the month as part of the overnight refresh is the only way to ensure this value is populated.

As we went live with FDI and Oracle ERP 01/01/2025, this isn't a huge issue at present, it adds on approximately 1 hour to the daily refresh. However… the scope for requiring full reloads of functional area is growing as we now need to reload the Project Costing functional area as well as potentially Accounts Payable (adhoc) to account for any changes to invoice account for tax reasons - updating the Commodity Code/Product Category in AP.

When we get 2 or 3 years down the line, I imagine having to reload large data volumes will start to significantly impact the length of time this activity takes.

My idea - Would it be possible to reload data for only the current financial/fiscal year only or current quarter/current month? as prior years would be static and not subject to change. This would mean rather than reloading several years worth of data, you're only reloading up to 12 months of data (or 3 months/1 month if quarter/current month becomes available) - significantly improving reload time, processing power and general user experience.

asmith223258

This would be helpful for our company as well