Scribd
Upload
40 views11 pages

OAFPersonalization

The document discusses personalization in OAF. Personalization allows modifying UI properties and fields. It is done by creating customizations stored in JDR tables. Lower level personalizations override higher levels. Personalizations can be migrated by exporting from one system and importing into another.

Uploaded by

Anu Chipurupally
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views11 pages

OAFPersonalization

The document discusses personalization in OAF. Personalization allows modifying UI properties and fields. It is done by creating customizations stored in JDR tables. Lower level personalizations override higher levels. Personalizations can be migrated by exporting from one system and importing into another.

Uploaded by

Anu Chipurupally
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

OAF Personalization

1
Outline

 About Personalization
 Sample Walkthrough
 Deployment of Personalization and Tables

2
About Personalization

 Used to modify UI Properties like enable/disable, readOnly, labelName Change


 Making field Required
 Applying CSS Properties
 Adding DFF Fields
 Used to create UI Components
 Personalizations done to the OA Framework are stored in the JDR% tables in the
database. The important part to note about creating personalization is that
once they are created, they do not get over written by patch application
 The way it works is, when an Oracle user accesses a page, the OA framework
first reads the original seeded page definition and then applies the
personalizations. As long as the underlying page definition is not changed
(Oracle rarely removes items from their pages), the personalizations will
remain intact.

3
Personalization Steps

 Set the value for following profiles


 “FND: Personalization Region Link Enabled” to Yes (Minimal will
also do but better to set Yes so that you get personalization links for
all the regions)
 “Personalize Self-Service Defn” to Yes
 “Disable Self-Service Personal” to No

4
Creating Personlization

 Once the profile options are set, personalizations can be


performed in multiple ways
 –Navigate to the self service page that needs the change
and click on the Personalize Page link.
 Or
 –Use the Functional Administrator responsibility, click the
Personalization tab and search for the document using the
document name.
 (Note: The document name may be alternatively obtained
by clicking on a Link “About this Page” at the bottom of
the self service page.
 To be able to see the About this Page link, the Profile
option FND: Diagnosticsshould be set to Yes at preferably
the user level, if not already set.)

5
Hierarchy

 •Personalization's at lower levels override


personalizations at higher levels
 • Values inherit the definition from the level
 immediately above unless changed
 • Order of precedence from highest to lowest:
 – Function ( Highest)
 – Site
 – Operating Unit
 – Responsibility (Lowest)

6
Personalization Migration

 Set profile option “FND: Personalization Document Root


Path”. The value of this profile option will be the
directory name on middle-tier.
 Ensure that this directory exists on mid-tier machine of
the destination environment

7
Source Environment Destination Environment
Login to Functional Administrator Set profile option “FND: Personalization
Responsibility Document Root Path”. The value of this profile
option will be the directory name on mid-tier
FTP the xxPersonalizations.tar to the directory
specific in above profile option

Navigate to tab “Personalization” Login to Functional Administrator


Responsibility

Click on Import/Export navigate to tab “Personalization”


Search the desired personalizations
for the application name Click on Import/Export

Extract the personalilzations Select and Import the personalizations that


have been imported

Login to linux/unix mid-tier and cd


to directory specified in profile
option
8
Do tar –cvf xxPersonalizations.tar ./*
Download The Personalization

 Functional Administrator → Personalization →


 Search the application which are personalized and to be
migrated to other instance.

9
JDR Tables/Packages

 jdr_utils.listdocuments('/oracle/apps/per', TRUE);

 jdr_utils.listcustomizations
(p_document
=> '/oracle/apps/per/irc/candidateSelfService/webui/RegCreateAccountPG');

 jdr_utils.printdocument
(p_document
=> '/oracle/apps/per/irc/candidateSelfService/server/customizations/site/0/Visit
orAM');

 jdr_utils.deletedocument(p_document
=> '/oracle/apps/per/irc/candidateSelfService/server/customizations/site/0/Visit
orAM');

10
JDR Tables

Table Details

Stores document paths, packages and there parent child


JDR_PATHS relationship.
Primary Key: PATH_DOCID

Stores components on documents and OA Framework pages.


JDR_COMPONENTS
Primary Key: COMP_DOCID, COMP_SEQ

Stores attribute/properties of components on documents and


JDR_ATTRIBUTES OA Framework pages.
Primary Key: ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ

Stores translated attribute values of document components or


JDR_ATTRIBUTES_TRAN OA framework pages.
S Primary Key: ATL_COMP_DOCID, ATL_LANG, ATL_COMP_REF,
ATL_NAME 11

You might also like