When migrating from Voyager to Alma, you may need to identify, review and resolve any duplicate vendor codes. In Alma, vendor codes must be unique.  For more information discuss this with your migration team.

Additional Information: Existing Voyager vendor data will be migrated once, during the initial test load. To load successfully, vendor codes and names need to be unique. Libraries might also consider making vendor names and codes unambiguous.

This query, which you can run using Voyager Prepackaged Access Reports, will identify duplicate vendor codes.

SELECT VENDOR.VENDOR_CODE, Count(VENDOR.VENDOR_ID) AS CountOfVENDOR_ID
FROM VENDOR
WHERE (((VENDOR.VENDOR_CODE) Is Not Null))
GROUP BY VENDOR.VENDOR_CODE
HAVING (((Count(VENDOR.VENDOR_ID))>1));

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.