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

    Claim Report and Letters (ill-73) p_ill_73

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    The ILL73 service is supposed to report on requests overdue from a supplier(status SV). All Unfilled requests are also showing up in the report (also WAP). Unfilled requests should be filtered out and not be part of the report. This makes the report long and wastes huge amount of paper. There is obviously some status filter that is not working properly.
    We also feel the statuses of SHP and WSP should be included along with the SV status as statuses that should be reported on. [16384-10311]

    This service is supposed to allow you to produce a report of ILL borrowing requests which should be claimed from suppliers. It will also produce letters to send to the suppliers.
    The report can be run with three options:
    Report and Letters to Suppliers
    Report Only
    Letters to Suppliers Only
    If you run it "Report Only" it appears to work. However if you use either of the other options, the report and the letters appear to list every request made on the system, even those which have been closed. [8192-86742]

    Resolution:
    This service creates a report of all ILL requests that were not received by the expected date (Requests with status SV/"Sent to Vendor"). There is also an option to print a letter to the Supplier for each individual outstanding ILL Request.

    Procedure to Run
    If you choose one of the options that produces letters to suppliers, the system will automatically update the Request Status field of the ILL Record to "Claimed" (A log entry is created).

    Expected Arrival Date (Z411-EXPECTED-ARRIVAL-DATE)
    Enter the date by which you expect the material to have arrived. All items that were due up to or including the date entered here will be reported and/or claimed.

    Only requests which are managed by the ILL Unit to which you are logged in will be handled by this service.

    This job can NOT be run from the ADMIN staff user.

    =============
    Command Line:
    =============
    csh -f $aleph_proc/p_ill_73 p_active_library,p_op_code,p_partner_list,p_exp_arrival_date,p_report_name,p_letter_name,p_report_format,p_letter_format,p_ill_unit,p_user_name

    csh -f $aleph_proc/p_ill_73 USM40,B,,20080505,jill73r,jill73l,00,00,ILL_LAW,GEORGE, >& /exlibris/aleph/a18_1/alephe/scratch/usm40_p_ill_73.20080101law &

    [The ">&" redirects both the "standard output" and the "standard error" to the named file. If the "standard error" is not redirected to the file, then the APDUs generated will appear on the screen, but not be saved to a log.]
    Please note that, even if, in this example, staff user "GEORGE" is denied permission to run ill-73 and cannot run it from the GUI interface, that staff username can be successfully used as a parameter when running it from the command line or job list. However, "GEORGE" must be a valid staff username and if the staff-username and ILL Unit do not match, then GEORGE's ILL Unit will be used instead of the ILL Unit specified. Also, GEORGE MUST be written in upper case.

    =============
    job_list
    =============
    02 14:23:00 Y USM40 p_ill_73 USM40,B,,20080505,jill73r,jill73l,00,00,ILL_LAW,GEORGE

    In order to run the service for ALL ILL Units at once, the staff username parameter should be left empty and the ILL Unit parameter should be "ALL".
    There is no output file. A sample log file name from $alephe_scratch: usm40_p_ill_73.00226

    --------------------------------------------------------------------------------
    Enhancement request
    We also need to send a letter to the requester to inform them of the situation. It would be very useful if this service could also generate such a letter to the requester.
    Even if this can be done via different service the desire is to have it be done via the same service which sends the letters to the suppliers

    [faq]



    This issue is still open and was escalated to Development for further investigation <2008-05-11 01:00:03>.


    • Article last edited: 10/8/2013
    • Was this article helpful?
    //doorbell.io feedback widged