Reporting tree definitions in financial reports
This article provides information about reporting tree definitions. A reporting tree definition is a report component, or building block, that helps define the structure and hierarchy of your organization.
Financial reporting supports flexible reporting, so that you can easily make changes as your business structure changes. Reports are built from various components, or building blocks. One of these building blocks is a reporting tree definition. A reporting tree definition helps define the structure and hierarchy of your organization. It's a cross-dimensional hierarchical structure that is based on the dimensional relationships in your financial data. It provides information at the reporting unit level and at a summary level for all units in the tree.
Reporting tree definitions can be combined with column definitions and report definitions, to create a building block group that can be used by multiple companies. A reporting unit is used for each box in an organizational chart. A reporting unit can be an individual department from the financial data, or it can be a higher-level summary unit that combines information from other reporting units. For a report definition that includes a reporting tree, one report is generated for each reporting unit and for the summary level.
All these reports use the row and column definitions that are specified in the report definition, unless the report definition specifies that the reporting tree from the row definition should be used. Row and column definitions are important components in the design and functionality of financial reports. Reporting trees increase the power of the components and support flexible reporting as the business structure changes. Financial reports that aren't based on a reporting tree use only some of the capabilities of financial reporting. You can use multiple reporting tree definitions together with the same row and column definitions to view your organization's data in various ways.
Reporting tree best practices
Before you create a reporting tree, consider the following best practices:
- First, determine which reporting dimensions your legal entity or company requires.
- Consider how you've set up your structure, and then draw an organizational chart of your company. The organizational chart will help you visualize how to group the reporting units into one or more reporting trees.
- Start with the lowest available level of detail, such as the departments and projects that are defined in the financial data. Add as many boxes to the level of detail as are require to show higher-level divisions or regions. Each box represents a potential reporting unit in any reporting tree that you create.
- You must also consider the best way to build your trees. You can use an automated build process to generate a reporting tree, or you can manually create a reporting tree. It's important that you understand both methods before you design your trees.
- You can use the reporting units that are defined in your financial data system to add reporting units to the reporting tree definition. Organizational hierarchies can also be selected as an option in tree types. For more information, see Organizations and organizational hierarchies overview.
Create multiple reporting trees
You can create an unlimited number of reporting trees to view your organization's data in various ways. Each reporting tree can contain any combination of departments and summary units. A report definition can contain a link to only one reporting tree at a time. By rearranging the structure of the reporting units, you can create different reporting trees. You can then use the same row and column definitions for each reporting tree. In this manner, you can quickly create different financial report layouts. If you create multiple reporting trees, you can print a series of financial statements each month that analyze and present your company's operations in various ways. For more information, see the examples of reporting unit structures at the end of this article.
Create a reporting tree definition
A reporting tree definition contains the columns that are described in the following table.
Reporting tree column | Description |
---|---|
Company | The company name for the reporting unit. The @ANY value, which is typically assigned only to the summary level, enables the reporting tree to be used for all companies. All child branches have a company assigned to them. |
Unit Name | The code that identifies this reporting unit in the graphical reporting tree. Be sure to establish a unique coding system that is consistent, and that will be easy for users to understand. |
Unit Description | The reporting unit title appears in the report header or footer if you enter UnitDesc as a code on the Headers and Footers tab of the report definition. The title appears in the report row description if you enter UnitDesc in the Description cell of the row definition. |
Dimensions | A reporting unit that draws information directly from the financial data. It defines the logical positioning and lengths for the account and related segments. Every reporting unit row must have a dimension in this column. You can also put a dimension in a summary unit row (for example, for expenses that are directly related to that unit). If you enter a dimension in a summary unit row, accounts that are used in parent units should not be used in child units. Otherwise, amounts might be duplicated. |
Row Definitions | The name of the row definition for the reporting unit. The same row definition is used for each unit of the reporting tree. When you generate a report, this row definition is used for each reporting unit. The row definition can include multiple financial dimensions links. If a row definition is specified in the reporting tree, select the Use row definition from reporting tree check box on the Report tab of the report definition. |
Financial Dimensions link | The financial dimensions link to use for the reporting unit. Financial dimensions links are defined for the row definition to identify the financial dimensions to link to. |
Page Options | This column controls whether the details for the reporting unit are suppressed when the report is viewed or printed. |
Rollup % | The percentage of the reporting unit that should be allocated to the parent unit. The percentage that you enter in this column applies to each row of the row definition before the value in the row is added to the parent report. For example, if a child unit must be divided evenly between two departments, the amounts in each row are multiplied by 50 percent before the value is added to the department report. One reporting unit can't have two parent units. To allocate the amounts from a reporting unit to two parent units, create another reporting unit that has the same dimension to roll up the additional 50 percent. Enter whole percentages without a decimal point. For example, 25 represents 25-percent allocation to the parent. If you include a decimal point (.25), 0.25 percent is allocated to the parent. To use a percentage that is less than 1 percent, use the Allow Rollup <1% option in the report definition. This option is on the Additional Options tab in the Report Settings dialog box. You access this dialog box from the Other button on the Settings tab of the report definition. |
Unit Security | Restrictions on the users and groups that can access the information for the reporting unit. |
Additional Text | Text that is included on the report. |
To create a reporting tree definition, follow these steps.
Open Report Designer.
Click File > New > Reporting Tree Definition.
Click Edit > Insert Reporting Units from Dimensions.
In the Insert Reporting Units from Dimensions dialog box, select the check box for each dimension to include in the reporting tree. The Insert Reporting Units from Dimensions dialog box contains the following sections.
Section Description Reporting dimension segmentation Use the Split Segments and Combine Segments buttons to change the number and length of segments. NOTE: You can combine only segments that you've split. To combine multiple dimensions, use wildcard characters in your dimension values. Include/Character position This section lists the dimensions that are defined in the financial data and shows the number of characters in the longest value that is defined for each dimension. Select the check box for a dimension to include that dimension in the reporting tree hierarchy. Segment hierarchy and ranges This section shows the dimension hierarchy. You can move the dimensions in the list to change their reporting order. In the From Dimension and To Dimension fields, you can specify a range of values in each dimension. If you don't specify a range, all dimension values are inserted into the reporting tree. NOTE: If you're using more than one dimension, only dimension combinations that have been posted to are returned in the results. For an illustration that shows an example of the Insert Reporting Units from Dimensions dialog box, see the "Example of the Insert Reporting Units from Dimensions dialog box" section later in this article.
To create additional segments (for example, by split one segment into two shorter segments), click the correct location in a Character position field, and then click Split Segments.
To merge two segments into one segment, click in either of the segment boxes to merge, and then click Combine Segments.
The hierarchy defines how dimensions report to each other and the range for each dimension. To change the hierarchy of the dimensions, in the Segment hierarchy and ranges area, select the dimension to move, and then click Move Up or Move Down.
To specify a range of dimension values to add to the new reporting tree, in the Segment hierarchy and ranges area, follow these steps:
- In the From Dimension field for that dimension, enter the first value in the range.
- In the To Dimension field, enter the last value in the range.
Repeat steps 7 through 8 for each dimension in the Segment hierarchy and ranges area.
After you've finished defining how your reporting units should be brought into the new reporting tree, click OK.
Click File > Save to save the reporting tree. Enter a unique name and description for the reporting tree, and then click OK.
Open an existing reporting tree definition
- In Report Designer, click Reporting Tree Definitions in the navigation pane.
- Double-click a name in the reporting tree list to open it.
- To view any building blocks that are associated with the reporting tree, right-click the reporting tree definition, and then select Associations.
Roll up data in a reporting tree
When you use a reporting tree, you can aggregate amounts from child reporting units at the level of the parent reporting unit. This aggregation is known as rolling up the data. The following rules are used to roll up amounts to parent units in a reporting tree:
In a reporting tree, child units must contain dimensions, unless the reporting tree is a single-level tree. Parent units usually don't contain dimensions in a reporting tree.
Note
If you specify dimensions for both child units and parent units, you might cause duplication of data in the report.
Reporting units that contain dimensions in the reporting tree correspond to the dimensions that are used in the row and column definitions. The combination of dimensions determines the amounts that are returned for that unit. For example, in example 2 later in this article, lines 6 and 7 return values only for departments 00 and 01, respectively.
The amounts for parent reporting units that don't contain dimensions in the reporting tree are determined from the child unit report and roll up the amount to the specified parent unit. For example, if the parent unit (see Contoso USA in example 2 of data roll-up examples) has two child units (022 and 023) and doesn't contain dimensions, a report is generated for each child and the parent. The parent total is the sum of the two child amounts.
Manage reporting units
Each reporting tree definition is displayed in unique views. There is a graphical view that shows the parent/child hierarchy and a worksheet view that shows the specific information for each reporting unit. The graphical view and the worksheet view are connected. When you select a reporting unit in one view, it's also selected in the other view. You can build cross-dimensional hierarchies that are based on the dimensional relationships in the financial data. When you create a reporting tree definition, you can use the same row definitions multiple times, regardless of whether you're generating a departmental income statement or a consolidated summary income statement. The dimensions that are defined in the row definition can be combined with dimensions in the reporting tree definition to provide various views of your organization's performance.
Reporting unit structure
The following types of reporting units are used in financial reporting:
- A detail unit draws information directly from the financial data.
- A summary unit summarizes data from lower-level units.
A parent reporting unit is a summary unit that aggregates summarized information from a detail unit. A summary unit can be both a detail unit and a summary unit. Therefore, a summary unit can draw information from a lower-level unit, or the financial data. A parent unit can be the child unit of a higher-level parent unit. A child reporting unit can be a detail unit that pulls information directly from the financial data. A child reporting unit can also be an intermediate summary unit. In other words, it can be the parent unit of a lower-level unit and also the child unit of a higher-level summary unit. In the most common scenario for reporting units, parent units have a blank cell in the Dimensions column, and child units have links to specific or wildcard dimension combinations.
Organize reporting units
You can rearrange the organizational structure of a reporting tree definition by moving reporting units in the graphical view. You can also promote reporting units to a higher level in the reporting tree or demote them to a lower level.
- In Report Designer, open the reporting tree definition to modify.
- In the graphical view of the reporting tree definition, select a reporting unit.
- Drag the unit to a new position. Alternatively, right-click the unit, and then select Promote Reporting Unit or Demote Reporting Unit.
- Click File > Save to save your changes.
Add text about a reporting unit
An additional text entry is a static text string of up to 255 characters that adds information to the reporting tree definition. For example, the additional text can be a short company description. You can create up to ten additional text entries for each reporting unit in a reporting tree definition. The additional text appears on the report for the reporting unit that the text is assigned to. You can add text entries from the Description column of the row definition, and from the Headers and Footers tab in the report definition.
- In Report Designer, open the reporting tree definition to modify.
- Double-click the Additional Text cell for the reporting unit row.
- In the Additional Text dialog box, in the first empty row, enter the text. The first row that contains text is referenced as UnitText1, regardless of its position in the Additional Text dialog box.
- To add more text entries for this reporting unit, enter the text in an empty row.
- Click OK.
Remove additional text from a reporting unit
- In Report Designer, open the reporting tree definition to modify.
- Double-click the Additional Text cell for the reporting unit row.
- In the Additional Text dialog box, select the entry to remove, and then click Clear. Alternatively, right-click the entry, and then select Cut.
- Click OK.
Restrict access to a reporting unit
You can prevent certain users and groups from accessing a reporting unit. You can also define restrictions so that they apply to child reporting units of the reporting unit.
- In Report Designer, open the reporting tree definition to modify.
- Double-click the Unit Security cell for the reporting unit row to restrict access to.
- In the Unit Security dialog box, click Users and Groups.
- Select the users or groups that should have access to the reporting unit, and then click OK.
- To restrict access to child reporting units, select the Add security to children reporting units check box.
- Click OK.
Remove access to a reporting unit
- In Report Designer, open the reporting tree definition to modify.
- Double-click the Unit Security cell for the reporting unit row to remove access to.
- In the Unit Security dialog box, select a name, and then click Remove.
- Click OK.
Examples
Reporting unit structure – Example 1
Here is the structure of the reporting units in the following reporting tree:
- The Contoso Japan reporting unit is a parent unit of the Contoso Japan Sales and Contoso Japan Consulting child units.
- The Contoso Japan Sales division unit is both a child unit of the Contoso Japan unit, and a parent unit of the Home Sales and Auto Sales units.
- The lowest-level detail reporting units (Home Sales, Auto Sales, Client Services, and Operations) represent departments in the financial data. These reporting units are in the shaded area of the diagram.
- The higher-level summary units summarize information from the detail units.
Reporting unit structure – Example 2
In the following diagram, the reporting tree has an organizational structure that is divided by business function.
Example of the Insert Reporting Units from Dimensions dialog box
The following illustration shows an example of the Insert Reporting Units from Dimensions dialog box. For this example, the results will return the combination of business units, cost centers, and departments.
The resulting reporting tree definition is sorted by business unit, then by cost center, and then by department. The dimension for the fifth reporting unit is Business Unit = [001], Cost Center =[], Department = [022], and identifies a reporting unit for accounts that are specific to business unit 001 and department 022.
Examples of data roll-up
The following examples show possible information that is used in a reporting tree definition for data that is rolled up.
Example 1
Example 2
Additional resources
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for