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_SS_RESULTS dependencies on QA_RESULTS

Line 114: -- for fetching their values from QA_RESULTS_FULL_V

110: --
111: -- bug 6266477
112: -- Loop through all the char_id and get their
113: -- result_column_names to build the select clause
114: -- for fetching their values from QA_RESULTS_FULL_V
115: -- skolluku Sun Oct 14 03:26:31 PDT 2007
116: --
117: WHILE char_id <= elements.last
118: LOOP

Line 156: l_comments_sql_string := 'SELECT ''' || char_id || '='' || ' || 'replace(' || l_rescol || ', ''@'', ''@@'') FROM QA_RESULTS_FULL_V WHERE plan_id = :2 and collection_id = :3 and occurrence = :4';

152: -- Here we will build result string for each COMMENT type element in the plan, separately
153: -- and concatenate them together to form a single COMMENTS result string to be used later in the code.
154: -- This is needed because of the limit in SQL output of 4000 characters.
155: -- skolluku
156: l_comments_sql_string := 'SELECT ''' || char_id || '='' || ' || 'replace(' || l_rescol || ', ''@'', ''@@'') FROM QA_RESULTS_FULL_V WHERE plan_id = :2 and collection_id = :3 and occurrence = :4';
157: EXECUTE IMMEDIATE l_comments_sql_string INTO l_comments_result_string USING p_plan_id, p_collection_id, p_occurrence;
158: IF l_comments_rescol_val IS NULL THEN -- First time.
159: l_comments_rescol_val := l_comments_result_string;
160: ELSE

Line 179: l_sql_string := 'SELECT ' || l_sql_string || ' FROM QA_RESULTS_FULL_V WHERE plan_id = :2 and collection_id = :3 and occurrence = :4';

175: -- Bug 9582246
176: -- In case only COMMENTS elements are present, skip this part.
177: -- skolluku
178: IF l_sql_string IS NOT NULL THEN
179: l_sql_string := 'SELECT ' || l_sql_string || ' FROM QA_RESULTS_FULL_V WHERE plan_id = :2 and collection_id = :3 and occurrence = :4';
180: EXECUTE IMMEDIATE l_sql_string INTO l_rescol_val USING p_plan_id, p_collection_id, p_occurrence;
181: END IF;
182:
183: -- Bug 9582246

Line 206: -- it fetches one value at a time from QA_RESULTS_FULL_V

202: input_val := elements(char_id).value;
203: --
204: -- bug 6266477
205: -- Commented the call to get_result_column_value since,
206: -- it fetches one value at a time from QA_RESULTS_FULL_V
207: -- resulting in performance issues. To avoid this the hit
208: -- to QA_RESULTS_FULL_V is done just once and collected
209: -- into the array elements_db in the earlier processing.
210: -- skolluku Sun Oct 14 03:26:31 PDT 2007

Line 208: -- to QA_RESULTS_FULL_V is done just once and collected

204: -- bug 6266477
205: -- Commented the call to get_result_column_value since,
206: -- it fetches one value at a time from QA_RESULTS_FULL_V
207: -- resulting in performance issues. To avoid this the hit
208: -- to QA_RESULTS_FULL_V is done just once and collected
209: -- into the array elements_db in the earlier processing.
210: -- skolluku Sun Oct 14 03:26:31 PDT 2007
211: --
212: -- Getting the value stored in QA_RESULTS, for the collection

Line 212: -- Getting the value stored in QA_RESULTS, for the collection

208: -- to QA_RESULTS_FULL_V is done just once and collected
209: -- into the array elements_db in the earlier processing.
210: -- skolluku Sun Oct 14 03:26:31 PDT 2007
211: --
212: -- Getting the value stored in QA_RESULTS, for the collection
213: -- element being processed
214: --
215: /*
216: saved_val := QA_ERES_PKG.get_result_column_value(

Line 224: -- value already existing in QA_RESULTS, it means that

220: p_char_id => char_id);
221: */
222: saved_val := elements_db(char_id).value;
223: -- If the input value is the same as the
224: -- value already existing in QA_RESULTS, it means that
225: -- the element has not been updated, in which case the
226: -- actions based on it are not to be fired. So setting
227: -- the validation flag for this element accordingly
228: --

Line 369: -- qa_results_api.insert_row

365: END get_action_messages;
366:
367: --
368: -- Post a result to the database. This is a wrapper to the QA API
369: -- qa_results_api.insert_row
370: --
371: -- This function is used by
372: --
373: -- CMRO/QA Integration /ahldev/ahl/12.0/patch/115/sql/AHLVQARB.pls

