Lost item replacement cost is not being charged when item is declared lost.

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

Description:
The Lost item replacement cost is not being charged when item is declared lost or when it goes to lost by running p_cir_51.

Resolution:
The problem is the lack of the "#" in column 5 of the abc50 tab34. This means that the program is choosing only items with a blank call number.

This is the first line of the abc50 tab34 (note: if you expand the email to the full width of the screen, the columns are more intelligible):

!1 2 3 4 5 6 7 8 9 10 11 12
!!!!!-!!-!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!>
##### 01 ## # ##### ##### 0 7.50 I/20.00


This is what it (and the subsequent lines) *should* look like:

!1 2 3 4 5 6 7 8 9 10 11 12
!!!!!-!!-!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!>
##### 01 ## # # ##### ##### 0 7.50 I/20.00


The problem also occurred in v18 and earlier versions, when the call number was in column 4. In v19, a Call Number Type column has been inserted as column 4 and the call number is now column 5.

In updating tab34 as part of the v18-v19 upgrade, you need to be sure to insert the "#" in column 5. See also, KBs 16834-16625 and 16384-3282.