Substitution variables are global placeholders for regularly changing information. Because changes to a variable value are reflected everywhere the variable is used, manual changes are reduced.
For example, many reports depend on reporting periods, if you generate a report based on the current month, you must update the report script manually every month. With a substitution variable, such as CurMnth, set on the server, you can change the assigned value each month to the appropriate time period. When you use the variable name in a Report Script, the information is dynamically updated when you run the final report.
You can use substitution variables with both Essbase - Aggregate Storage and block storage applications in the following areas:
- Aggregate storage outline formulas. See Using MDX Formulas.
- Block storage outline formulas. See Using Substitution Variables in Formulas.
- Essbase - Calculation Script (block storage databases only)
See these Oracle Essbase Administration Services Online Help topics: “Setting Headers in the Rules File” and “Mapping Field Names.”
- Partition definitions. See Substitution Variables in Partition Definitions.
- Data source name (DSN) specifications in Essbase - Rules File for SQL data source. See Oracle Essbase SQL Interface Guide.
- Security filters. See Filtering Using Substitution Variables.
- MDX statements See Using Substitution Variables in MDX Queries.
You can set substitution variables on the Essbase Server at any of the following levels:
- Server : Essbase Server—providing access to the variable from all applications and databases on the Essbase - Servers
- Application : Application—providing access to the variable from all databases within the application
- Database : Database—providing access to the variable within the specified database