Skip to Content
author's profile photo Former Member
Former Member

Relation proposal to program to project

Dear experts,

My client has a requirement that a project proposal that is approved, will need to be become a project.

Does PPM 5.0 provide backward traceability in the sense that you can always know at some point from which proposal a project has originated? Can you please explain how this works (i.e. do i need to create a new project after the proposal has been agreed?) ?

Related to this I would like to know whether you can link projects to programmes in the portfolio management part of the software so that dependencies become visible. Can somebody explain how this works in PPM 5.0? Is there a change log available so that you can look back in history which projects used to be related to programes? Can you move one project related to programme 1 to say programme 2 without losing project 1's attributes?

Your view on this will be much appreciated.

Best regards,


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on May 01, 2012 at 11:31 AM

    Hi Wilco,

    The particular portfolio item can be proposal in initial stages and then subsequenty moved to the project. The proposal is checkbox field available for portfolio item.

    The proposal checkbox can be governed at item type or decision point level of portfolio item.

    The programme is represented by intiative in SAP PPM. An initiative can have multiple items assigned to it. And if required, the item can be moved from one initiative to another.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 01, 2012 at 02:49 PM


    I believe you can use Portfolio item status for projects which are getting converted from proposal to active projects. To support statuses you can bring decision point name as Proposal which will get approved once the Proposal gets confirmed. This will give you backward traceability of projects stages from Proposal to active project.

    As mentioned above you can define initiative for Program management. You can define Program owner and various projects under one Program.

    To define dependency within different Projects there dependency editor wherein you can define interdependency within different projects in one program or across Programs. This dependency is just for information and does not drive actually the scheduling dependencies.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for your quick responses gents.

      @ Both: Does PPM remind old dependencies? Is there some change log functionality behind this dependency functionality?

      @ Pramod, just to be sure. When moving 1 item to another initiative, I will need to define / key in the new dependencies manually or is there some intelligence behing these fields that reveal the impact of moving one to another?



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.