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

Description:
The util f/2/10 utility ("Display/Check Overdue Fine Calculation") is reporting an error and not calculating the fines correctly:

Enter item barcode (Q to stop) : 32792022524270
Enter bor ID (Q to stop) : 2538
Enter bor status [40] (Q to stop) :
Z36-BOR-STATUS: 40
Z36-ITEM-STATUS: 03
Z30-ITEM-PROCESS-STATUS:
TAB16: ABC50 03 ## 40 + 00000028 00 A 2359 0000 00050 500 999 D + 00000014 + 0000 010 014 09 0000010.00 0000000000 0000000000 000 2 01
Enter due date (yyyymmdd or Q to stop) : 20110721
Enter due hour (hhmm or Q to stop) : 2359
Enter return date (yyyymmdd or Q to stop) : 20110720
Enter return hour (hhmm or Q to stop) : 2359
Enter recall due date [00000000] (yyyymmdd or Q to stop): 20110625
Enter recall type [01 ]:
Load: /tmp/utf_files/exlibris/aleph/u20_1/abc50/tab/tab18.eng
Error (cash_get_vat_rate) : failed to read tab18 for active-library = ABC50 cash-type =
Error (cash_get_vat_rate) : failed to read tab18 for active-library = ABC50 cash-type =
Fine is: 2.00

The utility gives the "Error ... cash-type" error shown above and the "Fine is" amount is incorrect.

Resolution:
The util f/2/10 utility calculates the recall fine maxiumum properly in the case where the pre-recall due date has been reached, but not in the case where it has not been reached.

The ./com/get_cash_0003_current_fine program checks to see if the item is "late"

IF SW-LATE = "N"
THEN
GO TO EX-GET-CASH-0003-CURRENT-FINE
END-IF

and, if not, it does not build the temporary z31 which is required for correct calculation of the recall fine maximum. This
is evident in these values you see in the util f/2/10 dialog when the pre-recall due date has not yet been reached:

z31-rec-key=
z31-key=

and the

Error (cash_get_vat_rate) : failed to read tab18 for active-library = ABC50 cash-type =

which appear when the pre-recall due date has not been reached.

• Article last edited: 10/8/2013