Most of developer always struggle when ever it come to migration of form personalization component, beacuse of limitation of full access in Production box. Therefore, It's better to use oracle seeded Migration tool FNDLOAD.
Once you created and done testing for personalizations in your development/test instance, you can move them to production instances.
As discussed in last post , Personalization is per Function not per form therefore this can extracted by the loader on a per-function basis.
You should take a note that upon uploading, all prior personalizations for that function are first deleted, and then the contents of the loader file are inserted. So be careful..)
FNDLOAD - A pain killer for migration
you can either Download for a specific form or specfic function of the form. In both the case same affrmcus.lct is used.
Download -specific form< /STRONG>
FNDLOAD <userid>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct <filename.ldt> FND_FORM_CUSTOM_RULES
form_name=<form name>< /FONT>
Download -for all personalizations< /FONT>
FNDLOAD <userid>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct <filename.ldt> FND_FORM_CUSTOM_RULES function_name=<function name>< /FONT>
- Function_name is a required parameter
- You cann't download lct file with out any supplied value.
FNDLOAD <userid>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct xxapperiod.lct FND_FORM_CUSTOM_RULES form_name=APXSUMPS
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct xxapperiod.lct
Because the architecture has built-in support for all languages, you don’t translate ldt files, but instead you enter multiple Actions for different languages.