Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Circjob 30 stops if accrued fine for patron in policy with due date prior to calendar start

    • Article Type: General
    • Product: Voyager
    • Product Version: 9

    Problem Symptoms:
    * Circjob 30 stops running if attempt to add overdue fine for item in policy where due date precedes calendar start date
    * /m1/voyager/xxxdb/rpt/circjob.log show message:
    Function AddOverdueFine failed.

    Item Barcode: {item_barcode} (id: {item_id})
    Patron Barcode: {patron_barcode} (id: {patron_id})
    Location Code: {circ happening location_code} (id: {location_id})

    Cause:
    This behavior is the result of VYG-6316

    Resolution:
    Issue VYG-6316 is resolved for Voyager 9.1.1 and higher.

    Additional Information

    Replication steps:
    1. In Circulation > Charge, charge an item to a patron and give due date in past.
    2. In System Administration > Circulation > Calendar > Set calendar for policy of circulation happening location to start after due date in step 1.
    3. Connect to server via SSH as user voyager.
    4. /m1/voyager/xxxdb/sbin/Pcircjob -j30
    5. Note that fine accrual job fails with message:
    Function AddOverdueFine failed.

    Item Barcode: {item_barcode} (id: {item_id})
    Patron Barcode: {patron_barcode} (id: {patron_id})
    Location Code: {circ happening location_code} (id: {location_id})

    Workaround:
    1. System Administration > Circulation > Calendars > calendar for impacted circulation policy
    2. Set Hours > Start Date to past date that allows calendar to include outstanding overdue item due dates
    OR
    1. System Administration > Circulation > Calendars > New
    2. Create new calendar with start & end dates that fill gap between outstanding overdue item due dates and current calendar start date for policy.
    3. Policy Definitions > {policy} > Calendars > Add new calendar to Selected calendars in policy.

    Category: Batch jobs - Voyager

    Subject: Voyager


    • Article last edited: 11/4/2014
    //doorbell.io feedback widged