Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Updating Order Index after update of z68 order record via SQL

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

    Description:
    Is there a service that the ALEPH GUI calls when a user clicks on the "update" button after making changes to a record? I am trying to tidy up data in our p_custom_03 service, which involves copying data from one field (z68_library_note mapped from from the 981 $d during the p_file_96 process) to three other order fields (z68_order_number_1, z68_vendor_code, z68_order_group, and z68_material_type).

    When this is done, the update query effectively updates the existing record fine, but the indexing does not take place automatically until the user opens the order record in the Acquisitions GUI, makes another change in one of the field values, and then clicks on the "update" button. I would like to automate this last series of manual actions by the user.

    What service/process do we need to call to have the values already in the underlying Oracle table indexed appropriately, so that the GUI searching/filtering functionalities work with the new values?

    Resolution:
    The order index table is the z79. When you click on "Update", the system generates new z79 records for this particular order.

    The p_acq_04 service rebuilds the z79 order index. There is no batch service which updates the z79 for a particular order or group of orders. The only option is to periodically run p_acq_04 to rebuild it in its entirety.


    • Article last edited: 10/8/2013