Recently we had encountered a situation, wherein end users where not able to get the R12 login page and
it just hangs, but all the opmn processess were up and running - adopmnctl.sh status gives status as
alive for all the components viz., HTTP, oafm, oacore & forms. The same environment was available and
end users were able to access without any isuses 15 minutes before. This error happens only when
multiple people login to the same page and perform simillar activity like employee self service form
etc. So where and what exactly could be the problem.
This is how we approached and resolved the issue.
First we checked apache error log. The following error was reported in the error log.
==============================================================
[warn] [client IP Address ] oc4j_socket_recvfull timed out
[error] [client IP Address ] mod_oc4j: There is no oc4j process (for destination: application://oacore) available to service request.
[error] [client IP Address] mod_oc4j: request to OC4J [servername:OC4J AJP Port Range for Oacore]
failed: Connect failed
==============================================================
Above error message does give us a hint that the problem is with oacore, but as i said earlier the oacore is alive according to opmn.
Next, we verified the oacore log file.
($INST_TOP/logs/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.err)
Error Message in the file
=======================================================
Exception in thread “OC4JMonitorThread” java.lang.OutOfMemoryError: Java heap space
=======================================================
While checking the error in file, parallely we opened another window to see the CPU and memory usage and we could see one java process was taking more than 100% CPU. This process was spawned by the opmn -d process and the process id didnt match with the oacore process id. Hint: adopmnctl.sh status will give the status as well the process id. It looked like a end client java process.
At this stage we had 3 options.
1. Kill the java process which is consuming high cpu.
2. Bounce oacore component
3. Adjust java (jvm) memory parameters
Each of the above options has its own implications and advantages. To minimize the downtime we decided to kill the java processes, and the moment we killed the java process, all the browsers which were hanging reported instantaneously Internal Server Error. This proved to be a bad decision.
So we moved to the next option, bouncing the oacore service which we are sure will resolve the issue (temporarily) and it did as expected. Basically when you bounce the services all the existing
connections and processess will be released which results in more available memory when you re-start the services.
Ok, now we tackled the problem and provided a temporary solution but we need to find a long term solution. This is option 3, adjusting java memory size.
Steps to change the heap size.
First, you need to identify how much is the maximum heap size that you can set. Click here.
Once you had identified the maximum heap size, we need to change the configuration files to make it
permanent.
Step 1: Edit opmn.xml file.
Location : $INST_TOP/ora/10.1.3/opmn/conf/
Open opmn.xml
Search for string Xms or Xmx or module-id=”OC4J”
This search should lead you to below location
‘<’process-type id=”oacore” module-id=”OC4J” status=”enabled” working-dir=”$ORACLE_HOME/j2ee/home”‘>’
‘<’category id=”start-parameters”‘>’
‘<’data id=”java-options” value=”-server -verbose:gc -Xmx512M -Xms128M ……] The default value for Maximum (-Xmx) and Minimum (-Xms) heap sizes are 512M and 128M respectively. Again here you have options, you can set both Xms and Xmx has the same value as Xmx if you feel all your sessoins require higher memory or set a lower value for Xms and the maximum value for Xmx. Dont forget to change the values under ‘<’category id=”stop-parameters”‘>’
opmn.xml also contains jvm configurations for other components - oafm & forms.
Step 2: Edit oc4j.properties file.
Location : ($INST_TOP/ora/10.1.3/j2ee/oacore/config)
This step is optional since we had already made changes in opmn.xml but there is no harm in making the change here. This step will come handy for troubleshooting specific components of Oracle viz., configurator, iSupplier or any other option which heavily utilizes/consumes CPU/memory.
Search for string Xms or Xmx or wrapper.
Option 1: If you find any of the above parameters change the values corresponding to the value you had mentioned in opmn.xml or even more than that, as long as you dont exceed the maximum heap size limit.
Option 2: If you DO NOT find any of the above parameters, then make an entry like this, under the heading “# Java Object Cache Configuration Parameters”
wrapper.bin.parameters=-Xms[Value]M -Xmx[Value]M -XX:NewSize=256M -XX:MaxNewSize=256M
Step 3: Edit Applications Context file
vi $CONTEXT_FILE
Location: $INST_TOP/appl/admin/SID_hostname.xml
search for string s_oacore_jvm_start_options
Change Xms and Xmx value. Repeat the same step for parameter s_oacore_jvm_stop_options.
Changes made in Step 3 will take effect the next time you run autoconfig, whereas Step 1 & 2 changes will take effect the next time you bounce opmn services, but the values are not permanent in the sense these will be wiped off next time you run autoconfig. Yes you can preserve the changes by placing it inbetween Begin and End customizations.
You can also increase the Garbage Collection threads parameter (-XX:ParallelGCThreads) to a higher value if you have JDK 1.5 or more than 2 cpus or more memory. For more information on this you can refer to Metalink Note: 362851 - Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12.
HAPPY LEARNING!
Post courtesy:OraclePitstop
Oracle Apps 11i/R12 --- Oracle 10gAS/Weblogic Server 11g --- Oracle 9i,10g,11g - Oracle APEX
Thursday, November 13, 2008
Sunday, November 9, 2008
Oracle Application Object Library- Profile Options
This section lists each profile option in Oracle Application Object Library. These profile options are available to every product in Oracle Applications. For each profile option, we give a brief overview of how Oracle Application Object Library uses the profile’s setting.
Unless otherwise noted, a profile option uses the Security hierarchy type.
A table is provided for most profile options that lists the access levels for the profile option. For Security profile options, there are four possible levels at which system administrators can view and update a profile option value: site, application, responsibility, and user. This table lists whether the profile option’s value is visible at each of these levels, and whether it is updatable at each level.
Account Generator:Debug Mode
This profile option controls Oracle Workflow process modes for the Account Generator feature. This profile option should normally be set to “No” to improve performance. If you are testing your Account Generator implementation and using the Oracle Workflow Monitor to see your results, set this profile option to “Yes”.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is ACCOUNT_GENERATOR:DEBUG_MODE.
Applications Help Web Agent
Applications Help Web Agent is optional and should only be used if you want to launch online help on a web server different from the one specified by the Applications Servlet Agent.
Attention: For most installations, this profile should be set to NULL. Only specify a value if you want to use a different web server than that for the Applications Servlet Agent.
Specify the entire online help URL for this profile’s value:
http://:/ OA_HTML/jsp/fnd/fndhelp.jsp?dbc= This new usage of HELP_WEB_AGENT provides one with the flexibility of reverting back to the previous Release 11i applet version of the tree navigator if desired. To do this, set this profile option to
http://[:]// fnd_help.launch?par_root= This is usually identical to the Applications Web Agent profile option but with the string “/fnd_help.launch?par_root=” appended at the end.
If this profile option is not set, the online help tree navigator will default to starting up at the host name and port number that is specified by the Applications Servlet Agent profile option. The DBC file used will be that of the database where online help was invoked.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is HELP_WEB_AGENT.
Applications Servlet Agent
This profile option must be set to the URL base for the servlet execution engine on Apache. Oracle Applications uses the value of this profile option to construct URLs for JSP and SERVLET type functions. The syntax is:
https://:/ Example:
https://ap523sun.us.oracle.com:8888/oa_servlets Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is APPS_SERVLET_AGENT.
Applications Web Agent
Provides the base URL for the Apps Schema’s WebServer DAD. You set this profile option during the install process.
This profile option must be set to the URL which identifies the mod_plsql PL/SQL Gateway Database Access Descriptor base URL for your Applications instance. Oracle Applications use the value of this profile option to construct URLs for ‘WWW’ type functions, Attachments, Export, and other features.
Use the following syntax to enter your URL:
https://:/pls/ Users can see but not update this profile option.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is APPS_WEB_AGENT.
Applications Web Authentication Server
The web server used for authentication for Oracle Self-Service Web Applications.
Users can see but not update this profile option.
This profile option is visible and updatable at the site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is WEB_AUTHENTICATION_SERVER.
Attachment File Directory
The directory in which file type attachments data is stored. You set this profile option during the install process.
Users can see but not update this profile option.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is ATTACHMENT_FILE_DIRECTORY.
AuditTrail:Activate
You can turn AuditTrail on or off (Yes or No). The default setting is No (Off).
When you enter or update data in your forms, you change the database tables underlying the forms you see and use.
AuditTrail tracks which rows in a database table(s) were updated at what time and which user was logged in using the form(s).
- Several updates can be tracked, establishing a trail of audit data that documents the database table changes.
- AuditTrail is a feature enabled on a form-by-form basis by a developer using Oracle’s Application Object Library.
- All the forms that support AuditTrail are referred to as an audit set.
- Not all forms may be enabled to support AuditTrail.
- To enable or disable AuditTrail for a particular form, you need access to Oracle Application Object Library’s Application Developer responsibility.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the site and application levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is AUDITTRAIL:ACTIVATE.
BIS/AOL:Debug Log Directory
The directory for BIS debugging log files.
Users can see and change this profile option.
System administrators can see and update this profile option at the site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is BIS_DEBUG_LOG_DIRECTORY.
Concurrent:Active Request Limit
You can limit the number of requests that may be run simultaneously by each user. or for every user at a site. If you do not specify a limit, no limit is imposed.
Users cannot see or update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | Yes |
The internal name for this profile option is CONC_REQUEST_LIMIT.
Concurrent:Attach URL
Setting this option to “Yes” causes a URL to be attached to request completion notifications. When a user submits a request, and specifies people to be notified in the Defining Completion Options region, everyone specified is sent a notification when the request completes. If this profile option is set to Yes, a URL is appended to the notification that enables them to view the request results on-line.
Only the System Administrator can update this profile option.
Users can see but not update this profile option.
This profile options is visible at all levels but can only updated at the Site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is CONC_ATTACH_URL.
Concurrent:Conflicts Domain
Specify a conflict domain for your data. A conflict domain identifies the data where two incompatible programs cannot run simultaneously.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_CD_ID.
Concurrent:Collect Request Statistics
Set this profile option to “Yes” to have statistics for your runtime concurrent processes collected.
To review the statistics you must run the Purge Concurrent Request and/or Manager Data program to process the raw data and have it write the computed statistics to the FND_CONC_STAT_SUMMARY table. You can then retrieve your data from this table using SQL*PLUS or on a report by report basis using the Diagnostics window from the Requests window.
Users cannot see nor change this profile option.
This profile option is visible at all levels bu can only be updated at the Site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is CONC_REQUEST_STAT.
Concurrent:Debug Flags
Your Oracle support representative may access this profile option to debug Transaction Managers. Otherwise, it should be set to null.
Users cannot see nor change this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_DEBUG.
Concurrent:Hold Requests
You can automatically place your concurrent requests on hold when you submit them.
The default is “No”. The concurrent managers run your requests according to the priority and start time specified for each.
Changing this value does not affect requests you have already submitted.
“Yes” means your concurrent requests and reports are automatically placed on hold. To take requests off hold, you:
- Navigate to the Requests window to select a request
- Select the Request Control tabbed region
- Uncheck the Hold check box
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_HOLD.
Concurrent:Multiple Time Zones
“Yes” sets the default value to ‘Sysdate-1′ for the ‘Schedules Start Date’ used by request submissions. Sysdate-1 ensures that you request is scheduled immediately regardless of which time zone your client session is running in. You should use this profile option when the client’s session is running in a different time zone than the concurrent manager’s session.
Users cannot see nor change this profile option.
This profile option is visible at all four levels and updatable at the Site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is CONC_MULTI_TZ.
Concurrent:PMON method
PMON refers to process monitor. The Internal Concurrent Manager monitors the individual concurrent managers’ processes to verify the managers are running.
This profile option should always be set to LOCK. Using the LOCK method, the Internal Concurrent Manager tries to get a lock on the individual concurrent manager’s process. The name of the lock is determined by a sequence (which is the ID of the individual manager) and the program in question. If the Internal Concurrent Manager is able to get the lock, then it knows the process is no longer running.
Users cannot see nor change this profile option.
This profile option is neither visible nor updatable from the System Profile Options form.
| Level | Visible | Allow Update |
| Site | No | No |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is CONC_PMON_METHOD.
Concurrent:Report Access Level
Determines access privileges to report output files and log files generated by a concurrent program. This profile option can be set by a System Administrator to User or Responsibility.
If your Concurrent:Report Access Level profile option is set to “User” you may:
- View the completed report output for your requests online
- View the diagnostic log file for those requests online. (system administrator also has this privilege)
- Reprint your completed reports, if the Concurrent:Save Output profile option is set to “Yes”.
- If you change responsibilities, then the reports and log files available for online review do not change.
If your Concurrent:Report Access Level profile option is set to “Responsibility”, access to reports and diagnostic log files is based on the your current responsibility.
- If you change responsibilities, then the reports and log files available for online review change to match your new responsibility. You can always see the output and log files from reports you personally submit, but you also see reports and log files submitted by any user from the current responsibility.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at the site, responsibility, and user levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_REPORT_ACCESS_LEVEL.
Concurrent:Report Copies
You can set the number of output copies that print for each concurrent request. The default is set to 1.
- Changing this value does not affect requests that you have already submitted.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_COPIES.
Concurrent:Request Priority
This displays the default priority number for your concurrent requests. Only a system administrator can change your request priority.
Requests normally run according to start time, on a “first-submitted, first-run” basis. Priority overrides request start time. A higher priority request starts before an earlier request.
Priorities range from 1 (highest) to 99 (lowest). The standard default is 50.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_PRIORITY.
Concurrent:Request Start Time
You can set the date and time that your requests are available to start running.
- If the start date and time is at or before the current date and time, requests are available to run immediately.
- If you want to start a request in the future, for example, at 3:45 pm on June 12, 2002, you enter 2002/06/12 15:45:00 as the profile option value.
Attention: You must ensure that this value is in canonical format (YYYY/MM/DD HH24:MI:SS) to use the Multilingual Concurrent Request feature.
- You must include both a date and a time.
- Changing this value does not affect requests that you have already submitted.
- Users can override the start time when they submit requests. Or, this profile option can be left blank and users will be prompted for a start time when they submit requests.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_REQ_START.
Concurrent:Save Output
The Concurrent: Save Output profile is used to determine whether the default behavior of certain concurrent programs should be to save or delete their output files. This only affects concurrent programs that were created in the character mode versions of Oracle Applications and that have a null value for “Save Output”.
- ”Yes” saves request outputs.
- Some concurrent requests do not generate an output file.
- If your request output is saved, you can reprint a request. This is useful when requests complete with an Error status, for example, the request runs successfully but a printer malfunctions.
- Changing this value does not affect requests you have already submitted.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_SAVE_OUTPUT.
Concurrent:Sequential Requests
You can force your requests to run one at a time (sequentially) according to the requests’ start dates and times, or allow them to run concurrently, when their programs are compatible.
- Concurrent programs are incompatible if simultaneously accessing the same database tables incorrectly affects the values each program retrieves.
- When concurrent programs are defined as incompatible with one another, they cannot run at the same time.
“Yes” prevents your requests from running concurrently. Requests run sequentially in the order they are submitted.
“No” means your requests can run concurrently when their concurrent programs are compatible.
Changing this value does not affect requests you have already submitted.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_SINGLE_THREAD.
Concurrent: Show Requests Summary After Each Request Submission
Using this new profile option, you can choose to either have the Requests Summary displayed each time you submit a request, or retain the request submission screen.
The default is “Yes”. “Yes” means the Requests Summary screen is displayed each time you submit a request.
If you choose “No”, a decision window is opened asking you if you wish to submit another request. When you choose to submit another request you are returned to the submission window and the window is not cleared, allowing you to easily submit copies of the same request with minor changes.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_REQ_SUMMARY.
Concurrent:Wait for Available TM
You can specify the maximum number of seconds that the client will wait for a given transaction manager (TM) to become available before moving on to try a different TM.
Users can see and update this profile option.
This profile option is visible and updatable at the site and application levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is CONC_TOKEN_TIMEOUT.
Concurrent:URL Lifetime
The numeric value you enter for this profile option determines the length of time in minutes a URL for a request ouput is maintained. After this time period the URL will be deleted from the system. This profile option only affects URLs created for requests where the user has entered values in the notify field of the Submit Request or Submit Request Set windows.
Attention: All request ouput URLs are deleted when the Pruge Concurrent Requests and Manager… program is run even if the URL liftime has not expired.
Users can see and update this profile option.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_URL_LIFETIME.
Currency:Mixed Precision
Use Mixed Currency Precision to specify how many spaces are available to the right of the decimal point when displaying numbers representing different currencies.
- Normally, currency numbers are right-justified.
- Each currency has its own precision value that is the number of digits displayed to the right of a decimal point. For U.S. dollars the precision default is 2, so an example display is 345.70.
- Set Mixed Currency Precision to be equal to or greater than the maximum
- precision value of the currencies you are displaying.
For example, if you are reporting on rows displaying U.S. dollars (precision=2), Japanese yen (precision=0), and Bahraini dinar (precision=3), set Mixed Currency Precision=3.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CURRENCY:MIXED_PRECISION.
Currency:Negative Format
You can use different formats to identify negative currency. The default identifier is a hyphen ( - ) preceding the currency amount, as in “-xxx”. You can also select:
Angle brackets < > <>
Trailing hyphen - xxx -
Parentheses ( ) ( xxx )
Square Brackets [ ] [ xxx ]
If you use the negative number formats of “(xxx)” or “[xxx],” in Oracle Applications Release 11, your negative numbers appear as “
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CURRENCY:NEGATIVE_FORMAT.
Note: Currency:Negative Format only affects the display currency. Non-currency negative numbers appear with a preceding hyphen regardless of the option selected here.
Currency:Positive Format
You can use different formats to identify positive currency values. The default condition is no special identifier.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CURRENCY:POSITIVE_FORMAT.
Currency:Thousands Separator
You can separate your currency amounts in thousands by placing a thousands separator. For example, one million appears as 1,000,000.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CURRENCY:THOUSANDS_SEPARATOR.
Database Instance
Entering a valid two_task connect string allows you to override the default two_task. This profile is specifically designed for use with Oracle Parallel Server, to allow different responsibilities and users to connect to different nodes of the server.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is INSTANCE_PATH.
Default Country
This is the default source for the Country field for all address zones and is used by the Flexible Address Formats feature, the Flexible Bank Structures feature and the Tax Registration Number and Taxpayer ID validation routines.
The profile can be set to any valid country listed in the Maintain Countries and Territories form and can be set to a different value for each user.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is DEFAULT_COUNTRY.
Enable Security Groups
This profile option is used by the Security Groups feature, which is used by HRMS security only.
The possible values are ‘None’ (N), ‘Hosted’ (HOSTED), and ‘Service Bureau’ (Y).
Only the System Administrator can update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is ENABLE_SECURITY_GROUPS.
Flexfields:AutoSkip
You can save keystrokes when entering data in your flexfields by automatically skipping to the next segment as soon as you enter a complete valid value into a segment.
- ”Yes” means after entering a valid value in a segment, you automatically move to the next segment.
- ”No” means after entering a valid value in a segment, you must press [Tab] to go to the next segment.
Note: You may still be required to use tab to leave some segments if the valid value for the segment does not have the same number of characters as the segment. For example, if a segment in the flexfield holds values up to 5 characters and a valid value for the segment is 4 characters, AutoSkip will not move you to the next segment.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:AUTOSKIP.
Flexfields:BiDi Direction
This profile option controls the appearance of the flexfields window in Applications running in Semitic languages. Possible values are “Left To Right” and “Right To Left”. If the profile option is not defined on a particular installation, the default value is “Right To Left”, where the window appears in a normal, left to right fashion, and the text and layout are reversed to accommodate the right-to-left nature of the Semitic language environment.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:BIDI_DIRECTION.
Flexfields:LOV Warning Limit
Use Flexfields:LOV Warning Limit to improve efficiency when retrieving a list of values.
Sometimes, particularly when no reduction criteria has been specified, an LOV can take a very long time to run if there is a very significant amount of data in it. Set this profile option to the number of rows to be returned before the user is asked whether to continue retrieving the entire list.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is QUICKPICK_ROWS_BEFORE_WARN.
Flexfields:Open Descr Window
You can control whether a descriptive flexfield window automatically opens when you navigate to a customized descriptive flexfield.
- ”Yes” means that the descriptive flexfield window automatically opens when you navigate to a customized descriptive flexfield.
- ”No” means that when you navigate to a customized descriptive flexfield, you must choose Edit Field from the Edit menu or use the List of Values to open the descriptive flexfield window.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:OPEN_DESCR_WINDOW.
Note: This profile option does not apply to descriptive flexfields in folders.
Flexfields:Open Key Window
You can control whether a key flexfield window automatically opens when you navigate to a key flexfield.
- ”Yes” means that the key flexfield window automatically opens when you navigate to a key flexfield.
- ”No” means that when you navigate to a key flexfield, you must choose Edit Field from the Edit menu or use the List of Values to open the key flexfield window.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:OPEN_KEY_WINDOW.
Flexfields:Shared Table Lock
This profile option is used by the Oracle Applications flexfields internal code only. You should not alter the value of this profile option unless instructed to do so by an Oracle representative.
The internal name for this profile option is FLEXFIELDS:SHARED_TABLE_LOCK.
Flexfields:Shorthand Entry
If shorthand flexfield entry is defined for your flexfield, you can use a shorthand alias to automatically fill in values for some or all of the segments in a flexfield.
| Not Enabled | Shorthand Entry is not available for any flexfields for this user, regardless of whether shorthand aliases are defined. |
| New Entries Only | Shorthand Entry is available for entering new records in most foreign key forms. It is not available for combinations forms, updating existing records, or entering queries. |
| Query and New Entry | Shorthand Entry is available for entering new records or for entering queries. It is not available for updating existing records. |
| All Entries | Shorthand Entry is available for entering new records or updating old records. It is not available for entering queries. |
| Always | Shorthand Entry is available for inserting, updating, or querying flexfields for which shorthand aliases are defined. |
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:SHORTHAND_ENTRY.
Flexfields:Show Full Value
If an alias defines valid values for all of the segments in a flexfield, and Flexfields: Shorthand Entry is enabled, when you enter the alias the flexfield window does not appear.
“Yes” displays the full flexfield window with the cursor resting on the last segment.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:SHOW_FULL_VALUE.
Flexfields:Validate On Server
This profile option is set to “Yes” to enable server side, PL/SQL flexfields validation for Key Flexfields. This improves performance when using Key Flexfields over a wide area network by reducing the number of network round trips needed to validate the entered segment combinations.
You may find, however, that your validation’s performance is better with client side validation. In this case, set this profile option to “No”.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FLEXFIELDS:VALIDATE_ON_SERVER.
FND: Debug Log Filename
The file name for the file to hold debugging messages used in the Logging Service. If the value of this profile option is null, then the Logging Service is turned off.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is AFLOG_FILENAME.
FND: Debug Log Level
The Logging Service can filter out debugging messages depending on their priority level.. There are five levels of the Debug/Trace Service:. In order from highest priority to lowest priority, they are: Errors, Exceptions, Events, Procedures, and Statements. The Debug Log Level is the lowest level that the user wants to see messages for.. The possible profile option values are Null (which means off), and the five priority levels above. For instance, if the “FND: Debug Log Level” profile is set to “EVENT”, then the file will get the messages that the programmer had marked as “EVENT”, “EXCEPTION”, or “ERROR”.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is AFLOG_LEVEL.
FND: Debug Log Module
The Logging Service can filter out debugging messages depending on their module. Module names are unique across applications and coding languages. If a module is specified for this profile option, then only messages for that module will be written to the log file. If this profile option is left blank then messages for all modules will be written to the log file.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is AFLOG_MODULE.
FND: Enable Cancel Query
Oracle Applications allows end users to cancel certain long-running queries, such as retrieving data in a block. When these operations exceed a threshold of time, approximately ten seconds, a dialog will display that allows the user to cancel the query.
Set the FND: Enable Cancel Query profile option to Yes if you wish to enable the ability to cancel a form query. This profile option may be set at the site, application, responsibility or the user level.
Users can see but not update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_ENABLE_CANCEL_QUERY.
FND: Indicator Colors
The default for this profile option is null, which means “Yes.” When this profile option is set to Yes:
- Required fields are displayed in yellow.
- Queryable fields are displayed in a different color while in enter-query mode.
- Fields that cannot be entered (read-only) are rendered in dark gray.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | No | No |
| Application | No | No |
| Responsibility | No | No |
| User | Yes | Yes |
The internal name for this profile option is FND_INDICATOR_COLORS.
FND: Native Client Encoding
FND: Native Client Encoding indicates the character set that a client machine uses as its native character set. The value must be one of the Oracle character sets and should correspond to the client native character set. The character set used in a client machine varies depending on language and platform. For example, if a user uses a Windows machine with Japanese, the value should be JA16SJIS. But if a user uses a Solaris machine with Japanese, the value should be JA16EUC. The value is normally set in the user level since each user uses different machine, but it can be set in every level for a default value.
This profile option is used when storing text data. When a user uploads a text file to be stored in the FND_LOBS table, the current value of FND: Native Client Encoding is stored along with the text data. With the value of this profile option, the server can then convert the text data to another character set as necessary when the text data is downloaded.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_NATIVE_CLIENT_ENCODING.
FND: Override Directory
The FND:Override Directory profile option is used by the Work Directory feature. The value of FND: Override Directory should be the directory containing your alternate files. Typically, this profile option should be set at the User level only.
Users can see and update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is APPLWRK.
FND: Resource Consumer Group
Resource consumer groups are used by the Oracle8i Database Resource Manager, which allocates CPU resources among database users and applications. Each form session is assigned to a resource consumer group. The system administrator can assign users to a resource consumer group for all of their forms sessions and transactions. If no resource consumer group is found for a process, the system uses the default group “Default_Consumer_Group”.
Users can see this profile option, but they cannot update it.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_RESOURCE_CONSUMER_GROUP.
Folders:Allow Customization
Your system administrator controls whether you can create or customize a folder definition layout in folder block.
- “Yes” means that you can create or customize a folder definition, that is, the entire Folder menu is enabled in the folder block.
- ”No” means that you can only open an existing folder definition in a folder block, that is, only the Open option is enabled in the Folder menu.
Users can see this profile option, but they cannot update it.
| Level | Visible | Allow Update |
| Site | No | No |
| Application | No | No |
| Responsibility | No | No |
| User | Yes | Yes |
The internal name for this profile option is FLEXVIEW:CUSTOMIZATION.
Forms Keyboard Mapping File
Use this profile option to define the path of the Keyboard Mapping File.
The “Keys” window displays the keystrokes to perform standard Forms operations, such as “Next Block” and “Clear Record.” This window can be viewed at anytime by pressing Ctrl+k. The keyboard mappings can be customized as follows:
- The System Administrator must locate the Oracle Forms resource file on the middle tier, typically called fmrweb.res.
- Make a copy of the file, name it as desired, and locate it in the same directory as the original.
- Open the new file in any text editor and make the desired keystroke mapping changes. Comments at the top of the file explain how the mappings are performed.
- To run the new mapping file, specify the complete path and file name in this profile option.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_FORMS_TERM.
Forms Runtime Parameters
Use this profile to specify certain forms runtime parameters. The profile value must be entered in as parameter=value. Each parameter-value pair must be separated by a single space. For example:
record=collect log=/tmp/frd.log debug_messages=yes
In order for the parameters updated in this profile option to go into effect, you must exit and log back in to Oracle Applications.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_MORE_FORM_PARAMS.
Gateway User ID
Oracle login for gateway account. This should be the same as the environment variable GWYUID. 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.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is GWYUID.
Help Localization Code
Localized context-sensitive help files are preferred when your System Administrator sets this profile option.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at the responsibility and user levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is HELP_LOCALIZATION_CODE.
Help Tree Root
This profile option determines which tree is shown in the navigation frame when context-sensitive help is launched.
If Help Tree Root is set to “null” or “NULL” (case insensitive), then the online help is launched in a single frame, without the navigation and search features.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is HELP_TREE_ROOT.
Help Utility Download Path
Use this profile option to define the directory into which the Help Utility downloads help files from the Oracle Applications Help System.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is HELP_UTIL_DL_PATH.
Help Utility Upload Path
Use this profile option to define the directory from which the Help Utility uploads help files to the Oracle Applications Help System.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is HELP_UTIL_UL_PATH.
Hide Diagnostics Menu Entry
This profile option determines whether users can access the Diagnostics menu entry from the Help menu. If it is set to Yes, the Diagnostics menu entry is hidden. If it is set to No, the Diagnostics menu entry is visible.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_HIDE_DIAGNOSTICS.
ICX: Client IANA Encoding
This profile option is used to determine the character set of text displayed by Java Server pages. This profile option must be set to match the character set of the Apache server on the Web tier in order for the online help system to support languages other than American English. The default setting is the Western European character set (ISO-8859-1).
This profile option should be set only at the site level.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is ICX_CLIENT_IANA_ENCODING.
ICX: Discoverer Launcher, Forms Launcher, and Report Launcher
These profile options are used by the Oracle Applications Personal Homepage.
Set the site level value of each of these profile options to the base URL for launching each application. The profile option value should be sufficient to launch the application, but should not include any additional parameters which may be supplied by the Personal Homepage.
Users can see these profile options, but they cannot update them.
These profile options are visible and updatable at all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for these profile options are ICX_DISCOVERER_LAUNCHER, ICX_FORMS_LAUNCHER, and ICX_REPORT_LAUNCHER.
ICX: Limit connect
This profile option determines the maximum number of connection requests a user can make in a single session.
Users cannot see or update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | Yes | Yes |
The internal name for this profile option is ICX_LIMIT_CONNECT.
ICX: Limit time
This profile option determines the absolute maximum duration (in hours) of a user’s session, regardless of activity.
Users cannot see or update this profile option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | Yes | Yes |
The internal name for this profile option is ICX_LIMIT_TIME.
ICX: Session Timeout
This profile option determines the length of time (in minutes) of inactivity in a user’s session before the session is disabled. If the user does not perform any operation in Oracle Applications for longer than this value, the session is disabled. The user is provided the opportunity to re-authenticate and re-enable a timed-out session. If re-authentication is successful, the session is re-enabled and no work is lost. Otherwise, Oracle Applications exit without saving pending work.
If this profile option to 0 or NULL, then user sessions will never time out due to inactivity.
Users can see this profile option, but they cannot update it.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is ICX_SESSION_TIMEOUT.
Indicate Attachments
This profile option allows you to turn off indication of attachments when querying records (for performance reasons).
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is ATCHMT_SET_INDICATOR.
Initialization SQL Statement - Custom
This profile option allows you to add site-specific initialization code (such as optimizer settings) that will be executed at database session startup. The value of this profile option must be a valid SQL statement.
The system administrator may set this profile option at any level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_INIT_SQL.
Initialization SQL Statement - Oracle
This profile option is used to add application-specific code. The value is a valid SQL statement (or a PL/SQL block for more than one statement), that is executed at startup of every database session.
The value of this profile option is delivered as seed data and cannot be updated.
Attention: Do not attempt to modify the value of this profile option. Use the profile option Initialization SQL Statement - Custom to add custom initialization code.
This profile option is set at the application level only. The initialization code will be executed only for responsibilities owned by that application.
| Level | Visible | Allow Update |
| Site | Yes | No |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is FND_APPS_INIT_SQL.
Java Color Scheme
If the Java Look and Feel profile option is set to Oracle, the Java Color Scheme can be specified as follows:
- Teal
- Titanium
- Red
- Khaki
- Blue
- Olive
- Purple
The Java Color Scheme profile has no effect if the Java Look and Feel is set to Generic.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_COLOR_SCHEME.
Java Look and Feel
Oracle Applications Professional User Interface can be run with either the Oracle Look and Feel or the Generic Look and Feel. The Oracle Look and Feel consists of a new look and feel for each item, and a predefined set of color schemes. The Generic Look and Feel adheres to the native interface and color scheme of the current operating system.
To specify the look and feel set this profile to “generic” or “oracle”.
If the Oracle Look and Feel is used, the profile Java Color Scheme can be set. The Java Color Scheme profile has no effect if the Java Look and Feel is set to Generic.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FND_LOOK_AND_FEEL.
Maximum Page Length
Determines the maximum number of lines per page in a report.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is MAX_PAGE_LENGTH.
MO:Operating Unit
Determines the Operating Unit the responsibility logs onto.
Users can see and update this profile option.
This profile option is visible and updatable at the responsibility level only.
| Level | Visible | Allow Update |
| Site | No | No |
| Application | No | No |
| Responsibility | Yes | Yes |
| User | No | No |
The internal name for this profile option is ORG_ID.
Node Trust Level
Determines the level of trust assigned to a Web server. This profile option uses the Server hierarchy type.
Users can see but not update this profile option.
This profile option is visible and updatable at the site and server level only.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | NA | NA |
| Responsibility | NA | NA |
| Server | Yes | Yes |
| User | No | No |
The internal name for this profile option is NODE_TRUST_LEVEL.
Personnel Employee:Installed
When enabled, “Personnel Employee:Installed” allows you as System Administrator to link an application username and password to an employee name.
- The “Person” field is usable on the Define Application User form (\ Navigate Security User).
Oracle Purchasing uses this capability to associate an employee in your organization with an Oracle Applications user.
The installation process enables this profile option. You cannot change the value of “Personnel Employee: Installed”.
Users cannot see nor change this profile option.
This profile option is visible at the site level, but cannot be updated.
| Level | Visible | Allow Update |
| Site | Yes | No |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is PER_EMPLOYEE:INSTALLED.
Printer
You can select the printer which 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.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is PRINTER.
RRA:Delete Temporary Files
When using a custom editor to view a concurrent output or log file, the Report Review Agent will make a temporary copy of the file on the client. Set this profile to “Yes” to automatically delete these files when the user exits Oracle Applications.
Only the System Administrator can update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FS_DELETE.
RRA:Enabled
Set this user profile to “Yes” to use the Report Review Agent to access files on concurrent processing nodes.
Only the System Administrator can update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FS_ENABLED.
RRA: Service Prefix
Using this new profile option allows you to override the default service name prefix (FNDFS_) assigned to the Report Review Agent. By assigning a new prefix to the Report Review Agent you can avoid having multiple instances of the Applications share executables.
Valid values for this option must be nine characters or less and use only alphanumeric characters or the underscore. We recommend using the underscore character as the last character of your value as in the default value “FNDFS_”.
Users cannot see or update this profile option.
This profile option is visible and updatable at the site level only.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is FS_SVC_PREFIX.
Attention: GLDI will not support the “RRA: Service Prefix” profile until release 4.0 and so uses the default prefix “FNDFS_” regardless of the value entered for the profile option. Consequently, you must ensure that at least one of your Report Review Agents maintains the default prefix in order for GLDI to access the application executables.
RRA:Maximum Transfer Size
Specify, in bytes, the maximum allowable size of files transferred by the Report Review Agent, including those downloaded by a user with the “Copy File…” menu option in the Oracle Applications Report File Viewer and those “temporary” files which are automatically downloaded by custom editors. For example, to set the size to 64K you enter 65536. If this profile is null, there is no size limit.
Only the System Administrator can update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FS_MAX_TRANS.
Self Service Personal Home Page Mode
This profile option determines the type of home page for users. The three possible values are: “Framework only”,” Personal Home Page”, and “Personal Home Page with Framework”.
| Framework only | The E-Business Suite Home page is used. |
| Personal Home Page | The Personal Homepage is used. |
| Personal Home Page with Framework | The Personal Homepage appears first when a user logs in. After the user chooses a responsibility, an Oracle Applications Framework page appears for navigation among the functions for that responsibility. |
After this profile option is set, you need to bounce the middle tier server to clear its cache and to see your changes.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is APPLICATIONS_HOME_PAGE.
Sequential Numbering
Sequential Numbering assigns numbers to documents created by forms in Oracle financial products. For example, when you are in a form that creates invoices, each invoice document can be numbered sequentially.
Sequential numbering provides a method of checking whether documents have been posted or lost. Not all forms within an application may be selected to support sequential numbering.
Sequential Numbering has the following profile option settings:
| Always Used | You may not enter a document if no sequence exists for it. |
| Not Used | You may always enter a document. |
| Partially Used | You will be warned, but not prevented from entering a document, when no sequence exists. |
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at the site, application, and responsibility levels.
Note: If you need to control Sequential Numbering for each of your set of books, use the ‘Responsibility’ level. Otherwise, we recommend that you use either the ‘Site’ or ‘Application’ level to set this option.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | No | No |
The internal name for this profile option is UNIQUE:SEQ_NUMBERS.
Server Timezone
The time zone of the database server.
Users can see this profile option, but they cannot update it.
This profile option is visible and updatable at the site, application, and responsibility levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | No | No |
The internal name for this profile option is SERVER_TIMEZONE_ID.
Session ID
This runtime profile option contains the session ID number of the last database session that was created.
Users can see this profile option, but they cannot update it.
This profile option is neither visible nor updatable from the System Profile Options form.
| Level | Visible | Allow Update |
| Site | No | No |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is DB_SESSION_ID.
Sign-On:Audit Level
Sign-On:Audit Level allows you to select a level at which to audit users who sign on to Oracle Applications. Four audit levels increase in functionality: None, User, Responsibility, and Form.
None is the default value, and means do not audit any users who sign on to Oracle Applications.
Auditing at the User level tracks:
- who signs on to your system
- the times users log on and off
- the terminals in use
Auditing at the Responsibility level performs the User level audit functions and tracks:
- the responsibilities users choose
- how much time users spend using each responsibility
Auditing at the Form level performs the Responsibility level audit functions and tracks:
- the forms users choose
- how long users spend using each form
- System Administrator visible, updatable at all levels.
Users cannot see nor change this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNONAUDIT:LEVEL.
Sign-On:Notification
“Yes” displays a message at login that indicates:
- If any concurrent requests failed since your last session,
- How many times someone tried to log on to Oracle Applications with your username but an incorrect password, and
- When the default printer identified in your user profile is unregistered or not specified.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNONAUDIT:NOTIFY.
Signon Password Failure Limit
The Signon Password Failure Limit profile option determines the maximum number of login attempts before the user’s account is disabled.
Users cannot see or update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNON_PASSWORD_FAILURE_LIMIT.
Signon Password Hard to Guess
The Signon Password Hard to Guess profile option sets rules for choosing passwords to ensure that they will be “hard to guess.” A password is considered hard-to-guess if it follows these rules:
- The password contains at least one letter and at least one number.
- The password does not contain the username.
- The password does not contain repeating characters.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNON_PASSWORD_HARD_TO_GUESS.
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.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNON_PASSWORD_LENGTH.
Signon Password No Reuse
This profile option specifies the number of days that a user must wait before being allowed to reuse a password.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SIGNON_PASSWORD_NO_REUSE.
Site Name
Site Name identifies an installation of Oracle Applications. The installation process sets this to “No Site Name Specified”.
You should set a value for “Site Name” after installation.
The Site Name appears in the title of the MDI window. If you want additional information on your installation to appear in the title, for example, “Test” or “Production”, you can add that information here
Users cannot see nor change this profile option.
This profile option is visible and updatable at the site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is SITENAME.
Socket Listener Activated
This profile option is a flag that indicates whether the FormsClient Controller (Socket Listener) should be started by the signon form.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is SOCKET_LISTENER_ACTIVATED.
Socket Listener Port
This profile option defines the port number used by the Forms Client Controller.
The default value for this profile option is ‘6945′.
Oracle Workflow uses this profile option. When a user chooses to launch a form from a Workflow notification, Oracle Workflow will look for the value of this profile option and launch the form in the specified port.
If the socket listener port is not set at user level, Oracle Workflow launches attached forms at the default port set for the site. However, if users have set different ports, Oracle Workflow launches the forms for each user at the specified port. By using different socket listener ports, two different users logged into Oracle Applications on the same machine can both launch attached forms at the same time without interference from each other.
The E-Business Suite Home page also uses the Socket Listener Port profile for launching forms from Framework HTML sessions. With this architecture, a user navigating through different forms/responsibilities in a Framework session will reuse the same Oracle Forms session instead of opening multiple ones. So a user will never have more than one Forms session open on his/her PC at any given time, for a given database.
It is possible to have multiple Oracle Forms sessions open where each is connected to a different database, but the Socket Listener Port profile must be set to a different value beforehand on each database. For example, set it to 6945 on database A, 6946 on database B, and 6947 on database C. This profile option must be set at the site level in advance of any users attempting to use this functionality, as it cannot be set on a per-user basis.
Users can see but not update this profile option.
This profile option is visible and updatable at the site, application, and responsibility levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | No | No |
The internal name for this profile option is SOCKET_LISTENER_PORT.
Stored Procedure Log Directory
Specifying a log directory enables stored procedures used with the Oracle database to generate and store log files. You must also set this log directory in the init.ora file of the database.
For example, if the Stored Procedure Log Directory is /rladev/rla/1.1/log and the Stored Procedure Output Directory is /rladev/rla/1.1/out, then the following entry should be made in the init.ora file of the database containing stored procedures that write to these directories:
UTL_FILE_DIR = /rladev/rla/1.1/log,/rladev/rla/1.1/out Users cannot see nor change this profile option.
This profile option is visible and updatable at the site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is UTL_FILE_LOG.
Stored Procedure Output Directory
Specifying a output directory enables stored procedures used with the Oracle database to generate and store output files. You must also set this output directory in the init.ora file of the database.
For example, if the Stored Procedure Log Directory is /rladev/rla/1.1/log and the Stored Procedure Output Directory is /rladev/rla/1.1/out, then the following entry should be made in the init.ora file of the database containing stored procedures that write to these directories:
UTL_FILE_DIR = /rladev/rla/1.1/log,/rladev/rla/1.1/out Users cannot see nor change this profile option.
This profile option is visible and updatable at the site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | No | No |
The internal name for this profile option is UTL_FILE_OUT.
TCF: HOST
Together with the TCF:PORT profile, this profile identifies the network location of the TCF Server. The TCF Server supports various parts of the Oracle Applications UI by executing some of their associated server logic and providing access to the database.
In most configurations, these profiles will be set by the TCF Server’s administrative utility ‘ServerControl’ at the same time the TCF Server is started up. ServerControl will set these two profiles (TCF:HOST, TCF:PORT) at the site level.
For particularly complex environments, it may be appropriate to direct different users to separate TCF Servers by setting these profiles to distinct values at the Application level. Consult the post installation instructions for details on TCF Server configuration options.
This profile option is visible at all levels and updatable at the site and application level only.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is TCF:HOST.
See: Administering the TCF Server
TCF: PORT
Together with the TCF:HOST profile, this profile identifies the network location of the TCF Server. The TCF Server supports various parts of the Oracle Applications UI by executing some of their associated server logic and providing access to the database.
In most configurations, these profiles will be set by the TCF Server’s administrative utility ‘ServerControl’ at the same time the TCF Server is started up. ServerControl will set these two profiles (TCF:HOST, TCF:PORT) at the site level.
For particularly complex environments, it may be appropriate to direct different users to separate TCF Servers by setting these profiles to distinct values at the Application level. Consult Installing Oracle Applications for details on the TCF Server configuration options.
Users can see and but not update this profile option.
This profile option is visible at all levels and updatable at the site and application level only.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is TCF:PORT.
See: Administering the TCF Server
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.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is TWO_TASK.
Utilities: Diagnostics
Utilities: Diagnostics determines whether a user can automatically use the Diagnostics features. If Utilities:Diagnostics is set to Yes, then users can automatically use these features. If Utilities:Diagnostics is set to No, then users must enter the password for the APPS schema to use the Diagnostics features.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is DIAGNOSTICS.
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 Oracle database documentation.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
Viewer: Application for HTML, PCL, PDF, Postscript, and Text
These profile options determine the applications a user will use to view reports in the given output formats. For example, you could set Viewer: Application for Text to ‘application/word’ to view a Text report in Microsoft Word.
Valid values are defined by the system administrator in the Viewer Options form.
Users can see and update these profile options.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal names for these profile options are FS_MIME_HTML, FS_MIME_PCL, FS_MIME_PDF, FS_MIME_PS, and FS_MIME_TEXT.
Viewer:Default Font Size
Using this new profile option, you can set the default font size used when you display report output in the Report Viewer.
The valid values for this option are 6, 8, 10, 12, and 14.
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is FNDCPVWR_FONT_SIZE..
Viewer: Text
The Viewer: Text profile option allows you to send report output directly to a browser window rather than using the default Report Viewer. Enter “Browser” in this profile option to enable this feature.
Users can see and update the Viewer:Text profile option.
This profile option is both visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Ys |
The internal name for this profile option is EDITOR_CHAR.
HAPPY LEARNING !
Post Courtesy :- Advait
Subscribe to:
Posts (Atom)