Subprojects MOD009A4F

Access path

Information

• In this module, a project structure is created in which the current project is divided into main and subprojects.

Details

• The project structure is created and displayed graphically.
• Each element (main project, subproject) is displayed in an individual box.
  • No tasks are displayed.
• Every box contains the most important project parameters.
• Every parent element contains a so called node field where the number of child elements is specified.
  • When you click on node fields, child elements are displayed or hidden.
  • When creating new child elements, the number in the node field of the parent element is automatically refreshed.

Module Variants

Base	Contains the header data of a project and the project end dates. This variant is loaded first by default.
Minimal	Contains the header data of the project only

Create and Assign a New Subproject

Procedure

• Click on the Create subproject button in the box of the project to which you want to subordinate a project, or right-click and select the command of the same name from the context menu.
• The What do you want to do? dialog message is displayed. Click on the Create new subproject button.
• A new project is created and subordinated to the required project at the same time.
  • Both the technical and the functional project ID are created automatically. In the project box, only the functional ID is displayed.
• Click on the calculation button in the toolbar. As a result, the entire project structure is recalculated and the newly created subproject is also displayed in the Schedule module.

Details

• Each new subproject in a project structure automatically inherits the cost center (upon creation) from its immediate parent project and the stakeholder from the main project of the project structure. This is controlled via the project_parameter_heredity global parameter.

Technical background information

• After subprojects have been created and the project has been calculated, a structure task for the respective child project will be created automatically in each parent project.
  • Structure tasks are links between parent and child projects.
  • In the standard program, structure tasks are not displayed and cannot be displayed by the user. For further information, click here.

Notes

• The option to create subprojects is now available in the main project. When a subproject is opened separately, no further subproject can be created.
  • As a result, subprojects can be created by users with multi-project manager rights and project manager rights but not by users with subproject manager rights.

Assign Existing Project as a Subproject

Information

• Already existing projects can be assigned to other projects as subprojects.

Procedure

Stop

Remove Subproject From the Structure

Information

• Subprojects can be removed or removed from the project structure.
  • If a subproject is removed from the structure, it is retained as an independent project.

Procedure

• Click on the Remove subproject from the structure button in the box of the subproject to be removed from the structure or select the context menu command of the same name.
• Confirm the Do you really want to remove the subproject from the structure? message with Yes.

Notes

• If the subproject to be deleted from the structure has subprojects itself, they are removed from the structure along with the subproject to be deleted.
• If the subproject to be removed from the structure has external links to other subprojects or to the main project, a prompt is displayed, asking whether it is to be deleted or not.

Change Existing Project Structure

Information

Stop

• Projects which contain status reports may not be subordinated to a project that already contains status reports. Disregarding this rule may result in incorrect data in status reports and thus leads to incorrect evaluations.

Change the Functional ID of Subprojects

Information

• PLANTA project distinguishes between functional ID and technical ID.
  • They are both generated automatically when a project, proposal, idea, or program is created and are equal at that point.
  • The functional ID is visible in various modules and can be changed if required for certain reasons.
  • The technical ID must not be changed. It is not visible in the module and remains unchanged even if the functional ID is changed.

Change functional ID

• In the header bar area (in the Subprojects module in the box of the required subproject), click on the button with a pen on the right hand side.
• The Do you really want to change the functional ID system wide? dialog message is displayed.
• Confirm it with Yes.
• A dialog window containing an input field is opened.
  • Enter the new ID here.
    • The functional ID needs to be defined uniquely in the system. If you enter an already existing ID and click outside the field, the The required object ID is already being used message is displayed and the value is reset.
    • In the Global Settings module, you can set whether the functional ID is to be changed globally (e.g. in existing status reports) via the change_project_functional_global parameter. If you have selected value "1", the change is applied globally.

Note

• In this module, only the functional ID of the subprojects can be changed via the function described above, the functional ID of the main project is changed in the Project Core Data of the main project.

Open Project (Sub or Main Project)

Procedure

Delete Subproject

Information

• It is not possible to delete subprojects directly from within the Subprojects module.

In order to delete a subproject, you can proceed as follows:

• 1: You can either remove the required subproject from the main project structure and subsequently delete the removed project like an individual project,
• 2: or delete a subproject from the main project. To do so,
  • click on the delete button in the Project Core Data of the main project.
  • The Delete module is opened.
• Click on the Delete button next to the required subproject.
• Confirm the Do you really want to delete this planning object? dialog message with Yes.
• A subproject can only be deleted if it has no subprojects itself.
  • If a subproject contains further child projects, a dialog message is displayed when deleting this subproject: Deletion not possible: there is a (are) subordinate project(s).
  • If you want to delete a subproject and its child projects, you have to delete all of its child projects beforehand.

Authorizations for the deletion of

• Projects
  • are granted to users with multi-project manager or multi-portfolio manager or multi-project/request manager rights,
    • If the user does not possess any of these rights, no delete button will be displayed in the Project Core Data module so that the Delete module cannot be opened.
    • If the project to be deleted already has actual postings (recorded hours worked, posted costs or revenues) the deleting user requires Authorizations in addition to the rights mentioned above. If the user does not possess either of these authorizations, a message will be displayed in the Project Core Data when the delete button is clicked on, which indicates that the user is not entitled to delete actual postings and the Delete module will not be opened.

---

See also: How to Structure Projects