Which two types of Groovy Rules are supported by Oracle?

Oracle EPM Cloud Planning officially supports two primary types of Groovy business rules. The first type (B) involves using Groovy to dynamically generate and execute a targeted Essbase calculation script at runtime. This is powerful for creating highly efficient calculations based on the current context, such as runtime prompts (RTPs), the user's point-of-view (POV), or the specific data cells being modified in a form. The second type (C) involves using Groovy's programming capabilities to perform complex data validations, manipulations, or to orchestrate multi-step processes. These rules can run before or after a data form save, check the entered data against business policies, and cancel the operation with an error message if validation fails.

A. Member formulas are defined directly on members in the Dimension Editor, typically using MDX or standard Essbase functions, not Groovy. Groovy rules are separate objects created in Calculation Manager.
D. This describes a potential use case or execution context (dashboards) for rules, not a fundamental type of Groovy rule. The core rule types are defined by their function (calculation generation vs. validation/process automation).

1. Oracle Cloud

EPM

Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud (December 2023)

Chapter 12: Working with Groovy Rules

Page 255.

The documentation explicitly states: "There are two types of Groovy business rules: 1. A Groovy business rule that generates a focused calculation for the data that was changed in a form. This type of rule can dynamically generate a calculation script at runtime based on the context. 2. A Groovy business rule that validates data in a form before the data is saved. This type of rule can perform data validations and cancel the operation if the data entered violates company policies." This directly supports answers B and C.

2. Oracle Cloud

EPM

Administering Planning (December 2023)

Chapter 11: Designing Business Rules

Section: About Groovy Business Rules.

This section reinforces the two primary use cases: "You can write a Groovy rule to: ... Dynamically generate calculation scripts at runtime based on context... Perform data validation and cancel the operation if the data entered violates company policies." This further validates the distinction between dynamic calculation script generation (B) and data validation/process control (C).