Line 459: qa_results_pub.insert_row(

455: -- was missed out in this procedure.
456: -- bso Tue Oct 8 18:37:00 PDT 2002
457: --
458:
459: qa_results_pub.insert_row(
460: p_api_version => 1.0,
461: p_init_msg_list => fnd_api.g_true,
462: p_org_id => x_org_id,
463: p_plan_id => x_plan_id,

Line 529: -- qa_results_api.insert_row

525:
526: --
527: -- This overloaded method is for transaction only
528: -- Post a result to the database. This is a wrapper to the QA API
529: -- qa_results_api.insert_row
530: --
531: -- This function is used by
532: --
533: -- iSP /qadev/qa/12.0/java/dde/eam/server/QaResultsVORowImpl.java

Line 633: qa_results_pub.insert_row(

629: -- Mon Mar 26 06:21:43 PDT 2007
630: --
631: initialize_seq_elements(x_plan_id, elements);
632:
633: qa_results_pub.insert_row(
634: p_api_version => 1.0,
635: p_init_msg_list => fnd_api.g_true,
636: p_org_id => x_org_id,
637: p_plan_id => x_plan_id,

Line 852: qa_results_pub.insert_row(

848: -- that the processing is being done for QWB application
849: -- that would ensure that the Row Validation is not done
850: -- again at the time of the data insertion
851: --
852: qa_results_pub.insert_row(
853: p_api_version => 1.0,
854: p_init_msg_list => fnd_api.g_true,
855: p_org_id => x_org_id,
856: p_plan_id => x_plan_id,

Line 1103: qa_results_pub.update_row(

1099: p_transaction_number => x_transaction_number,
1100: p_plan_transaction_id => NULL);
1101: END IF;
1102:
1103: qa_results_pub.update_row(
1104: p_api_version => 1.0,
1105: p_init_msg_list => fnd_api.g_true,
1106: p_commit => y_committed,
1107: p_plan_id => x_plan_id,

Line 1126: -- message_array returned from qa_results_pub.update_row was

1122:
1123: IF qa_validation_api.no_errors(error_array) THEN
1124:
1125: -- Bug 4057388. Display a message action was not firing in eam.
1126: -- message_array returned from qa_results_pub.update_row was
1127: -- not converted to output string x_mesasges.
1128: -- srhariha.Thu Dec 30 22:32:00 PST 2004
1129:
1130: get_action_messages(message_array, x_plan_id, x_messages);

Line 1352: qa_results_pub.update_row(

1348: -- that the processing is being done for QWB application
1349: -- that would ensure that the Row Validation is not done
1350: -- again at the time of the data updation
1351: --
1352: qa_results_pub.update_row(
1353: p_api_version => 1.0,
1354: p_init_msg_list => fnd_api.g_true,
1355: p_commit => y_committed,
1356: p_plan_id => x_plan_id,

Line 1561: FROM qa_results

1557: -- ntungare Mon Apr 10 07:03:13 PDT 2006
1558: --
1559: CURSOR upd_cur IS
1560: SELECT occurrence, last_update_date
1561: FROM qa_results
1562: WHERE occurrence = p_occurrence
1563: AND plan_id = p_plan_id
1564: FOR UPDATE NOWAIT;
1565:

Line 1661: -- would be present in the QA_RESULTS table.

1657: -- Bug 5932426
1658: -- Checing if the Txn is an update Txn or an
1659: -- Insert Txn. If the txn is update, then the
1660: -- Plan_id - Collection_id - Occurrence combination
1661: -- would be present in the QA_RESULTS table.
1662: -- ntungare Sat Apr 14 00:53:40 PDT 2007
1663: --
1664: Cursor C1 is
1665: Select 1 from QA_RESULTS

Line 1665: Select 1 from QA_RESULTS

1661: -- would be present in the QA_RESULTS table.
1662: -- ntungare Sat Apr 14 00:53:40 PDT 2007
1663: --
1664: Cursor C1 is
1665: Select 1 from QA_RESULTS
1666: WHERE plan_id = p_plan_id
1667: and collection_id = p_collection_id
1668: and occurrence = p_occurrence;
1669:

Line 1779: DELETE FROM qa_results

1775: x_plan_id IN NUMBER,
1776: x_collection_id IN NUMBER,
1777: x_occurrence IN NUMBER) IS
1778: BEGIN
1779: DELETE FROM qa_results
1780: WHERE plan_id = x_plan_id AND
1781: collection_id = x_collection_id AND
1782: occurrence = x_occurrence;
1783: END delete_result;

Line 1804: DELETE FROM qa_results

1800: -- bso Sat Oct 1 13:03:17 PDT 2005
1801: --
1802: qa_performance_temp_pkg.add_ids(c_key, x_occurrences);
1803:
1804: DELETE FROM qa_results
1805: WHERE plan_id = x_plan_id AND
1806: collection_id = x_collection_id AND
1807: occurrence IN
1808: (SELECT id

Line 1837: qa_results_pub.enable_and_fire_action (

1833: IS
1834:
1835: BEGIN
1836:
1837: qa_results_pub.enable_and_fire_action (
1838: p_api_version => 1.0,
1839: p_commit => FND_API.G_TRUE,
1840: p_collection_id => q_collection_id,
1841: x_return_status => q_return_status,