There are certain profiles options related to personalization.

1) Personalize Self-Service Defn : In order to do Personalization this profile has to set

to "Yes" at appropriate level.

After setting this a "Personalize Page" link will appear in the global menu (top and
bottom of page). User can click on this page and do Personalization.

2) FND: personalization region Link Enabled : If you set this profile value to "Yes"
and "Personalize Self-Service Defn" is also "Yes" the you can do Personalization at
region level.
3) Disable Self-Service Personal : If you set to "Yes" at Site level all the OA
Framework Extensions will be disabled.If you set to "Yes" at Application level then
Personalization related to localization will be disabled.
Personalization doesn't require single piece of coding.Through Personalization we can
achieve following things.

 Changing web bean properties like Tip,Label,Rendered,Read-only etc..

 Changing order of fields
 Adding new beans like button,drop down list,lov etc...
 Embedding other regions
Here I will explain how to do Personalization with an example.We are going to
personalize the standard Supplier creation page.The requirement matrix is as follows.

Responsibility
Fields
Payables Manager Payables, Vision Operations(USA)
Inactive Date Show Hide

Hold From Payment Show Hide

Alias Hide Hide

Navigation : Payables Manager>Suppliers>Entry

Identify Pages to be personalized
First thing we have to do is to identify the pages to be Personalized.For this identify the
page(s) in which field resides.After that click on the "About this Page" link in the bottom
of the page.

a) Inactive Date is spanned across two pages.So we have to personalize both.So the
pages identified are as follows
 /oracle/apps/pos/supplier/webui/QuickUpdatePG
/oracle/apps/pos/supplier/webui/OrganizationPG
b) For Hold From Payment

/oracle/apps/pos/supplier/webui/QuickUpdatePG
/oracle/apps/pos/supplier/webui/ByrInvPG
c) For Alias

/oracle/apps/pos/supplier/webui/QuickUpdatePG
Idenfify the level of Personalization
Second thing we have to do is to identify the level of Personalization.In our scenario we
have to personalize in two levels.

Field Level of Personalization

Inactive Date Responsibility

Hold From Payment Responsibility

Alias Site

Personalize the page

We can personalize a page in two ways.
 Click on Personalize Page link in the global menu.
 Go to Functional Administrator responsibility.Click
on Personalization tab.Give Document Path.Click on Personalize Page

Making Inactive Date as rendered false

 Click on Personalize link
of /oracle/apps/pos/supplier/webui/QuickUpdatePG
 For Inactive Date we are going to hide this bean in Payables, Vision
Operations (USA)reponsibility.So check the context in the personalize
page.If the responsibility is different choose appropriate responsibility

 Click on Expand All

 Locate the Inactive Date in the page.Press Personalize

 Change the Rendered property at Responsibility level to false

  Press Apply and in the next page.After that press "Return to
Application"
Inactive Date personalization is completed for QuickUpdatePG.
Same way complete personalization of Inactive
Date for /oracle/apps/pos/supplier/webui/OrganizationPG.
Making Hold From Payment as rendered false
Repeat the same steps as above
for /oracle/apps/pos/supplier/webui/QuickUpdatePGand /oracle/apps/pos/supplier/
webui/ByrInvPG.
Hiding Alias
Change the Rendered property to false in Site level.

QuickUpadtePG Before Personalization

QuickUpadtePG After Personalization
View through Payables, Vision Operations (USA)

b) User Level Personalization s: OAF allows end users to creates views on top of
standard search regions.These type of views are called User Level Personalizations.
Migrating Personalizations
Following steps we need to perform to migrate Personalization from one instance to
another.
Events in source instance.
 Set profile option "FND: Personalization Document Root Path"
appropriatly before exporting personalization.
 Go to Functional Administrator.Click on Personalization tab.
 Under Import/Export click on Personalization Repository.
 Give Document Root Path as "/oracle/apps/pos/supplier/webui" and
press Go.Page will display all the Personalizations.
 Select all the listed Personalization s which you want to export and
press Export to File System.
  Go to the path in "FND: Personalization Document Root Path" and run
" tar -cvf xxPersonalizations.tar ./* ".
 Transfer the xxPersonalizations.tar to destination in Binary mode.
Events in destination instance.
 Set profile option "FND: Personalization Document Root Path"
appropriately before importing Personalizations.
 Copy .tar file to middle tier directory pointed by "FND: Personalization
Document Root Path".
 Run " tar -xvf xxPersonalizations.tar ".
 Go to Functional Administrator.Click on Personalization tab.
 Under Import/Export click on Exported Personalizations.
 Click on Import from File System.

