• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
When we run item-05 - Shelf-List report, the system sometimes retrieves a blank report. After blank output, the log file at $alephe_scratch, has this error message: "Failed to access Location Index." When there is output, the error message does NOT appear in the log.
We get results if:
From Call No = Q
To Call No = T
But we get a blank result with:
From Call No = QA7
To Call No = QA9

Resolution:
The Failed to access Location Index error: The location index is a combination of the call number type and the call number.
In the log file it appears as:
p_location_from
p_location_to
p_location_type
The service, Rebuilding Call No. Index (item-06), rebuilds the location keys in the Item (Z30) records.
It is best to run the report with the values of "From" and "To" set to the full Item Call Number text, as they appear in the GUI Item record or in the report, such as:
From: $$kE$$hAND
To: $$kE$$hDIL
This report runs on this field, of the Z30 record:
Barcode 31510000037284, ADM 000016698:
02 z30_call_no_type ............1
02 z30_call_no .................$$kE$$hAAR <--- this field
02 z30_call_no_key .............1 e aar

Note:  The b_item_05 program calls the filing_call_no program which reads the ./xxx50/tab/tab_filing_call_no table to create a "normalized" call number which is matched against the z30_call_no_key of the item.  Since the tab_filing_call_no table entry *usually* specifies a "del_subfield" routine, the subfield code (such as the above "$$k") does not usually need to be entered in.  Of course, there's *never* any harm including it since, if  "del_subfield" *is* specified, it will be deleted and a proper match will result.

• Article last edited: 10/8/2013