Found that, FNDCPASS fail to change the password for APPLSYS/APPS after upgrading to 12.0 and database from 10.2.0.2 to 11.1.0.6
Solution to the issue,
The database SEC_CASE_SENSITIVE_LOGON parameter defaults to TRUE. When this occurs the password sensitivity conversion does not occur. Passwords that are input as lower case are automatically updated as upper case. As a workaround set the parameter to FALSE in the init.ora, run autoconfig on application tiers and bounce the database.
Showing posts with label FND. Show all posts
Showing posts with label FND. Show all posts
Friday, 28 May 2010
Thursday, 27 May 2010
Db Linksare Lost After Changing Apps User Password FNDCPASS
After changing the Apps password using FNDCPASS, DB_Link gets invalid.
When you changed the apps password then all the db links should have the new APPS password, run the AutoConfig after changing the APPS password and this will update all, please note that there is no need to run adautoconfig each time you use FNDCPASS, only if you are changing any of the following users:
APPLSYS
APPS
APPS_MRC
APPLSYSPUB
PORTAL30 & PORTAL30_SSO
In case you are using Oracle Login Server and Portal 3.0.9 with E-Business Suite 11i
When you changed the apps password then all the db links should have the new APPS password, run the AutoConfig after changing the APPS password and this will update all, please note that there is no need to run adautoconfig each time you use FNDCPASS, only if you are changing any of the following users:
APPLSYS
APPS
APPS_MRC
APPLSYSPUB
PORTAL30 & PORTAL30_SSO
In case you are using Oracle Login Server and Portal 3.0.9 with E-Business Suite 11i
How to Change Applications R12 Passwords using Applications Schema Password Change Utility (FNDCPASS)
Oracle Applications provides a command line utility, FNDCPASS, to change/reset Oracle Applications schema passwords. This utility changes the password registered in Oracle Applications tables, changes the schema password in the database and can also change user passwords.
Note: You cannot change a schema name, such as APPLSYS or GL, after a product is installed, with FNDCPASS. Ensure that the entire Oracle Applications system has been shut down before changing any schema passwords. All users should log out and the Applications system should be down before running this utility.
If Oracle Applications user passwords are being changed then the relevant users should not be logged in.
Before changing any passwords, you should make a backup of the tables FND_USER and FND_ORACLE_USERID
A). To change the APPS and APPLSYS schema password:
Use the following command to change passwords for schemas that are used by shared components of Oracle Applications.
FNDCPASS < logon > 0 Y < system/password> SYSTEM < username > < new_password>
FNDCPASS uses the following arguments when changing the APPLSYS password. When specifying the SYSTEM token, FNDCPASS expects the next arguments to be the APPLSYS username and the new password.
Validates APPLSYS.
Re-registers password in Oracle Applications.
Changes the APPLSYS and all APPS passwords (for multi-APPS schema installations) to the same password.
Because everything with a Privilege Level [set to any of ('E', 'U', 'D')] in the FND_ORACLE_USERID table must always have the same password, FNDCPASS updates these passwords as well as APPLSYS's password.
For example, the APPS password will be updated when the APPLSYS password is changed.
ALTER USER is executed to change the ORACLE password for the above ORACLE users.
For instance, the following command changes the APPLSYS password to 'WELCOME'.
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME
Note: The SYSTEM token is used when changing the APPLSYS password.
B). To change an Oracle Applications schema password (other than APPS/APPLSYS):
Use this command to change the password of a schema provided by an individual product in Oracle Applications.
FNDCPASS 0 Y ORACLE < username> < new_password>
Note: The ORACLE token is used when changing an Oracle Applications schema password.
Use the above command with the following arguments. When specifying the ORACLE token, FNDCPASS expects the next arguments to be an ORACLE username and the new password.
FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1
C). To change all ORACLE schema passwords:
Use this command to change the passwords of all schemas provided by Oracle Applications products.
FNDCPASS < logon> 0 Y < system/password> ALLORACLE < new_password>
Use the above command with the following arguments. When specifying the ALLORACLE token, FNDCPASS expects the next argument to be the new password.
FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME
Note: The ALLORACLE token is used when changing all ORACLE schema passwords.
D). To change an Oracle Applications user's password:
Use this command to change an individual Oracle Applications user's password.
FNDCPASS < logon> 0 Y < system/password> USER < username> < new_password>
Note: The USER token is used when changing an Oracle Applications user password.
Use the above command with the following arguments. When specifying the USER token, FNDCPASS expects the next arguments to be an Oracle Applications username and the new password.
FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME
Using the FNDCPASS Utility:
Here is an example of changing an Oracle user's password, where is the Oracle schema name.
1. Use the FNDCPASS utility to change the password.
FNDCPASS < APPS username>/< APPS password> 0 Y \
< SYSTEM username>/< SYSTEM password> ORACLE < username> < new_password>
When changing the APPS or APPLSYS passwords, replace ORACLE with SYSTEM.
Note: Passwords for APPLSYS and the APPS schemas -- including the MRC schema -- must be the same. If you change the password for one, FNDCPASS automatically changes the others.
2. Update configuration files.
If you changed the APPS schema password (and APPLSYS) or the APPLSYSPUB password, update the following configuration files using AutoConfig (do not manually edit these files). They are used when connecting to Oracle Applications.
If you changed the APPS (and APPLSYS) password, update the password in this file:
• ORACLE_HOME/reports/server/CGIcmd.dat
If you changed the APPLSYSPUB password, update the password in these files:
• FND_TOP/resource/appsweb.cfg
• OA_HTML/bin/appsweb.cfg
• INST_TOP/admin/fnd/12.0.0/secure/< host_name>_< dbname>.dbc
Note: When changing APPS (or APPLSYS) and APPLSYSPUB passwords, do not restart the system until the entire password change process has been completed
3. Verify the new password.
If you changed the password for APPS (and APPLSYS), restart all concurrent managers, then log on to Oracle Applications to test the new password.
Note: You cannot change a schema name, such as APPLSYS or GL, after a product is installed, with FNDCPASS. Ensure that the entire Oracle Applications system has been shut down before changing any schema passwords. All users should log out and the Applications system should be down before running this utility.
If Oracle Applications user passwords are being changed then the relevant users should not be logged in.
Before changing any passwords, you should make a backup of the tables FND_USER and FND_ORACLE_USERID
A). To change the APPS and APPLSYS schema password:
Use the following command to change passwords for schemas that are used by shared components of Oracle Applications.
FNDCPASS < logon > 0 Y < system/password> SYSTEM < username > < new_password>
FNDCPASS uses the following arguments when changing the APPLSYS password. When specifying the SYSTEM token, FNDCPASS expects the next arguments to be the APPLSYS username and the new password.
- logon - The Oracle username/password.
- system/password - The username and password for the SYSTEM DBA account.
- username - The APPLSYS username. For example, 'applsys'.
- new_password - The new password.
Validates APPLSYS.
Re-registers password in Oracle Applications.
Changes the APPLSYS and all APPS passwords (for multi-APPS schema installations) to the same password.
Because everything with a Privilege Level [set to any of ('E', 'U', 'D')] in the FND_ORACLE_USERID table must always have the same password, FNDCPASS updates these passwords as well as APPLSYS's password.
For example, the APPS password will be updated when the APPLSYS password is changed.
ALTER USER is executed to change the ORACLE password for the above ORACLE users.
For instance, the following command changes the APPLSYS password to 'WELCOME'.
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME
Note: The SYSTEM token is used when changing the APPLSYS password.
B). To change an Oracle Applications schema password (other than APPS/APPLSYS):
Use this command to change the password of a schema provided by an individual product in Oracle Applications.
FNDCPASS
Note: The ORACLE token is used when changing an Oracle Applications schema password.
Use the above command with the following arguments. When specifying the ORACLE token, FNDCPASS expects the next arguments to be an ORACLE username and the new password.
- logon - The Oracle username/password.
- system/password - The username and password for the SYSTEM DBA account.
- username - The Oracle username. For example, 'GL'.
- new_password - The new password.
FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1
Use this command to change the passwords of all schemas provided by Oracle Applications products.
FNDCPASS < logon> 0 Y < system/password> ALLORACLE < new_password>
Use the above command with the following arguments. When specifying the ALLORACLE token, FNDCPASS expects the next argument to be the new password.
- logon - The Oracle username/password.
- system/password - The username and password for the SYSTEM DBA account.
- new_password - The new password.
FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME
Note: The ALLORACLE token is used when changing all ORACLE schema passwords.
Use this command to change an individual Oracle Applications user's password.
FNDCPASS < logon> 0 Y < system/password> USER < username> < new_password>
Note: The USER token is used when changing an Oracle Applications user password.
Use the above command with the following arguments. When specifying the USER token, FNDCPASS expects the next arguments to be an Oracle Applications username and the new password.
- logon - The Oracle username/password.
- system/password - The username and password for the System DBA account.
- username - The Oracle Applications username. For example, 'VISION'.
- new_password - The new password.
FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME
Using the FNDCPASS Utility:
Here is an example of changing an Oracle user's password, where
1. Use the FNDCPASS utility to change the password.
FNDCPASS < APPS username>/< APPS password> 0 Y \
< SYSTEM username>/< SYSTEM password> ORACLE < username> < new_password>
When changing the APPS or APPLSYS passwords, replace ORACLE with SYSTEM.
Note: Passwords for APPLSYS and the APPS schemas -- including the MRC schema -- must be the same. If you change the password for one, FNDCPASS automatically changes the others.
If you changed the APPS schema password (and APPLSYS) or the APPLSYSPUB password, update the following configuration files using AutoConfig (do not manually edit these files). They are used when connecting to Oracle Applications.
If you changed the APPS (and APPLSYS) password, update the password in this file:
• ORACLE_HOME/reports/server/CGIcmd.dat
If you changed the APPLSYSPUB password, update the password in these files:
• FND_TOP/resource/appsweb.cfg
• OA_HTML/bin/appsweb.cfg
• INST_TOP/admin/fnd/12.0.0/secure/< host_name>_< dbname>.dbc
Note: When changing APPS (or APPLSYS) and APPLSYSPUB passwords, do not restart the system until the entire password change process has been completed
If you changed the password for APPS (and APPLSYS), restart all concurrent managers, then log on to Oracle Applications to test the new password.
Wednesday, 26 May 2010
What is FNDLOAD and what it is used for ?
FNDLOAD is a concurrent program that can move Oracle Applications data between database and text file. FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database. Conversion between database format and text file format is specified by a configuration file.
Oracle currently supports the migration of the following types of data using FNDLOAD
- Printers / Print queues / Executables Printers / Print queues / Executables.
- Roles / Responsibilities / Forms Roles / Responsibilities / Forms.
- Menus / Users / Request Sets Menus / Users / Request Sets.
- Request Groups / Request Queues Request Groups / Request Queues.
- Work shifts / Programs / Libraries Work shifts / Programs / Libraries.
- Attachments / Help Files Attachments / Help Files.
- Mime Types Mime Types.
- Security Information.
.ldt & .lct stands for Loader datafile & Loader configuration files, used frequently in migrating customization, profile options, configuration data, etc.. across Instances.
Advantages when using FNDLOAD
Disadvantages
The Syntax
To use FNDLOAD, the following syntax is needed.
FNDLOAD apps/appspwd 0 Y mode configfile datafile entity [parameter1.....]
0 & Y are flags for FND Executable like FNDCPASS & FNDLOAD where
Example of download:
FNDLOADapps/pwd 0 Y DOWNLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM CONCURRENT_PROGRAM_NAME= concurrent_program_short_name> APPLICATION_SHORT_NAME=application_short_name
Example of Upload
FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt – CUSTOM_MODE=FORCE undocumented parameter
Where is Config File Located
Configuration files with extension .lct
On linux – all the configuration files are in $FND_TOP/patch/115/import directory
On linux Oracle also places the original configuration files in $FND_TOP/admin/import directory
Data files with extension .ldt
The configfiles (.lct) are delivered and maintained by Oracle
It has entity definitions, parent-child relationships and user input parameters identified by :NAME
Downloading a parent automatically downloads all children – (Example) Concurrent Program download
Working example for these code objects :
Printer Styles
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=printer style name
Lookups
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=prod LOOKUP_TYPE=lookup name
Descriptive Flexfield with all of specific Contexts
$ FNDLOAD apps/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XX_PO_HEADERS_DFF.ldt DESC_FLEX APPLICATION_SHORT_NAME=PO DESCRIPTIVE_FLEXFIELD_NAME='PO_HEADERS'
Please note that PO is the Application Shortname against which descriptive flexfield against PO Headers is registered
PO_HEADERS is the name of Descriptive Flexfield against PO Headers
You can find the details using this script
SELECT application_id, DESCRIPTIVE_FLEXFIELD_NAME, application_table_name
FROM fnd_descriptive_flexs_vl
WHERE APPLICATION_TABLE_NAME like 'PO_HEAD%' ORDER BY APPLICATION_TABLE_NAME
/
To upload into another environment
$FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct XX_PO_HEADERS_DFF.ldt
Concurrent Programs
$ FNDLOAD apps/ O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUST_PROG_IMP.ldt PROGRAM APPLICATION_SHORT_NAME="XX_GS_IMP" CONCURRENT_PROGRAM_NAME="XX_CUST_PROG_IMP"
Please note that XX_GS_IMP will be your custom Application Shortname where concurrent program is registered
XX_CUST_PROG_IMP Will be the name of your request group
XX_CUST_PROG_IMP.ldt is the file where concurrent program definition will be extracted to upload to the target instance
$ FNDLOAD apps/ O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUST_PROG_IMP.ldt
Value Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=value set name
Value Sets with values
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=value set name
Profile Options
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME=profile option APPLICATION_SHORT_NAME=prod
Requset Group
$ FNDLOAD apps/ O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_REPGROUP_NAME.ldt REQUEST_GROUP REQUEST_GROUP_NAME="XX_REPGROUP_NAME" APPLICATION_SHORT_NAME="XX_MYGROUP"
Please note that XX_MYGROUP will be your Application Shortname where request group is registered
and XX_REPGROUP_NAME Will be the name of your request group
Next need to upload this Request Group info to the target instance after having transferred the ldt file
FNDLOAD apps/ O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_REPGROUP_NAME.ldt
Request Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME=prod REQUEST_SET_NAME=request set
Responsibilities
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY=responsibility
Menus
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=menu_name
Forms/Functions
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES The Upload syntax for all styles: FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt
Responsibilities
$ FNDLOAD apps/ O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XX_RESPON_NAME.ldt FND_RESPONSIBILITY RESP_KEY="XX_RESPON_NAME"
please note that XX_RESPON_NAME is the responsibility key in source instance
Now need to upload this information to target instance after having transferred the ldt file
FNDLOAD apps/ O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XX_RESPON_NAME.ldt
Users
FNDLOAD apps/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XX_FND_USER_PASSWD.ldt FND_USER USER_NAME='USER_NAME'
When you look at the ldt file, you can find this kind info, and do not worry about password, it will be encrypted only.
BEGIN FND_USER "username"
OWNER = "ANONYMOUS"
LAST_UPDATE_DATE = "2010/01/07"
ENCRYPTED_USER_PASSWORD =
"ZG19D5C2DB16C4F5DD4D5D9A2F0CE3FEEB07BAF9CD0A591B64CA8B357C38EE7B17533B0C00D1DBA278D83E0A8994737B2C63"
SESSION_NUMBER = "3375"
START_DATE = "2007/01/01"
END_DATE = "*NULL*"
LAST_LOGON_DATE = "2010/04/30"
DESCRIPTION = "Name of the user"
PASSWORD_DATE = "2010/01/07"
PASSWORD_ACCESSES_LEFT = "*NULL*"
PASSWORD_LIFESPAN_ACCESSES = "*NULL*"
PASSWORD_LIFESPAN_DAYS = "*NULL*"
EMAIL_ADDRESS = "username@test.com"
FAX = "*NULL*"
To upload the FND_USER using FNDLOAD command use
FNDLOAD apps/ 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XX_FND_USER_PASSWD.ldt
when you upload the FND_USER details with FNDLOAD, need to be complete these actions priorily.
1. After uploading using FNDLOAD, user will be promoted to change their password again during their next signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER
3. In the Target Environment , make sure that you have done FNDLOAD for new responsibilities,functions, menu, request group etc., prior to running FNDLOAD on users.
Oracle currently supports the migration of the following types of data using FNDLOAD
- Printers / Print queues / Executables Printers / Print queues / Executables.
- Roles / Responsibilities / Forms Roles / Responsibilities / Forms.
- Menus / Users / Request Sets Menus / Users / Request Sets.
- Request Groups / Request Queues Request Groups / Request Queues.
- Work shifts / Programs / Libraries Work shifts / Programs / Libraries.
- Attachments / Help Files Attachments / Help Files.
- Mime Types Mime Types.
- Security Information.
.ldt & .lct stands for Loader datafile & Loader configuration files, used frequently in migrating customization, profile options, configuration data, etc.. across Instances.
Advantages when using FNDLOAD
- Because downloaded data is stored in a text file, version administration is possible
- No learning curve. this is relief for developer/dbas
- Fully supported and recommended by Oracle
- Capture the migrations in a file and use it during installations(log file).
- Pin-point when something happened and where (database) easily
- AOL data migration process is now simplified!
Disadvantages
- Applications patching mechanisms use FNDLOAD heavily possibility of negative impact is not zero
- No validation against migrating database/instance sensitive data
The Syntax
To use FNDLOAD, the following syntax is needed.
FNDLOAD apps/appspwd 0 Y mode configfile datafile entity [parameter1.....]
- The mode is either DOWNLOAD or UPLOAD.
- The configfile is the file that Fndload needs to download on upload data.
- T he data file is the output file, in which the downloaded data is written
- The entity is the entity you want to download
0 & Y are flags for FND Executable like FNDCPASS & FNDLOAD where
- 0 is request id (request ID 0 is assigned to request ID's which are not submitted via Submit Concurrent Request Form.
- 'Y' indicates the method of invocation. i.e. it is directly invoked from the command-line not from the Submit Request Form.
Example of download:
FNDLOADapps/pwd 0 Y DOWNLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM CONCURRENT_PROGRAM_NAME= concurrent_program_short_name> APPLICATION_SHORT_NAME=application_short_name
Example of Upload
FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt – CUSTOM_MODE=FORCE undocumented parameter
Where is Config File Located
Configuration files with extension .lct
On linux – all the configuration files are in $FND_TOP/patch/115/import directory
On linux Oracle also places the original configuration files in $FND_TOP/admin/import directory
Data files with extension .ldt
The configfiles (.lct) are delivered and maintained by Oracle
It has entity definitions, parent-child relationships and user input parameters identified by :NAME
Downloading a parent automatically downloads all children – (Example) Concurrent Program download
Working example for these code objects :
Printer Styles
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=printer style name
Lookups
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=prod LOOKUP_TYPE=lookup name
Descriptive Flexfield with all of specific Contexts
$ FNDLOAD apps/
Please note that PO is the Application Shortname against which descriptive flexfield against PO Headers is registered
PO_HEADERS is the name of Descriptive Flexfield against PO Headers
You can find the details using this script
SELECT application_id, DESCRIPTIVE_FLEXFIELD_NAME, application_table_name
FROM fnd_descriptive_flexs_vl
WHERE APPLICATION_TABLE_NAME like 'PO_HEAD%' ORDER BY APPLICATION_TABLE_NAME
/
To upload into another environment
$FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct XX_PO_HEADERS_DFF.ldt
Concurrent Programs
$ FNDLOAD apps/
Please note that XX_GS_IMP will be your custom Application Shortname where concurrent program is registered
XX_CUST_PROG_IMP Will be the name of your request group
XX_CUST_PROG_IMP.ldt is the file where concurrent program definition will be extracted to upload to the target instance
$ FNDLOAD apps/
Value Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=value set name
Value Sets with values
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=value set name
Profile Options
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME=profile option APPLICATION_SHORT_NAME=prod
Requset Group
$ FNDLOAD apps/
Please note that XX_MYGROUP will be your Application Shortname where request group is registered
and XX_REPGROUP_NAME Will be the name of your request group
Next need to upload this Request Group info to the target instance after having transferred the ldt file
FNDLOAD apps/
Request Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME=prod REQUEST_SET_NAME=request set
Responsibilities
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY=responsibility
Menus
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=menu_name
Forms/Functions
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES The Upload syntax for all styles: FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt
Responsibilities
$ FNDLOAD apps/
please note that XX_RESPON_NAME is the responsibility key in source instance
Now need to upload this information to target instance after having transferred the ldt file
FNDLOAD apps/
Users
FNDLOAD apps/
When you look at the ldt file, you can find this kind info, and do not worry about password, it will be encrypted only.
BEGIN FND_USER "username"
OWNER = "ANONYMOUS"
LAST_UPDATE_DATE = "2010/01/07"
ENCRYPTED_USER_PASSWORD =
"ZG19D5C2DB16C4F5DD4D5D9A2F0CE3FEEB07BAF9CD0A591B64CA8B357C38EE7B17533B0C00D1DBA278D83E0A8994737B2C63"
SESSION_NUMBER = "3375"
START_DATE = "2007/01/01"
END_DATE = "*NULL*"
LAST_LOGON_DATE = "2010/04/30"
DESCRIPTION = "Name of the user"
PASSWORD_DATE = "2010/01/07"
PASSWORD_ACCESSES_LEFT = "*NULL*"
PASSWORD_LIFESPAN_ACCESSES = "*NULL*"
PASSWORD_LIFESPAN_DAYS = "*NULL*"
EMAIL_ADDRESS = "username@test.com"
FAX = "*NULL*"
To upload the FND_USER using FNDLOAD command use
FNDLOAD apps/
when you upload the FND_USER details with FNDLOAD, need to be complete these actions priorily.
1. After uploading using FNDLOAD, user will be promoted to change their password again during their next signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER
3. In the Target Environment , make sure that you have done FNDLOAD for new responsibilities,functions, menu, request group etc., prior to running FNDLOAD on users.
Subscribe to:
Posts (Atom)