Profile Options in Oracle Application Object Library
This section lists each profile option in Oracle Application Object Library. These profile options are grouped into categories based on their functional area and 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 (at which levels the system administrator can set 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.
Concurrent Processing Execution
The internal name for this profile category is FND_CP_EXECUTION.
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 | No | No |
Responsibility | No | 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 online.
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 | Yes |
Responsibility | Yes | Yes |
User | Yes | Yes |
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 but can only be updated at the Site level.
Level | Visible | Allow Update |
Site | Yes | Yes |
Application | Yes | Yes |
Responsibility | Yes | No |
User | Yes | No |
The internal name for this profile option is CONC_REQUEST_STAT.
Concurrent:Date Parameter Increment Option
Use this profile to control how date parameters are automatically incremented for concurrent requests. In the Standard Request Submission window, the user can specify if to run a request periodically. The user can then specify that the interval be based on the start date of the requests, or specify the interval using a unit of time and number of units.
If this profile is set to “Start Date” then the date parameters for a given request will be incremented according to the difference between the requested start date of the request and the requested start date of the previous request. If this profile is set to “Resubmit” any date parameters are incremented according to the current request’s date parameter and the amount of time represented by the number of units (RESUBMIT_INTERVAL) and the unit of time (RESUBMIT_INTERVAL_UNIT_CODE).
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_DATE_INCREMENT_OPTION.
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 | No | No |
Responsibility | No | No |
User | No | No |
The internal name for this profile option is CONC_MULTI_TZ.
Concurrent:Print on Warning
Set this profile option to “Yes” if you want concurrent request output to be printed if the requests completes with a status of Warning.
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_PRINT_WARNING.
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: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: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 Processing File Server
The internal name for this profile category is FND_CP_FILE_SERVER.
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.
Concurrent Processing Manager
The internal name for this profile category is FND_CP_MANAGER.
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:GSM Enabled
Use this profile option to enable Generic Service Management.
Level | Visible | Allow Update |
Site | Yes | Yes |
Application | No | No |
Responsibility | No | No |
User | No | No |
The internal name for this profile option is CONC_GSM_ENABLED.
Concurrent:OPP Process Timeout
This profile option specifies the amount of time the manager waits for the OPP to actually process the request.
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_PP_PROCESS_TIMEOUT.
Concurrent:OPP Response Timeout
This profile option specifies the amount of time a manager waits for the OPP to respond to its request for post processing.
Level | Visible | Allow Update |
Site | Yes | Yes |
Application |