- Article Type: General
- Product: Aleph
- Product Version: 20
After rep_change 2597, it?s impossible to move an Order that is linked to one or more subscriptions. It?s very common to have an Order linked to one bib Record, and also have many Subscription records linked to various other Bib records, while pointing to the Order record. Now, if you need to move the Order to another ADM, you have to break the Order link in all the Subscription records, move the Order, and then add the Order link back in on all the Subscription records
v20 rep_change 003572
Description: After rep_change #2597 it is impossible to move an order that is linked to one or more subscriptions.
Solution: It is now possible again to move an order that is linked to a subscription record by using "move_z68_to_adm_2" instead of "move_z68_to_adm" in tab_move_record
Header of xxx01/tab/tab_move_record:
! move_z68_to_adm: moves a selected order to another ADM record. This move
! - Orders (Z68)
! - Items + history (Z30, Z30H)
! - Order and subscription log (Z71)
! - Arrival information (Z78)
! - Acquisition claims (Z501)
! - Transactions - Budget (Z601)
! - Invoice - Line item (Z75)
! The move is not performed if:
! - The order is linked to a subscription record.
! - The item is linked to an incoming or to an outgoing
! ILL request.
! - The item is linked to an HOL record
! - The item is linked to a subscription record
! move_z68_to_adm_2: Same as move_z68_to_adm, but the move is performed even
! if the order is linked to a subscription record.
One customer reported that with Aleph 21.1.3 (2448) the functionality changed so that move_z68_to_adm permitted the move of an order which had a linked subscription. This is puzzling, but, if this is the case, then it would seem that either could be used. (Note: we find that the move_z68_to_adm_2 program continues to exist in version 22.)
Category: Serials (500)
- Article last edited: 4/1/2014