Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Changing vendor codes (with SQL)

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

    Description:
    The University has elected to change the Vendor codes. Since the Vendor code is the rec_key for z70, we would like to know the impact of such a change. I realize we cannot update the primary key, so overwriting the vendor code is not an option. Creating new vendor numbers would be ideal, but we have 6851 vendors in our vendor table. We thought of using the z70_additional_vendor_code, but then we lose the indexing and ordering would be difficult. Do you have any idea as to how we could accomplish this?

    Resolution:
    A job to change vendor codes (p_acq_26) has been added in version 16.02.
    So the following applies only to *pre*-16.02.

    Here are all the files where vendor-code key is included:

    Z121-VENDOR-CODE; Z30-VENDOR-CODE; Z30H-VENDOR-CODE; Z601-VENDOR-CODE; Z68-VENDOR-CODE; Z70-VENDOR-CODE; Z70-EDI-VENDOR-CODE; Z70-ADDITIONAL-VENDOR-CODE; Z72-VENDOR-CODE; Z720-VENDOR-CODE; Z75-VENDOR-CODE; and Z77-VENDOR-CODE

    (In 15.2 there's also a "Z403-VENDOR-CODE" and a "Z74-VENDOR-CODE".)

    Note also that the Z602 {SUB-LIBRARY / ORDERING UNIT (for BUDGETS, VENDORS and USERS)} is not in this grep list --though there *can* be Z602 records for vendors. (The field in the Z602 record is called "Z602-KEY-TEXT".)

    Also, the z70_vendor_code is used in both the z79 Order Index and in the z111 ADM (vendor) keywords index.
    Those would need to be rebuilt (by running p_acq_04 and p_manage_111, respectively) after the change was made.


    (keywords: p-manage-111 manage-111 manage_111 acq_26 p-acq-26 acq-26 acq_04 p-acq-04 acq-04)


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged