What logic does p_file_20 use to update z305 records?

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

Description:
We've made a couple of changes to our circ policies in tab31, and want to apply this to existing borrowers. Most of the affected borrowers are due to be updated through a PLIF load soon. Will this reset borrower defaults? Or should I do an SQL update on the z305 records?

Also, under what circumstances are the EXPIRY-DATE and the borrower status updated?

Resolution:
In the case of a new record, the p_file_20 PLIF load takes the value for each of the following variables from tab31:

LOAN-PERMISSION,
PHOTO-PERMISSION,
OVER-PERMISSION,
MULTI-HOLD,
LOAN-CHECK,
HOLD-PERMISSION,
RENEW-PERMISSION,
RR-PERMISSION,
IGNORE-LATE-RETURN,
PHOTO-CHARGE,
HOLD-ON-SHELF,
CASH-LIMIT (TAB31-BALANCE)

and puts them into the Z305 (borrower) record.

For for an update, it inserts the preceding tab31 values only when the borrower status has changed (that is, when the BOR-REC-STATUS is different than the existing z305_bor_status). {Note: Prior to v17 rep_change 442 (v18 rep_ver 11879) the PLIF always updated existing z305's with values from tab31. With this rep_change/rep_ver, this is done only when the borrower status has changed.}

For the EXPIRY-DATE: the program takes the date from the incoming PLIF record. If that's blank, it leaves the existing Z305-EXPIRY-DATE as is. Unless that too is blank, in which case it uses the TAB31-EXPIRY-DATE.

The program always gets the values for the Borrower status and Borrower type from the incoming PLIF record.