When a report row is restricted to a specific reporting unit, that row displays the linked data for the named reporting unit, only, and ignores the data for other reporting units in the reporting tree. For example, you can create a row that provides details for the total operating expenses for a specific department.

Your report may contain duplicate data when the report contains both a reporting tree and a row definition that has more than just the natural account. For example, suppose that you have a reporting tree that lists the six departments in your organisation and also have a row definition that lists a specific account department combination in the row. When you generate the report, the specific account and department combination listed in the row is printed on every level of the reporting tree, even though that department may not match what is in the tree. This is because the row overrides what is normally filtered out by the report definition.

Restricting a row to a specific reporting unit is one way to avoid duplication of data.

Note
When you restrict a row that includes dimensions to a child reporting unit, the row amount is included without duplication for that unit and for its parent units.