Once Personalization is done in the
development environment they can be migrated to another instance without redoing
them. For each screen personalized, xml files are created with the Personalization information. These can be migrated using the following steps.
Export Personalization
All the Personalization needs to be exported from the development instance using the
following steps.
i. Set ‘FND:
Personalization Document Root Path’ to desired location in the application
server.
ii. Bounce the Apache.
iii. Log on to
Functional Administrator à
Home à Personalization
Tab à Import/Export à Personalization
Repository
iv. Date filters and
application filters could be used to narrow down the search.
v. Select the
personalization that needs to be migrated. (Hint – Do not select the complete
list. Ensure that only the required personalization are exported to avoid any
wanted items going into the other instance)
vi. Click Export to
File System button
Establish Mapping
For
the responsibility level personalization, the export option creates the folder
name with the responsibility id in the source instance. This does not work in
the target instance with the same name because the target instance may have a
different responsibility id.
i. Open the folders
under ‘/oracle/apps/per/customizations/responsibility/’
ii. Rename the folders
with the corresponding responsibility id from the target instance
iii. Repeat this for all
modules and screens
Import the
personalization in the target instance by doing the following steps.
i. Set ‘FND:
Personalization Document Root Path’ to desired location in the application
server.
ii. Bounce the Apache.
iii. Move the dump from
step 2 to this folder. Make sure all the folders are intact as they were from
source system.
iv. Log on to
Functional Administrator à
Home à Personalization
Tab à Import/Export à Exported
Personalization
v. The folder
structure that is copied in step iii should appear
vi. Select all or the
desired folders/files
vii. Click Import form
File System.
