APPS.QA_CORE_PKG dependencies on QA_PLAN_ELEMENT_API

Line 39: -- Bug 3754667. We'll use the qa_chars_api and qa_plan_element_api

35: */
36:
37: BEGIN
38:
39: -- Bug 3754667. We'll use the qa_chars_api and qa_plan_element_api
40: -- functions to use the cache instead of the cursors that fetches
41: -- from the DB each time.
42: -- kabalakr. Wed Jul 28 03:06:38 PDT 2004.
43:

Line 67: name := qa_plan_element_api.qpc_result_column_name(P_ID, ELEMENT_ID);

63: FETCH c3 INTO name;
64: CLOSE c3;
65: */
66:
67: name := qa_plan_element_api.qpc_result_column_name(P_ID, ELEMENT_ID);
68:
69: end if;
70:
71: return name;

Line 162: /* Bug 3754667. We would use the cache implementation in qa_plan_element_api

158: result NUMBER;
159:
160: BEGIN
161:
162: /* Bug 3754667. We would use the cache implementation in qa_plan_element_api
163: rather than fetching the mandatory flag from the DB each time. kabalakr.
164:
165: select mandatory_flag into result
166: from qa_plan_chars

Line 171: result := qa_plan_element_api.qpc_mandatory_flag(GIVEN_PLAN_ID, ELEMENT_ID);

167: where plan_id = GIVEN_PLAN_ID and char_id = ELEMENT_ID;
168:
169: */
170:
171: result := qa_plan_element_api.qpc_mandatory_flag(GIVEN_PLAN_ID, ELEMENT_ID);
172:
173: if (result = 1) then
174: return true;
175: else