Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    fix_doc_merge routine in combination with the fix_doc_001_sysno_inv routine

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    Combining a fix calling fix_doc_001_sysno_inv and a merge routine in manage_18 does not work as expected.

    I tried in 16.02 using FIX4 (calls fix_doc_001_sysno_inv in tab_fix) but also a merge routine (overlay profile 06 in tab_merge_overlay). The procedure was "update current records" "use merge routine to update entire record". The result was that only a record that matched to a record with STA DELETED was overlaid, all other records ended up in the reject file. The manage_18 reject file is supposed to be for records that match to deleted records, not those that don't. It seems reversed.

    Instead of this approach, I substituted using manage_37 to run the fix_doc_001_sysno_inv, then took that output file and ran the merge profile successfully with manage_18.

    I think there needs to be a warning that this combination of steps cannot be run with manage_18 all at once any more.

    Resolution:
    If you want to run a fix_doc_merge routine in combination with the fix_doc_001_sysno_inv routine, the fix_doc_001_sysno_inv should be run first, using p_manage_37. Then the fix_doc_merge can be run as part of the p_manage_18 load.

    (keywords: p-manage-18 p-manage-37 p_manage_18 p_manage_37)

    • Article last edited: 10/8/2013