Design Approach for Actual and Budget Consolidation Using FSK

Hi OS Community,

I’m an EPM Consultant working mainly on Financial Consolidation, and I would appreciate some guidance on a scenario‑specific consolidation design question.

Currently, our Actuals consolidation process is working correctly and uses the standard XFW_FSK_Accounts lookup table to drive account mapping during consolidation.
This includes full account‑level detail, which is required for statutory reporting and analysis.

Now we need to enable consolidation for the Budget scenario, the rules for Budget should be the same as Actual , but with a different level of granularity:

• The Budget scenario is loaded at a higher‑level Account hierarchy

Main Question

What is the recommended way to use a different account mapping lookup table for Budget while keeping the existing XFW_FSK_Accounts logic for Actuals?

More specifically:

• Can we assign or reference a different account lookup table (e.g. XFW_FSK_Accounts_Budget) within the consolidation Business Rules, based on the Scenario?
• Is it best practice to:
  • Use Scenario‑driven logic inside the consolidation BRs to switch lookup tables?
  • Or create separate consolidation rules for Actual vs Budget?
• Are there any framework‑supported patterns for handling multi‑scenario account mappings where hierarchies differ?

If anyone has implemented a similar approach or can point to best practices / documentation, your insights would be greatly appreciated.

Thanks in advance for your help!

Best regards,
Carolina