Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 44 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 278 Oracle Analytics and AI News
- 55 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
FDI vs. OAC: Time Zone in Workbooks Preview Feature
There is a new time zone feature that came out as an OAC preview feature in the November release. This feature allows the user to override the default time zone and shows timestamp data in their time zone instead of the default. Useful when you have data produced in GMT time and user in Eastern time.
This feature can be turned on in OAC Advanced Settings in the console, but in FDI the option is not available in System Settings for their November release. Nor is it a FDI Feature or as a SM Extension. There are preview features and time options available in FDI System Settings, so why not this one? The FDI OAC About references the same documentation as OAC and the docs don't exclude FDI.
Is there any reason why this is not available? Or is turn on elsewhere in FDI?
https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/time-zones-preview.html
Answers
-
The FDI OAC may not be at the same update level. Typically FDI features will be updated in the FDI "What's New" documentation.
I will move this to the FDI forum, since it is not an OAC question.1 -
@SteveF-Oracle Will this feature be added in OAS 2026 DV?
0 -
As per my experience, it is not necessary that if a feature is available in OAC, it will be available in FDI as well.
Reason is FDI must stay aligned with Fusion application semantics. Fusion Applications store and process timestamps in application-defined time zones. It already apply time zone logic consistently across:
- Transactions
- OTBI
- ESS jobs
- BICC extracts
If Oracle allowed per-user time zone overrides in FDI:
- Two users could see different dates for the same transaction
- KPIs like “Daily Revenue”, “Aging”, “Backlog” would no longer reconcile with Fusion UI
- Oracle Support would lose a single source of truth
It will break one of FDI’s main promises: analytics must reconcile with Fusion.
Hope it helps!
0 - Transactions





