quitar personalizacion

7/30/2019 Quitar Personalizacion

1/5

Como quitar una Personalizacion ID 304670.1

Goal

You created a personalization using the Personalization UI provided

with OA Framework. You followed the OA Framework Personalization & Extensibility Guide

Note 236618.1 (OA Framework Personalization and ExtensibilityGuide: Version 5.7+)

However, after creating the personalization, the page is no longeraccessible and you need to back-out or remove thispersonalization to allow access to the page.

Fix

There are a few methods to remove the 'faulty' personalization fromthe OA Framework page.

Introduction:

Before starting to delete personalizations it's useful to understandsome background how these are stored in Applications. All pagedefinitions for OAF pages are stored as (XML) document in the MDSrepository (located in the database). The reference to this is adocument name with following format:

/oracle/apps///

For example the Home Page document name is:

/oracle/apps/fnd/framework/navigate/webui/HomePG

When creating personalizations in the OAF page the above mentioneddocument is not changed. Instead a separate document is created inthe MDS repository containing the personalization(s) done. For each'level' of personalization one document is stored with following format

/

oracle/apps///customizations///

For example for the OA Framework home page the following documentmay exist Personalizations made at SITE level are saved in followingdocument

/

oracle/apps/fnd/framework/navigate/webui/customizations/site/0/Ho

mePG

Personalizations made for Function = OAHOMEPAGE are saved in
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=236618.1https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=236618.1


2/5

following document

/

oracle/apps/fnd/framework/navigate/webui/customizations/function/

OAHOMEPAGE/HomePG

Personalizations made for Organization = 204 are saved in followingdocument

/

oracle/apps/fnd/framework/navigate/webui/customizations/org/204/H

omePG

Beware that each document may include multiple personalizationactions. When adding a personalization at SITE level the customizationdocument for that level is updated. This makes that if adding a specificpersonalization introduces a problem and the personalizationdocument is deleted also all other personalizations made at that level

will be lost!!

Method 1 - Using responsibility Functional Administrator >Personalization (OA Framework 5.10+)

This is the recommended method to remove personalization (if it's notpossible to access the OAF page anymore). It uses the default pagesfor maintaining personalization and only affects the OAF page involved.1) Login to Oracle Applications as SYSADMIN2) Select Functional

Administrator [resp] > Personalization [tab]3) Fill in the criteria tolocate the OA Framework page and press Go Tip: Check'Personalized' checkbox to only query the pages having apersonalization4) Identify the correct page from the results returned5)Depending on the situation you have following options: Cause offailure is known (e.g. last change made) and can be removed

Click pencil "Personalize Page" and confirm personalization levels. Revert the personalization step causing the problem Apply the changes

Retest if the page is now accessible again.Cause of the failure is unknown or can not be simply removed

Click pencil "Manage Personalizations" Now Deactivate or Delete the personalization document (*)(*) The difference between Deactivate and Delete is that in the case ofDeactivating the personalization document in the MDS repository is notremoved, while this is the case for Delete. Especially when there are


3/5

multiple personalization documents, but it's not clear which causes theproblem the 'Deactivate' allows these to be tested individually withoutthe need to reload or recreate the personalization documents.

Method 2 - Temporary disable all Personalizations

In case it's not possible to determine the exact document name of theOAF page failing the following method can be used. The caveat of thismethod however is that during the change of profile option mentionedthis makes *all* personalizations will be disabled so will also affectother pages. So only to be used on TEST environment or duringmaintenance window for PROD environment.1) Login to OracleApplications as SYSADMIN and select System Administrator [resp] >Profile - System2) Update the Profile Option: "Disable Self-ServicePersonal" = YES This can be set at SITE and APPLICATION level3)

Navigate to the OAF page personalized (may be done using anotheruser) It should now open since personalizations are not taken intoaccount4) Enter the personalization UI using the 'Personalize' link 5)Depending on the situation you have following options: Cause ofthe failure is known (e.g. last change made)

Revert the personalization step causing the problem Apply the changes

Cause of the failure is unknown

Click pencil "Manage Personalizations" Now Deactivate or Delete the personalization document (*)(*) The difference between Deactivate and Delete is that in the case ofDeactivating the personalization document in the MDS repository is notremoved, while this is the case for Delete. Especially when there aremultiple personalization documents, but it's not clear which causes theproblem the 'Deactivate' allows these to be tested individually withoutthe need to reload or recreate the personalization documents. 6) Loginagain and select System Administrator responsibility7) Update theProfile Option: "Disable Self-Service Personal" = NO (for the level it wasset to YES)8) Retest the OAF page is rendered fine again

Method 3 - Removing personalization document in thedatabase using JDR_UTILS package

This method only requires access to the database and must be usedwith great care to ensure the correct document is deleted. For thismethod you need to know the document name of the OAF page with


4/5

the personalization (See Introduction section)1) Login to SQLPlus asAPPS user2) Run the following commands to show the availablepersonalization documents

SQL> set serverout on;

SQL> execjdr_utils.listcustomizations('/oracle/apps///');

e.g.

SQL> exec

jdr_utils.listcustomizations('/oracle/apps/fnd/framework/navigate

/webui/HomePG');

3) This returns the documentnames of the personalization documentfor this OAF page. For example for SITE level on Homepage

/oracle/apps/fnd/framework/navigate/webui/customizations/site/0/Ho

mePG

4) Backup the personalization document by exporting it to a file (so itcan be reloaded if needed). Make sure you are backing up the correctdocument. It should have "/customizations/" in the document name.From the web server, use the OS command:

adjava -mx128m -nojit

oracle.jrad.tools.xml.exporter.XMLExporter \

/

oracle/apps///customizations/// / \

-username apps \

-password \

-dbconnection "(description=(address_list=(ADDRESS=(PROTOCOL=TCP)

(HOST=)(PORT=)))(CONNECT_DATA=(SID=)))" \

-rootdir /tmp

This create an XML document in the /tmp directory, like

/

tmp/oracle/apps////

/.xml

5) Delete the personalization document. Be VERY careful you aredeleting the personalization and not the base document !

SQL> exec

jdr_utils.deletedocument('/oracle/apps///

customizations///');

For the home page example this is:


5/5

SQL> exec

jdr_utils.deletedocument('/oracle/apps/fnd/framework/navigate/web

ui/customizations/site/0/HomePG');

6) Restart Apache to ensure that Java caching is cleared7) Retest theissue and confirm that OAF page is not accessible again 8) To restore

the personalization document deleted, use the command (optional)

-adjava -mx128m -nojit oracle.jrad.tools.xml.importer.XMLImporter

\

/

tmp/oracle/apps////

/.xml \

-username apps \

-password apps \

-dbconnection "(description=(address_list=(ADDRESS=(PROTOCOL=TCP)

(HOST=)(PORT=)))(CONNECT_DATA=(SID=)))" \

-rootdir /tmp

quitar personalizacion

Documents