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.

[Home] [Help]

APPS.QA_SS_RESULTS dependencies on QA_RESULTS

Line 108: -- for fetching their values from QA_RESULTS_FULL_V

104: --
105: -- bug 6266477
106: -- Loop through all the char_id and get their
107: -- result_column_names to build the select clause
108: -- for fetching their values from QA_RESULTS_FULL_V
109: -- skolluku Sun Oct 14 03:26:31 PDT 2007
110: --
111: WHILE char_id <= elements.last
112: LOOP

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

140: END LOOP;
141:
142: -- Execute the statement and fetch the values into an array
143: -- using result_to_array.
144: l_sql_string := 'SELECT ' || l_sql_string || ' FROM QA_RESULTS_FULL_V WHERE plan_id = :2 and collection_id = :3 and occurrence = :4';
145: EXECUTE IMMEDIATE l_sql_string INTO l_rescol_val USING p_plan_id, p_collection_id, p_occurrence;
146: elements_db := qa_validation_api.result_to_array(l_rescol_val);
147:
148: -- Reinitialize the char_id variable since, the comparison

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

155: input_val := elements(char_id).value;
156: --
157: -- bug 6266477
158: -- Commented the call to get_result_column_value since,
159: -- it fetches one value at a time from QA_RESULTS_FULL_V
160: -- resulting in performance issues. To avoid this the hit
161: -- to QA_RESULTS_FULL_V is done just once and collected
162: -- into the array elements_db in the earlier processing.
163: -- skolluku Sun Oct 14 03:26:31 PDT 2007

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

157: -- bug 6266477
158: -- Commented the call to get_result_column_value since,
159: -- it fetches one value at a time from QA_RESULTS_FULL_V
160: -- resulting in performance issues. To avoid this the hit
161: -- to QA_RESULTS_FULL_V is done just once and collected
162: -- into the array elements_db in the earlier processing.
163: -- skolluku Sun Oct 14 03:26:31 PDT 2007
164: --
165: -- Getting the value stored in QA_RESULTS, for the collection

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

161: -- to QA_RESULTS_FULL_V is done just once and collected
162: -- into the array elements_db in the earlier processing.
163: -- skolluku Sun Oct 14 03:26:31 PDT 2007
164: --
165: -- Getting the value stored in QA_RESULTS, for the collection
166: -- element being processed
167: --
168: /*
169: saved_val := QA_ERES_PKG.get_result_column_value(

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

173: p_char_id => char_id);
174: */
175: saved_val := elements_db(char_id).value;
176: -- If the input value is the same as the
177: -- value already existing in QA_RESULTS, it means that
178: -- the element has not been updated, in which case the
179: -- actions based on it are not to be fired. So setting
180: -- the validation flag for this element accordingly
181: --

Line 316: -- qa_results_api.insert_row

312: END get_action_messages;
313:
314: --
315: -- Post a result to the database. This is a wrapper to the QA API
316: -- qa_results_api.insert_row
317: --
318: -- This function is used by
319: --
320: -- CMRO/QA Integration /ahldev/ahl/12.0/patch/115/sql/AHLVQARB.pls

