Defining Scenario Members

The Scenario dimension represents a set of related data, such as budget, actual, or forecast. You define scenario members by using the attributes in the Scenario Member Attributes table.

The frequency of a scenario specifies the time period level at which data can be input. You can input and view either periodic or year-to-date data values. For example, if you input data as year-to-date values, when you select Periodic as the data view, the system automatically derives the periodic values from the year-to-date values.

For each scenario, you can specify how to display missing data. Oracle Hyperion Financial Management interprets missing data as zero for display on reports and for calculating summary periods. You can specify whether a zero for missing data is interpreted as zero for the current period (Periodic) or as zero for year-to-date (YTD).

You also enable process management options by scenario. You can select whether to enable process management, select the maximum level of reviews for process units, and select the start year for phased submissions.

Table 4-6 Scenario Member Attributes

Attribute	Description
ConsolidateYTD	Specifies the data view for consolidation - Year-to-Date or Periodic. This attribute is required. Specify Y for YTD or N for Periodic. If you set ConsolidateYTD to N, you must also set both ZeroViewForAdj and ZeroViewForNonadj options to Periodic.
DefaultFreq	Specifies the types of periods for which data input is valid for the scenario. This attribute is required. For example, a value of Monthly indicates that you can extract input data only in month-based periods, not in quarter-based or year-based periods. The frequency must be defined in the application profile.
DefaultParent	Specifies the default parent for the scenario.
DefaultView	Specifies the data view (Year-to-Date or Periodic) to use when Scenario View is selected in the point-of-view bar. This attribute is required. Specify YTD or Periodic. If you change the default view for a scenario and line-item detail has been entered, you should first extract the line-item detail and save it. Then delete the line-item detail from the scenario before changing the view. You must change the extracted line-item detail to match the new default view before reloading it.
DefFreqForICTrans	Specifies the default frequency for intercompany transaction data. This attribute must be a valid frequency and can contain a maximum of 80 characters. The default for this attribute is blank.
Description	Specifies the description for the scenario. The description can contain up to 80 characters, including spaces.
EnableDataAudit	Specifies whether changes to data for the scenario should be tracked in the data audit log. This attribute for an account or a scenario determines what can be audited. Specify one of these values: Y to automatically audit all accounts. Even accounts that have EnableDataAudit set to False will be audited. O to audit only those accounts that have EnableDataAudit set to True. N to disable auditing for all accounts.
MaximumReviewLevel	Specifies the maximum level of reviews for process units for the scenario. Each process unit can have up to 10 levels of review. Specify a review level from 1 to 10. This attribute is required.
Member	Specifies the name for the scenario. This attribute is required. The name must be unique and can contain up to 80 characters, including spaces, but cannot start with a space. Do not use these characters in the scenario name: Asterisk (*) At sign (@) Comma (,) Curly brackets ({}) Double quotation marks"" Minus sign (-) Number sign (#) Period (.) Plus sign (+) Semicolon (;) Slash mark (/)
PhasedSubmissionStartYear	In applications for which process management phased submissions is enabled, specifies the start year for phased submissions.
SecurityClass	Specifies the name of a valid security class that defines users who can access the data for the scenario. Security class names can contain up to 80 characters. For example, a user with None access rights to a scenario can open journal periods for the scenario.
SupportsProcessManagement	Specifies whether the scenario supports Process Management. Specify one of these values: Y to enable the Process Management without email alerts N to disable the Process Management option A to enable Process Management and email alerts
UserDefined1, UserDefined2, UserDefined3	Stores custom information for the scenario. You can enter a maximum of 256 characters. The UserDefined1, UserDefined2, and UserDefined3 functions retrieve the text stored in this attribute.
UsesLineItems	Specifies whether accounts can use line-item detail in this scenario. Specify Y if the scenario can accept line items or N if the scenario cannot accept line items. If you change this attribute after line-item detail is entered, the stored line item detail may no longer be valid for the scenario. These behaviors occur: If the scenario accepted line items and now it cannot, the line-item detail stored in the database is no longer valid. Only the total is displayed. If the scenario did not accept line items and now it can, there is a total amount but no corresponding line-item detail information for the scenario. You can extract the total and then load it as line-item detail data so that the total matches the line-item detail information. If the scenario does not accept line item detail initially, and if there is data present for the scenario, then it is not possible to enable line item details for the scenario or for any accounts in the scenario. To enable line items for that scenario, you must delete existing data, enable the line items in metadata and reload the data into the application.
ZeroViewForAdj	Specifies how to interpret missing, adjusted data values for the period. This attribute is required. Specify YTD or Periodic. If you set ConsolidateYTD to N, you must also set both ZeroViewForAdj and ZeroViewForNonadj options to Periodic.
ZeroViewForNonadj	Specifies how to interpret missing, nonadjusted data values for the period. This attribute is required. Specify YTD or Periodic. If you set ConsolidateYTD to N, you must also set both ZeroViewForAdj and ZeroViewForNonadj options to Periodic.