When migrating from Voyager to Alma, you may need to identify, review and resolve any duplicate (non-unique) Fund Codes in a single Fiscal Period. See the Voyager To Alma Migration Guide for additional help on how non-unique (and null) Fund Codes are migrated, or discuss this with your migration team.

This query, which you can run using Voyager Prepackaged Access Reports, can help you identify both null Fund Codes and duplicate Fund Codes.

SELECT FUND.FUND_ID,
   FUND.LEDGER_ID,
   FISCAL_PERIOD.FISCAL_PERIOD_NAME,
   LEDGER.LEDGER_NAME,
   FUND.FUND_NAME,
   FUND.FUND_CODE,
   FUND.ORIGINAL_ALLOCATION,
   FISCAL_PERIOD.START_DATE,
   FISCAL_PERIOD.END_DATE
FROM FISCAL_PERIOD
   INNER JOIN (LEDGER
   INNER JOIN FUND
   ON LEDGER.LEDGER_ID = FUND.LEDGER_ID)
   ON FISCAL_PERIOD.FISCAL_PERIOD_ID = LEDGER.FISCAL_YEAR_ID;

For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.

Posted as is. If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.