Profile Options provide flexibility to Oracle Apps.
These are provided to keep the application flexible. The business rules in various countries and various companies can be different. Hence the profile options are delivered by Oracle in such a manner to avoid hard-coding of logic, and to let the implementation team at site decide the values of those variables.
A profile is a set of changeable options that affects the way you application run.AOL establishes a value for each option in user's profile when the user log on or change responsibility. user can change the value of profile options at any time. we different types of profile levels they are
1) site
2) application
3) responsibility
4) user levels
here user is the highest level of the hierarchy followed by responsibility application and at lowest level site. Higher level option values override lowerlevel option values.
SQL TO CHECK THE PROFILE OPTION VALUE FROM DATABASE
===================================================
SELECT SUBSTR(e.profile_option_name,1,30) PROFILE,
DECODE(a.level_id,10001,'Site',10002,'Application',10003,'Responsibility',10004,'User') L,
DECODE(a.level_id,10001,'Site',10002,c.application_short_name,10003,b.responsibility_name,10004,d.user_name) LValue,
NVL(a.profile_option_value,'Is Null') Value,
SUBSTR(a.last_update_date,1,25) UPDATED_DATE
FROM fnd_profile_option_values a
INNER JOIN fnd_profile_options e ON a.profile_option_id = e.profile_option_id
LEFT OUTER JOIN fnd_responsibility_tl b ON a.level_value = b.responsibility_id
LEFT OUTER JOIN fnd_application c ON a.level_value = c.application_id
LEFT OUTER JOIN fnd_user d ON a.level_value = d.user_id
WHERE e.profile_option_name LIKE '%&1%'
ORDER BY profile_option_name;
How to set profile option value from Back end
==============================================
DECLARE
stat BOOLEAN;
BEGIN
DBMS_OUTPUT.DISABLE;
DBMS_OUTPUT.ENABLE (100000);
stat := fnd_profile.SAVE ('ORG_ID', 286, 'SITE');
IF stat
THEN
DBMS_OUTPUT.put_line ('Stat = TRUE - profile updated');
ELSE
DBMS_OUTPUT.put_line ('Stat = FALSE - profile NOT updated');
END IF;
COMMIT;
END;
Here :
PROFILE_NAME >> ORG_ID
PROFILE_VALUE >> 286
LEVEL >> SITE
http://www.club-oracle.com/articles/set-profile-option-value-from-back-end-276/
PROFILE OPTIONS GENERALLY CHANGED AFTER CLONE (Corp)
=====================================================
ICX: Discoverer Release : 1 digit number specifying the Discoverer release
ICX: Discoverer End User Layer Prefix : XXGDWEUL
ICX: Discoverer use Viewer : NO
ICX:Discoverer Launcher : http://ebsdiscolinux.noa.corp.com:8039/discwb4/html/discolaunch.htm?Connect=[APPS_SECURE]
ICX: HTML directory : http://adeda01n.ami.corp.com:8039/OA_HTML/
ICX: Media directory : http://adeda01n.ami.corp.com:8039/OA_MEDIA/
ICX: Forms Launcher : http://adeda01n.ami.corp.com:8039/dev60cgi/f60cgi/?play=&record=names
ICX:Session Timeout : 60
ICX: Report Server : q594_APPS
ICX: Report Launcher : http://adeda01n.ami.corp.com:8039/dev60cgi/rwcgi60
ICX: Report Cache : http://adeda01n.ami.corp.com:8039/CACHE
ICX: Limit connect : 1000
Site Name : Q594 - last Refresh : 24-JUL-10
BNE Server Log Path : (NULL after clone) profile related to webadi . To debug the issues give logfile name.
BNE UIX Physical Directory : (NULL after clone)
BNE Server Log Path : free to choose, eg. in the IAS_TOP/Apache/Jserv/logs (use the full path)
VEA:DBC Profile : <NULL> This should point to $FND_TOP/secure/<dbserver>_<sid>.dbc
OTHER IMPORTANT PROFILE OPTIONS
================================
Concurrent:Report Copies
You can set the number of output copies that print for each concurrent request. The default value is 1.
Changing this value does not affect requests that you have already submitted.
Users can see and update this profile option.
Printer
You can select the printer that prints your reports. If a printer cannot be selected, contact your System Administrator. Printers must be registered with Oracle Applications.
Users can see and update this profile option.
Gateway User ID
Oracle login for gateway account. For example, applsyspub/pub.
Users can see and but not update this profile option.
This profile option is visible at all levels but may only be updated at the site level.
The internal name for this profile option is GWYUID.
Signon Password Length
Signon Password Length sets the minimum length of an Applications signon password. If no value is entered the minimum length defaults to 5.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
Default= 5 Char
Recommended= 6 Chars
Two Task
TWO_TASK for the database. This profile is used in conjunction with the Gateway User ID profile to construct a connect string for use in creating dynamic URLs for the Web Server. This should be set to the SQL*NET. alias for the database.
Note: The TWO_TASK must be valid on the node upon which the WebServer is running
Users can see and but not update this profile option.
This profile option is visible at all levels but may only be updated at site level.
The internal name for this profile option is TWO_TASK.
Utilities:SQL Trace
SQL trace files can now be generated for individual concurrent programs. The trace can be enabled at the user level by setting the profile "Utilities:SQL Trace" to "Yes". This profile can be enabled for a user only by System Administrator so that it is not accidentally turned on and disk usage can be monitored.
For more information on SQL trace, see the ORACLE7 Server SQL Language Reference Manual.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the all levels.
Concurrent:Use ICM
"Yes" allows you to use the Internal Concurrent Manager to resolve request conflicts instead of the Conflict Resolution Manager.
Only the System Administrator can update this profile option.
Sign-On: Audit Level Profile Option. The available options are: -
NONE - No monitoring.
USER - Will only show you a list of logged in users.
RESPONSIBILITY - Will show you the user logged in and the responsibility they are using.
FORM - Will go down to the lowest level of detail and show you the User, Responsibility and Form being accessed.
Security Profile Options
1)Sign-on:Audit Level
Default=None
Recommended=Form
Use Standard Sigon Audit report to view data
Truncate FND_SIGNON_XXXX tables periodically
2)Sign-on:Notification
Default=No
Recommended=Yes
3)ICX:Session Timeout
Default=None
Recommendation=30 Mins
Also Set Jserv Sessiontimeout in Zone.properties
Depending on what audit level you have selected for the profile option under discussion you may also generate various reports as indicated below: -
Signon Audit Concurrent Requests Report - used to view information about who is requesting what concurrent requests and from which responsibilities and forms.
Signon Audit Forms Report - used to view who is navigating to what form and when they do it.
Signon Audit Responsibilities Report - used to view who is selecting what responsibility and when they are doing it.
Signon Audit Users Report - used to view who signs on and for how long.
Utilities: Diagnostics profile option
The profile option Utilities: Diagnostics “determines whether a user can automatically
use the Diagnostics features (excerpt from the SA Users Guide). If the profile option is
set to No, the users must enter the password for the APPS schema in order to use the
feature. The diagnostics features allow a user to see and change information in the
database. By setting this profile option to ‘Yes’, the system allows a user to change data
at the database level without requiring the Apps login.
Another alternative to close this loophole is to disable the Diagnostics Menu altogether
by setting the profile option “Hide Diagnostics menu entry” to ‘Yes’.
FND: Debug Log Level
Following possible values are available, but I suggest you set this to "Statement" level when debugging code.
LEVEL_UNEXPECTED : Internal Level Id is 6
LEVEL_ERROR : Internal Level Id is 5
LEVEL_EXCEPTION : Internal Level Id is 4
LEVEL_EVENT : Internal Level Id is 3
LEVEL_PROCEDURE : Internal Level Id is 2
LEVEL_STATEMENT : Internal Level Id is 1
FND: Debug Log Enabled
Set this profile to Yes
FND: Debug Log Module
Set this to %
Initialization SQL Statement – Custom
against your username before reproducing the issue. The value of this profile will be set so as to enable trace using event 10046, level 12.
Concurrent: Active Request Limit
Concurrent: Hold Requests
Concurrent: Multiple Time Zones
Concurrent: Report Access Level
FND: Debug Log Filename
FND: Debug Log Level
Forms Runtime Parameter
Password Profile Options
1) Sigon Password Length
Default= 5 Char
Recommended= 6 Chars
2)Signon Password Hard to Guess
Default=No
Recommended=Yes
3)Sigon Password No Reuse
Default=0(Zero) -No limit on resuse
Recommended=At least 180 Days
4)Sigon Password Failure Limit
Default=0 attempts- no lockout
Recommended=3
Implement custom workflow to notify admin of lockout
CONCURRENT MANAGER PROFILE OPTIONS
----------------------------------
1. Concurrent: Active Request Limit
Value: Numeric
This profile options will restrict the number of concurrent requests that may be
run simultaneously by each user. If you do not specify a limit, then no
limit is imposed.
2. Concurrent: Attach URL
Values: YES/NO
If you set this option to YES, then this causes a URL to be attached to request
completion notifications. For example, when a user submits a request and uses the 'Defining Completion Options' region to specify people to be notified, a notification is sent each of the people designated.
3. Concurrent: Collect Request Statistics
Values: YES/NO
If you set this option to YES, this causes applications to collect statistics
on your run-time concurrent processes.
4. Concurrent: Conflicts Domain
Values: LOV (list of values: domains)
This option identifies the domain within which all the incompatibilities
between programs has to be resolved
5. Concurrent: Debug Flags
This option is used to debug the transactions managers.
You should only use this option at the request of Oracle Support.
6. Concurrent: Directory for Copy
You can identify a directory on your operating system to store copies of
your report output or log files. This directory is used when a copy
operation is requested in character mode of the applications.
7. Concurrent: Enable Request Submission in View Mode
Values: YES/NO
Setting this option to YES will enable the 'Submit a New Request' button
when users invoke the form FNDRSRUN (Find Requests Form). Navigation
path is either: (1) Menu: Help > View My Requests, or (2) navigate
(with system administrator responsibility) to, Requests > View.
8. Concurrent: Hold Requests
Values: YES/NO
This option enables you to automatically place requests on hold after
submission.
9. Concurrent: Multiple Time Zones
Values: YES/NO
When the client's session and the concurrent manager are running in different
times zones, use this option to ensure that the request is scheduled immediately
regardless of you client session's time zone.
10. Concurrent: PMON Method
This option is presented for documentation purposes only. Users cannot see or alter this profile option. This option is not visible or cannot be updated from the System Profile Option (FNDPOMPV) form. The PMON method refers to the process
monitor. The Internal Concurrent Manager (ICM) monitors the individual
concurrent managers' processes to verify the managers are running. Normally,
the PMON method must be set to LOCK. To change the profile option setting,
you must execute the SQL script "afimpmon.sql" which resides in directory
"$FND_TOP/sql/".
11. Concurrent: Report Access Level
Values: RESPONSIBILITY/USER
This option determines access privileges to report output files
and log files generated by a concurrent program. This option can be
set by a system administrator or by the user.
12. Concurrent: Report Copies
Values: Numeric
This option determines the number of default copies that print for each
submitted concurrent request.
13. Concurrent: Request Priority
Values: Numeric
Concurrent requests in Oracle Applications are queued. Requests normally
run according to a start time on a first submitted, first run basis. Priority
overrides this request start time. A higher priority request starts before an earlier request. This option displays the default priority for you concurrent requests. Only a system administrator can change your request priority.
14. Concurrent: Request Start Time
Values: Numeric (Date/Time)
With this profile option, you can set the date and time that your
requests are available to start running
* If the start time is at or before the current date and time,
requests are available to run immediately
* Start a request in the future, for example, at 6:00 PM on
December 31, 2000, enter the following value,
31-DEC-2000 18:00
* This profile option requires the date and time,
for example, 31-DEC-2000 18:00
* Changing values does not affect request already submitted
15. Concurrent: Save Output
Values: YES/NO
Setting this option to YES will save the output from a concurrent
request to a file.
16. Concurrent: Sequential Requests
Values: YES/NO
Setting this option to YES will force concurrent requests to run sequentially
in the order in which they were submitted.
17. Concurrent: Show Requests Set Stages
Values: YES/NO
Set this option to YES to show request set stages in the concurrent
request screens.
18. Concurrent: Show Requests Summary After Each Request Submission
Values: YES/NO
By default the Request Summary (FNDRSRUN) form appears
after every request submission. Set this option to NO if you have
multiple requests to submit and do not wish to see the Request Summary
form after each submission.
19. Concurrent: URL Lifetime
Value: Numeric
If the profile option 'Concurrent: Attach URL' has been set to YES, a URL
is associated the output of an execution and is passed to anyone flagged
for notification during the request submission. This option
specifies how long (in minutes) the URL is to be kept active.
20. Concurrent: Use ICM
Values: YES/NO
ICM (Internal Concurrent Manager)
Set this option to YES to use the Internal Concurrent Manager to resolve
request conflicts (result from programs that are defined to be incompatible)
instead of using the Conflict Resolution Manager (CRM).
21. Concurrent: Wait for Available TM
Value: Numeric
TM (Transaction Manager)
Use this option to specify the number of minutes that a client will wait
for a given transaction manager to become available before trying a
different transaction manager.
UPDATE PROFILE OPTION FROM BACKEND
DECLARE
stat boolean;
BEGIN
dbms_output.disable;
dbms_output.enable(100000);
stat := FND_PROFILE.SAVE('XX_PROFILE_NAME', 'XX_NEW_VALUE', 'SITE');
IF stat THEN
dbms_output.put_line( 'Stat = TRUE - profile updated' );
ELSE
dbms_output.put_line( 'Stat = FALSE - profile NOT updated' );
END IF;
commit;
END;