Sub-projects rolling up incorrect in Master plan

[wdritt]

Hello, I have a master project with 13 or so sub projects inserted in it. I
have this setup in Proj Pro to show "Inserted projects are calculated like
summary tasks"

I also have the master project itself displaying the project summary task.

My problem is that the master project's summary task appears to be combining
the sub project info in regards to the Duration. This in turn is pushing out
my Finish date.

So in this case my projects range in the 400-700 day range, all starting in
January of 2008. The master project summary row shows a duration of 9000
days and a finish date of 2042. When it should be showing the duration as
744 and the end date in 2010.

I assume I am missing a setting somewhere. I have recreated this and
reviewed all of my settings, but still get this problem.

 

[Gary L. Chefetz]

Wdritt:

Do the projects contained within the Master project contain links to each
other or additional tasks within the master project? I suspect so, and that
the date calculations you're seeing is the result of impossible scheduling
scenarios between the projects such as might be caused by a circular
relationship between one or more of the constituent projects. The result is
that it pushes the schedule out to the ridiculous date..

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[wdritt]

Gary, you are correct. I came on board after these plans were originally
created and am working on some of those issues. But it helps to know that
those circular relationships are what is causing the sumamry of teh master to
go out of wack.

Thanks!
--
Thanks,
WDR

Wdritt:

Do the projects contained within the Master project contain links to each
other or additional tasks within the master project? I suspect so, and that
the date calculations you're seeing is the result of impossible scheduling
scenarios between the projects such as might be caused by a circular
relationship between one or more of the constituent projects. The result is
that it pushes the schedule out to the ridiculous date..

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Gary L. Chefetz]

Wdritt:

I can't be certain without looking, but it fits the old addage "if it quacks
like a duck and waddles like a duck..."


----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

Gary, you are correct. I came on board after these plans were originally
created and am working on some of those issues. But it helps to know that
those circular relationships are what is causing the sumamry of teh master
to
go out of wack.

Thanks!

 

[wdritt]

Gary, I have seen posts refer to teh following site for a good macro to fix
circular tasks. There is one there for tracing and filtering but in the
macro notes it states:
"Note: Does not work with Inserted/Consolidated projects as it does not
handle external tasks"

Are you aware of a macro or a best practice in going through a master
project with a lot of external links and trying to resolve these issues?

Thanks

 

[Gary L. Chefetz]

I suppose someone could write one, but I'm not aware of anyone offering such
an beast. Frankly, I think the solution to this problem is to insist on a
better schedule model. That is the way I solve these types of problems, but
I'm a bit of a fanatic when it comes schedule models. IMO, any schedule
model that requires as much effort as you seem to need to sort out the flow,
is essentially flawed and should be revisited.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

Gary, I have seen posts refer to teh following site for a good macro to
fix
circular tasks. There is one there for tracing and filtering but in the
macro notes it states:
"Note: Does not work with Inserted/Consolidated projects as it does not
handle external tasks"

Are you aware of a macro or a best practice in going through a master
project with a lot of external links and trying to resolve these issues?

Thanks