Hierarchy Profile Options

This article is an attempt to explain the Hierarchy Profile Options with examples. Can all the profile options be set at Organization Level and Server level? You need to set “Hierarchy Type” field in Profile Option definition to enable that profile to be eligible for Hierarchy Level. This functionality was introduced in 11.5.9 How to find from SQL*Plus whether a Profile Option is Hierarchy Enabled? SELECT HIERARCHY_TYPE  FROM fnd_profile_options_vl where profile_option_name = 'profile option short name' ; If the above SQL returns SERVER, then the profile is enabled at Server Level. If the above SQL returns ORG, then the profile is enabled for Organization Level. If the above SQL returns SERVRESP, then the profile is enabled for both Server and Responsibility Level. Why the need of Organization Level profile option? For example multiple responsibilities can be attached to same Operating Unit. In such event, it can get tedious to attach the same profile option to each such responsibility. By attaching an Organization Level Profile Option to an Operating Unit implies that all such responsibilities inherit Org Level Profile value. Will Organization Level Profile override the Responsibility Level Profile? Yes Give me some example usages of Server Level Profiles Managing Timezones In a single Global DB Instance implementation, you may desire to display different time in UI screen, depending upon the local timezone. If you have a separate Middle Tier Server for each timezone, then timezone profile options [Enable Timezone Conversions, Client Timezone, Server Timezone] can be set at Server Level. External WWW Facing Mid Tiers It is possible that for security reasons, you may desire to change the functionality of Application when its accessed from External WWW facing mid-tier. Such security profiles can be assigned at server level. For example, profile option “Node Trust Level” can be set to a value of external against a server to flag the specific mid-tier server as External. See Link for details. Give me some example usages of Organization Level Profiles Managing Timezones In a single Global DB Instance implementation, you may desire to display different time in UI screen, depending upon the local timezone. If you can’t afford to have a separate Middle Tier Server for each timezone, then timezone profile options [Enable Timezone Conversions, Client Timezone, Server Timezone] can be set at Organization Level, as each Organization assumingly will be in a specific timezone. Setting Org Level Profile Option in HRMS A HRMS Business Group can be assigned to various Oracle HRMS Responsibilities. Keeping a track of profiles against all such responsibilities, which belong to a specific Business Group can be tedious. Hence you may simplify this by simply assigning the profile to Business Group Organisation. What is the order of precedence for Profiles? Security Profiles: Site Level >> Application Level >> Resp Level >> User Level Server Profiles: Site Level >> Server Level >> User Level Organization Profiles : Site Level >> Organization Level >> User Level