This section lists each profile option in Oracle Application Object Library, which are available to every Oracle Application. For each profile option, we give a brief overview of how Oracle Application Object Library uses the profile's setting.
Setting this profile option to 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; in this case, we recommend that you set it to No temporarily at the user level. Running the Account Generator with this profile option set to No fills up the workflow tables and can slow system performance.
This profile option lets you automatically place your concurrent requests on hold when you submit them.
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.
Setting the profile to Yes allows your concurrent requests and reports to be automatically placed on hold. To take requests off hold:
Navigate to the Concurrent Requests Summary window to select a request
Select the Request Control tabbed region
Uncheck the Hold check box
This profile option determines access privileges to report output files and log files generated by a concurrent program. This option can be set to User or Responsibility.
Setting the profile to User means only the user who submitted a request may:
view the completed report output for that request online;
view the diagnostic log file for that request online;
reprint a completed report, if the Concurrent: Save Output profile option is set to Yes.
If a user changes responsibilities, the reports and log files available for online review do not change, but are still determined by the user who submitted the concurrent requests.
Setting the profile option to Responsibility means access to reports and diagnostic log files is based on the responsibility the user is currently using. In this case, for any requests submitted from their current responsibility, any user may:
view the completed report output for a request online;
view the diagnostic log file for a request online;
reprint a completed report, if the Concurrent: Save Output profile option is set to Yes.
If a user changes responsibilities, the reports and log files available for online review change to match the user's current responsibility. Users can always see the output and log files from reports they personally submitted, but may also see reports and log files submitted by any user from the current responsibility.
This profile option lets you set the number of output copies that print for each concurrent request. The default value is 1.
Changing this value does not affect requests that you have already submitted.
This displays the default priority number for your concurrent requests. You cannot change your request priority. The priority of your requests is set by your System Administrator.
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 value is 50.
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-98 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.
You can save your request outputs in a standard file format.
The default setting saves request outputs in standard file format.
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 that you have already submitted.
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.
Setting it to Yes prevents your requests from running concurrently. Requests run sequentially in the order they are submitted.
Setting it to No means your requests can run concurrently when their concurrent programs are compatible.
Changing this value does not affect requests you have already submitted.
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.
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 -
If you run Oracle Applications in character mode, you can also use:
Parentheses ( ) ( xxx ) Square Brackets [ ] [ xxx ]
If you use the negative number formats of (xxx) or [xxx] in the GUI version of Oracle Applications, your negative numbers appear as <xxx>.
You can use different formats to identify positive currency values. The default condition is no special identifier.
This is the only format available for positive numbers in the GUI version of Oracle Applications. If you use the character mode positive number formats of +xxx or xxx+, your positive numbers appear as xxx in the GUI windows.
You can separate your currency amounts in thousands by placing a thousands separator, for example, a comma ( , ), every three digits (or 103 power).
If your currency amount does not fit within the field window, the thousands separator does not display.
This is the default source for the Country field for all address regions and is used by the Flexible Address Formats feature, the Flexible Bank Structures feature, and the Tax Registration Number and Taxpayer ID validation routines.
This profile can be set to any valid country listed in the Maintain Countries and Territories window and can be set to a different value for each user.
If the Default Country profile option is not defined, Receivables uses the value of the Default Country field in the System Options window as the default when you enter addresses.
The Flexible Bank Structure, Tax Registration Number, and Taxpayer ID validation routines are only performed for customers and banks in the home Country. If the current transaction does not have a Country value, the Default Country profile value is used to determine whether validation is required. If the Default Country profile is not defined, validation will not be performed.
You can save keystrokes when entering data in your flexfields by automatically skipping to the next segment as soon as you enter a valid value into a segment.
Setting it to Yes means after entering a valid value in a segment you automatically move to the next segment.
Setting it to No means after entering a valid value in a segment you must press [Return] to go to the next segment.
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.
If set to Not Enabled, Shorthand Entry is not available for any flexfields for this user, regardless of whether shorthand aliases are defined.
If set to New Entries Only, Shorthand Entry is available for entering new records in most foreign key windows. It is not available for combinations windows, updating existing records, or entering queries.
If set to Query and New Entry, Shorthand Entry is available for entering new records or for entering queries. It is not available for updating existing records.
If set to All Entries, Shorthand Entry is available for entering new records or updating old records. It is not available for entering queries.
If set to Always, Shorthand Entry is available for inserting, updating, or querying flexfields for which shorthand aliases are defined.
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.
You can override this by selecting Flexfields: Show Full Value, which displays the full flexfield window with the cursor resting on the last segment.
This profile option displays the name of the language used by your application windows and menus. Only your system manager can change this profile option.
You can set the maximum number of lines per page for your printer.
You should set Maximum Page Length to a value appropriate for the paper size your printer uses.
The default value of 58 accommodates A4 type paper in landscape mode.
If your printer uses 8 1/2" by 11" size paper, you can set Maximum Page Length to 66.
You can choose between Lotus-style (left-to-right scrolling) or Macintosh-style (pull-down) menus.
Both menus have the same sequence of menu choices for each application function.
You can automatically display a pop-up window asking if you want to see a message explanation. By setting this option to:
If set to Yes, you see a DecisionPoint window when a message explanation is available.
If set to No, you do not see a DecisionPoint window when a message explanation is available. You acknowledge messages by pressing any key.
Messages appearing in the message line near the bottom of the screen are typically generated by the application you are running.
Occasionally, an application may share another application's messages. The Message: Shared Application profile option lets you identify another application whose error messages can be referenced.
You can select the printer that prints your reports. If a printer cannot be selected, contact your System Administrator. Printers must be registered with Oracle Applications.
You can automatically reduce a list of values to a list containing only values starting with a character(s) you specify, by selecting AutoReduction: Normal.
When you select AutoReduction: PowerSkip you can reduce a list of values to only those starting with a character(s) you specify, and your cursor automatically skips to the next differing character.
For example, if you had a long list of quarterly reports, two starting with the letter z (ZDept CF1 and ZDept CF2), when you type the letter z the list of values list is reduced to two values, and the cursor automatically skips to the last character. You then type 1 or 2 to select a report.
In the example above, with AutoReduction set to Normal, you must type all the characters if you want to use the AutoReduction feature to select one of the reports.
After you reduce a list of values to a single choice, AutoSelect automatically enters the value for you.
Use QuickPick: AutoReduction to help reduce list of value lists to a single choice. Then with QuickPick: AutoSelect you can, for example:
Specify the first character(s) of the choice you want
If only one value begins with the character(s), AutoSelect automatically selects the correct choice, closes the pop-up window, and enters the value.
To enter a QuickPick value when AutoSelect is set to No, you must press [Return] after selecting the value.
Sequential Numbering assigns numbers to documents that you create in Oracle financial products. For example, when you are in a window 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 windows within an application can 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.
This profile option is visible and updatable at the site, application, and responsibility levels, as described in the table below.
Note: The ability to set the Sequential Numbering profile option at the responsibility level was added for the Multiple Organizations Support feature. We recommend setting this option at either the site or application level unless you are implementing this feature.
| 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.
You can display 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 user name, but an incorrect password.
When the default printer identified in your user profile is unregistered or not specified.