- Article Type: General
- Product: Voyager
- Product Version: 7.2.0
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
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.
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.
- Article last edited: 3/17/2015