When migrating from Voyager to Alma, you may want to cleanup bad item prices. Due to operator error there are instances where the item price is obviously wrong (for example, way too high).
Note that in Voyager that for item records that contain a value other than zero, that explicit value is used as a lost item replacement fee and not the replacement cost value set in SYSADMIN for the item type. That is why these data are important and will be a part of the questionnaire during Alma migration.
This query, which can be run using Voyager Prepackaged Access Reports, will list item price fields with any value other than zero, and display them sorted from highest to lowest price. It includes ITEM_ID, ITEM_BARCODE, and more.
SELECT ITEM.ITEM_ID, ITEM_BARCODE.ITEM_BARCODE, ITEM_TYPE.ITEM_TYPE_NAME,
BIB_TEXT.TITLE_BRIEF, LOCATION.LOCATION_NAME, MFHD_MASTER.DISPLAY_CALL_NO,
MFHD_ITEM.ITEM_ENUM, ITEM.COPY_NUMBER, CCur([PRICE]/100) AS PriceInDollars
FROM ((((((ITEM LEFT JOIN ITEM_BARCODE ON ITEM.ITEM_ID = ITEM_BARCODE.ITEM_ID)
INNER JOIN LOCATION ON ITEM.PERM_LOCATION = LOCATION.LOCATION_ID)
INNER JOIN BIB_ITEM ON ITEM.ITEM_ID = BIB_ITEM.ITEM_ID)
INNER JOIN BIB_TEXT ON BIB_ITEM.BIB_ID = BIB_TEXT.BIB_ID)
INNER JOIN MFHD_ITEM ON ITEM.ITEM_ID = MFHD_ITEM.ITEM_ID)
INNER JOIN MFHD_MASTER ON MFHD_ITEM.MFHD_ID = MFHD_MASTER.MFHD_ID)
INNER JOIN ITEM_TYPE ON ITEM.ITEM_TYPE_ID = ITEM_TYPE.ITEM_TYPE_ID
ORDER BY Len([PRICE]) DESC , ITEM.PRICE DESC;
For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.
If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.