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.HR_CALENDAR_NODE_TYPE_SWI dependencies on HR_MULTI_MESSAGE

Line 44: hr_multi_message.enable_message_list;

40: savepoint create_node_type_swi;
41: --
42: -- Initialise Multiple Message Detection
43: --
44: hr_multi_message.enable_message_list;
45: --
46: -- Remember IN OUT parameter IN values
47: --
48: --

Line 90: p_return_status := hr_multi_message.get_return_status_disable;

86: -- Derive the API return status value based on whether
87: -- messages of any type exist in the Multiple Message List.
88: -- Also disable Multiple Message Detection.
89: --
90: p_return_status := hr_multi_message.get_return_status_disable;
91: hr_utility.set_location(' Leaving:' || l_proc,20);
92: --
93: exception
94: when hr_multi_message.error_message_exist then

Line 94: when hr_multi_message.error_message_exist then

90: p_return_status := hr_multi_message.get_return_status_disable;
91: hr_utility.set_location(' Leaving:' || l_proc,20);
92: --
93: exception
94: when hr_multi_message.error_message_exist then
95: --
96: -- Catch the Multiple Message List exception which
97: -- indicates API processing has been aborted because
98: -- at least one message exists in the list.

Line 105: p_return_status := hr_multi_message.get_return_status_disable;

101: --
102: -- Reset IN OUT parameters and set OUT parameters
103: --
104: p_object_version_number := null;
105: p_return_status := hr_multi_message.get_return_status_disable;
106: hr_utility.set_location(' Leaving:' || l_proc, 30);
107: when others then
108: --
109: -- When Multiple Message Detection is enabled catch

Line 116: if hr_multi_message.unexpected_error_add(l_proc) then

112: -- Multiple Message List. Otherwise re-raise the
113: -- error.
114: --
115: rollback to create_node_type_swi;
116: if hr_multi_message.unexpected_error_add(l_proc) then
117: hr_utility.set_location(' Leaving:' || l_proc,40);
118: raise;
119: end if;
120: --

Line 124: p_return_status := hr_multi_message.get_return_status_disable;

120: --
121: -- Reset IN OUT and set OUT parameters
122: --
123: p_object_version_number := null;
124: p_return_status := hr_multi_message.get_return_status_disable;
125: hr_utility.set_location(' Leaving:' || l_proc,50);
126: end create_node_type;
127: -- ----------------------------------------------------------------------------
128: -- |---------------------------< delete_node_type >---------------------------|

Line 153: hr_multi_message.enable_message_list;

149: savepoint delete_node_type_swi;
150: --
151: -- Initialise Multiple Message Detection
152: --
153: hr_multi_message.enable_message_list;
154: --
155: -- Remember IN OUT parameter IN values
156: --
157: --

Line 186: p_return_status := hr_multi_message.get_return_status_disable;

182: -- Derive the API return status value based on whether
183: -- messages of any type exist in the Multiple Message List.
184: -- Also disable Multiple Message Detection.
185: --
186: p_return_status := hr_multi_message.get_return_status_disable;
187: hr_utility.set_location(' Leaving:' || l_proc,20);
188: --
189: exception
190: when hr_multi_message.error_message_exist then

Line 190: when hr_multi_message.error_message_exist then

186: p_return_status := hr_multi_message.get_return_status_disable;
187: hr_utility.set_location(' Leaving:' || l_proc,20);
188: --
189: exception
190: when hr_multi_message.error_message_exist then
191: --
192: -- Catch the Multiple Message List exception which
193: -- indicates API processing has been aborted because
194: -- at least one message exists in the list.

Line 200: p_return_status := hr_multi_message.get_return_status_disable;

196: rollback to delete_node_type_swi;
197: --
198: -- Reset IN OUT parameters and set OUT parameters
199: --
200: p_return_status := hr_multi_message.get_return_status_disable;
201: hr_utility.set_location(' Leaving:' || l_proc, 30);
202: when others then
203: --
204: -- When Multiple Message Detection is enabled catch

Line 211: if hr_multi_message.unexpected_error_add(l_proc) then

207: -- Multiple Message List. Otherwise re-raise the
208: -- error.
209: --
210: rollback to delete_node_type_swi;
211: if hr_multi_message.unexpected_error_add(l_proc) then
212: hr_utility.set_location(' Leaving:' || l_proc,40);
213: raise;
214: end if;
215: --

Line 218: p_return_status := hr_multi_message.get_return_status_disable;

214: end if;
215: --
216: -- Reset IN OUT and set OUT parameters
217: --
218: p_return_status := hr_multi_message.get_return_status_disable;
219: hr_utility.set_location(' Leaving:' || l_proc,50);
220: end delete_node_type;
221: -- ----------------------------------------------------------------------------
222: -- |---------------------------< update_node_type >---------------------------|

Line 253: hr_multi_message.enable_message_list;

249: savepoint update_node_type_swi;
250: --
251: -- Initialise Multiple Message Detection
252: --
253: hr_multi_message.enable_message_list;
254: --
255: -- Remember IN OUT parameter IN values
256: --
257: l_object_version_number := p_object_version_number;

Line 292: p_return_status := hr_multi_message.get_return_status_disable;

288: -- Derive the API return status value based on whether
289: -- messages of any type exist in the Multiple Message List.
290: -- Also disable Multiple Message Detection.
291: --
292: p_return_status := hr_multi_message.get_return_status_disable;
293: hr_utility.set_location(' Leaving:' || l_proc,20);
294: --
295: exception
296: when hr_multi_message.error_message_exist then

Line 296: when hr_multi_message.error_message_exist then

292: p_return_status := hr_multi_message.get_return_status_disable;
293: hr_utility.set_location(' Leaving:' || l_proc,20);
294: --
295: exception
296: when hr_multi_message.error_message_exist then
297: --
298: -- Catch the Multiple Message List exception which
299: -- indicates API processing has been aborted because
300: -- at least one message exists in the list.

Line 307: p_return_status := hr_multi_message.get_return_status_disable;

303: --
304: -- Reset IN OUT parameters and set OUT parameters
305: --
306: p_object_version_number := l_object_version_number;
307: p_return_status := hr_multi_message.get_return_status_disable;
308: hr_utility.set_location(' Leaving:' || l_proc, 30);
309: when others then
310: --
311: -- When Multiple Message Detection is enabled catch

Line 318: if hr_multi_message.unexpected_error_add(l_proc) then

314: -- Multiple Message List. Otherwise re-raise the
315: -- error.
316: --
317: rollback to update_node_type_swi;
318: if hr_multi_message.unexpected_error_add(l_proc) then
319: hr_utility.set_location(' Leaving:' || l_proc,40);
320: raise;
321: end if;
322: --

Line 326: p_return_status := hr_multi_message.get_return_status_disable;

322: --
323: -- Reset IN OUT and set OUT parameters
324: --
325: p_object_version_number := l_object_version_number;
326: p_return_status := hr_multi_message.get_return_status_disable;
327: hr_utility.set_location(' Leaving:' || l_proc,50);
328: end update_node_type;
329: end HR_CALENDAR_NODE_TYPE_SWI;