DBA Data[Home] [Help]

APPS.QA_ALERT_PKG dependencies on ALR_ACTIONS

Line 7: -- alr_actions_s and returned in x_action_id parameter.

3:
4:
5: --
6: -- Create an Alert Action record. Action ID will be generated from
7: -- alr_actions_s and returned in x_action_id parameter.
8: --
9: -- Output variable: x_return_status will be
10: -- fnd_api.g_ret_sts_success if successful
11: -- fnd_api.g_ret_sts_error if error

Line 13: PROCEDURE insert_alr_actions(

9: -- Output variable: x_return_status will be
10: -- fnd_api.g_ret_sts_success if successful
11: -- fnd_api.g_ret_sts_error if error
12: --
13: PROCEDURE insert_alr_actions(
14: p_application_id NUMBER,
15: p_name VARCHAR2,
16: p_alert_id NUMBER,
17: p_action_type VARCHAR2,

Line 52: INSERT INTO ALR_ACTIONS(

48: x_return_status OUT NOCOPY VARCHAR2
49: ) IS
50:
51: BEGIN
52: INSERT INTO ALR_ACTIONS(
53: application_id,
54: action_id,
55: name,
56: alert_id,

Line 89: alr_actions_s.nextval,

85: last_updated_by,
86: last_update_login)
87: VALUES (
88: p_application_id,
89: alr_actions_s.nextval,
90: p_name,
91: p_alert_id,
92: p_action_type,
93: p_end_date_active,

Line 129: END insert_alr_actions;

125:
126: EXCEPTION WHEN OTHERS THEN
127: x_return_status := fnd_api.g_ret_sts_error;
128:
129: END insert_alr_actions;
130:
131:
132: --
133: -- Update an Alert Action record. This function can be used to

Line 143: PROCEDURE update_alr_actions(

139: -- Output variable: x_return_status will be
140: -- fnd_api.g_ret_sts_success if successful
141: -- fnd_api.g_ret_sts_error if record is not found
142: --
143: PROCEDURE update_alr_actions(
144: p_rowid VARCHAR2,
145: p_application_id NUMBER,
146: p_action_id NUMBER,
147: p_name VARCHAR2,

Line 187: UPDATE ALR_ACTIONS

183: --
184: -- rowid is given, use it as WHERE clause to achieve best
185: -- performance.
186: --
187: UPDATE ALR_ACTIONS
188: SET
189: application_id = p_application_id,
190: action_id = nvl(p_action_id, action_id),
191: name = p_name,

Line 230: UPDATE ALR_ACTIONS

226: --
227: -- Duplicating the SQL has better performance than to fiddle
228: -- with nvl(p_rowid) in one SQL. Better readability too.
229: --
230: UPDATE ALR_ACTIONS
231: SET
232: action_id = nvl(p_action_id, action_id),
233: name = p_name,
234: alert_id = p_alert_id,

Line 276: END update_alr_actions;

272: ELSE
273: x_return_status := fnd_api.g_ret_sts_success;
274: END IF;
275:
276: END update_alr_actions;
277:
278:
279: --
280: -- Create an alr_action_sets record.