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_MULTI_MESSAGE dependencies on HR_UTILITY

Line 235: -- hr_utility.raise_error) was incorrect. As HRMS

231: -- Background
232: -- ==========
233: -- Modification to fix bug 2661569 (changing a hardcoded
234: -- call from fnd_message.raise_error to
235: -- hr_utility.raise_error) was incorrect. As HRMS
236: -- error messages can be setup in two ways. Either
237: -- using the hr_utility or fnd_message packages. The
238: -- following solution ensures that when an error is
239: -- raised it is done in a consistent way to how the

Line 237: -- using the hr_utility or fnd_message packages. The

233: -- Modification to fix bug 2661569 (changing a hardcoded
234: -- call from fnd_message.raise_error to
235: -- hr_utility.raise_error) was incorrect. As HRMS
236: -- error messages can be setup in two ways. Either
237: -- using the hr_utility or fnd_message packages. The
238: -- following solution ensures that when an error is
239: -- raised it is done in a consistent way to how the
240: -- error was setup. i.e. If the error was setup using
241: -- hr_utility then hr_utility.raise_error will be

Line 241: -- hr_utility then hr_utility.raise_error will be

237: -- using the hr_utility or fnd_message packages. The
238: -- following solution ensures that when an error is
239: -- raised it is done in a consistent way to how the
240: -- error was setup. i.e. If the error was setup using
241: -- hr_utility then hr_utility.raise_error will be
242: -- called. Otherwise if the error was setup using
243: -- fnd_message then fnd_message.raise_error will
244: -- be called.
245: --

Line 248: -- When an error is raised using the hr_utility.raise_error

244: -- be called.
245: --
246: -- Solution Overview
247: -- =================
248: -- When an error is raised using the hr_utility.raise_error
249: -- the error details are not cleared from the hr_utility
250: -- package. Hence we cannot just call
251: -- hr_utility.get_message_details and assume that when
252: -- 'NO_MESSAGE' has been called that the error has been

Line 249: -- the error details are not cleared from the hr_utility

245: --
246: -- Solution Overview
247: -- =================
248: -- When an error is raised using the hr_utility.raise_error
249: -- the error details are not cleared from the hr_utility
250: -- package. Hence we cannot just call
251: -- hr_utility.get_message_details and assume that when
252: -- 'NO_MESSAGE' has been called that the error has been
253: -- set-up using fnd_message. This is because if one message

Line 251: -- hr_utility.get_message_details and assume that when

247: -- =================
248: -- When an error is raised using the hr_utility.raise_error
249: -- the error details are not cleared from the hr_utility
250: -- package. Hence we cannot just call
251: -- hr_utility.get_message_details and assume that when
252: -- 'NO_MESSAGE' has been called that the error has been
253: -- set-up using fnd_message. This is because if one message
254: -- is set-up using hr_utility then all following messages
255: -- set-up using fnd_message would also look as if they

Line 254: -- is set-up using hr_utility then all following messages

250: -- package. Hence we cannot just call
251: -- hr_utility.get_message_details and assume that when
252: -- 'NO_MESSAGE' has been called that the error has been
253: -- set-up using fnd_message. This is because if one message
254: -- is set-up using hr_utility then all following messages
255: -- set-up using fnd_message would also look as if they
256: -- have been set-up using hr_utility. The solution needs
257: -- obtain the error details currently held in both
258: -- hr_utility and fnd_message. If error details returned

Line 256: -- have been set-up using hr_utility. The solution needs

252: -- 'NO_MESSAGE' has been called that the error has been
253: -- set-up using fnd_message. This is because if one message
254: -- is set-up using hr_utility then all following messages
255: -- set-up using fnd_message would also look as if they
256: -- have been set-up using hr_utility. The solution needs
257: -- obtain the error details currently held in both
258: -- hr_utility and fnd_message. If error details returned
259: -- from both packages are the same then hr_utility has
260: -- been used. If they are different then fnd_message must

Line 258: -- hr_utility and fnd_message. If error details returned

254: -- is set-up using hr_utility then all following messages
255: -- set-up using fnd_message would also look as if they
256: -- have been set-up using hr_utility. The solution needs
257: -- obtain the error details currently held in both
258: -- hr_utility and fnd_message. If error details returned
259: -- from both packages are the same then hr_utility has
260: -- been used. If they are different then fnd_message must
261: -- have been used for the latest message.
262: --

Line 259: -- from both packages are the same then hr_utility has

255: -- set-up using fnd_message would also look as if they
256: -- have been set-up using hr_utility. The solution needs
257: -- obtain the error details currently held in both
258: -- hr_utility and fnd_message. If error details returned
259: -- from both packages are the same then hr_utility has
260: -- been used. If they are different then fnd_message must
261: -- have been used for the latest message.
262: --
263: -- Solution Details

Line 266: -- hr_utility package to find out if the error message

262: --
263: -- Solution Details
264: -- ================
265: -- Obtain the error message details from the
266: -- hr_utility package to find out if the error message
267: -- was raised from through that package. If the
268: -- the 'NO_MESSAGE' string is returned then the error
269: -- can't have been set using the hr_utility package.
270: --

Line 269: -- can't have been set using the hr_utility package.

265: -- Obtain the error message details from the
266: -- hr_utility package to find out if the error message
267: -- was raised from through that package. If the
268: -- the 'NO_MESSAGE' string is returned then the error
269: -- can't have been set using the hr_utility package.
270: --
271: -- Obtain error details from the hr_utility package
272: --
273: hr_utility.get_message_details

Line 271: -- Obtain error details from the hr_utility package

267: -- was raised from through that package. If the
268: -- the 'NO_MESSAGE' string is returned then the error
269: -- can't have been set using the hr_utility package.
270: --
271: -- Obtain error details from the hr_utility package
272: --
273: hr_utility.get_message_details
274: (msg_name => l_hr_msg_name
275: ,msg_appl => l_hr_msg_appl

Line 273: hr_utility.get_message_details

269: -- can't have been set using the hr_utility package.
270: --
271: -- Obtain error details from the hr_utility package
272: --
273: hr_utility.get_message_details
274: (msg_name => l_hr_msg_name
275: ,msg_appl => l_hr_msg_appl
276: );
277: --

Line 279: -- can't have been setup using the hr_utility package,

275: ,msg_appl => l_hr_msg_appl
276: );
277: --
278: -- If the 'NO_MESSAGE' string is returned then the error
279: -- can't have been setup using the hr_utility package,
280: -- it must be in fnd_message.
281: --
282: if l_hr_msg_name = 'NO_MESSAGE' then
283: fnd_message.raise_error;

Line 302: -- and hr_utility packages are different then the

298: l_fnd_msg_name := 'NO_MESSAGE';
299: end if;
300: --
301: -- If the message names returned from the fnd_message
302: -- and hr_utility packages are different then the
303: -- latest message cannot have been setup using the
304: -- hr_utility package.
305: if l_fnd_msg_name <> l_hr_msg_name then
306: fnd_message.raise_error;

Line 304: -- hr_utility package.

300: --
301: -- If the message names returned from the fnd_message
302: -- and hr_utility packages are different then the
303: -- latest message cannot have been setup using the
304: -- hr_utility package.
305: if l_fnd_msg_name <> l_hr_msg_name then
306: fnd_message.raise_error;
307: else
308: hr_utility.raise_error;

Line 308: hr_utility.raise_error;

304: -- hr_utility package.
305: if l_fnd_msg_name <> l_hr_msg_name then
306: fnd_message.raise_error;
307: else
308: hr_utility.raise_error;
309: end if;
310: end if;
311: else
312: -- All other message types should be ignored.