Differences between Financial Reporting and Management Reporting

When you migrate a report from Financial Reporting to Management Reporting, the system will convert as many elements of the original report into the Management Reporting equivalent as possible. However, there are differences between the two products, and not all elements exist in both products. You should consider the migrated report as a starting point for converting a Financial Reporting to Management Reporting, but it is likely that you will have to modify certain elements after the report has been migrated in order to produce a report that is equivalent to the original report. This topic will help you understand the differences between Financial Reporting and Management Reporting so that you can modify the migrated report as necessary.

Financial Reporting Functions and their Management Reporting Equivalents

The following section describes the functions that are available in Financial Reporting and their Management Reporting equivalents where available.

Note:

The syntax for text functions differs between the two products. Financial Reporting requires << and >> brackets around functions (for example, <<MemberName()>>). Management Reporting does not require the brackets.

Table B-1 Financial Reporting Functions and Management Reporting Equivalents

Financial Reporting Function Management Reporting Equivalent
Annotation  
CalcStatus  
CellText CellText
Datasource  
Date DateTime
GetCell CellValue
GetHeading HeadingValue
GridDimension  
HFMCurrency  
LabeledCellText  
ListOfCellDocuments  
MemberName MemberName
MemberAlias MemberAlias
MemberDescription MemberProperty
MemberProperty MemberProperty
MemberQualifiedName MemberName
Page PageNumber
PageIndex PageNumber
PageCount PageCount
PlanningAnnotations  
ProcessManagementStatus  
ReportAuthor ReportAuthor
ReportCreated ReportCreateOn
ReportDesc ReportDescription
ReportFolder ReportLocation
ReportModified ReportModifiedOn
ReportModifiedBy ReportModifiedBy
ReportName ReportName
ReportRunBy ReportRunBy

Note:

The Management Reporting text function "DateTime" has two parameters, one for date and one for time, the Financial Reporting "Date" function only has one parameter format string. When migrating Financial Reporting reports using the "Date" function, where the time is also specified, the migrated function in Management Reporting needs to be modified to include an extra parameter of "none", otherwise the time result is repeated. For example, a migrated text function as follows: DateTime("dd-MMM-yy h:mm:ss a") needs to be manually modified to the following: DateTime("dd-MMM-yy h:mm:ss a", none)

In Financial Reporting, the text functions allowed for the use of cur, curr or current to indicate the current row, column, or grid. Management Reporting does not support curr. Instead, the functions allow for optional parameters where curr was used.

For example, in the Financial Reporting function <<MemberName("curr", "curr", "Product", "curr")>>, where the "curr" elements stand for grid name, row, column, or page, the "curr" elements are not necessary in Management Reporting. The Management Reporting equivalent would be MemberName("Product"). The "grid" defaults to the grid that contains the function (or the only grid if the text function was in a text object and there was a single grid). If there are more than one grid, and the text function occurs in a text object, then the gridname parameter is required.

Differences in the Point of View (POV)

There are differences between the way that Financial Reporting and Management Reporting manage the POV:

  • In Financial Reporting, by default a grid POV has a value of "User Point of View". In Management Reporting, the default value is "Default".

  • In Financial Reporting, both the grid and user POV are able to have choice lists. In Management Reporting, the list is called a "Suggested List". See Setting Up the Point of View.

  • In Financial Reporting, a report designer can select an initial member to be used on the Grid POV. If a dimension on the Grid POV has a selection, this acts as the initial member for that dimension on the Grid POV every time the report is run. In Management Reporting, a report designer cannot select an initial member to be used in the Local POV when the report is run. If a Suggested List is defined, the local POV uses the last selected Global POV member for the dimension as an initial member when the report is run. However, if the suggested list is defined as a single member selection, then the POV Dimension uses that member as the initial member when the report is run, even when display suggestions only option is not selected.

  • Financial Reporting Grid POV dimensions that have “User Point of View” selected will be migrated to use the Global POV in Management Reporting. If the report has multiple data sources, only the first data source’s dimension will be migrated to the Global POV. All other Financial Reporting Grid POV dimensions will be migrated to the Local POV in Management Reporting.

  • In Financial Reporting, grids can have page axes. In Management Reporting, the page axis functionality is supported through the 'Print All Selections' option on a dimension in the POV. If the member selection contains a Prompt it will be migrated as a Global POV dimension in Management Reporting.

  • In Financial Reporting, in the grid editor a user sees the values of the user POV for dimensions on the grid POV. In Management Reporting, the user sees only 'Default', or the 'Suggested List' members.

