{"id":914,"date":"2026-03-06T11:42:51","date_gmt":"2026-03-06T11:42:51","guid":{"rendered":"https:\/\/forgefuse.wasmer.app\/?p=914"},"modified":"2026-03-06T11:42:51","modified_gmt":"2026-03-06T11:42:51","slug":"how-to-get-more-details-from-an-oracle-e-business-suite-oaf-page-or-form-window","status":"publish","type":"post","link":"https:\/\/forgefuse.wasmer.app\/index.php\/how-to-get-more-details-from-an-oracle-e-business-suite-oaf-page-or-form-window\/","title":{"rendered":"How to Get More Details from an Oracle E-Business Suite OAF Page or Form Window"},"content":{"rendered":"\n

When troubleshooting, analyzing functionality, or preparing customizations in Oracle E-Business Suite (EBS)<\/strong>, it\u2019s often necessary to inspect what is happening behind the scenes on a page or form. Oracle provides several built-in profile options<\/strong> that expose additional diagnostics, metadata, and personalization tools for Oracle Application Framework (OAF)<\/strong> pages and Oracle Forms.<\/p>\n\n\n\n

This article explains the most useful profile options, what they do, and how to enable them in Oracle EBS.<\/p>\n\n\n\n

\n\n\n\n

Why Enable Diagnostics and Personalization?<\/h4>\n\n\n\n

Oracle EBS uses two main UI technologies:<\/p>\n\n\n\n

    \n
  • Oracle Application Framework (OAF)<\/strong> \u2013 used for most Self-Service web pages<\/li>\n\n\n\n
  • Oracle Forms<\/strong> \u2013 used for many traditional transactional windows<\/li>\n<\/ul>\n\n\n\n

    These pages and forms contain internal components such as:<\/p>\n\n\n\n

      \n
    • Regions<\/li>\n\n\n\n
    • Items<\/li>\n\n\n\n
    • Controllers<\/li>\n\n\n\n
    • Application modules<\/li>\n\n\n\n
    • Blocks<\/li>\n\n\n\n
    • Fields<\/li>\n<\/ul>\n\n\n\n

      Normally, this technical information is hidden. By enabling specific profile options<\/strong>, administrators can expose this metadata directly in the UI.<\/p>\n\n\n\n

      This is extremely useful when:<\/p>\n\n\n\n

        \n
      • Creating OAF personalizations<\/strong><\/li>\n\n\n\n
      • Debugging UI issues<\/li>\n\n\n\n
      • Identifying region\/item IDs<\/strong><\/li>\n\n\n\n
      • Investigating form fields and blocks<\/li>\n\n\n\n
      • Preparing custom extensions<\/strong><\/li>\n\n\n\n
      • Working with Oracle Support<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        Key Profile Options to Enable<\/h4>\n\n\n\n

        The following profile options should be enabled to access extended diagnostics and personalization functionality.<\/p>\n\n\n\n

        \n\n\n\n

        1. Personalize Self-Service Defn = YES<\/h5>\n\n\n\n

        This profile option enables the Personalize Page<\/strong> functionality in Oracle self-service pages.<\/p>\n\n\n\n

        When set to YES<\/strong>, users with appropriate responsibilities will see the “Personalize Page”<\/strong> link at the top of OAF pages.<\/p>\n\n\n\n

        What It Allows You To Do<\/h6>\n\n\n\n

        The Personalize Page feature allows administrators to:<\/p>\n\n\n\n

          \n
        • Hide or show regions<\/li>\n\n\n\n
        • Modify prompts and labels<\/li>\n\n\n\n
        • Change item properties<\/li>\n\n\n\n
        • Add conditions for rendering<\/li>\n\n\n\n
        • Control behavior based on responsibility, user, or function<\/li>\n<\/ul>\n\n\n\n
          Why It\u2019s Important<\/h6>\n\n\n\n

          Without this profile option, the OAF personalization framework cannot be accessed<\/strong> from the UI.<\/p>\n\n\n\n

          Once enabled, you can inspect page components such as:<\/p>\n\n\n\n

            \n
          • Region IDs<\/li>\n\n\n\n
          • Item IDs<\/li>\n\n\n\n
          • Message fields<\/li>\n\n\n\n
          • Buttons<\/li>\n\n\n\n
          • Tables<\/li>\n<\/ul>\n\n\n\n

            This is essential when implementing UI-level customizations without modifying underlying code<\/strong>.<\/p>\n\n\n\n

            \n\n\n\n
            2. FND: Personalization Region Link Enabled = YES<\/h5>\n\n\n\n

            This profile option exposes a direct personalization link on each region<\/strong> of an OAF page.<\/p>\n\n\n\n

            When enabled, Oracle adds small Personalize links\/icons next to page regions<\/strong>.<\/p>\n\n\n\n

            What It Does<\/h6>\n\n\n\n

            Instead of navigating through the full page hierarchy, this option allows you to:<\/p>\n\n\n\n

              \n
            • Jump directly to personalization for a specific region<\/strong><\/li>\n\n\n\n
            • Identify region names quickly<\/li>\n\n\n\n
            • Edit only the relevant part of the page<\/li>\n<\/ul>\n\n\n\n
              Benefits<\/h6>\n\n\n\n

              This is particularly useful on complex pages with many nested regions, such as procurement or HR pages.<\/p>\n\n\n\n

              Without this option, locating the correct region within the full page hierarchy can take significantly longer.<\/p>\n\n\n\n

              \n\n\n\n
              3. Disable Self-Service Personal = NO (Site Level)<\/h5>\n\n\n\n

              This profile option controls whether self-service personalization is allowed at all.<\/p>\n\n\n\n

              Behavior<\/h6>\n\n\n\n
                \n
              • YES<\/strong> \u2192 Personalizations are disabled<\/li>\n\n\n\n
              • NO<\/strong> \u2192 Personalizations are allowed<\/li>\n<\/ul>\n\n\n\n
                Why It Matters<\/h6>\n\n\n\n

                Even if personalization options are enabled elsewhere, the Personalize Page<\/strong> link will not appear if this profile option is set to YES<\/strong>.<\/p>\n\n\n\n

                For personalization to work correctly, it must remain:<\/p>\n\n\n\n

                Disable Self-Service Personal = NO<\/code><\/pre>\n\n\n\n
                This option is typically controlled at the Site level<\/strong>.<\/p>\n\n\n\n
                \n\n\n\n
                4. FND: Diagnostics = YES<\/h5>\n\n\n\n
                This is one of the most useful profile options for administrators and developers.<\/p>\n\n\n\n
                When enabled, it activates the Diagnostics menu<\/strong> in the upper-right corner of OAF pages.<\/p>\n\n\n\n
                Diagnostic Tools Provided<\/h6>\n\n\n\n
                The Diagnostics menu provides access to several useful tools, including:<\/p>\n\n\n\n
                  \n
                • About This Page<\/strong><\/li>\n\n\n\n
                • Page Hierarchy<\/strong><\/li>\n\n\n\n
                • Item Properties<\/strong><\/li>\n\n\n\n
                • Region Information<\/strong><\/li>\n\n\n\n
                • Controller Details<\/strong><\/li>\n\n\n\n
                • Application Module Details<\/strong><\/li>\n<\/ul>\n\n\n\n
                  About This Page<\/h6>\n\n\n\n
                  The About This Page<\/strong> option is one of the most important diagnostic features.<\/p>\n\n\n\n
                  It displays:<\/p>\n\n\n\n
                    \n
                  • Page path<\/li>\n\n\n\n
                  • Controller class<\/li>\n\n\n\n
                  • Application module<\/li>\n\n\n\n
                  • Page hierarchy<\/li>\n\n\n\n
                  • Region IDs<\/li>\n\n\n\n
                  • Item IDs<\/li>\n\n\n\n
                  • Parameter values<\/li>\n<\/ul>\n\n\n\n
                    Example information you might see:<\/p>\n\n\n\n
                    \/oracle\/apps\/po\/req\/webui\/ReqSummaryPG<\/code><\/pre>\n\n\n\n
                    This information helps developers understand exactly how a page is structured.<\/p>\n\n\n\n
                    \n\n\n\n
                    Additional Diagnostics for Oracle Forms<\/h4>\n\n\n\n
                    While the previous profile options mainly apply to OAF pages<\/strong>, they also unlock useful tools when working with Oracle Forms<\/strong>.<\/p>\n\n\n\n
                    When FND: Diagnostics = YES<\/strong> is enabled, an additional Diagnostics<\/strong> option becomes available in the Forms menu.<\/p>\n\n\n\n
                    Accessing Diagnostics in Forms<\/h5>\n\n\n\n
                    In an Oracle Forms window:<\/p>\n\n\n\n
                    Help \u2192 Diagnostics<\/code><\/pre>\n\n\n\n
                    Additional options may appear such as:<\/p>\n\n\n\n
                      \n
                    • Examine<\/strong><\/li>\n\n\n\n
                    • Trace<\/strong><\/li>\n\n\n\n
                    • Properties<\/strong><\/li>\n\n\n\n
                    • Custom Code<\/strong><\/li>\n\n\n\n
                    • Debug<\/strong><\/li>\n<\/ul>\n\n\n\n
                      The Examine Tool<\/h5>\n\n\n\n
                      The Examine<\/strong> feature is particularly useful.<\/p>\n\n\n\n
                      It allows you to inspect runtime values such as:<\/p>\n\n\n\n
                        \n
                      • Form field values<\/li>\n\n\n\n
                      • Block names<\/li>\n\n\n\n
                      • Database items<\/li>\n\n\n\n
                      • Profile values<\/li>\n\n\n\n
                      • System variables<\/li>\n<\/ul>\n\n\n\n
                        For example, you can check:<\/p>\n\n\n\n
                          \n
                        • Which database column<\/strong> a field is mapped to<\/li>\n\n\n\n
                        • The block name<\/strong> and item name<\/strong><\/li>\n\n\n\n
                        • Current profile option values<\/strong><\/li>\n<\/ul>\n\n\n\n
                          This is extremely useful when debugging Oracle Forms behavior or identifying underlying table fields.<\/p>\n\n\n\n
                          \n\n\n\n
                          How to Enable These Profile Options<\/h4>\n\n\n\n
                          Profile options are typically managed from the System Administrator responsibility<\/strong>.<\/p>\n\n\n\n
                          Step-by-Step Guide<\/h4>\n\n\n\n
                            \n
                          1. Log in to Oracle E-Business Suite<\/strong><\/li>\n\n\n\n
                          2. Switch to the System Administrator<\/strong> responsibility<\/li>\n\n\n\n
                          3. Navigate to:<\/li>\n<\/ol>\n\n\n\n
                            Profile \u2192 System<\/code><\/pre>\n\n\n\n
                              \n
                            1. In the Find System Profile Values<\/strong> window, search for the desired profile option.<\/li>\n<\/ol>\n\n\n\n
                              Example:<\/p>\n\n\n\n
                              FND: Diagnostics<\/code><\/pre>\n\n\n\n
                                \n
                              1. Query the profile option.<\/li>\n\n\n\n
                              2. Set the value at the User level<\/strong> (recommended).<\/li>\n\n\n\n
                              3. Save the changes.<\/li>\n<\/ol>\n\n\n\n
                                Repeat this process for each profile option.<\/p>\n\n\n\n
                                \n\n\n\n
                                Recommended Setup for Troubleshooting<\/h4>\n\n\n\n
                                For troubleshooting and diagnostics, configure the following values:<\/p>\n\n\n\n
                                Profile Option<\/th>Value<\/th><\/tr><\/thead>
                                Personalize Self-Service Defn<\/td>YES<\/td><\/tr>
                                FND: Personalization Region Link Enabled<\/td>YES<\/td><\/tr>
                                Disable Self-Service Personal<\/td>NO (Site level)<\/td><\/tr>
                                FND: Diagnostics<\/td>YES<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                \n\n\n\n
                                Important Recommendation: Enable Them for the User You Log In With<\/h4>\n\n\n\n
                                Although profile options can be set at multiple levels:<\/p>\n\n\n\n
                                  \n
                                • Site<\/li>\n\n\n\n
                                • Application<\/li>\n\n\n\n
                                • Responsibility<\/li>\n\n\n\n
                                • User<\/li>\n<\/ul>\n\n\n\n
                                  It is strongly recommended to enable these profile options only at the User level<\/strong>, specifically for the FND user account you are using to log into the environment<\/strong>.<\/p>\n\n\n\n
                                  Why This Is Recommended<\/h5>\n\n\n\n
                                  Setting them at the User level<\/strong> ensures that:<\/p>\n\n\n\n
                                    \n
                                  • Only your session sees diagnostics and personalization tools<\/li>\n\n\n\n
                                  • Business users are not exposed to technical features<\/li>\n\n\n\n
                                  • Production environments remain secure<\/li>\n\n\n\n
                                  • Troubleshooting can be done safely<\/li>\n<\/ul>\n\n\n\n
                                    Typical Workflow<\/h5>\n\n\n\n
                                      \n
                                    1. Log in as your administrator account<\/li>\n\n\n\n
                                    2. Enable the profile options for that user<\/strong><\/li>\n\n\n\n
                                    3. Log out of Oracle EBS<\/li>\n\n\n\n
                                    4. Log back in<\/li>\n\n\n\n
                                    5. Open the page or form you want to analyze<\/li>\n<\/ol>\n\n\n\n
                                      You will now see the Diagnostics<\/strong> and Personalize Page<\/strong> options available only for your account.<\/p>\n\n\n\n
                                      \n\n\n\n
                                      Best Practices<\/h5>\n\n\n\n
                                      These profile options are powerful and should be used carefully.<\/p>\n\n\n\n
                                      Recommended practices:<\/p>\n\n\n\n
                                        \n
                                      • Enable them only for administrators or developers<\/strong><\/li>\n\n\n\n
                                      • Prefer User-level configuration<\/strong><\/li>\n\n\n\n
                                      • Avoid enabling diagnostics globally in production<\/li>\n\n\n\n
                                      • Use them temporarily during troubleshooting<\/strong><\/li>\n\n\n\n
                                      • Document any personalizations created<\/li>\n<\/ul>\n\n\n\n
                                        \n\n\n\n
                                        Conclusion<\/h4>\n\n\n\n
                                        These features make it much easier to troubleshoot issues, analyze page structures, inspect form fields, and implement personalizations without modifying underlying code.<\/p>\n\n\n\n
                                        For Oracle EBS developers, DBAs, and system administrators, mastering these diagnostics tools\u2014and enabling them safely at the User level for the account you are logged in with<\/strong>\u2014is an essential skill that can significantly simplify troubleshooting and customization tasks.<\/p>\n\n\n\n
                                        Oracle E-Business Suite provides powerful built-in tools for analyzing and customizing both OAF pages<\/strong> and Oracle Forms<\/strong>. By enabling profile options such as Personalize Self-Service Defn<\/strong>, FND: Personalization Region Link Enabled<\/strong>, Disable Self-Service Personal<\/strong>, and FND: Diagnostics<\/strong>, administrators can access detailed technical information directly from the UI.<\/p>\n","protected":false},"excerpt":{"rendered":"
                                        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.<\/p>\n","protected":false},"author":1,"featured_media":915,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":19,"footnotes":""},"categories":[2,18],"tags":[19,15],"class_list":["post-914","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-article","category-orace-e-business-suite","tag-e-business-suite","tag-oracle"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/posts\/914","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/comments?post=914"}],"version-history":[{"count":0,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/posts\/914\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/media\/915"}],"wp:attachment":[{"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/media?parent=914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/categories?post=914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forgefuse.wasmer.app\/index.php\/wp-json\/wp\/v2\/tags?post=914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}