APPS.QA_VENDORMERGE_GRP dependencies on QA_RESULTS

Line 10: -- qa_results table.

6:
7:
8: --
9: -- Helper procedure to perform the actual updates to the
10: -- qa_results table.
11: --
12: PROCEDURE update_qa_results(
13: p_from_vendor_id NUMBER,
14: p_to_vendor_id NUMBER) IS

Line 12: PROCEDURE update_qa_results(

8: --
9: -- Helper procedure to perform the actual updates to the
10: -- qa_results table.
11: --
12: PROCEDURE update_qa_results(
13: p_from_vendor_id NUMBER,
14: p_to_vendor_id NUMBER) IS
15:
16: BEGIN

Line 21: -- create a custom index on QA_RESULTS.VENDOR_ID to make it

17: --
18: -- Quality only stores vendor ID, not vendor site, nor party
19: -- therefore updating vendor ID only. This UPDATE statement
20: -- is potentially long running. The customer is advised to
21: -- create a custom index on QA_RESULTS.VENDOR_ID to make it
22: -- more performing if this operation is run frequently.
23: --
24:
25: UPDATE qa_results

Line 25: UPDATE qa_results

21: -- create a custom index on QA_RESULTS.VENDOR_ID to make it
22: -- more performing if this operation is run frequently.
23: --
24:
25: UPDATE qa_results
26: SET vendor_id = p_to_vendor_id
27: WHERE vendor_id = p_from_vendor_id;
28:
29: END update_qa_results;

Line 29: END update_qa_results;

25: UPDATE qa_results
26: SET vendor_id = p_to_vendor_id
27: WHERE vendor_id = p_from_vendor_id;
28:
29: END update_qa_results;
30:
31:
32: --
33: -- Vendor Merge.

Line 78: update_qa_results(

74: fnd_msg_pub.initialize;
75: END IF;
76:
77: -- Perform actual update to database table.
78: update_qa_results(
79: p_from_vendor_id => p_dup_vendor_id,
80: p_to_vendor_id => p_vendor_id);
81:
82: -- NULL is intentionally treated as false by this statement.