Logon script not updating

Posted by / 05-May-2019 09:17

Some of the examples in this FNDLOAD article include:- FNDLOAD to transfer Request Groups FNDLOAD for moving Concurrent Programs FNDLOAD to download and upload Forms Personalizations ( or Personalisations depending on where you are located ) To FNDLOAD Web ADI, visit the link Web ADI FNDLOAD Use FNDLOAD for transferring value set definitions.

--Please note that when transferring Key Flex Fields and Descriptive flex fields the respective value sets against each segment will be extracted and loaded automatically.

If possible, try to follow a good practice of modifying FNDLOADable data only by FNDLOAD on production environment.5. When I uploaded the DFF, Created By: Creation Date Updated By: Update Date: same as Updated By: Update Date: from the instance from which i downloaded the information. Hi Vishal The dates or rather the entire Row Who information will be passed in fromm Source System, i.e. Open the lct file by doing vi $FND_TOP/patch/115/import/search for string fnd_flex_loader_apis.up_desc_flex In the parameter last_update_date you can pass sysdate, replacing the value read from ldt file Please note this is customization and is not supportable The reason value sets were not included is because they always get downloaded or uploaded along with Flexfield Segments or Conc Program Parameters.

As the name suggests, FNDLOAD is useful for FND Related objects. Some of the things that can be migrated using Oracle i Setup are GL Set of Books, HR Organization Structures, HRMS Employees, Profile Options Setup, Suppliers, Customers, Tax Codes & Tax Rates, Financials Setup, Accounting Calendars, Chart of Accounts, GL Currencies. I was missing single quotes around APPLICATION_SHORT_NAME and hence was giving me an error. Is there a way to show the sysdate as creation date ? But anyway, please find the script for FNDLOAD of value set $FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_SSHR_01_ETH_VALUE_VALUE_SET FLEX_VALUE_SET_NAME=XX_HRMS_ETH_ORIGIN Thanks, Anil Passi Hi Vishal The dates or rather the entire Row Who information will be passed in fromm Source System, i.e. Open the lct file by doing vi $FND_TOP/patch/115/import/search for string fnd_flex_loader_apis.up_desc_flex In the parameter last_update_date you can pass sysdate, replacing the value read from ldt file Please note this is customization and is not supportable The reason value sets were not included is because they always get downloaded or uploaded along with Flexfield Segments or Conc Program Parameters.

This can be validated via below SQL ## select user_menu_name from fnd_menus_vl where menu_name = ' ICX_POR_SSP_HOME' ; ## Also note that we do not pass in the User_menu_name in this example ## OK, now to upload this file $FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/ICX_POR_SSP_---------------------------------------------------------------------------------------------------------------------------- ## Well, now for FND Messages to download a single message FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/\ XX_ICX_POR_LIFECYCLE_PAY_FND_NEW_MESSAGES APPLICATION_SHORT_NAME=' ICX' MESSAGE_NAME=XX_ICX_POR_LIFECYCLE_PAY_TIP ## Or you may as well download all the messages within an application FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/\ XX_ALL_GMS_MESSAGES_00FND_NEW_MESSAGES APPLICATION_SHORT_NAME=' XXGMS' ## now to upload using FNDLOAD FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/XX_ICX_POR_LIFECYCLE_PAY_---------------------------------------------------------------------------------------------------------------------------- ## Now it's the turn of Lookup values.

Again, its not a rocket science FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD XX_TRX_BATCH_FND_LOOKUP_TYPE APPLICATION_SHORT_NAME =' XXGMS' LOOKUP_TYPE="XX_TRX_BATCH_STATUS" ## Note that ## XX_TRX_BATCH_STATUS is the name of FND Lookup Type in this example ## This will download all the lookup codes within the defined lookup ## To upload FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD XX_TRX_BATCH_---------------------------------------------------------------------------------------------------------------------------- ## You can also move the User definitions from FND_USER FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/./XX_FND_USER_FND_USER USER_NAME=' ANILPASSI'#Do not worry about your password being extracted, it will be encrypted as below in ldt file#BEGIN FND_USER "ANILPASSI"# OWNER = "PASSIA"# LAST_UPDATE_DATE = "2005/10/19"# ENCRYPTED_USER_PASSWORD = "ZGE45A8A9BE5CF4339596C625B99CAEDF136C34FEA244DC7A"# SESSION_NUMBER = "0"To upload the FND_USER using FNDLOAD command use FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/./XX_FND_USER_Notes for using FNDLOAD against FND_USER:-1.

By doing so, you will download and extract all the test data in GL Codes that might not be applicable for production. There are several variations possible for FNDLOAD, for example you can restrict the download and uploads to specific segments within Descriptive Flex Fields.

In past I have noticed undesired results when the Lookup gets modified manually directly on production, and then the FNDLOAD is run for similar changes.## Next you will be required to download the Sets Linkage definition ## Well, lets be clear here, the above sequence is more important while uploading FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_GL_MY_INTERFACE_REQ_SET REQUEST_SET_NAME="FNDRSSUB4610101_Will_look_like_this" FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_GL_MY_INTERFACE_SET_REQ_SET_LINKS REQUEST_SET_NAME="FNDRSSUB4610101_Will_look_like_this" ## Note that FNDRSSUB4610101 can be found by doing an examine on the ########-----where user_request_set_name = ' User visible name for the request set here' ## Now for uploading the request set, execute the below commands FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/XX_GL_MY_INTERFACE_FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/XX_GL_MY_INTERFACE_SET_---------------------------------------------------------------------------------------------------------------------------- ## Now for the responsibility FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/XX_PERSON_FND_RESPONSIBILITY RESP_KEY="XX_PERSON_RESPY" ## note that XX_PERSON_RESPY is the responsibility key ## Now to upload FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/XX_PERSON_---------------------------------------------------------------------------------------------------------------------------- ## OK, now for the forms personalizations ## For the forms personalizations, I have given three examples as below.FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_FND_FORM_CUSTOM_RULES function_name="PERWSHRG-404" FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_HZ_ARXCUDCI_FND_FORM_CUSTOM_RULES function_name="HZ_ARXCUDCI_STD" FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_AP_FND_FORM_CUSTOM_RULES function_name="AP_APXVDMVD" ## Note that the function name above is the function short name as seen in the Function Definition Screen ## Now to upload the forms personalizations that are defined against these forms functions....However in any implementation, you will be required to migrate the Setups in Financials and Oracle HRMS from one environment to another. 1nd Question, I could not find a script above for migrating value sets with the data for them as well. But anyway, please find the script for FNDLOAD of value set $FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/XX_SSHR_01_ETH_VALUE_VALUE_SET FLEX_VALUE_SET_NAME=XX_HRMS_ETH_ORIGIN Thanks, Anil Passi Hi Anil, I used FBNDLOAD to donload/upload the ldt for Request Set & its Links.I am sucsessful to download the Request Set & its Links from one instance, but the upload to another instance gives error as follows: --------------------- Uploading from the data file XX_THA_GLDOIUPR_REP_Altering database NLS_LANGUAGE environment to AMERICAN Dump from LCT/LDT files (/u02/appluat/uatappl/fnd/11.5.0/patch/115/import/afcprs et.lct(115.26), XX_THA_GLDOIUPR_REP_DEF.ldt) to stage tables Dump LCT file /u02/appluat/uatappl/fnd/11.5.0/patch/115/import/afcprset.lct(115.

logon script not updating-84logon script not updating-20logon script not updating-84

Checked the ldt file it shows only the lookup type definition.

One thought on “logon script not updating”