Grid Object Differences

When working with grid objects, consider the following:

  • In Management Reporting grid headers are frozen by default.

  • The heading type 'Entity Short Name' is not supported in Management Reporting.

  • Management Reporting does not have a Hide Grid property; all hidden grids are managed in the Hidden Sheet. Hidden grids in Financial Reporting are moved to the Hidden Sheet in Management Reporting, where they can be edited and managed. Any grids that are in the Hidden Sheet will not be displayed in the report output.

  • The Row/Column property for ‘Page Break Before = Position at Top’ is not supported in Management Reporting. Row/Column page breaks will always appear in the same position on the following page.

  • The member selection 'Show Supporting Detail' option is valid only on the row axis when there is a single layer and the account dimension is on the row.

  • In Financial Reporting, the 'Show Supporting Detail' unary operator is set at the row level. In Management Reporting, it is set at the grid level. If the Financial Reporting report contains different property values for 'Show Supporting Detail' for different rows, the system displays a migration error.

  • If the grid object has a page axis member selection set to 'Current Point of View', the system will replace the selection with the dimension-name-member. This condition is not valid in Management Reporting, since the page axis member selection is migrated to a suggested list on a grid POV dimension. In the log for the migration, the system will display :" In grid object 'Grid1', the page axis member selection has a 'Current-Point-of-View' reference, which is not valid."

  • If the Financial Reporting page axis member selection contains multiple prompts, the member selection will be migrated to a single prompt in Management Reporting.

  • A single grid cannot reference multiple data sources in Management Reporting. If a Financial Reporting grid references multiple data sources, the system displays a migration error.

  • Since a Management Reporting grid does not have a page axis, if a Financial Reporting grid contains sorting on the page axis, the system displays a migration error in the migration log.

  • The 'Show Row Headings before Column' property, which allows you to create butterfly-type reports, is not supported in Management Reporting.

  • For migrated Financial Reporting reports where the cell shading is set to white (FFFFFF) by default, you must set the Management Reporting report cell shading to "Transparent" in order to use the grid property for row banding. Otherwise, the system will recognize the cell shading as having an existing format applied and row banding will not be applied.

  • In Management Reporting the Financial Reporting Conditional Format of Format Cells then Alignment then Indent Increases For Each Generation By: is not supported. Indent by Generation can be applied as a cell property after import.

  • If a user has merged heading and data cells in Financial Reporting and imports the report to Management Reporting, the import splits the merged cells into merged heading cells and merged data cells. This will change how the report looks and works and the user will need to modify the report.

  • Management Reporting does not support empty formula rows or columns in a grid, when importing Financial Reporting (FR) reports with empty formula rows or columns, a warning message is displayed. The report designer will need to edit the Management Reporting grid formula to either set up a formula and enter "0" or replace the formula row or column with a separator row or column, if nothing is needed to display.

Image Object Differences

Financial Reporting supports a stretch option for images. Management Reporting does not support stretching or cropping; instead, the image will be sized to the correct aspect ratio.

Text Object Differences

In Financial Reporting, the text object has an 'AutoSize' property. In Management Reporting, the size options for height are:

  • Fixed (equivalent to AutoSize=Off)

  • Fit (equivalent to AutoSize=On)

  • Minimum

Chart Object Differences

The following Financial Reporting chart properties are not supported in Management Reporting charts:

Note:

After importing a Financial Reporting report with Combo charts, the chart line colors in Management Reporting do not match the colors in Financial Reporting.

  • Font Angles: Font angles for all font settings for text in the Format Chart dialog box

  • Format Chart:

    • Appearance:

      • Title Box Color

      • Title Box Border Color, Type, and Width

      • Grid Depth

    • Legend:

      • Suppress Repeating Labels

      • Background Border Type and Width

    • Axes:

      • X-axis Background Color

      • X-axis Border Color, Type, and Width

      • Y-axis Background Color

      • Y-axis Border Color, Type, and Width

      • Y-axis Override Number Format

      • Y2-axis Title Box

      • Y2-axis Override Number Format

    • Pie Options:

      • Pie Label Position

      • Pie Slice Angle

Alignment Differences

In Financial Reporting, an object can be top/left/bottom and left/right/center aligned. However, the object is aligned with the appropriate edge of the page (taking into account the margins and header/footer height). In Management Reporting, the same alignment options are supported. However, the object can be aligned a certain distance from the appropriate edge. This is supported via the ‘Indent’ alignment property.

Member Selection Differences

