What Application and System Settings Can I Specify?

You can control many aspects of the application and the system, such as:

  • How to display thousands, decimals, and negative numbers in forms

  • Approvals actions to be taken when you're out of the office

  • Actions about which you want to be notified

  • Display the full names of users rather than user IDs

To change application and system settings:

  1. Click Application, and then click Settings.

  2. Specify defaults for the following application settings:

    • Alias Setting—For option descriptions, see Specifying a Default Alias Table and Setting Member and Alias Display Options

    • Number Formatting—For option descriptions, see Number Formatting

    • Approvals—Select whether to display aliases, show the approval units that are not started, and show approval units as aliases in approvals notifications

    • Notifications—Enable notifications for task lists, approvals, and job console

    • Page—Set defaults for indenting members on a page and setting the number of items on the page drop-down

      Note:

      The Number of Items on the Page Drop-down option lets you shorten the member list so that the Search box can be more easily seen. If the list is shortened to 10 members, for example, then you won't need to scroll to see the Search box.

    • Other Options—Set options for date format, attribute dimension date format, partial grid fetch size, whether to suppress application management options in Smart View, and whether to enable data loads for ad hoc read-only roles. For example, in the option Set Number of Seconds Before Rules Run in Background, enter a value between 0 and 600.

    • Predictive Planning—Predictive Planning options for specifying the scenario/version to use for historical data values, and the prediction interval to use for worst case and best case values. Note that if no version member is specified for historical data, Predictive Planning uses Actual ([Current Form]) as the basis for historical data, which results in using the first version on the form for the historical data.

  3. Specify options for the following system settings:

    • Display Users’ Full Names—If selected, the system displays the user's full name (for example, Max Hennings). If cleared, the system displays the user's ID (for example, VHennings).

    • Include Shared Members in Cube Refresh

    • Email Character Set

    • Business Rules Notification—If set to Yes, notifies users or groups when rules (which are enabled for notification in Calculation Manager) are completed or encounter errors. In Notify These Users, select the users or groups to notify.

    • Allow Drill Down on Shared Members in Ad Hoc FormYes enables drilling on shared members in an ad hoc grid. No disables drilling on shared members in an ad hoc grid.

    • Minimize Approval Process Emails—Reduces the number of emails a user receives when using Approvals. The default is No.

      If Yes is selected, only one email notification (for the approved parent entity) is sent to the new owner of the planning unit. Separate email notifications aren’t sent for every child entity in the planning unit hierarchy. If No is selected, owners that are set at parent nodes will receive emails for the selected node as well as an email for each child node.

    • Enable Use of the Application for—Determines whether users can access the application in administration mode, such as during backups. When you select Administrators, if any nonadministrative users are logged on to the application, they are forced off the system and will not be able to log on. To restore access to an application for all users, select All users.

    • Assign Application Owner—Assign ownership of the application to another administrator.

    • Enable the Display of Substitution Variables—Set how substitution variables display in the Member Selection dialog box when users respond to runtime prompts in business rules. Display All displays all substitution variables. Display None displays no substitution variables. Enable Filtering displays only substitution variables that are valid for the runtime prompt.

    • Smart View Suppression Behavior—Choose a suppression behavior in Oracle Smart View for Office for cases where rows and columns contain missing data or zeroes.

      • Legacy (default)—Suppresses rows, or columns, or both that contain No Data/Missing or Zero, but not both.

      • Standard—Suppresses rows, or columns, or both that contain both No Data/Missing and Zero.

    • Smart View Ad Hoc Behavior—Choose to enable enhanced ad hoc features and behaviors in Smart View:

      • Native (default)—Does not enable enhanced ad hoc features.

        Supported for all Smart View releases.

      • Standard—Enables enhanced ad hoc features.

        Supported for Smart View release 11.1.2.5.900 and later.

      The enhanced ad hoc features and behaviors are:

      • In-grid POV—POV members are placed on the grid instead of in the POV toolbar.

      • Submit without refresh—Using the default Submit Data button in the Smart View ribbon, all cells in a grid are submitted, including all data cells that have been explicitly modified (made dirty) and those that were not modified. For this operation, all data cells are marked dirty and submitted. Once the submit operation is complete, the entire grid will be refreshed.

      • Free-form support—Supports empty columns and rows anywhere in a grid and changing the alias table. Additionally, supports member auto-refresh where deleted members are returned to the grid upon refresh.

      • Multiple-grid ad hoc—Supports multiple ad hoc grids on the same Excel worksheet. With multiple-grid ad hoc, you can submit data from any grid on the sheet. Grids based on aggregate storage cubes and block storage cubes are supported on the same sheet. Each grid is independent; for example, if required, you can change the alias table for only one grid on the sheet.

    • Enable currency calculation based on scenario time period—Choose whether to enable currency calculations in forms and batch currency rules based on the scenario time period. Selecting Yes restricts currency calculations to the range defined for the scenario time period. Selecting No calculates everything based on exchange rates and reporting currency and is not restricted based on the scenario time period range. Note that the behavior of the currency conversion script is dependent on this application setting at the time the rule is executed.

    • Export EPM Cloud Smart List textual data during daily maintenance for incremental data import—Choose whether to perform a complete export during the daily maintenance process or to create an application backup:

      • Yes—Performs a complete export, such that data, including the Planning Smart List data, can be incrementally imported to an application (this option may lengthen the maintenance process duration)

      • No (default)—Creates an application backup during the maintenance process, such that data can be used as part of a full restoration

      For more information, see Setting the Daily Maintenance Process Time.

    • Link Accounts by Default—For block storage (input) cubes, select whether to XREF linked account members by default.

      • Yes (default)—XREFs will be created on account members, and the application will work the same way it has in earlier releases.
      • No—XREFs will not be created for account members, which may improve the application’s performance. With No selected, after Cube Refresh is run, all existing XREFs on account members will be deleted, and non-source cubes will no longer show data from the source cube.

      Note:

      HSP_LINK and HSP_NOLINK UDAs on specific account members override the XREF setting for those account members. For example, if this option is set to No and you use the @XREF function to look up a data value in another cube to calculate a value from the current cube, you can add theHSP_LINK UDA to such members to create the @XREF function only for these specific members. If this option is set to Yes, HSP_NOLINK works the same way it worked in earlier releases and prevents XREFs from being created on specific members.