EPM Cloud Form Behavior in Smart View
Forms behave differently in Oracle Smart View for Office than they do in Oracle Enterprise Performance Management Cloud applications.
Data source types: Planning, Financial Consolidation and Close, Tax Reporting
-
Attributes in EPM Cloud forms are not displayed in Smart View.
-
Saving ad hoc grids as forms is not supported for grids containing attributes.
-
In forms containing custom attributes:
-
Smart View does not support using custom attributes as filters for base (regular) dimension members. The web interface supports this and displays custom attributes at runtime in the format:
base/regular dimension member name(small rectangle symbol).associated attribute dimension member name
-
Both the web interface and Smart View support using custom attribute dimensions as independent dimensions; for example, placing them on rows, columns, or the page POV, as with regular dimensions.
-
-
Multiple levels in an outline are displayed differently in Smart View than pages on the web application. Smart View displays up to four levels, while the web application displays up to two levels.
-
Excluding members does not affect totals on a form. When a member is excluded in the form definition (layout), the member is only excluded from displaying on the form; the member is not excluded from calculation.
-
If an administrator hides a dimension in the row axis of a form, this dimension does not display in the row header of the form in Smart View.
-
If an administrator has set up a form to use formatting from the web application, and not from Smart View, then no Smart View formatting options (from the Options dialog, Formatting tab) will be applied. This is true whether the Use Cell Styles or Use Excel Formatting option is selected in Smart View.
-
In composite forms, sections that display as charts in the web application will display as grids in Smart View.
-
In forms, the handling of decimal place settings between Excel, Smart View, and Oracle Hyperion Planning may, at times, cause rounding issues in submitted data. This can occur even when the decimal precision is set to two decimal places in both Excel and Oracle Hyperion Planning. For example, in a form, you may enter
68.68
, but Smart View sends the data to Oracle Hyperion Planning as68.67999999999
, instead of68.68
. -
If row drop-down menus are enabled on a form, then Smart Push (which pushes data from different cubes into one form) cannot be used.
-
When connected to an EPM Cloud provider, dynamic members, or "members on-the-fly," can be added in forms (and ad hoc grids) in the using business rules. See Launching Business Rules in Excel.
-
When you create a formula on members that calculates the value for a Summary Time Period and then you modify the data for the Summary Time Period member, sometimes Smart View considers that cell to be a dirty cell.
-
In Smart View, the display order of business rules attached to a form differs from the display order in Oracle Hyperion Planning.
-
When two forms are on two separate worksheets, the rule variable on the first form changes to the default value after refreshing the page dimension on the second form. This may cause the business rule to invoke an incorrect value for a runtime prompt variable. If this happens, display the runtime prompt to see its value before submitting the rule for execution.
-
In Smart View, the currency symbol in a cell is displayed differently from the Oracle Hyperion Planning web interface when the Oracle Hyperion Planning option, "Allow multiple currencies per entity," is set to true.
-
When the application Page preference, Indentation of Members, is set to "Indent level 0 members only," the indentation of dimensions in a form may be displayed incorrectly.
See also: Guidelines for Working with Native Excel Formatting and Forms in EPM Cloud