When working with grid objects, consider the following:

  • Duplicate members in the same segment are not allowed and are removed.

  • The Financial Reporting advanced member selection operators such as AND, UNION, OR and NOT are converted to the Management Reporting member selection functions Intersect (which combines multiple members and functions, previously the AND operator in Financial Reporting) and Except (excludes a member or function from another function, previously the NOT operator in Financial Reporting). The Financial Reporting OR and UNION operators performed the same operation and are the default for any member selections, therefore there is no need to specify anything additional in Management Reporting for these two operators. There are two migration differences for the NOT operator:

    • Management Reporting member selections do not support migrating nested 'Not' statements. For example, "member-selection1 and not member-selection2" is migrated, while "member-selection1 and not not member-selection2" is not.

    • Management Reporting member selections do not support migrating a 'Not' statement on the first member selection. For example, "member-selection1 and not member-selection2" is migrated, while "not member-selection1 and member-selection2" is not.

  • In Financial Reporting, member selection supports SuppressSharedMembers. In Management Reporting, suppress shared members is supported as an option on an existing member selection (added via a member selection menu).

  • Management Reporting does not support a user-defined 'User member list', as Financial Reporting does.

  • The following Financial Reporting member selection functions are not supported in Management Reporting:

    • MatchEX

    • TopOfHierarchy

    • LSiblings

    • RSiblings

    • Top

    • AllMembers

  • In Financial Reporting, a system-member-list is either a named level or a named generation. The underlying data source provides these names, which take the form of 'Lev<n>,<dimension name>' or 'Gen<n>,<dimension name>' by default. However, a data source administrator can also give a user-specified name to a level or generation (for example, SKU or Country). If the system-member-list is one of the default names, it gets converted to the 'LevelMembers' or 'GenerationMembers' member selection functions. If the system-member-list has a non-default name, the system cannot determine what the available list of names is without connecting to the data source. Therefore, the system displays a migration error and the member selection is converted to the dimension parent member.

  • When migrating members, any member name in Financial Reporting that is prefixed with a "$" (meaning it is a substitution variable ) is converted to a substitution variable and prefixed with an "&" in Management Reporting.

  • In Financial Reporting Web Studio, duplicate prompt labels in a grid are permitted. In Management Reporting , duplicate prompt labels are not permitted. If the reuse of prompt definitions in multiple locations is required, a Saved Selection should be created for the prompt and select the Saved Selection from the multiple locations. If the Financial Reporting Web Studio report contains duplicate prompt labels, where one prompt definition allows selection of multiple members and another prompt definition, with the same label, is used as a single selection in a member selection function (for example, Children (Prompt), upon migration to Management Reporting, the report designer will need to manually adjust the duplicate prompt labels where validation errors occur.
  • In Financial Reporting Web Studio, the Property member selection function works with member names and aliases, attribute members as well as UDAs. In Management Reporting, the use of member names and aliases is not supported

Features Not Supported in Management Reporting

The following Financial Reporting features are not supported in Management Reporting:

  • Export to Office

  • Planning Unit Annotations

  • Annotations

  • auto calculation

Other Differences

Keep in mind the following considerations when migrating reports:

  • MemberOverride is not supported in Management Reporting

  • Drill to content cannot be used to drill to a cell file attachment sourced from an Essbase Linked Reporting Object or Oracle Enterprise Performance Reporting Cloud cell file attachment.

  • Linked objects are not supported in Management Reporting. If a linked object is found in a Financial Reporting report that is being migrated, the system will display a migration error.

  • If you migrate an EPM Cloud report (for example, Oracle Enterprise Planning and Budgeting Cloud) with conditional formatting or suppression by Account Type (for example, suppressing rows with an account type of Revenue), you may have to update the conditional expression in order for it to be applied correctly. This is because in Financial Reporting, the conditional expressions for Account Type check only if the type is Expense or NonExpense, while in Management Reporting, the expression checks if the account type is an Asset, Liability, Equity, Revenue, Expense, or NonExpense type. As a result, you should update the conditional expression to check for the true account type. For example, expressions that suppress a Revenue account type (which is considered NonExpense in Financial Reporting) must be updated to suppress the true account type of Revenue after the report is migrated.

  • Management Reporting does not support a 'Custom' paper format size. The migration will convert this size to 'Letter'.

  • Management Reporting does not support a Super A3 paper format size. The migration will convert this size to 'Letter'.

  • In Financial Reporting users can add MemberOverride to the CellText function. In Management Reporting this is not currently supported.