Setting User Profile Options
As System Administrator, you use the System Profile Values window to set 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. See: System Profile Values Window.
When you set a user profile, you provide Oracle Applications with standard information (such as printer) that describes a user, responsibility, application, or site. You can set values for user profile options at each profile level.
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 username.
The values you set 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 a profile option may be set at more than one level, site has the lowest priority, superseded by application, then responsibility, with user having the highest priority. For example, a value entered at the site level may be overridden by values entered at any other level. A value entered at the user level has the highest priority, and overrides values entered 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 the option.
Suggestion: As System Administrator, you should set site-level option values before specifying profile options at the other three levels after the installation of Oracle Applications. The options specified at the site-level work as defaults until the same options are specified at the other levels.
Application users may 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, and some profile options, while visible, may not be updated by end users.
System Profile Values Window
Use this window to view and set profile option values.
You can view and set profile options at the site, application, responsibility, and user levels. Your settings affect users as soon as they sign on or change responsibility. See: Overview of Setting User Profiles.
Profile Values Block
Set values for profile options at one or more levels. Each value overrides those set to its left. For example, a User Value setting overrides a Responsibility Value setting, which overrides an Application Value setting, which overrides a Site Value setting.
Profile
This field displays the name of a profile option.
Site
This field displays the current value, if set, for all users at the installation site.
Application
This field displays the current value, if set, for all users working under responsibilities owned by the application identified in the Find Profile Values block.
Responsibility
This field displays the current value, if set, for all users working under the responsibility identified in the Find Profile Values block.
User
This field displays the current value, if set, for the application user identified in the Find Profile Values block.
Suggestion: You should set site-level default values for any required options after installation of an application. If you do not assign a particular profile option at any of the four levels, that option does not have a default value and may cause errors when you use forms, run reports, or run concurrent requests.
Find System Profile Values Block
Specify the level or levels at which you wish to view and set profile option values.
Display
You can view the values set for your installed profile options at each of four levels:
o Site, which affects all users at an installation site.
o Application, which affects all users working under responsibilities owned by a particular application.
o Responsibility, which affects all users working under a specific responsibility.
o User, which affects a unique application user.
You can find the values for all profile options that include a specific character string, such as "OE:" for Oracle Order Entry. You can also display only profile options whose values are currently set.
Site
Check the Site check box if you wish to display the values for profile options at an installation site.
Application
Select an application if you wish to display profile option values for responsibilities owned by that application.
Responsibility
Select a responsibility if you wish to display profile option values for a specific responsibility.
User
Select an application user if you wish to display profile option values for a specific user.
Profile
Enter the name of the profile option whose values you wish to display. You may search for profile options using character strings and the wildcard symbol (%). For example, to find all the profile options prefixed by "Concurrent:", you could enter "Conc%" and press the Find button.
Profiles with No Values
Select whether to display all profiles, including those without currently set values. If this check box is unselected, only profiles with current values are retrieved.
Find
Choose the Find button to display all profile options, or the profile options you are searching for, at the level or levels you specified.
verview of Setting User Profiles
A user profile is a set of changeable options that affect the way your application looks and behaves. As System Administrator, you control how Oracle Applications operate by setting user profile options to the values you want. You can set user profile options at four different levels: site, application, responsibility, and user.
Major Features
Set of Books
You can further control security by assigning a set of books to a responsibility, application or site. A set of books is a company or group of companies within Oracle Applications that share a common account code, calendar, and functional currency.
Setting Your Personal User Profile
You can change a user profile option value using the Profile Values window. The Menus appendix in your product's reference guide tells you how to navigate to this menu.
Using this window, you can display all your options and review the values your system administrator has set for them. You can also change those options that are updatable if you like. Changes you make to a User-level profile option take effect when you either change responsibilities or close and re-login into the application. If changes are made in character mode you must follow the same steps to apply the changes to applications running in GUI mode. Changes you make to your User-level options are still in force when you log in again.
If you never set your own User-level option values, your user profile options assume the Site-, Application-, Responsibility-, or User-level values your system administrator has set for them.
To change a profile option value:
1. Navigate to the Profile Values window.
This window displays all your user profile options and their values. If you wish to display only specific user profile options, first choose Enter from the Query menu to enter search criteria in the Profile Name field, then choose Run from the Query menu to run the search.
The name of the user profile option appears in the Profile Name field while the Default Value field displays the run-time value of that option. The System Administrator sets default values for many of the profile options. Some profile options may not display a default value.
2. Move your cursor to the User Value field of the option whose value you wish to modify.
3. Enter a new value for the option if it is updatable, or if the <List> lamp appears, choose a value from the list of available values.
If the profile option is not updatable, the message "Item is protected against update," appears on the message line when you try to change the value. You can change most of your user profile options; values you enter in the User Value field override values preset by the System Administrator. A few profile options cannot be changed, but are displayed for informational purposes only.
For most personal profile options, Oracle Applications automatically checks the value you enter to ensure it is valid.
Attention: Number or date values are not validated, therefore, you must make sure that you enter a valid value for profile options that require a number or date; otherwise, your personal profile option may not work as you expect.
Though you cannot delete a profile option from your personal profile, you can clear its value (if it is updatable) by highlighting the field and pressing [Backspace] or by choosing Clear Field from the Edit menu. If you clear the value, the change does not take effect until you sign on again or change responsibilities.
4. Choose Save from the Action menu to save your change.
Your change will take effect when you either change responsibilities or log out and log back in.
Common User Profile Options
The following list of user profile options affects all Oracle Applications products. The alphabetical list includes only those options that can be viewed and/or changed by you at the User-level using the Personal Profile Values window. These user profile options affect your user interface and the behavior of Oracle Applications features, such as concurrent processing and flexfields.
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.
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>/
Only the System Administrator can update this profile option.
Attachment File Upload Directory
Provides the directory path used to upload attachment files. Your System Administrator sets this profile option during the install process.
Only the System Administrator can update this profile option.
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.
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:
o Navigate to the Requests window to select a request
o Select the Request Control alternative region
o Uncheck the Hold check box
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.
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:
o View the completed report output for your requests online
o View the diagnostic log file for those requests online. (system administrator also has this privilege)
o Reprint your completed reports, if the Concurrent:Save Output profile option is set to "Yes".
o 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.
o 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.
Only the System Administrator can update this profile option.
Concurrent:Report Copies
You can set the number of output copies that print for each concurrent request. The default is set to 1.
o Changing this value does not affect requests that you have already submitted.
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.
Only the System Administrator can update this profile option.
Concurrent:Request Start Time
You can set the date and time that your requests are available to start running.
o If the start date and time is at or before the current date and time, requests are available to run immediately.
o 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.
o You must include both a date and a time.
o Changing this value does not affect requests that you have already submitted.
Concurrent:Save Output
You can save your request outputs in a file.
o "Yes" saves request outputs.
o Some concurrent requests do not generate an output file.
o 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.
o Changing this value does not affect requests you have already submitted.
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.
o Concurrent programs are incompatible if simultaneously accessing the same database tables incorrectly affects the values each program retrieves.
o 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.
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.
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.
Concurrent:Use ICM
"Yes" allows you to use the Internal Concurrent Manager to resolve request conflicts instead of the Conflict Resolution Manager.
Only the System Administrator can update this profile option.
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>".
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.
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.
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.
Only the System Administrator can update this profile option.
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.
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.
o "Yes" means after entering a valid value in a segment, you automatically move to the next segment.
o "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.
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.
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.
Flexfields:Open Descr Window
You can control whether a descriptive flexfield window automatically opens when you navigate to a customized descriptive flexfield.
o "Yes" means that the descriptive flexfield window automatically opens when you navigate to a customized descriptive flexfield.
o "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.
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.
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.
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.
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.
Folders:Allow Customization
Your system administrator controls whether you can create or customize a folder definition layout in folder block.
o "Yes" means that you can create or customize a folder definition, that is, the entire Folder menu is enabled in the folder block.
o "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.
Only the System Administrator can update this profile option.
Gateway User ID
Oracle login for gateway account. For example, applsyspub/pub.
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.
Only the System Administrator can update this profile option.
Indicate Attachments
This profile option allows you to turn off indication of attachments when querying records (for performance reasons).
Only the System Administrator can update this profile option.
MO:Operating Unit
Determines the Operating Unit the responsibility logs onto.
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.
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.
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.
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.
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.
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.
Only system administrators can change this profile option.
Session ID
This runtime profile option contains the session ID number of the last database session that was created.
Sign-On:Notification
"Yes" displays a message at login that indicates:
o If any concurrent requests failed since your last session,
o How many times someone tried to log on to Oracle Applications with your username but an incorrect password, and
o When the default printer identified in your user profile is unregistered or not specified.
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.
Only system administrators can change this profile option.
Only system administrators can change this profile option.
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 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
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
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
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:
o Name of the application's executable file, when the file can be found in your computer's default path (for example, write.exe), or
o 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.
Only system administrators can change this profile option.
Warning About Changing Data
Warning: Do Not Use Database Tools to Modify Oracle Applications Data
Oracle provides powerful tools you can use to insert, update, and delete information in an Oracle7 database. But, if you use Oracle tools like SQL*Plus or Oracle Data Browser to modify Oracle Applications data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications forms, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications.
When you use Oracle Applications forms to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. But, if you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.
Warning: Oracle Applications does not support any customization of Oracle Application Object Library tables or modules, even by Oracle consultants. Oracle Application Object Library table names begin with "FND_".
Do not write data directly into or change data in FND_ tables through any custom program or using any tool, including SQL*Plus, Oracle Data Browser, database triggers or other programming tools. You risk corrupting your database and damaging all your applications.
Consequently, we STRONGLY RECOMMEND that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle Applications tables, unless we tell you to do so in our installation, implementation, or open interface guides.
No comments:
Post a Comment