Creating a Business Ruleset

You can create a business ruleset from the System, Filter, Custom, and Deployment views, and from the Ruleset and Template Designers.

To create a business ruleset:

  1. Right-click RuleSets, and then select New.
  2. In the New RuleSet dialog box, enter a name and select and application type and application, and then click OK.

    If you are adding a ruleset from the System View, the application type and application are automatically populated.

    If you selected a Oracle Hyperion Financial Management application type and application, select the Calculation Type.

  3. From Existing Objects, drag existing rules and rulesets and drop them into the flow chart.

    Oracle Hyperion Planning and Oracle Essbase rulesets can contain rules and rulesets that are created in, and deployed to, different applications. Financial Management rules and rulesets must belong to the same calculation type or belong to the Generic calculation type.

    Rules in Financial Management applications are launched sequentially within a ruleset, so the order of the rules is important.

  4. Do any of the following tasks:
    • To change the order of the rules in the ruleset, click the up or down arrows, or right-click the rule, and then select Move Up or Move Down.

    • To remove a rule from the ruleset, right-click the rule, and then select Remove.

    • To open a business rule for editing, right-click the rule, and then select Open.

  5. In Properties, enter properties for the ruleset.

    In the RuleSet Designer, if you select a rule within the ruleset you are creating, its properties are displayed in Properties instead of the ruleset's properties.

    Select Enable Parallel Execution if you want the rules and rulesets in the ruleset to launch simultaneously. By default the rules and rulesets belonging to a ruleset launch sequentially - each rule or ruleset in the ruleset must run without errors before the next rule or ruleset is launched.

    If the ruleset contains nested rulesets, and the nested rulesets have a different Enable Parallel Execution setting than the parent ruleset, the setting of the nested ruleset applies. For example, if you have ruleset1 (that is flagged for parallel processing) and it contains rule1, rule2, and ruleset2 (flagged for sequential processing), the rules and rulesets in ruleset2 are processed sequentially, even though ruleset1 is flagged for parallel processing.

    Financial Management users only:

    • Select Enable Logging so, if the rules in the ruleset have log text, the log text is included in the log file when the ruleset is launched. You can enable logging for rules, rulesets, and components. However, you specify what log text to include, if any, with a business rule's formula statements.

      Note:

      If logging is not enabled for a ruleset, but is enabled for a rule and component that belong to the ruleset, no log file is created because the log setting for the ruleset overrides the settings for the rule and component.

    • Select Enable Timer so the time taken to process the ruleset is recorded in the log file when the ruleset is launched. You can enable the timer for rules, rulesets, and components. The process time is included in the log file for every object whose timer is enabled. For example, if you have a ruleset whose timer is enabled and the ruleset contains three rules whose timers are enabled, the time taken to process the ruleset, and each rule in the ruleset, is recorded.

    • Select Enable Launch so the ruleset can be launched in Financial Management.

      Note:

      You cannot launch business rules in Financial Management.

    Oracle General Ledger users only: Use the Start Date and End Date features to specify a date range during which the business ruleset may be launched. You will be unable to launch the business ruleset outside of this date range.

    • Select Start Date to access a calendar from which you can select a start date after which the business ruleset may be launched.

    • Select End Date to access a calendar from which you can select an end date prior to which the business ruleset may be launched.

  6. On the Usages tab, review what rulesets are using this ruleset, if any.

    By default, a ruleset is used by no other rulesets when you create it so this tab is empty when you initially create the business ruleset.

    If you select a rule in the ruleset, you can see the names of the business rulesets.

  7. On the Variables tab, review and enter information about the variables used in the ruleset.

    Select Merge Variables to merge all instances of the same variable used in the rules within this ruleset so only the first instance of each variable is displayed when the rule is launched. If you do not merge variables, all instances of each variable are displayed.

    If you select Merge Variables, the first value that the user enters for the runtime prompt is used for all subsequent occurrences of that runtime prompt during validation and launch.

    Note:

    You can merge variables for Planning, Essbase, or Oracle General Ledger variables,

  8. Click Save button.