DBA Data[Home] [Help]

APPS.JTF_DIAGNOSTIC dependencies on JTF_DIAGNOSTIC_ALERT

Line 2785: from jtf_diagnostic_alert

2781:
2782: begin
2783: select LAST_UPDATED_BY, LAST_UPDATE_DATE
2784: into db_luby, db_ludate
2785: from jtf_diagnostic_alert
2786: where appid = p_appid and
2787: groupname = p_groupname
2788: and testclassname = p_testclassname
2789: and type = p_type;

Line 2802: update jtf_diagnostic_alert

2798: p_cust_mode))
2799: then*/
2800: -- seed data must not be changed by customers.Hence overwriting data always
2801: -- so that it covers up any changes by mistake
2802: update jtf_diagnostic_alert
2803: set last_updated_by = f_luby,
2804: last_update_date = f_ludate,
2805: object_version_number = object_version_number + 1,
2806: LEVEL_VALUE = to_number(p_LEVEL_VALUE),

Line 2819: insert into jtf_diagnostic_alert(

2815:
2816: when no_data_found then
2817: -- Record doesn't exist - insert in all cases
2818:
2819: insert into jtf_diagnostic_alert(
2820: SEQUENCE,
2821: GROUPNAME,
2822: APPID,
2823: TYPE,

Line 2834: jtf_diagnostic_alert_s.nextval,

2830: LAST_UPDATE_LOGIN,
2831: CREATION_DATE,
2832: security_group_id)
2833: values(
2834: jtf_diagnostic_alert_s.nextval,
2835: p_groupname,
2836: p_appid,
2837: p_type,
2838: p_testclassname,