Oracle EBS OAF vs Forms Personalization

Oracle EBS OAF Personalization vs Forms Personalization – Understanding the Difference

Introduction
Oracle E-Business Suite (EBS) provides multiple ways to customize standard application behavior without modifying Oracle’s seeded code. Two of the most commonly used customization techniques are Forms Personalization and Oracle Application Framework (OAF) Personalization.

What is Forms Personalization?

Forms Personalization is a declarative customization feature used to modify the behavior of Oracle Forms without changing the underlying source code.

Typical Use Cases:

  • Default values
  • Mandatory fields
  • Hide/display fields
  • Enable/disable buttons
  • Warning messages
  • Execute custom PL/SQL
  • Launch forms
  • Validate user input

Example

Condition: Responsibility = Purchasing Super User
Action: Default Ship-To Organization = Chennai Plant

Where are Forms Personalizations Stored?

  • FND_FORM_CUSTOM_RULES
  • FND_FORM_CUSTOM_ACTIONS
  • FND_FORM_CUSTOM_SCOPES
  • FND_FORM_CUSTOM_PROP_LIST

What is OAF Personalization?

OAF Personalization customizes Oracle Self-Service web pages such as iProcurement, iSupplier, iExpenses, HR Self-Service, etc.

Common changes:

  • Hide regions
  • Rename labels
  • Make fields read-only
  • Mandatory fields
  • Rearrange layout

Accessing OAF Personalization

Path: Functional Administrator → Personalization → Personalize Page

Levels: Site, Organization, Responsibility, User

Forms vs OAF

Aspect Forms Personalization OAF Personalization
Technology Oracle Forms Web pages (OA Framework)
Storage Database metadata tables MDS repository
Logic Support Supports PL/SQL Primarily UI metadata changes

When to Use

Use Forms Personalization for Oracle Forms validations and logic. Use OAF Personalization for Self-Service UI customization.

Common Upgrade Mistakes

Many upgrade projects extract only Forms Personalizations and miss OAF Personalizations, leading to missing UI behavior after go-live.

Best Practices

  • Maintain an inventory of all personalizations
  • Document personalization levels
  • Remove obsolete customizations
  • Validate after patching
  • Prefer personalization over code customization

Real-World Lesson

During an Oracle EBS migration project, only Forms Personalizations were extracted initially. The client expected OAF Personalizations as well, reinforcing the need to review both customization types.

Key Takeaways

Forms and OAF Personalizations address different technologies. Both should be assessed during upgrades and migrations to ensure complete functionality.

Recent Posts