How to Extend an OAF Page in Oracle EBS Without Touching Seeded Code

Extend an OAF page the supported way

1. 1For layout, prompt or rendered changes, log in with Personalize Self-Service Defn, navigate to the page, and use About This Page > Personalize (or the Personalize Page link) to open the personalization hierarchy.
2. 2Add or override attributes such as Prompt, Rendered, Read Only or Required at the site, responsibility or user level; each is stored as an MDS customization document, not a code change.
3. 3For controller-level logic, create a Java class that extends the seeded controller, for example a class named with your XX prefix extending the original CO, implementing processRequest and processFormRequest with a call to super() first.
4. 4Register the new class as a Controller Extension against the region that uses the seeded controller through the Personalization UI, rather than editing the region's Controller property in the seeded page directly.
5. 5For a new field or attribute, extend the seeded View Object (create an Extended VO in JDeveloper and substitute it for the base VO usage on the Application Module) instead of modifying the base VO's XML.
6. 6Package the customization under your own top, for example XXCUST, mirroring the seeded object's package path under $XXCUST_TOP/mds and $XXCUST_TOP/oracle/apps with your XX prefix at the front.
7. 7Migrate MDS customizations between instances with the JPXImporter/JPXExporter utilities, keyed to the customization layer, site, organization or user, that the change was made at.

Extending VOs and EOs for new columns

Common pitfalls

• !Editing seeded page XML directly on the file system instead of using Personalization or MDS layers, which is overwritten by the next patch
• !Forgetting to call the super() method first in an extended controller, silently breaking base functionality
• !Using Substitution when Extension would have been enough, increasing future patch conflict risk
• !Mismatched package and directory structure under the custom top, causing a ClassNotFoundException at runtime
• !Not testing a personalization across all three levels, site, responsibility and user, before assuming it fully rolled out
• !Migrating MDS customizations with the wrong customization layer key, so the change never applies in the target instance