eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.QA_TCA_PKG dependencies on QA_RESULTS

Line 20: -- p_entity_name should always be 'QA_RESULTS'.

16: --
17: -- This is Oracle Quality's party merge API provided to TCA.
18: -- See Bug 3741531
19: --
20: -- p_entity_name should always be 'QA_RESULTS'.
21: --
22: -- p_from_id is NULL for a bulk party merge.
23: --
24: -- x_to_id is the new ID for merging purpose. Since we are

Line 57: -- We shall handle only HZ_PARTIES in QA_RESULTS.

53: x_to_id := p_from_id;
54: x_return_status := fnd_api.g_ret_sts_success;
55:
56: --
57: -- We shall handle only HZ_PARTIES in QA_RESULTS.
58: --
59: IF p_entity_name = 'QA_RESULTS' AND
60: p_parent_entity_name = 'HZ_PARTIES' AND
61: p_from_fk_id <> p_to_fk_id THEN

Line 59: IF p_entity_name = 'QA_RESULTS' AND

55:
56: --
57: -- We shall handle only HZ_PARTIES in QA_RESULTS.
58: --
59: IF p_entity_name = 'QA_RESULTS' AND
60: p_parent_entity_name = 'HZ_PARTIES' AND
61: p_from_fk_id <> p_to_fk_id THEN
62:
63: --

Line 71: -- on qa_results.party_id. This statement is also documented

67: -- this RETURN will be executed, guaranteeing good performance.
68: --
69: -- Should customer uses Party element and the quality result
70: -- table is big, customer is adviced to create a custom index
71: -- on qa_results.party_id. This statement is also documented
72: -- in TCA's party merge implementation guide.
73: -- See bug 3741531 text.
74: --
75: OPEN c;

Line 83: UPDATE qa_results qr

79: RETURN;
80: END IF;
81: CLOSE c;
82:
83: UPDATE qa_results qr
84: SET qr.party_id = p_to_fk_id,
85: qr.last_update_date = sysdate,
86: qr.qa_last_update_date = sysdate,
87: qr.last_update_login = hz_utility_pub.last_update_login,