Currently the Portfolio module does not easily show the links with projects/programs. For example, an organization is heavily run by programs. These programs contain one or more projects, each with different launch dates, The Program serves as the overall release date. When viewing the data, the user wants to see Projects and the associated program. Assume one project belongs to one program.
Project 1 Program A
Project 2 Program A
Project 3 Program B
Project 4 Program C
Project 5 Program C
Etc.. and then of course other common attributes. We have configured the program page (and projects) quite heavily.
Would this require adding an attribute on the project field that shows the associated program? If so, how would that be done?
The Portfolio module has a Project Hierarchy image that takes you to the Project Hierarchy where you can see parents/children, but that is a pop up so it does not show that cohesiveness.
Has anyone figured out a decent way to show the program/project relationship in a Portfolio (13.3/14.2) -- If you include both,then your portfolio double counts it. Or does anyone have any best practices when trying to view a portfolio including programs and projects?
I logged an Enhancement (idea) to improve the Portfolio module with the relational data (master/sub; programs/projects, etc)
Creating a hierarchical portlet should solve your problem, especially as you can add a Gantt view to see the overall timeline of the program and underlying projects.
The view would then be:
Below is an example on NSQL query to create a hierarchial portlet on portfolio. This has to be updated to suit your needs, but should work as a frame.
select rownum unique_row
from pfm_portfolios pp
join pfm_investments pi on pi.portfolio_id = pp.id
join inv_investments inv on inv.id = pi.investment_id
where @where:param:user_def:string:hg_row_id@ is null
and inv.odf_object_code = 'project'
where data.portfolio_id = @WHERE:PARAM:XML:INTEGER:/data/id/@value@
Thank you -- appreciate it. However, we are really trying to use the portfolio module itself to incorporate programs and the subprojects. We have portlets, but this is within the actual portfolio module-- Investments list, target planning, waterline, etc.. I was seeking any best practices or "tricks" in that area
Unfortunately I do not think there is an OOTB way of achieving what you are requesting from the portfolio module .
If you are on 14.2, there might be a possibility to create an ad-hoc report from Jaspersoft that's displaying the requested information.
Another workaround that we used for a customer was to use projects and sub-projects, and the hierarchy functionality.
For the customer a program was actually a master projects with the value "Program" on the OOTB lookup named Project Category.
Using the hierarchy we were able to visualize the aggregated financial data for the whole "Program".
Then a portfolio was created, with the same name as the "Program" where only the sub-projects of that specific "Program" were added. The “Programs” themselves do not carry any financials for the customer and could therefore be easily transferred to a Portfolio.
Using this method we were able to use the OOTB Portfolio functionalities and give the values the customer was requested.
Don't know if this solved your specific case, but it might give you some ideas .
thanks again. Yes, the OOTB does not support program/projects well, as it will list each and basically does not show relationships. The master/sub does not work for this business unit, which is why they've been using programs for years. I was just wondering if anyone else used programs heavily and how they managed that within the Portfolio module. I can see where creating a portfolio to mimic the program may work, but for this group, they are using it like releases. Therefore, the program has its own set of dates (custom fields) aside from the projects. the projects are the bigger focus within the portfolio, but they need to be able to see which program is associated to the project.
IF we created a custom field on the project to populate the associated program (essentially the parent under Hierarchy), then that could possibly be brought into the Portfolio, but I don' t know if that is possible to create such a field to read that data.
That's a nice solution.
Creating a lookup to map the project to progam, and adding the lookup attribute to the attribute registry from the portfolio investments objects, which is then placed on the portfolio investments view would give a quick and easy way to see the projects too program relations for one specific projects .
A custom portlet via a tab or link out to a portlet page will be your best bet in the current version
You might want to vote up this idea
Hierarchical data visualisation (OBS, Objects, Resources etc)