To Enable diagnostics - examine menu in oracle forms.
If oracle R12 application forms menu does not show Help > Diagnostics > Examine.
Open the system administrator responsibility - system - profile options
Search for Profile, Utilities:Diagnostics and provide the username then search.
Set yes for both user level and site level and save.
Logout and login oracle forms again it will work.
SELECT EXTRACTVALUE(XMLType(text),'//oa_context_file_loc')
appl_top, status
FROM fnd_oam_context_files
WHERE name NOT IN ('TEMPLATE','METADATA','config.txt')
AND CTX_TYPE='A'
AND (status IS NULL OR UPPER(status) IN ('S','F'))
AND EXTRACTVALUE(XMLType(text),'//file_edition_type') = 'run';
To determine the PATCH files system:
SELECT EXTRACTVALUE(XMLType(text),'//oa_context_file_loc')
appl_top, status
FROM fnd_oam_context_files
WHERE name NOT IN ('TEMPLATE','METADATA','config.txt')
AND CTX_TYPE='A'
AND (status IS NULL OR UPPER(status) IN ('S','F'))
AND EXTRACTVALUE(XMLType(text),'//file_edition_type') = 'patch';
Sql Query to check list of all discoverer reports and a run count:
SELECT STAT.QS_DOC_NAME,
STAT.QS_DOC_OWNER,
MAX(STAT.QS_CREATED_DATE),
COUNT(1)
FROM EUL_US.EUL5_QPP_STATS STAT
GROUP BY STAT.QS_DOC_NAME,
STAT.QS_DOC_OWNER
ORDER BY MAX(STAT.QS_CREATED_DATE) DESC
;
ICX:Session Timeout to change the session Timeout in Oracle Apps R122 version:
Increase oracle forms session timeout in r122
To change oracle forms session time out via "ICX:session Timeout" Profile in oracle application.
ICX:Session Timeout is a profile provided in Oracle apps which controls the time for which a session is valid. Post that time out limit, the user gets below error.
Log on session is no longer valid. Would you like to log back in so you can continue working? If you do not log in, any outstanding data changes in your forms will not be saved.
When the user clicks on the Yes button, App opens the login page. Enter the password and login again to continue. Click No to exit from the current session.
30 minutes is the value of this profile in any production instance. It is fine for production instance but for development instance, this may not be ideal, as you will repeatedly get this message and you need to log in again and again.
Just increase the value of this profile to avoid the timeout message.
Set ICX:Session Timeout profile
Now let me show how you can change this profile. You can set this profile at the site or user level. It is always better to set at the user level.
Log in to Oracle Apps Instance. Navigate to System Administrator->Profile->System. Query profile the ICX:Session Timeout for the user. The default value is 30 and is set at the site level. We are going to set it a user level.
Enter the new value greater than 30 and click on Save.
Log off and log in again.
This will make sure that your Oracle apps session will never time out in a smaller interval.
Summary
ICX:Session Timeout provides an easy way to increase the session limit. It is good to increase only in development or test instance, but production let it be default 30.
This tip should work for both Oracle App 11i and R12 release. I hope you found this small tip useful. Please share and subscribe.
To set the User Session Timeout, test the following steps in a development instance and then migrate accordingly:
If suppose we executed autoconfig on application again default value 30 will be added to "ICX:session Timeout" Profile.
So we need to change the value in autoconfig file itself.
1.If R12.2 EBS instance view $CONTEXT_FILE change the value for vairable "s_sessiontimeout" in config file then execute the autoconfig.sh in oracle application.
That will update the "ICX: Session Timeout" Profile in applications.
2.If R12.1.3 EBS instance view $CONTEXT_FILE change the value for variable "s_oc4j_sesstimeout" in config file then execute the autoconfig.sh in oracle application.
That will update the "ICX: Session Timeout" Profile in applications.
How to Open oracle EBS application forms and report in MS Edge(Due to Internet explorer is going to retired on June 2022).
Step to follow,
1.Open MS Edge browser then open browser setting - select default browser options - right side "internet explorer compatability"
Allow sites to be reloaded in Internet Explorer mode option change to Allow
Let Internet Explorer open sites in Microsoft Edge option change to Allow.
2.Enter the oracle application login link in the browser then browser right corner click on the 3 dots then choose the "Reload the internet explorer mode" option.Browser will be refresh.
Now you can able to login and open the forms on MS edge brower.
You have encountered an unexpected error,please contact system administrator,
While opening oracle R12 application url login , we getting above error,
"You have encountered an unexpected error,please contact system administrator".
This is happen due to disable and enable user end_dates in fnd_user table using updates scripts.
Answer: 1
Please try to disable and enable user end_dates in fnd_user table using fnd_user_packages,
In order to access this application, you must install the J2SE Plugin version 1.6.0_25. To install this plugin, click here to download the oaj2se.exe executable. Once the download is complete, double-click the oaj2se.exe file to install the plugin. You will be prompted to restart your browser when the installation is complete.
Eventhough we installed java 6 if we got this error ,
Please add the application domain link to the compatability settings,
Internet explorer > open oracle r12 application url page > select settting/tools > drop down list choose the view compatability settings > add the application domain link > close.
Now it will open oracle forms.
Form dead "frmweb" Process Running for more than a day in EBS R12 Instance due to CPU utilization reached 100%.
Steps to resolve this issue.
Solution:
Installing Oracle BI
Publisher Desktop for Word (for Office) is not a difficult task.
First you have to
download it from Oracle. You will get
the BIPublisher32.exe or BIPublisher64.exe file.
Run this file and you
will get the following screen:
|
