APPS.QA_CHART_CONTROL_PKG dependencies on QA_CHART_DATA

Line 78: -- qltcontb has been called to populate qa_chart_data

74: x_row_count OUT NOCOPY NUMBER) IS
75:
76: --
77: -- This is a very specific private procedure that assumes
78: -- qltcontb has been called to populate qa_chart_data
79: -- (the old data point table), it then migrates the data over
80: -- to the qa_chart_control table. It does a direct INSERT INTO
81: -- qa_chart_control...SELECT FROM qa_chart_data. This is not
82: -- the most efficient way to achieve a histogram, but in order

Line 81: -- qa_chart_control...SELECT FROM qa_chart_data. This is not

77: -- This is a very specific private procedure that assumes
78: -- qltcontb has been called to populate qa_chart_data
79: -- (the old data point table), it then migrates the data over
80: -- to the qa_chart_control table. It does a direct INSERT INTO
81: -- qa_chart_control...SELECT FROM qa_chart_data. This is not
82: -- the most efficient way to achieve a histogram, but in order
83: -- to completely re-use the legacy code for implementation and
84: -- maintenance efficient and, more importantly, to not destabilize
85: -- existing code, this is a reasonable approach.

Line 138: qa_chart_data;

134: p_bottom_ucl,
135: p_bottom_mean,
136: p_bottom_lcl
137: FROM
138: qa_chart_data;
139:
140: x_row_count := sql%ROWCOUNT;
141:
142: END populate_data;

Line 251: FROM qa_chart_data;

247:
248: DELETE
249: /* Small amount of data from one session only. */
250: /* FTS expected and reviewed by bso 1/13/2006. */
251: FROM qa_chart_data;
252:
253: END create_chart;
254:
255: