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.HZ_BES_BO_RAISE_PKG dependencies on FND_PROFILE

Line 10: G_BLK_EVT_RAISE CONSTANT VARCHAR2(1):=FND_PROFILE.VALUE('HZ_BO_EVENTS_FORMAT_BULK');

6: -- This global variable will read the profile that defines whether
7: -- event raising is to be done in bulk or not.
8: -- This profile is set at site level only. The value of the profile is set to Y.
9: -- This is to ensure that, out of the box, event raising is going to be in bulk.
10: G_BLK_EVT_RAISE CONSTANT VARCHAR2(1):=FND_PROFILE.VALUE('HZ_BO_EVENTS_FORMAT_BULK');
11: -- Private procedures
12: -- out() -- This is to write a mesg to out file.
13: -- log() -- This is to write a mesg to log file
14: -- outandlog() -- This is to write a mesg to both out and log files.

Line 444: G_PROF_VAL := FND_PROFILE.value( 'HZ_EXECUTE_API_CALLOUTS');

440: LOG('bes_main(+)');
441:
442: -- check if the profile is set to v2 and v3 or just v3 events.
443: -- in cases other than the above there is no need of any processing.
444: G_PROF_VAL := FND_PROFILE.value( 'HZ_EXECUTE_API_CALLOUTS');
445:
446: IF G_PROF_VAL = 'N' OR G_PROF_VAL = 'Y' THEN
447: -- this means either no vents must be raised or only v2 events must be raised
448: -- hence, raise an error.