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

    Circjob 24:Exception types not reported

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

    Bug Report Form for Issue 16384-17793 / VYG-4555
    Module(s): Circjob
    Server platform(s) affected: all

    Release(s) replicated in: 7.2.3-8.1
    Last version without bug (if applicable): n/a

    Expected results:
    Circjob 24 should output all exceptions to the exception reports.

    Actual results:
    Circjob 24 removes exception types 53, 54, and 55 from the CIRC_TRANS_EXCEPTION table, but does not write anything to the exception reports for those specific exception types.

    Workflow implications: Staff does not have record of these exceptions in the reports.

    Replication steps:
    1. Create each of the exceptions by charging an item over the limit set in the following three places:
    a. SysAdmin>Circulation>Policy Definitions>Patron Tab>Rules>Max Overdue Items Apply (Exception Type 53)
    b. SysAdmin>Circulation>Patron Groups>Global Items Borrowed Limit>New Limit for particular item type. (Exception Type 54)
    c. SysAdmin>Circulation>Policy Defintions>Matrix>Modify>Max Items Borrowed for this Patron Group and Item Type (Exception type 55)
    2. select * from CIRC_TRANS_EXCEPTION where EXCEPT_TYPE_ID in (53,54,55); to see the exceptions in the database.
    3. Run /m1/voyager/xxxdb/sbin/Pcircjob –j24
    4. Look at the crcrprts.XXX.inp files and see that the exceptions from step 2 are not in the outputted files.
    5. select * from CIRC_TRANS_EXCEPTION where EXCEPT_TYPE_ID in (53,54,55); and see that the exceptions from step 2 were removed from the table by circjob 24.

    Other information:
    -------------- --------------------------------------------------
    53 Policy Group Charge Limit Override
    54 Item Type Charge Limit Override
    55 Policy Group Item Type Charge Limit Override


    • Article last edited: 3/20/2015
    • Was this article helpful?