• Article Type: General
• Product: Voyager
• Product Version: 7.1.0

Description:
Bug Report Form for Issue 16384-8273

Module: Acquisitions
Release(s) replicated in: 7.1.1
Server Platform(s) affected: Solaris/all
PC O/S (if this is PC specific): n/a
Browser type & version (if WebVoyage): n/a

Expected Results: When the line item copy is linked to a different mfhd, any items created through that line item in Acquisitions should automatically be linked to the new holdings record.

Actual Results: When the line item copy is linked to a different mfhd, only the last item created through that line item in Acquisitions is automatically re-linked to the new holdings record.

Workflow Implications: For serials where an item is created for each individual issue, operators might have to manually re-link hundreds of items.

Replication steps:
Create a PO, add a line item, and create a serials check-in record associated with this line item (or find an existing component) – note: the PO must be approved.
On the Subscription Maintenance>Component Details tab for the component, make sure that Create Items is checked.
Go to Serials Check-in and check in several issues.
In Cataloging, look up this record and view the hierarchy – note that all items created from serials check-in are linked to the mfhd that’s linked to the line item.
In Cataloging, create a new mfhd associated with this bib.
In Acq, bring up the PO, highlight the line item and go to Line Item>Edit Approved.
Fill in appropriate ledger/fund information.
In the Link to Holdings field, click the ellipsis on the far right.
Click OK to the “Changing the holdings record will automatically delete the previous holdings record and re-link its items to the new holdings record” message.
Pick your new mfhd from the list presented to you, and click Re-link.
Click Save.
You’ll receive a message stating that the original holdings record could not be deleted – click OK.
Go back to Cataloging and view the hierarchy again – you’ll see that now the last issue checked in is associated with the new mfhd; however, all the rest are still associated with the original mfhd (which then prevents its deletion).

Resolution:

• Article last edited: 3/19/2015