Entering Runtime Prompt Variables
Note:
-
You cannot add a RUNTIMESUBVARS section to the script of an Oracle Essbase business rule in Oracle Hyperion Calculation Manager. Rule level runtime prompt variables that are created in Calculation Manager are converted into RUNTIMESUBVARS only when you deploy Essbase applications.
-
If you launch a business rule with runtime prompts in Administration Services, MaxL, or any component that can launch a calc script, the runtime prompts in that business rule must have default values.
-
You can enter or edit values for runtime prompt variables when validating, debugging, deploying, analyzing, or launching a rule in Calculation Manager. You can also enter or edit runtime prompt variables when you are validating or deploying business rulesets. If the runtime prompt contains member limits, the validation checks only for valid member names (it does not validate whether the member is within the limit). Numeric and Integer type variables are validated for runtime prompt limits.
-
When you deploy Essbase business rules with runtime prompts to Essbase, you can use Oracle Essbase Administration Services, MaxL, or any component that can launch a calc script to launch the business rules. When you deploy these business rules, they are converted to Essbase calc scripts, and the runtime prompt variables are converted to RUNTIMESUBVARS in the Essbase script.
-
For information on desiging runtime prompts to honor Approvals security for members, see About Runtime Prompts in Approvals Security in Oracle Hyperion Planning Administrator's Guide.
To enter values for runtime prompt variables: