In addition to Global Preferences, each of the OFS Analytical Applications has its local application preferences. In the same way as in Global Preferences, Application Preferences (for each application) employs a "delegation" model that allows Administrators to set some preference items for all users while allowing non-administrative users to personalize other preference items.
Application Preferences allow both Administrators and End Users to establish default values and to manage other core application parameters that affect the way business rules are created and the way Profitability Management processes are run.
The procedure for working with and managing Application Preferences includes the following steps:
· Updating Application Preferences.
Updating Profitability Management Application Preferences is a one-step process. You navigate to the Application Preferences screen and define your Preferences.
To update the Profitability Management application preferences, follow these steps:
1. Select Profitability Management from the LHS menu, and then select Application Preferences to display the Application Preferences page.
2. Input values for all the Profitability Management Application Preference items as described in Table 1.
Figure 1: Application Preference page
This illustration shows the Application Preference to enter the preference details of your application. Based on the preference details, you can manage other core application parameters that affect the system to create business rules and run Profitability Management Processes. Enter the parameter details and click Apply. See the following table for parameter details.
3. The following table describes the key terms used for this procedure.
|
Term |
Description |
|---|---|
|
Show Preferences For |
There are two modes in which you can access Application Preference. 1. Administrator: If you have Administrator privileges, you can define preferences for the "All User" group and their individual account, which may be the same or different from the "All User" settings. The Administrator can also designate the "All User" preferences as Editable or Non-editable on a row by row basis. If the individual preference is selected as "is Editable", then End Users can update or override the Administrator's default value for their own individual account. If the "is Editable" box is deselected, then End Users cannot change the default for their individual account. · End User: If you do not have administrator privileges, then certain preference items may have been pre-set by the administrator and the you may not be allowed to change the value. All Application Preference settings are displayed, regardless of access privilege. |
|
Active for Master Maintenance |
If you have more than one application available on their LHS menu, then you must designate Application Preferences from one of the applications as "Active for Master Maintenance". Certain preferences such as the default folder and read/write access setting will be referenced by items within Master Maintenance based on this selection. |
|
Security Map |
This option allows you to select an existing security map. Security Maps can be used to control the dimensions and dimension members each user can access when building and executing rules. For more information on Security Mapping, see the Oracle Financial Services Analytical Applications Infrastructure User Guide Release 8.1.0.0.0. |
|
As of Date |
All processes reference this date at runtime to determine the data to include in the process. The As-of-Date value you set in Application Preferences applies to interactive job execution (that is, when you choose to execute a rule directly from a Summary screen). For batch processing, the As-of-Date is derived from the Information Date. |
|
Show Execution Parameters |
If this option is selected, a pop-up window is displayed whenever you execute a process interactively from a Summary screen. Within this pop-up window, you may confirm or modify your run execution parameters (As-of-Date and Legal Entity). |
|
Legal Entity |
Similar to As-of-Date, all processes reference Legal Entity at runtime to determine the data to include in the process. The value of Legal Entity you set in Application Preferences applies to interactive job execution (that is, when you choose to execute a process directly from a Summary screen) and batch processing (that is, when you choose to execute a process from Simplified Batch). NOTE: Legal Entity is designed to support implementations that require multi-entity or multi-tenant functionality. For details, see Appendix: Multi-Entity. If your implementation does not require this functionality, you can utilize the Default Legal Entity in all your processes. No additional parameter is required for Legal Entity for command-line execution. EPM Engines read the default Legal Entity from the Application preference value saved for the User who is executing from the command-line. The default legal entity is a per-user preference setting. To set this, follow these steps:The default legal entity is a per-user preference setting. To set this, follow these steps: 1. Create a security-map in AAI containing the legal-entity hierarchy as an application admin. Set the default security-map in user preferences. 2. Navigate to "execution parameters" in user-preferences and choose the default legal-entity member. 3. If you do not want to use the Multi-Entity feature with Security, you need to save the Application preference for the user executing the batch. The typical selection for Legal Entity is Default Member in Application Preferences. nDefault implies -1 code. nThe default value for the Legal Entity dimension column in all instruments and ledger tables is -1. NOTE: Legal Entity only acts as a run-time parameter for Variable Allocation rules. The Legal Entity is an optional run-time parameter. Legal Entity does not apply to allocation rules using the table. |
|
Disable Legal Entity |
If Disable Legal Entity is selected in the Application preferences screen is checked, then the Legal Entity will no longer be a runtime parameter. This is an optional parameter. |
|
Default Total Error Message Limit |
Profitability Management Processes log error details are stored in the FSI_PROCESS_ERRORS table. This parameter defines the limit on the total number of errors that will be logged for any PFT Process. |
|
Default Error Message Limit Per Item |
This parameter defines the total number of errors that will be logged for a given type of error. |
|
Debugging Output Level |
The debugging output level determines the amount of SQL that will be written to the processing log. There are three levels available: · Do not output SQL to log file: A log file will not be created. · Show Significant Calculation SQL: Log file is created and will contain those SQLs that are tagged as significant. · Show all SQL: Log file is created and will contain all the SQL that the engines execute. The system administrator can access the Allocation Engine log files in the following location on the server: · $OFSAA_LOG_HOME/<MIS_DATE>/<INFODOM>/Allocation Engine/ folder The file names will be prefixed with the application initials and will also contain the unique batch run ID of the execution request. For example: Allocation Engine_<INFODOM>_Task1_<Allocation SYSID>.log The system administrator can access the UNDO log files in the following location on the server: § $OFSAA_LOG_HOME/<SYS_DATE>/<INFODOM>/Allocation Engine/ folder The file names will be prefixed with the application initials and will also contain the unique batch run ID of the execution request. Processing - Application Specific |
|
Enable UNDO for Selected Allocations |
Set this value to Yes to enable UNDO functionality for individual allocation rules. For details, see Allocation Execution History. |
|
Enable Mass UNDO |
Set this value to Yes to enable Mass UNDO functionality. For details, see Allocation Execution History. |
|
Enable UNDO for Selected Batches |
Set this value to Yes to enable UNDO for selected batches. For details, see Allocation Execution History. |
|
Enable UNDO for Selected Allocation Models |
Set this value to Yes to enable UNDO for selected allocation models. For details, see Allocation Execution History. |
|
Maximum Circular Allocation Iterations |
This value governs the maximum number of circular iterations within a Circular Allocation Model. Its purpose is to ensure that circular models will terminate without going into an infinite loop even if the model does not converge on the value of the Threshold Source Balance or Threshold Percentage you have selected for your model. For details, see Allocation Models. |
|
Scenario Values |
The Application Preference setting for the Scenario dimension allows you to run the same rules for different scenarios, such as Actuals, Budget, and so on. These values are inherited by rules that specify Use Application Preferences in their Sources, Drivers, or Outputs. For more details, see Allocation Specification. · Scenario for Source: When an allocation rule's Source is configured as Use Application Preferences in the Allocation Source section, the value used by the rule in its Source is the one specified in Application Preferences. · Scenario for Driver: When an allocation rule's Driver is configured as Use Application Preferences in the Allocation Source section, the value used by the allocation rule in its Driver is the one specified in Application Preferences · Scenario for Output: When an allocation rule's Output (applicable to both Debit and/or Credit) is configured as Use Application Preferences in the Dimension section, the value used by the allocation rule is the one specified in Application Preferences. |
|
Assumption Management Defaults |
|
|
Folder Name |
This parameter allows you to define the default folder selection. The folder selection for all rule types will default to this selection within the Summary page search screen and when creating a new rule. This selection acts as the starting value for convenience only and users can change to any other available value at their discretion. |
|
Access Type |
This parameter allows you to set the default access typesetting. Selections include Read / Write and Read Only. This selection acts as the starting value, users can change at their discretion. |
If you are the application administrator, define default values for the "All User" group by making the appropriate selection from the "Show Preference For," drop-downlist at the top of the page. Pay attention to the "Is Editable" status and determine which items require administrative control and which items non-administrative users will be able to set for themselves.
4. Select Apply to confirm changes.
5. Select Reset to Default if you want to clear all previously applied inputs and return to the original default state.