Strategy for profit and loss like reports

Question

Hi.  We run 2012 enterprise and I'm reading the general prep steps for a new report at technet.microsoft.com/en-us/library/dd220520.aspx .
My report is similar to a profit and loss in that any line might need to be presented in a format (eg % vs $ etc) different from the line before it.  Basically its not a traditional repeating pattern of info from line to line like you might see in something
like an inventory report.
There is a time dimension across the top with the budget value in col 1 and then a break down of actuals (eg by week) to the right of that column.
The report placement of most rows can be predicted (ie fixed) because they are summaries only.  But a few are variable when an unknown number of product line details are shown. 
The business sections (eg sales, performance etc) need to run together and give the user a scrolling feel (minimally in the browser) rather than a page break after each section.
Because there is at least one matrix required due to the variable portion I mentioned, I'm already nervous about that thing rs does sometimes when two controls (one on top of the other) dont take on a seamless look.
I'm also wondering if each row (eg sales, costs, etc etc) should be sourced by a separate dataset or if I should come up with a generic query with union alls supporting all data formats with an indicator on the row specifying what line (hdg) name of
the report it should be shown on along with perhaps some sort order value?  By "all data formats" I mean a numeric data type that could hold anything (%s, dollars, counts etc) picked up by the query and worry about the specific reformatting
of that data type in the report itself on a line by line basis.
Any advice would be appreciated.  I'm a big fan of keeping my future maint costs low on something like this.

Answer 1

Thx Alisa.  The most important part of my strategy question has to do with breaking things up into multiple controls (tablix etc) and datasets or delivering all via one query into one control.
When a report follows a very nice pattern I've never had a doubt.  For instance, an inventory report that repeatedly lists item, qty on hand, plant location etc etc would fit the "pattern"category.
But when a report looks like this i start asking questions...
                    Budget                  Jan Actual             Feb
Actual              Mar Actual            Apr Actual
Sales             $x,xxx,xxx.xx        $x,xxx,xxx.xx        $x,xxx,xxx.xx        $x,xxx,xxx.xx       
$x,xxx,xxx.xx  
Cost               $x,xxx,xxx.xx        $x,xxx,xxx.xx        $x,xxx,xxx.xx       
$x,xxx,xxx.xx        $x,xxx,xxx.xx 
% to Sales                 x.xx%                   x.xx%                  
x.xx%                  x.xx%                   x.xx%
Quality Issues          xxxxxxx                  xxxxxxx              
xxxxxxx               xxxxxxx                 xxxxxxx
...because as you can see different numeric data types are involved.   This example is overly simplified.  Would you source this from one dataset?  And deal with the varying data type formatting in the rs rendering rules, or perhaps
use 3 or 4 datasets with 3 or 4 controls?   My report actually has close to 50 rows and the numeric data types vary.  The only pattern I have is that a row hdg would come in and all 5 columns would be used from row to row.  I can easily
include a sort order in one dataset.   No particular row or group of rows is reusable in other reports.