Note: Instead of using Functional Administrator you can user java

oracle.jrad.tools.xml.importer.XMLImporter also to upload Personalizations.
Release 11.5.10 provides a feature called Personalize Page, which gives us
the ability to customize the look and feel of the Self Service Applications.

Setting the Profile option Personalize Self-Service Defn to “Yes”, enables this
feature. If it is set to “No”, the Personalize Page link will not be seen
prohibiting you from customizing the self-service page.

There are other profile options that need to be turned on depending on the
personalizations required.

FND: Personalization Region Link Enabled = Yes

FND: Personalization WYSIWYG Enabled = Yes

Personalizations allow you to make changes at various levels:

Function: One can define functions and can define granular level
personalization based upon these functions.

Site: Personalizations that affect all users with access to the given
application component.

Operating Unit: Personalizations that affect all users with access to the given
operating unit.

Responsibility: Personalizations that affect all users with access to the given
responsibility.

Some of the customizations that can be achieved using Personalization:

In all our examples we will be considering iExpense self –service Application.

1) To remove the Cash and Other Expenses Link from the Navigation train
(Road Map) on

General Information Entry Page

 Navigate to the General Information Entry Page

 Click on “Personalize Page” on the right hand corner of the page (shown
in the above screenshot).
 You will see the following page come up. Select the Complete View Radio
button.
 Scroll down to the “Location” Section

 Click the Pencil Icon next to “Link: Cash and Other Expenses”
 Set the Personalization Property “Rendered” to “False” at the
Responsibility Level
 Click on Apply to save the changes.
 On returning back to the Application, you will see that the Cash and Other
Expenses link is hidden from the Navigation Train.

 Add the below Text to Cash and Other Expenses page:

 Cash, Mileage and other out of pocket expenses will not be processed for
payment in iExpenses after December 17th, 2008. Please use SAP system
to enter such expenses.

 Navigate to the Cash and Other Expenses Page and click on “Personalize
Page” on the right hand corner of the page.
 You will see the following page come up. Select the Complete View Radio
button.

 Scroll down to the “Page Layout” Section and click on Create Item Icon
next to it.

 Enter the Following information:

Select the Item Style as “Formatted Text”.

Specify a name for this item in the field ID.

Enter CSS Class as OraErrorNameText to display the text in Red Color.

Text as Cash, Mileage and other out of pocket expenses will not be
processed for payment in iExpenses after December 17th, 2008. Please
use SAP system to enter such expenses
 Click Apply to save the changes.
 Reorder an item: By default, the above text would be displayed at the
bottom of the page. To bring it to the top, click Reorder icon next to
“Page Layout”
 Select the Personalize Radio button under Responsibility section

 Move the item that has been created to the first position using the Arrow
to the right
 Click Apply button to save the changes.
 On returning to the application, you will see the text is displayed as seen
below,

 Hide the Receipt Based Expenses table to prevent the user from entering
any expenses in this section.
 Navigate to the Cash and Other Expenses Page and click on “Personalize
“use this table to enter receipt-Based Expenses” under the Receipt-Based
Expenses Header.
 You will see the following page come up. Select the Complete View Radio
button. Click on the Pencil icon next to the “Table: Use this table to …”

 Set the Personalization Properties “Rendered” to False at the

responsibility level.
 Click on Apply to save the changes.
 On returning to the application, you will see that the Receipt based
Expenses table is hidden

Similarly anything could be hidden (Buttons, column etc) by setting its

property “Rendered” to “False”.
 To Make the field “Expense Cost Center” Read only in the General
Information Page:
 Navigate to the General Information Entry Page

 Click on “Personalize Page” on the right hand corner of the page (shown
in the above screenshot).
 You will see the following page come up. Select the Complete View Radio
button.
 Scroll down to the Name “Message Text Input: Expense Cost Center” and
click on the Pencil icon next to it.

 Set the property “Read only” to True at the responsibility level. Click on
apply to save the changes.

 Upon returning to the application, you will see that the Expense cost
Center filed has been made Read only making it non-updatable.
 To change the Field Name Purpose to Expenses Justification in General
Information Page.
 Navigate to the General Information Entry Page

 Click on “Personalize Page” on the right hand corner of the page (shown
in the above screenshot).
 You will see the following page come up. Select the Complete View Radio
button.
 Scroll down to the Name “Message Text Input: Purpose” and click on the
Pencil icon next to it.

 Change the Property “Prompt” to “Expenses Justification” at responsibility

level and click on Apply to save the changes.

 Upon returning to the application, you will see that the field name is
changed.
Similarly, the display name could be changed for buttons and other objects
too.