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.JTF_DIAGNOSTIC dependencies on JTF_DIAGNOSTIC_ALERT

Line 3065: from jtf_diagnostic_alert

3061:
3062: begin
3063: select LAST_UPDATED_BY, LAST_UPDATE_DATE
3064: into db_luby, db_ludate
3065: from jtf_diagnostic_alert
3066: where appid = p_appid and
3067: groupname = p_groupname
3068: and testclassname = p_testclassname
3069: and type = p_type;

Line 3082: update jtf_diagnostic_alert

3078: p_cust_mode))
3079: then*/
3080: -- seed data must not be changed by customers.Hence overwriting data always
3081: -- so that it covers up any changes by mistake
3082: update jtf_diagnostic_alert
3083: set last_updated_by = f_luby,
3084: last_update_date = f_ludate,
3085: object_version_number = object_version_number + 1,
3086: LEVEL_VALUE = to_number(p_LEVEL_VALUE),

Line 3099: insert into jtf_diagnostic_alert(

3095:
3096: when no_data_found then
3097: -- Record doesn't exist - insert in all cases
3098:
3099: insert into jtf_diagnostic_alert(
3100: SEQUENCE,
3101: GROUPNAME,
3102: APPID,
3103: TYPE,

Line 3114: jtf_diagnostic_alert_s.nextval,

3110: LAST_UPDATE_LOGIN,
3111: CREATION_DATE,
3112: security_group_id)
3113: values(
3114: jtf_diagnostic_alert_s.nextval,
3115: p_groupname,
3116: p_appid,
3117: p_type,
3118: p_testclassname,