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

    p_cir_52: Is it possible to include the fine overdue on this Email?

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

    Description:
    I use the program overdue-sum-single-0 to send Email to patrons for the late documents.

    Is it possible to include the fine overdue on this Email?

    (The same problem occurs with p_cir_51.)

    Resolution:
    The ./abc01/form_eng/overdue-sum-single-0.xsl contains the following lines which are lacking on your overdue-sum-single-0.xsl :

    <xsl:call-template name="display-grid-gen">
    <xsl:with-param name="label" select="'Current Fine'"/>
    <xsl:with-param name="value" select="./current-fine"/>
    <xsl:with-param name="type" select="'right'"/>
    <xsl:with-param name="header" select="$header"/>
    </xsl:call-template>

    If you add the preceding lines in the SECTION-02 (GRID) of ./overdue-sum-single-0.xsl, you will get the fine included.

    [After the preceding change did not work.]

    Comparing your print file to ours, I see that *none* of the parameters following the z36 lines appear.

    In ours we see:

    <z36-delivery-time></z36-delivery-time>
    <z36-tail-time></z36-tail-time>
    <sum>3.00</sum>
    <recall-status>Not recalled</recall-status>
    <current-fine> 43.00</current-fine>
    </section-02>

    In yours:

    <z36-delivery-time></z36-delivery-time>
    <z36-tail-time></z36-tail-time>
    </section-02>


    At the point where these other variables are produced, the b_cir_52_b program calls the create_overdue_summary_z31 which reads tab32. It takes the value from column 8 of tab32 to see what additional Transaction-no. type should be used from tab18.eng.

    This is your abc50 tab32:

    ! 1 2 3 4 5 6 7 8
    !!!!!-!!-!!-!!-!!!-!!!-!-!!!!
    ##### ## ## 00 003 003 O ^M
    ##### ## ## 01 001 001 O ^M
    !##### ## ## 01 012 012 O ^M
    ##### ## ## 02 021 021 L ^M

    You will note the "^M" in column 8. I think the program is interpreting this as data; trying to find this value in tab18; and, failing to do so, exiting without including the "<sum>", "<recall-status>", and "<current-fine>".

    The problem of the "^M" and its solution is described in KB 16384-1537.


    • Article last edited: 10/8/2013