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_RESULT_GRP dependencies on QA_RESULT_GRP

Line 1: PACKAGE BODY QA_RESULT_GRP AS

1: PACKAGE BODY QA_RESULT_GRP AS
2: /* $Header: qltgresb.plb 120.8.12000000.2 2007/02/20 21:43:03 shkalyan ship $ */
3:
4: G_PKG_NAME CONSTANT VARCHAR2(30):='QA_RESULT_GRP';
5:

Line 4: G_PKG_NAME CONSTANT VARCHAR2(30):='QA_RESULT_GRP';

1: PACKAGE BODY QA_RESULT_GRP AS
2: /* $Header: qltgresb.plb 120.8.12000000.2 2007/02/20 21:43:03 shkalyan ship $ */
3:
4: G_PKG_NAME CONSTANT VARCHAR2(30):='QA_RESULT_GRP';
5:
6: -- R12 ERES Support in Service Family. Bug 4345768 Start
7: -- Global variable to hold the status of the eRecord for Txn Acknowledgement.
8: g_erec_success CONSTANT VARCHAR2(30) := 'SUCCESS';

Line 218: -- records - even if the parent transaction calls QA_RESULT_GRP.ENABLE

214: -- to fire the action. Before this fix qltdactb.do_actions was called
215: -- without any condition and because of this whenever the procedure
216: -- Enable is called the actions are also fired unnecessarily which is
217: -- not correct. The actions should fire only once for the enabled
218: -- records - even if the parent transaction calls QA_RESULT_GRP.ENABLE
219: -- more than once, the updation of qa_results and action firing will
220: -- happen only the first time and nothing would happen during the
221: -- consecutive calls.
222: -- ntungare Thu Sep 8 07:37:32 PDT 2005

Line 1326: END qa_result_grp;

1322:
1323: END purge_results_erecords;
1324: -- R12 ERES Support in Service Family. Bug 4345768 End
1325:
1326: END qa_result_grp;