Overview of Setting Profile Options
Profile categories, or hierarchy types, enable system administrators to group and set profile options according to their business needs or the needs of the installation. You can view and set a profile option at the levels of its hierarchy type. As a system administrator, you can use the System Profile Values window in Oracle Applications Forms to set up profile options for your user community. If you change a user profile option value, your change takes effect as soon as your users log on again or change responsibilities, and bounce the apache server. When you set up a user profile, you provide Oracle Applications with standard information (such as printer) that describes a user, Responsibility, application, or site. You can set up values for user profile options at each of the following profile levels.
- Site: Option settings pertain to all users at an installation site.
- Application: Option settings pertain to all users of any Responsibility associated with the application.
- Responsibility: Option settings pertain to all users currently signed on under the Responsibility.
- User: Option settings pertain to an individual user, identified by their application user name.
The values you set up at each level provide run-time values for each user's profile options. An option's run-time value becomes the highest level setting for that option.
When you can set a profile option at more than one level, the priorities from lowest to highest are:
- Site has the lowest priority.
- Application supersedes Site.
- Responsibility supersedes Application.
- User has the highest priority.
For example, values at the Application, Responsibility, or User levels can override a value at the Site level. A value at the User level has the highest priority and overrides values at any other level.
For example, for a given user, assume the printer option is set only at the Site and Responsibility levels. When the user logs on, the printer option assumes the value set at the Responsibility level, since it is the highest level setting for that option.
Note: As a System Administrator, you should set site-level option values before specifying profile options at the other levels after the installation of Oracle Applications.
The options specified at the site-level work as defaults until the same options are specified at other levels. Application users can use the Personal Profile Values window to set their own personal profile options at the user level. Not all profile options are visible to users. End-users might not be able to update some visible profile options. For more information about profile options, see the Oracle Applications System Administrator's Guide.
Set Up Profile Options
The following procedure describes how to set up any profile option.
Module
Oracle Applications Forms
Responsibility
System Administrator Responsibility
Navigation
Profile > System...Find System Profile Values window
Steps
- Select the levels at which you want to set the profile option. The available levels include:
- Site.
- Application: If you select this level, then choose the Application for which you want to set the profile option.
- Responsibility: If you select this level, then choose the Responsibility for which you want to set the profile option.
- User: If you select this level, then choose the User for whom you want to set the profile option.
- In the Profile field, enter the profile name, such as Knowledge: Active Knowledge Base System, or a wildcard search criterion such as Knowledge%.
- Click Find.
The System Profile Values form displays the results of your search. - Verify or set the profile option(s) at the levels that you selected.
You can set user profiles at different levels by using one of the three hierarchies.
1) Security
2) Organization
3) Server
2) Organization
3) Server
Security Levels Profile
Most profile options use the Security hierarchy, In which setting a user profile effects application users across one of the four different levels.
- Site Level : Setting apply to all users at an installation site.
- Application Level : All users of specific application and will override the site level.
- Responsibility Level : All users currently signed in under the responsibility and will override the options set at the site and application levels.
- User Level : Applies to user level and will override all other options
Organization Levels Profile
The second hierarchy type is Organization, where organization refers to an Operating Unit. For example, clerks in different organizations may need to have different values for a given profile option, depending on their organization, but clerks in the same organization would use the same value.
profiles using the Organization type use the hierarchy Site – Organization – user, where a user level option overrides the organization-level option, which, in turn, overrides the site-level option.
Profile Hierarchy Levels : Server
The Server hierarchy type is used when the the system needs to determine the server on which the user’s session is running. For example, the profile “Applications Web Agent” can be defined using the Server hierarchy type. The setting of this profile option can differ for an internal server and an external one.
Profile Options in Oracle Application Object Library
Account Generator:Purge Runtime Data
“Yes” ensures that the Oracle Workflow data used to generate accounting flexfield code combinations using the Account Generator is purged after the Account Generator has completed.
This profile option should always be set to “Yes” unless you are debugging the Account Generator. Running the Account Generator with this profile set to “No” fills up the workflow tables and slows performance.
Users can see and 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 ACCOUNT_GENERATOR:PURGE_DATA.
Applications Web Agent
Provides the base URL for the Apps Schema’s WebServer DAD. Your System Administrator sets this profile option during the install process.
Use the following syntax to enter your URL:
http://<WebServer.Machine_Name>/<DAD_name>/
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.
Attachment File Upload Directory
Provides the directory path used to upload attachment files. Your System Administrator sets 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.
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: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.
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 alternative 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. The Internal Concurrent Manager uses one of two methods to monitor the individual managers’s processes:
| RDBMS (default) | RDBMS refers to relational database management system. The Internal Concurrent Manager reads a database table holding values submitted by the individual managers. When a manager is no longer running, the table value for that manager changes. |
| OS | OS refers to operating system. The Internal Concurrent Manager sends a signal to the operating system for each manager’s system process ID to verify the process is intact. |
Attention: The OS method should only be used when a hardware platform or operating system requires it.
To change this profile option setting, you must execute a SQL script from the applsys account. The script is titled afimpmon.sql and is located in the sql directory of the Application Object Library product directory. For example, in UNIX, the path may be $FND_TOP/sql/afimpmon.sql.
Additional Information: Oracle Applications Installation Manual for your operating system
Attention: Contact Oracle Worldwide Support before changing your Concurrent:PMON method profile option setting.
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, 1998, you enter 12-JUN-1998 15:45:00 as the profile option value.
- You must include both a date and a time.
- 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_REQ_START.
Concurrent:Save Output
You can save your request outputs in a file.
- “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: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.
Concurrent:Use ICM
“Yes” allows you to use the Internal Concurrent Manager to resolve request conflicts instead of the Conflict Resolution Manager.
Users can see this profile option, but they cannot update it.
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 ICM_RESOLVE.
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 < > < xxx >
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 “<xxx>”.
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.
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 [Return] 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:Shared Table Lock
This profile option is reserved for a future release. You should not alter the value of this profile option.
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.
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
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.
This profile option is visible and updatable at the user level.
| 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.
Gateway User ID
Oracle login for gateway account. For example, applsyspub/pub.
Users can see and but not update this profile option.
This profile option is visible at all levels but may only be updated at the site level.
| 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 System Base URL
Help System Base URL provides the URL to the Applications Help System. Your System Administrator sets this profile option during the install process.
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 HELP_BASE_URL.
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.
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.
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:URL
Specify a URL which points to the CGI script on your WebServer 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 FILE_SERVER_URL.
Note: This profile option is valid only for those environments which support Oracle Web-Deployed Applications report viewer.
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.
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.
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 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.
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.
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.
Stored Procedure Log Directory
Specifying a log directory enables stored procedures used with Oracle 7.3 to generate and store log files. You must also set this log directory in theinit.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 Oracle 7.3 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.
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:SQL Trace
SQL trace files can now be generated for individual concurrent programs. The trace can be enabled at the user level by setting the profile “Utilities:SQL Trace” to “Yes”. This profile can be enabled for a user only by System Administrator so that it is not accidentally turned on and disk usage can be monitored.
For more information on SQL trace, see the ORACLE7 Server SQL Language Reference Manual.
Users cannot see nor change this profile option.
This profile option is visible and updatable at the all levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
Viewer: Text, PostScript, PDF, and HTML
You can use the viewer of your choice when reviewing online the log and output files from your concurrent requests. In almost all cases, you need to specify different viewers for reviewing text files, postscript (bitmap) files, PDF files, and HTML files. Oracle Report programs with VERSION=2.0b as the concurrent program’s execution option produce postscript files.
To link the Oracle Applications concurrent processing facility with a text, postscript, PDF, or HTML, with the appropriate application installed on your computer, enter as the profile option value the:
- Name of the application’s executable file, when the file can be found in your computer’s default path (for example, write.exe), or
- Full path to the application’s executable file, when the file is not in the default path of your compute (for example,c:\windows\bin\write.exe).
You should also enter any required parameters that may be necessary to invoke the application in a particular mode.
Attention: In a client-server environment, PC clients can access log and output files on the servers by using either a Report Review Agent or a PC-NFS mount.
Users can see and update the Viewer profile options.
These profile options are both 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 names for these four profile options are EDITOR_CHAR, EDITOR_PS, VIEWER_PDF, and VIEWER_HTML.
How To Change Look And Feel and Colors
There are two system profile options that can be used to change look and feel.
- Java Look and Feel.
Java Look and Feel can have two values: GENERIC or ORACLE.
If set to GENERIC, then set Java Color Scheme to blank.
Which will leave look and feel to generic.
The Generic look and feel adheres to the native interface and color scheme of the current operating system.
If set to ORACLE (or if the value is left blank), then the profile option 'Java Color Scheme' can be used to personalize the colors of your screen. - Java Color Scheme.
If 'Java Look and Feel' is set to ORACLE (or if the value is left blank), then 'Java Color Scheme' can be set to the following values:- Blaf (in R12: Swan)
- Blue
- Khaki
- Olive
- Purple
- Red
- Teal
- Titanium
Do the following:
- Login to Oracle Applications as the System Administator responsibility.
- Navigate to Profile > System.
- Ensure that the Site display is checked.
- Query up 'Java Color Scheme' for the profile.
- Select the appropriate color under the Site column.
- Save the selection.
- Sign off and back on (or change responsibility) for your new color scheme to take effect.
Be aware that the 'Java Color Scheme' profile has no effect if 'Java Look and Feel' is set to GENERIC.
No comments:
Post a Comment