Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. IMPORT_RULE_PO table contains unnecessary rows

    IMPORT_RULE_PO table contains unnecessary rows

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.0

    Description:
    Issue 16384-18337
    Module: Sysadmin
    Server platform affected: n/a (Oracle table-related problem)
    PC OS :n/a
    Browser & version: n/a
    Releases reported in: 7.2.0
    Replicated in: 8.0.0-8.1.1
    Last version without bug: n/a

    Expected results: Every time a user updates a Bulk Import Rule with Order settings defined, a new row should not be added to IMPORT_RULE_PO

    Actual results:
    Every time a user updates a Bulk Import Rule with Order settings defined, a new row is added to IMPORT_RULE_PO

    Workflow implications: No negative impact except for time wasted trying to figure out what the extra rows are for.

    Replication steps:
    Log into SQLplus and look at the import_rule table that has a import_rule_po_id greater than 0. Retrieve the import_rule_po data for that import rule. Notice the import_rule_po_id.
    Log into Sysadmin and retrieve the Bulk Import Rule that you were just looking at in the database.
    Once in the Bulk Import Rule, click on the Orders button. Update any of the settings (e.g. the Vendor Code).
    Log back into SQLplus and look at the import_rule_po entries, you will see that there is a new row and the old row is still there.

    Other information: It appears that every time we update a bulk import rule with PO/Order settings defined, a new row is added to IMPORT_RULE_PO. Each new row has its own import_rule_po_id, which links it to the relevant row in IMPORT_RULE (whose own import_rule_po_id column gets updated with the new value).

    Customers who have been using EOD for a long time will have many unused rows and it's confusing when running reports or looking at the data.

    Resolution:


    • Article last edited: 3/17/2015
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Import records from file get "Unrecognized record format encountered" partway through file
      • IMPORT:Bi-directional merge not working of 040a at top of hierarchy
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. 7.2.0
      2. contype:kba
      3. Prod:Voyager
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved