Chapter 5a

Create
New Projects

May 2005

SAP AG 2005 ZA5510 Chapter 5a Page 1

 Chapter Overview

Create a Project

Basic Project Data

Additional Project Data

Including Additional Phases
from Blueprints
(Working with Includes)

Master Projects

SAP AG 2005, ZA5510 05a- 2

SAP AG 2005 ZA5510 Chapter 5a Page 2

 Create a Project

1
2

SAP AG 2005, ZA5510 05a- 3

You are in the Projects (1) initial access view.

In area Project on tab Create (2) you
A. Enter the unique project number. The system allows characters, spaces, numbers. The project number is
the project ID which it is displayed as well in the cProjects system as in the BW reporting and in cARC.
Note: The system checks whether the project number you entered already exists when you save the
project on the next screen. If a project with the same number exists an error message is displayed and
your project is not saved. You can then change the project number and save after that.
B. Select the adequate project type.
Note: Project types starting with ACC... will lead to the creation of a CATS integrated project; this involves
that you will not confirm efforts manually within cProjects but via CATS. (See Chapter on CATS
Integration)
C. Select a template in the Copy Template drop down box. A template generates the basic project structure
with checklists, documents and links to SAP document templates, the cProjects Blueprint. Otherwise
you create an entirely plain and empty project.
D. Leave the check boxes Resolve Checklist References and Use project roles checked, which they are by
default. This completes the generation of the basic project structure.
Click the button Continue (3). This will open your new project.
Note: The system creates the new project only if you save the project on the following screen.

SAP AG 2005 ZA5510 Chapter 5a Page 3

 Basic Project Data
1

8 2

3
4

7
SAP AG 2005, ZA5510 05a- 4

This screen will be shown after you have clicked the Continue button, after entering a name and choosing a
template for your new project. (See the previous slide in this chapter.) You are in the Projects (1) initial
access view on the Structure tab page. In the Detail (2) view you find the Basic Data tab, where you will
maintain your basic projects data.
The following steps should be performed right after creation of each project:
A. Enter the project Name (3). This text will be displayed as the header in the project structure to the left. To
avoid confusion it is recommended to chose the same text for project Number (4) and project Name.
B. The Responsible Role (5) is Project Lead by default. Select a different one if required.
Note: You should assign a person to this role immediately, see chapter 13, Roles & Resources.
C. Enter dates in the Set Start Date or Set End Date field (6) if you want to define a fixed project start or end
date respectively. If you do not enter any dates, the system uses the current date as project start date by
default.
D. Select the Calendar (7) you want to use for this project as default. You can set different calendars on task
level, see chapter 7, Create Tasks.
E. It is helpful to immediately add the project to your favorites on the cProjects start screen by clicking the
Favorites (8) button.
F. Save the project with the Save button (9). The project is not created in the system until you save it.

SAP AG 2005 ZA5510 Chapter 5a Page 4

 Additional Project Data

1 3 4

SAP AG 2005, ZA5510 05a- 5

A. On the Additional Data tab page (1) you should define the Organizational Unit (2). This is a precondition for
releasing the project or parts of it. See chapter 7, Create Tasks for details on the other fields on this tab
page.
B. You should also create a link to a WBS elements of the Release Master Plan. This is done on the tab page
Object Links (3), see chapter 10, Object Links.
Note: Make sure that in cARC the relevant Workpackages contain the newly created project name as well.
This assignment of Workpackages in cARC is typically coordinated by a central group like e.g. the BSG
Operations teams.
C. Finally you should define the default authorizations for the project, e.g. whether it is visible for the entire SAP,
which it is by default after creation. This is done on tab page Authorization (4) and described in chapter 11,
Authorizations & User Groups.
Note: Please do not remove SAP Group as an organizational unit in the authorizations. SAP expects that
all cProjects are visible to all SAP employees (exception may be special research projects).
D. After defining the values for Org. Unit and WBS Link you can release your project (on the Basic Data Tab).
Releasing a project is the precondition for CATS integrated projects to become productive. The system
creates an internal order referring to your project.
Note: After releasing a project you can still change the WBS link, but it is no longer possible to change the
assignment to the organizational unit. The system inherits the organizational unit as an attribute to the
internal order in ISP. In case you must change the organizational unit please contact your area controller.

SAP AG 2005 ZA5510 Chapter 5a Page 5

 Additional Project Data

1 3 4

SAP AG 2005, ZA5510 05a- 6

A. On the Additional Data tab page (1) you need to define the leading Organizational Unit (2). This is a
precondition for releasing the project or parts of it. See chapter 7, Create Tasks for details on the other fields
on this tab page.
B. You should also create a link to a WBS element of the Release Master Plan. This is done on the tab page
Object Links (3), see chapter 10, Object Links.
Note: Make sure that in cARC the relevant Workpackages contain the newly created project name as well.
This assignment of cARC Workpackages to cProjects is typically coordinated by a central group like e.g. the
Operations teams.
C. Finally you should define the default authorizations for the project, e.g. whether it is visible for the entire SAP,
which it is by default after creation. This is done on tab page Authorization (4) and described in chapter 11,
Authorizations & User Groups.
Note: Please do not remove SAP Group as an organizational unit in the authorizations. SAP expects that
all cProjects are visible to all SAP employees (exception may be special research projects).
D. After defining the values for Org. Unit and WBS Link you can release your project (on the Basic Data Tab).
Releasing a project is the precondition for CATS integrated projects to become productive. The system
creates an internal order referring to your project.
Note: After releasing a project you can still change the WBS link, but it is no longer possible to change the
assignment to the organizational unit. The system inherits the organizational unit as an attribute to the
internal order. In case you must change the organizational unit please contact your area controller.

SAP AG 2005 ZA5510 Chapter 5a Page 6

 Including Additional Phases from Blueprints

1
3

SAP AG 2005, ZA5510 05a- 7

You can include Phases defined in other blueprints into your own project.
A. On the Structure tab (1) select the header of your project (2).
B. Press the Include button (3).
The search screen is displayed.
C. Press the Find (4) button.
You will get a list of the phases from blueprints which you can include into your project.
D. To select a phase click on it (5).
The phase is now included at the end of your project structure.

NOTE: To move the position of the phase change the Predecessor Phase on the Basic Data tab.
The new phase can not be included between two phases with the Status Released. At least the succeeding
phase must have the status Created.

SAP AG 2005 ZA5510 Chapter 5a Page 7

 Master Projects

1 3

4
5
Bill Clinton
Clara Anderson

2 Robin Wood

Robin Wood

SAP AG 2005, ZA5510 05a- 8

Master Projects help to gain a quick overview on assigned project in real-time

 On the tab Assigned Projects (1) you can assign cProjects to a Master Project allowing a compact overview
on overall project status and work effort of the assigned projects (2).
Note: Only development effort is counted (task types DEV* without DEV_CORR).
 Master Projects are centrally created by our Operations Teams on request.
 As all projects also Master Projects need to be assigned to a RMP Object link on the tab Object Links (3).
However, Master Projects do not contain tasks neither work efforts.
Note: Efforts of a Master Project Lead should be collected in an regular cProject if required.
 The leading hierarchy for all BW reports remains ISP-PS with its WBS hierarchy.
 Press Assign Project (4) to add a new cProject in the list.
 In the top line overall sum of efforts is displayed (5).

SAP AG 2005 ZA5510 Chapter 5a Page 8

 Summary Chapter 5a

Create a Project

Basic Project Data

Additional Project Data

Including Additional Phases
from Blueprints
(Working with Includes)

Master Projects

SAP AG 2005, ZA5510 05a- 9

SAP AG 2005 ZA5510 Chapter 5a Page 9