If workplan versioning is enabled for the projects in a program hierarchy, Oracle Projects creates links between the working workplan version for the program and the latest published workplan version for each of the linked projects. If a linked project does not have a published workplan version, then Oracle Projects links the working version of a program to the current working version of the project.
Note: Information does not roll up from a working workplan version of a project to the working workplan version of the program. For more information, see: Rolling Up Program Workplan Information.
If you are not using workplan versioning features, a single workplan version of the program is linked to the workplans of the projects in the program hierarchy. After you create program links, select Process Updates to roll up all plan and actual information from the linked projects to the program. All future updates roll up to the program automatically.
You can publish workplan versions for a program and its linked projects independently. However, if you publish a program workplan version before you publish any workplan version for a linked project, then Oracle Projects does not create a link between the published workplan version for the program and the working workplan version for the linked project. However, the link between the working workplan version for the program and its linked project is maintained.
When you publish a workplan version for a linked project, Oracle Projects automatically runs the PRC: Process Structure Updates concurrent program. This concurrent program rolls up information from the linked projects to the current working version of the program.
Note: When you run PRC: Process Structure Updates for a single project in the hierarchy, Oracle Projects automatically runs the concurrent program for all linked projects and performs a rollup of information for the entire hierarchy.
If you publish a workplan version for a linked project after a program workplan is published, Oracle Projects rolls up the updates to the current working version of the program. To roll up the latest progress information to the program, you must republish the program.
Note: Oracle Projects maintains links from the previous published workplan version for the program to the corresponding workplan versions for the linked projects.
After you publish a workplan version for a program or a project in the program hierarchy, you can designate it as a baseline version. You can separately designate workplan versions for a program or any of its linked projects as baseline versions. Designating a published workplan version for a program as the baseline version does not affect the workplan versions for the projects in the program hierarchy.
Oracle Projects allows you to link the baseline workplan version for a program to a non-baseline workplan version for a linked project. However, in such a scenario, the rolled-up information at the program level may not reconcile with the information from the linked project. The discrepancy occurs because the information for the linked project is from the baseline version of the workplan, whereas the information at the program level is from a non-baseline workplan version of the linked project.