Project and Portfolio Management Practitioners Forum
cancel

Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

Highlighted
Alexei Malinovs
Respected Contributor.

Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

Dear Community,

We are testing an upgrade at the moment from 6.0 to 7.5.

I noticed one weird thing.
In 6.0 we have Request with Project plan attached to it as areference.

In 7.5 we expect this to become one Project with Work plan.

However, after upgrade in 7.5 I found out TWO projects with the same name.

Project 1 created out of Request and has no Workplan

Project 2 created out of Project plan and has Workplan attached to it.


Question:
Why is this happening?

Cheers,
Alexei
4 REPLIES
Alexei Malinovs
Respected Contributor.

Re: Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

Actually, I noticed that this is not an exception but a rule.

Every Request with attached Project Plan in 6.0 was upgraded to 2 Projects in 7.5.

First project is created out of Request and has a Requrest Workflow

Second project is created out of Project plan and has some default Workflow

Question 1: Is it normal?
Question 2: How to fix the situation so that in 7.5 there is only one Project with Workflow from Request? Like it was in 6.0?
Marlene Mazzeo
Super Contributor.

Re: Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

We had this same issue when we completed our first attempt at upgrading from 6.0 to 7.1. Our problem was that most users did not list their Project Plan on their Project, so there was no link between the two. Because of this, any project plan/work plan without this link ended up with a Project Type of Enterprise. There is a field on the request type where you are able to select the associated work plan, but I don't remember what that field is called, since we completed this in early 2008. I think the KCRT_FG_PFM_PROJECT table will show you which projects do not have an associated project plan/ work plan, based on the PRJ_PROJECT_PLAN_ID.
Sascha Mohr
Acclaimed Contributor.

Re: Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

Marlene is right, a reference between project and request is not enough.
The request for the project (more precisely its request header type) needs to have the appropriate field groups and these contain the field in question that creates this special link. Me too, I don't remember the field's name. Look at the token names of the fields in the best practice request type for projects, especially those starting with PFM.
You will need to fix this in release 6; doing it after the upgrade is much more difficult because of the changed data model.
Alexei Malinovs
Respected Contributor.

Re: Upgrade 6.0-->7.5: Request with Project plan become 2 Projects

Thank you for giving me a hope to fix the issue. I have sent a request to HP support. Let's see what they say how to fix the problem.