You should not personalize a configurable page by accessing it from the Functional Administrator Responsibility. Your configurable page might contain controller code that is dependent on certain parameters that are available only when the page itself is launched from its intended flow, and the page might fail with unexpected errors.
You can tell that your page is a configurable page if you attempt to access it from the Functional Administrator home page and the Page Layout Personalization page appears. You should instead run the actual page in Oracle E-Business Suite and initiate the Personalization UI from the global Personalize Page link, on the rendered page. You can then personalize it using the Page Layout Personalization page.
Note: This restriction applies only to configurable pages whose flexibleLayout and flexibleContent regions are defined in their base metadata. This restriction does not apply to pages that start out as non-configurable, but are later personalized by administrators who add new flexibleLayout and flexibleContent regions using the Create Item page in the Personalization UI. The Functional Administrator Responsibility always displays the Page Hierarchy Personalization page when it launches personalizations for these pages that have been made configurable via prior personalizations.
If the controller of your configurable page depends on URL parameters and you select the Personalize Page link to personalize the configurable page, the Page Layout Personalization page will retain those URL parameters. As a result, when you select the Return to Application link to return to the configurable page, the URL parameters will be made available again to the configurable page's controller.