Record of fiscal Periods missed on Produccion

[Daiana Botta]

I generated fiscal periods for the years 2025 and 2026. I saved them in an update set and successfully commited them to production. However, the records don't appear in the table. Why could this have happened? Is it better to do this manually in production? Thanks! 🙂

[Shashank_Jain · Accepted solution]

@Daiana Botta ,

• Fiscal periods are data records, not configurations.

• Update Sets only track configuration changes (dictionary, UI, scripts, etc.), not transactional/data records.

• So when you generated fiscal periods in dev, those records weren’t actually stored in the update set—even though the generator logic was.

• That’s why after committing, nothing shows up in production.

How to Properly Move Fiscal Periods

There are two recommended approaches:

Option A – Generate directly in Production (Best Practice)

• Run the Generate Fiscal Periods job in Production.

• This ensures clean, environment-specific data.

• Fiscal calendars are usually unique to each environment and are considered foundation data.

Option B – Use Data Management Tools
If you must move them between environments:

• Use Import Sets / Export XML (right-click record → Export → XML, then Import in prod).

Hope it helps!

[jameswoodfo]

Could you provide more specific information on where the fiscal periods are not showing? For example:

• Do you not see a list of fiscal periods?
• Can you not see fiscal periods on cost plans?
• When creating a portfolio plan in Strategic Planning Workspace, can you not use fiscal periods?

That said, I have definitely moved fiscal periods by adding them to an update set. However, you have to careful and put related information as well in that update set.