
How to Get More Details from an Oracle E-Business Suite OAF Page or Form Window
By enabling a few key profile options, administrators and developers can gain access to diagnostic links, region details, item IDs, controller information, and personalization tools directly from the UI.

When troubleshooting, analyzing functionality, or preparing customizations in Oracle E-Business Suite (EBS), it’s often necessary to inspect what is happening behind the scenes on a page or form. Oracle provides several built-in profile options that expose additional diagnostics, metadata, and personalization tools for Oracle Application Framework (OAF) pages and Oracle Forms.
This article explains the most useful profile options, what they do, and how to enable them in Oracle EBS.
Why Enable Diagnostics and Personalization?
Oracle EBS uses two main UI technologies:
- Oracle Application Framework (OAF) – used for most Self-Service web pages
- Oracle Forms – used for many traditional transactional windows
These pages and forms contain internal components such as:
- Regions
- Items
- Controllers
- Application modules
- Blocks
- Fields
Normally, this technical information is hidden. By enabling specific profile options, administrators can expose this metadata directly in the UI.
This is extremely useful when:
- Creating OAF personalizations
- Debugging UI issues
- Identifying region/item IDs
- Investigating form fields and blocks
- Preparing custom extensions
- Working with Oracle Support
Key Profile Options to Enable
The following profile options should be enabled to access extended diagnostics and personalization functionality.
1. Personalize Self-Service Defn = YES
This profile option enables the Personalize Page functionality in Oracle self-service pages.
When set to YES, users with appropriate responsibilities will see the “Personalize Page” link at the top of OAF pages.
What It Allows You To Do
The Personalize Page feature allows administrators to:
- Hide or show regions
- Modify prompts and labels
- Change item properties
- Add conditions for rendering
- Control behavior based on responsibility, user, or function
Why It’s Important
Without this profile option, the OAF personalization framework cannot be accessed from the UI.
Once enabled, you can inspect page components such as:
- Region IDs
- Item IDs
- Message fields
- Buttons
- Tables
This is essential when implementing UI-level customizations without modifying underlying code.
2. FND: Personalization Region Link Enabled = YES
This profile option exposes a direct personalization link on each region of an OAF page.
When enabled, Oracle adds small Personalize links/icons next to page regions.
What It Does
Instead of navigating through the full page hierarchy, this option allows you to:
- Jump directly to personalization for a specific region
- Identify region names quickly
- Edit only the relevant part of the page
Benefits
This is particularly useful on complex pages with many nested regions, such as procurement or HR pages.
Without this option, locating the correct region within the full page hierarchy can take significantly longer.
3. Disable Self-Service Personal = NO (Site Level)
This profile option controls whether self-service personalization is allowed at all.
Behavior
- YES → Personalizations are disabled
- NO → Personalizations are allowed
Why It Matters
Even if personalization options are enabled elsewhere, the Personalize Page link will not appear if this profile option is set to YES.
For personalization to work correctly, it must remain:
Disable Self-Service Personal = NO
This option is typically controlled at the Site level.
4. FND: Diagnostics = YES
This is one of the most useful profile options for administrators and developers.
When enabled, it activates the Diagnostics menu in the upper-right corner of OAF pages.
Diagnostic Tools Provided
The Diagnostics menu provides access to several useful tools, including:
- About This Page
- Page Hierarchy
- Item Properties
- Region Information
- Controller Details
- Application Module Details
About This Page
The About This Page option is one of the most important diagnostic features.
It displays:
- Page path
- Controller class
- Application module
- Page hierarchy
- Region IDs
- Item IDs
- Parameter values
Example information you might see:
/oracle/apps/po/req/webui/ReqSummaryPG
This information helps developers understand exactly how a page is structured.
Additional Diagnostics for Oracle Forms
While the previous profile options mainly apply to OAF pages, they also unlock useful tools when working with Oracle Forms.
When FND: Diagnostics = YES is enabled, an additional Diagnostics option becomes available in the Forms menu.
Accessing Diagnostics in Forms
In an Oracle Forms window:
Help → Diagnostics
Additional options may appear such as:
- Examine
- Trace
- Properties
- Custom Code
- Debug
The Examine Tool
The Examine feature is particularly useful.
It allows you to inspect runtime values such as:
- Form field values
- Block names
- Database items
- Profile values
- System variables
For example, you can check:
- Which database column a field is mapped to
- The block name and item name
- Current profile option values
This is extremely useful when debugging Oracle Forms behavior or identifying underlying table fields.
How to Enable These Profile Options
Profile options are typically managed from the System Administrator responsibility.
Step-by-Step Guide
- Log in to Oracle E-Business Suite
- Switch to the System Administrator responsibility
- Navigate to:
Profile → System
- In the Find System Profile Values window, search for the desired profile option.
Example:
FND: Diagnostics
- Query the profile option.
- Set the value at the User level (recommended).
- Save the changes.
Repeat this process for each profile option.
Recommended Setup for Troubleshooting
For troubleshooting and diagnostics, configure the following values:
| Profile Option | Value |
|---|---|
| Personalize Self-Service Defn | YES |
| FND: Personalization Region Link Enabled | YES |
| Disable Self-Service Personal | NO (Site level) |
| FND: Diagnostics | YES |
Important Recommendation: Enable Them for the User You Log In With
Although profile options can be set at multiple levels:
- Site
- Application
- Responsibility
- User
It is strongly recommended to enable these profile options only at the User level, specifically for the FND user account you are using to log into the environment.
Why This Is Recommended
Setting them at the User level ensures that:
- Only your session sees diagnostics and personalization tools
- Business users are not exposed to technical features
- Production environments remain secure
- Troubleshooting can be done safely
Typical Workflow
- Log in as your administrator account
- Enable the profile options for that user
- Log out of Oracle EBS
- Log back in
- Open the page or form you want to analyze
You will now see the Diagnostics and Personalize Page options available only for your account.
Best Practices
These profile options are powerful and should be used carefully.
Recommended practices:
- Enable them only for administrators or developers
- Prefer User-level configuration
- Avoid enabling diagnostics globally in production
- Use them temporarily during troubleshooting
- Document any personalizations created
Conclusion
These features make it much easier to troubleshoot issues, analyze page structures, inspect form fields, and implement personalizations without modifying underlying code.
For Oracle EBS developers, DBAs, and system administrators, mastering these diagnostics tools—and enabling them safely at the User level for the account you are logged in with—is an essential skill that can significantly simplify troubleshooting and customization tasks.
Oracle E-Business Suite provides powerful built-in tools for analyzing and customizing both OAF pages and Oracle Forms. By enabling profile options such as Personalize Self-Service Defn, FND: Personalization Region Link Enabled, Disable Self-Service Personal, and FND: Diagnostics, administrators can access detailed technical information directly from the UI.
