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.QLTDACTB dependencies on QLTDACTB

Line 1: PACKAGE BODY QLTDACTB as

1: PACKAGE BODY QLTDACTB as
2: /* $Header: qltdactb.plb 120.25.12020000.3 2013/04/05 03:50:29 ntungare ship $ */
3: -- 2/8/95 - created
4: -- Kevin Wiggen
5:

Line 2: /* $Header: qltdactb.plb 120.25.12020000.3 2013/04/05 03:50:29 ntungare ship $ */

1: PACKAGE BODY QLTDACTB as
2: /* $Header: qltdactb.plb 120.25.12020000.3 2013/04/05 03:50:29 ntungare ship $ */
3: -- 2/8/95 - created
4: -- Kevin Wiggen
5:
6:

Line 637: -- would not fire because for specification at element level in qltdactb we check

633: -- not supported at plan level we call Quality APIs from EAM with spec_id as -1
634: -- (even if one of the elements in the collection plan has specification limits
635: -- defined). When spec_id is -1 the existing code assigns NULL to spec_id(This
636: -- happens in qltssresb.plb). If we pass NULL then the actions based on the elements
637: -- would not fire because for specification at element level in qltdactb we check
638: -- whether spec_id is 0 and then fire the actions. If it is NULL then no action
639: -- would fire. So made Y_SPEC_ID to have the value as 0 if spec_id is NULL or <= 0.
640: -- ntungare Wed Mar 29 02:58:45 PST 2006.
641:

Line 3288: END QLTDACTB;

3284: END high_val;
3285:
3286:
3287:
3288: END QLTDACTB;
3289: