Custom
Posted on July 20, 2008. Filed under: Custom, DBA/Admin Tips, R12 | Tags: fndload, form, menu, responsibility |
Below are the commands
===========================
RESPONSIBILITY
===========================
For migrating a responsibility we need the responsibility key value.
Steps to get the RESPONSIBILITY KEY VALUE
Login as Sysadmin
System Administrator -> Security : Responsibility -> Define
Press F11 -> Enter the Responsibility Name -> Get the responsibility key value from the Responsibility Key Text Field.
To Download
FNDLOAD apps/[APPS_PWD] 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct [give some name].ldt FND_RESPONSIBILITY RESP_KEY=”[RESPONSIBILITY_KEY_VALUE]”
To Upload
FNDLOAD apps/[APPS_PWD] 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct [name given above].ldt
===========================
MENU
===========================
To Download
FNDLOAD apps/[APPS_PWD] 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct [give some name].ldt MENU MENU_NAME=”[MENU_NAME]”
To Upload
FNDLOAD apps/[APPS_PWD] 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct [name given above].ldt
=======================
FORMS PERSONALIZATIONS
=======================
For migrating the forms personalizations we need the function name that is associated with the form.
Steps to get the form function name (eg. Users Form)
Login as Sysadmin
System Administrator -> Security : User -> Define
Once the form opens up
On the Tool Bar Click Help -> Diagnostics -> Custom Code -> Personalize
This will open a new form with function name. This is the value we require.
You can perform simillar step for any form that you want to migrate by opening the form to be migrated.
To Download
FNDLOAD apps/[APPS_PWD] 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct [give some name].ldt FND_FORM_CUSTOM_RULES function_name=”[FUNCTION_NAME]”
To Upload
FNDLOAD apps/[APPS_PWD] 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct [give some name].ldt
=======================
PRINTER DEFINITIONS
=======================
You can follow this link for migrating printer definitions.
Happy Migrating !!!
cheers,
OraclePitStop.
Read Full Post |
Make a Comment ( 4 so far )
Posted on March 13, 2008. Filed under: Custom | Tags: Custom, schema, XX |
Have you ever wondered why custom schema names always start with ‘XX<some_name>’. Before getting into the detail lets see what happens if the custom schema name doesnt start with ‘XX’.
Impact: If you dont have a custom schema name starting with ‘XX’, be assured that this schema will be no longer available in your instance when you perform an UPGRADE. During upgrade Oracle apps will wipe out all unregistered schemas which doesnt start with ‘XX’.
Oracle had assured its customers that it will not touch any schemas that starts with ‘XX’. This is the reason why you find custom schema names with ‘XX’ prefixed.
cheers,
OraclePitStop
Read Full Post |
Make a Comment ( 6 so far )
OraclePitStop - Lets share some knowledge 