Problem Description: This is related to Publishing Project files to MS Project Server for Web access. When I publish the Master Project to the MS Project Server with Subprojects embedded in it, only the main tasks for the Subprojects are showing in the published Project plan (in Projects menu) of Web Access. All the tasks other than the main tasks are not listing in the project plan. Please advise me if I am not following the correct steps. I am using a Resource pool to assign resources to different subprojects. In the Project menu if I am selecting any view other than Tasks related views, I am getting the following message. "Either the project manager has not published the project plan or there is no information in the project plan to display.". If the project plan (only main tasks of the subprojects) are viewable, then it should be published. Am I missing anything while publishing? Please advise me if I am not following the currect procedures. Saving Changes...
Sumesh,
Just stumbled across your post, and from what I understand with Project Server 2003...from the help with project 2003 regarding subprojects and master projects...
Note: If you are using Microsoft Office Project Professional 2003, do not save master projects to Microsoft Office Project Server 2003. Erroneous reporting data could result. Project Professional 2003 and Project Server 2003 have built-in reporting and analysis features that replace the need to create master projects and subprojects.
Saving Changes...
Anonymous
From what I know of Project Server, you should not be publishing the Master Project to the server. You can always save it to the server and do your analysis in Project Professional.
If you publish the Master Project (consisting of sub-projects) to the server it will result in duplicate tasks and assignments and alerts and could result in erroneous reporting data. Saving Changes...
I have worked with MS Enterprise Project Server. You are correct, if you use a Master Project only the summary of the sub projects shows in the Web Access.
When you use Enterprise, the system is designed to take all resource assignments into account. This eliminates the necessity to build a master project for looking at resource allocation.
Although you can view individual projects with Web Access, I find the Web Access most useful when looking at numerical information regarding multiple projects, resources, costs, etc.
When you use Portfolio Modeler or Portfolio Analyzer, you can select the projects that you want to include and the resources you want to include in the model. Portfolio Analyzer makes heavy use of summary data in OLAP cubes and pivot tables.
The biggest adjustment is in thinking of resources in a shared environment and can be they are allocated to a number of projects and tasks.
You may want to use Master Projects in MS Project Pro to create gantt timelines with multiple projects and filter resources. In that case make sure you link to the original projects when you make the master so as not to duplicate your resources.
Hope that helps. The additions in Enterprise are what was missing from the standalone environment if you are managing multiple corporate projects. The MS site has some good demos if you want to see more. Saving Changes...