Line 406: qa_results_pub.insert_row(

402: -- was missed out in this procedure.
403: -- bso Tue Oct 8 18:37:00 PDT 2002
404: --
405:
406: qa_results_pub.insert_row(
407: p_api_version => 1.0,
408: p_init_msg_list => fnd_api.g_true,
409: p_org_id => x_org_id,
410: p_plan_id => x_plan_id,

Line 476: -- qa_results_api.insert_row

472:
473: --
474: -- This overloaded method is for transaction only
475: -- Post a result to the database. This is a wrapper to the QA API
476: -- qa_results_api.insert_row
477: --
478: -- This function is used by
479: --
480: -- iSP /qadev/qa/12.0/java/dde/eam/server/QaResultsVORowImpl.java

Line 580: qa_results_pub.insert_row(

576: -- Mon Mar 26 06:21:43 PDT 2007
577: --
578: initialize_seq_elements(x_plan_id, elements);
579:
580: qa_results_pub.insert_row(
581: p_api_version => 1.0,
582: p_init_msg_list => fnd_api.g_true,
583: p_org_id => x_org_id,
584: p_plan_id => x_plan_id,

Line 783: qa_results_pub.insert_row(

779: -- that the processing is being done for QWB application
780: -- that would ensure that the Row Validation is not done
781: -- again at the time of the data insertion
782: --
783: qa_results_pub.insert_row(
784: p_api_version => 1.0,
785: p_init_msg_list => fnd_api.g_true,
786: p_org_id => x_org_id,
787: p_plan_id => x_plan_id,

Line 1034: qa_results_pub.update_row(

1030: p_transaction_number => x_transaction_number,
1031: p_plan_transaction_id => NULL);
1032: END IF;
1033:
1034: qa_results_pub.update_row(
1035: p_api_version => 1.0,
1036: p_init_msg_list => fnd_api.g_true,
1037: p_commit => y_committed,
1038: p_plan_id => x_plan_id,

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

1053:
1054: IF qa_validation_api.no_errors(error_array) THEN
1055:
1056: -- Bug 4057388. Display a message action was not firing in eam.
1057: -- message_array returned from qa_results_pub.update_row was
1058: -- not converted to output string x_mesasges.
1059: -- srhariha.Thu Dec 30 22:32:00 PST 2004
1060:
1061: get_action_messages(message_array, x_plan_id, x_messages);

Line 1283: qa_results_pub.update_row(

1279: -- that the processing is being done for QWB application
1280: -- that would ensure that the Row Validation is not done
1281: -- again at the time of the data updation
1282: --
1283: qa_results_pub.update_row(
1284: p_api_version => 1.0,
1285: p_init_msg_list => fnd_api.g_true,
1286: p_commit => y_committed,
1287: p_plan_id => x_plan_id,

Line 1492: FROM qa_results

1488: -- ntungare Mon Apr 10 07:03:13 PDT 2006
1489: --
1490: CURSOR upd_cur IS
1491: SELECT occurrence, last_update_date
1492: FROM qa_results
1493: WHERE occurrence = p_occurrence
1494: AND plan_id = p_plan_id
1495: FOR UPDATE NOWAIT;
1496:

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

1588: -- Bug 5932426
1589: -- Checing if the Txn is an update Txn or an
1590: -- Insert Txn. If the txn is update, then the
1591: -- Plan_id - Collection_id - Occurrence combination
1592: -- would be present in the QA_RESULTS table.
1593: -- ntungare Sat Apr 14 00:53:40 PDT 2007
1594: --
1595: Cursor C1 is
1596: Select 1 from QA_RESULTS

Line 1596: Select 1 from QA_RESULTS

1592: -- would be present in the QA_RESULTS table.
1593: -- ntungare Sat Apr 14 00:53:40 PDT 2007
1594: --
1595: Cursor C1 is
1596: Select 1 from QA_RESULTS
1597: WHERE plan_id = p_plan_id
1598: and collection_id = p_collection_id
1599: and occurrence = p_occurrence;
1600:

Line 1710: DELETE FROM qa_results

1706: x_plan_id IN NUMBER,
1707: x_collection_id IN NUMBER,
1708: x_occurrence IN NUMBER) IS
1709: BEGIN
1710: DELETE FROM qa_results
1711: WHERE plan_id = x_plan_id AND
1712: collection_id = x_collection_id AND
1713: occurrence = x_occurrence;
1714: END delete_result;

Line 1735: DELETE FROM qa_results

1731: -- bso Sat Oct 1 13:03:17 PDT 2005
1732: --
1733: qa_performance_temp_pkg.add_ids(c_key, x_occurrences);
1734:
1735: DELETE FROM qa_results
1736: WHERE plan_id = x_plan_id AND
1737: collection_id = x_collection_id AND
1738: occurrence IN
1739: (SELECT id

Line 1768: qa_results_pub.enable_and_fire_action (

1764: IS
1765:
1766: BEGIN
1767:
1768: qa_results_pub.enable_and_fire_action (
1769: p_api_version => 1.0,
1770: p_commit => FND_API.G_TRUE,
1771: p_collection_id => q_collection_id,
1772: x_return_status => q_return_status,