Alias |
Member description (maximum of 80 characters)
To use the Alias property, you create an Alias dimension, define properties, and associate the Alias dimension with another dimension. For example, you can create an Alias dimension with the values English, French, and Italian and then associate the Alias dimension with the Scenario dimension.
|
Alias |
Consolidate YTD
|
Specifies the view for consolidation. A value for this property is required. Specify Y for YTD or N for periodic.
|
ConsolidateYTD |
Default Frequency
|
Specifies the types of periods for which data input is valid for the scenario. A value for this property 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.
To enter a value for this property, you must create an association between the Scenario and View dimensions.
|
DefaultFrequency |
Default Frequency For IC Transactions
|
Specifies the default frequency for intercompany transactions. This property must be a valid frequency and can contain a maximum of 20 characters. The default for this property is <blank>.
To enter a value for this property, you must create an association between the Scenario and View dimensions.
|
DefFreqForICTrans |
Default Parent
|
Specifies the default parent for the scenario. The default parent value is a derived value and you cannot enter a value.
|
DefaultParent |
Default View
|
Specifies the view to use when Scenario View is selected in the point-of-view bar. A value for this property 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 loading it.
|
DefaultView |
Enable Data Audit
|
Specifies whether the scenario is audited. This property 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 Enable Data Audit set to False are audited.
-
O to audit only those accounts that have Enable Data Audit set to True
-
N to disable auditing for all accounts
Default Value: N
|
EnableDataAudit |
Enable Process Management
|
Specifies whether Process Management functionality is enabled. Specify one of these values:
-
Y to enable the Process Management option
-
N to disable the Process Management option
-
A to enable Process Management and e-mail alerting
Default Value: N
|
HfmEnableProcessManagement |
Maximum Review Level
|
Specifies the maximum Process Management review level for the scenario. Specify a review level from 1 to 10. A value for this property is required.
|
MaximumReviewLevel |
Name
|
Name for the scenario (required)
Names can contain up to 80 characters, including spaces, and cannot start with a space or contain these characters:
-
Ampersand ( & )
-
Asterisk ( * )
-
At sign ( @ )
-
Comma ( , )
-
Curly brackets ( { } )
-
Double quote ( “ )
-
Minus sign ( - )
-
Number sign ( # )
-
Period ( . )
-
Plus sign ( + )
-
Semicolon ( ; )
-
Slash mark ( / )
|
Name |
Phased Submission Start Year |
Specifies the start year. You can set the start year by deploying an application in Performance Management Architect or by loading metadata in a classic Financial Management application. This setting enables flexibility of setting a year of a scenario to start phased submission of process management.
|
PhasedSubStartYear |
Security Class
|
Name of the security class that defines the users who can access the scenario data (can contain up to 80 characters)
To enter a value for this property, you must associate the Scenario and Security Class dimensions.
|
SecurityClass |
User Defined 1, User Defined 2, User Defined 3
|
Custom information for the scenario (maximum of 80 characters)
The User Defined 1, User Defined 2, and User Defined 3 functions retrieve the text stored in this property.
|
UserDefined1
UserDefined2
UserDefined3
|
Uses Line Items
|
Specifies whether the scenario can have line items. Specify Y if the scenario can accept line items or N if the scenario cannot accept line items.
Note:
If you change this property after line-item detail is entered, the stored line item detail may no longer be valid for the scenario. The following 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.
|
UsesLineItems |
Zero View For Adjustments
|
Specifies how to interpret missing, adjusted data values for the period. A value for this property is required. Specify YTD or Periodic.
|
ZeroViewForAdj |
Zero View For Non-adjustments
|
Specifies how to interpret missing, unadjusted data values for the period. A value for this property is required. Specify YTD or Periodic.
|
ZeroViewForNonAdj |