Action needed : CX/HCM Customers in FAIDP: If you use Enterprise Calendar please read this

Krithika Raghavan-Oracle

If you use Enterprise Calendar in your reporting and have selected Gregorian Calendar

We request you to take specific, time-bound actions to ensure smooth and uninterrupted functioning of your FAIDP reports that depend on Enterprise Calendar. 
Please ignore this request if you do not use Enterprise Calendar (and have selected Gregorian Calendar) in your reporting. 

• Background

As part of ongoing enhancements to improve reporting performance and future-proof aggregate calculations, Oracle FAIDP will introduce a new data pipeline parameter in an upcoming release. The parameter identifies the fiscal calendar to be used as the Enterprise Calendar for your FAIDP instance. It is configured such that, when you upgrade to 26R2, it will default to your present Enterprise Calendar value selection in the Reporting Configuration UI.
However, pipeline parameters UI will not support Gregorian, so, if your current selection is the default Gregorian option, you need to switch this now.

If you are already using a fiscal calendar as your Enterprise Calendar, the reporting config setting should show a fiscal calendar selected, so no action is needed.

• What you need to do and Why

Reporting Config UI:

Select a fiscal calendar from the Enterprise Calendar drop down in your Reporting Configuration UI. The current 'Gregorian' option in your environment will not get transferred over with the 26R2 upgrade. If there is no fiscal calendar that aligns with Gregorian, then create a temp fiscal calendar that mimics Gregorian and pick that.

Custom Analyses/Reports (applicable only for HCM customers):

If you have built reports using Enterprise Calendar attributes, they need to be replaced with Gregorian attributes, i.e., sourcing from 'Time' dimension in subject areas.
Note that this is needed if your business requirement is to use Gregorian but for some reason you have used an Enterprise Calendar attribute.

• Timeline

We ask that you make this change at the earliest available opportunity, but not later than Mar 30, 2026

If you need assistance please reach out to your CoE team member or respond to this thread. We will have someone help you.

****

Frequently asked questions

My reporting config setting already points to a fiscal calendar for Enterprise. Do I need to do anything?

No, you don’t need to do anything now. 

After I make the suggested change, will my reports function as before? Is there any impact?

Your reports should show the same data/results as before because you are switching the reporting config to a fiscal calendar that follows Gregorian (Jan - Dec) .

How do I benefit from doing this?

You will benefit in the longer term in terms of improved report performance. This step will help FAIDP development to introduce design changes at the backend for reports using Enterprise Calendar to run faster.

What is the risk if I don’t take this action now?

All your reports that depend on Enterprise Calendar will show no data when your instance is upgraded to 26R2. 

Balachandra_Devadiga

ok. noted

Bhaskar Konar

This is very helpful for planning ahead of the 26R2 upgrade - especially the guidance around handling Gregorian vs. fiscal calendars.

Thanks for the detailed update and clear action steps @Krithika Raghavan-Oracle.

Tatenda Mukaro

This is awesome

User_T1TK5

@Krithika Raghavan-Oracle - The headline says "…attention CX/HCM Customers…". No impact to ERP customers?

Anitha Ramarao-Oracle

Yes, no impact to ERP customers as we already use fiscal year there. Please note in ERP this SA could have impact Projects (Time and Labor). So you need to take action if using this subject area

User_T1TK5

@Anitha Ramarao-Oracle - thanks for the clarification. just to further the understanding -

• if the customer is on ERP alone, then no impact and no changes.
• if the customer in CX and/or HCM then apply these suggested changes
• if the customer is on multiple pillars that include ERP plus HCM or CX, then apply the suggested changes

please confirm if these statements are correct.

Anitha Ramarao-Oracle

Please note the action is applicable only If you are using HCM / CX and "Projects(Time and Labour)" SA on ERP and meet the below criteria:
- you have selected "Gregorian" in Enterprise Calendar in Reporting Configuration and
- you are using Enterprise calendar in your reports

Precisely, we don't want anyone to be using Gregorian in Enterprise Calendar under report configuration