Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A consolidated report that has different year-end dates is incorrect in Microsoft Management Reporter


Symptoms

When you consolidate companies that have different year-end dates, the report may not produce the expected results.

↑ Back to the top


Cause

Period end dates may not match causing unexpected mismatches between consolidating company periods.

↑ Back to the top


Resolution

There are two options to make the report work correctly.  These options are found in the report definition, on the Settings tab.  Click Other and then click the Additional Options tab. 

NoteThe default company is considered the company that is specified in the report definition.  If @ANY is used, then the default company is the company that you are currently logged into.

Option 1

“Rollup by using default company period number”

The period that is specified in the column definition is used for all companies that are defined in the tree.

For example, 6/30/2012 is Period 12 for the default company and is Period 6 for the second company.  If the report was run for period 12, the default company would pull data from June, whereas the second company would pull data from December.  

In order to retrieve data for June for both companies, you would have to set one column to period 12 and a second column to period 6.  Each column would then have to be restricted to its respective company in the tree, by using the Reporting Unit.

This option is the default setting.

Option 2

“Rollup by using default company period end date”

The period that is specified in the column definition is used to find the date from default company.

If the default company’s Period 12 has end date of 6/30/2012 then this date will be used against all companies regardless of period numbers.  Using this example, the second company would pull data from period 6. 

↑ Back to the top


More Information

Issue with YTD columns

YTD columns may not work as expected with different year end date companies as YTD is precalculated on the source company calendar not the default company.


Workaround

Create Periodic columns for each period and sum in a CALC column. This may have to be done by using a Rollup by end date and columns to specify BASE-1, BASE-2, and so on.

Beginning balances would have to be accounted for, since this method would not include beginning balances.


Using Budget data

A Date Range Budget must be created for each of the non-default company calendars. Data in the Date Range Budget has to correspond to the default company dates and may cross between different source company regular budgets.

Default company calendar must be consistent when you run the report.


↑ Back to the top


Keywords: kbmbsmigrate, kbmbspartner, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2703112
Revision : 1
Created on : 1/7/2017
Published on : 4/17/2012
Exists online : False
Views : 81