Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    UB/circjob:43 doesn't fix negative total_fees_due_ub for non-UBing patrons

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

    Description:
    Bug Report Form for Issue 16384-8289

    Module: Universal Borrowing, circjob
    Release(s) replicated in: 7.1.0
    Server Platform(s) affected: Solaris/all
    PC O/S (if this is PC specific): n/a
    Browser type & version (if WebVoyage): n/a

    Expected Results: Circjob 43 should correct the total_fees_due_ub value in the patron table.

    Actual Results: If a patron has a negative value in patron.total_fees_due_ub and the patron has no available UB data (no rows in ub_patron_record, ub_fine_fee, etc.), the negative value remains.
    If the value is negative but the patron *does* have some UB data, or if the value is positive, but there is no UB data, circjob 43 does catch the error and correct the value.

    Workflow Implications: Some patrons will not have their total_fees_due_ub reset by circjob 43; the only way to correct this counter is for Support to do it via SQL.

    Replication steps:

    Create a new patron in db A (but don’t create a stub; this way there won’t be any UB data)
    Via SQL, set patron.total_fees_due_ub = -5000 for this patron.
    Run circjob 43, and then re-check the value – you’ll see it’s still set to -50.
    Create a stub patron in db B (so now there *will* be UB data for the patron)
    Re-run circjob 43 – this time, in the log.ubsynch, you’ll see something like this:
    ========== Patron ID 389 ==========
    Patron 389 has 1 stub records to be checked.

    Patron 389: stub patron 430 at db B:
    1 active UB circulation transactions found.

    Patron 389: Total UB Fines reset from -50.00 to 0.00

    If you now re-check the total_fees_due_ub value for the patron, you’ll see that it has indeed been set to 0.

    Resolution:
    Fixed in Voyager 8.2.1


    • Article last edited: 3/16/2015