EBSbeginner
Profile Options in Oracle EBS
Understand what profile options are and how they control application behavior at multiple hierarchy levels
Profile options are user-configurable settings that control the behavior and appearance of EBS applications without requiring code changes. Examples include MO: Operating Unit, HR: User Type, and Sequential Numbering. Each profile has a hierarchy of levels at which it can be set: Site, Application, Responsibility, and User, with the more specific level always taking precedence.
Profile options are like thermostat settings in an office building: there's a building-wide default (Site), but individual floors (Responsibility) or offices (User) can override it — and the more specific setting always wins.
Key Concepts
1
Profile options are stored in FND_PROFILE_OPTIONS (definition) and FND_PROFILE_OPTION_VALUES (actual values at each level). Developers commonly retrieve profile values at runtime using the FND_PROFILE.VALUE API in PL/SQL, which automatically resolves the correct value based on the current session's hierarchy context.
FND_PROFILE.VALUE
2
A classic real-world example is MO: Operating Unit, which determines the default operating unit context for a user session in a multi-org environment, directly influencing which subledger transactions and setups a user can see. Similarly, FND: Debug Log Enabled controls whether detailed diagnostic logging is captured, invaluable during troubleshooting.
MO: Operating UnitFND: Debug Log Enabled
3
Interviewers often test whether a candidate knows the precedence order and can explain why a value 'isn't taking effect' — usually because it was set at a level that's overridden by a more specific one, or because the session cache needs refreshing.