cProjects 3.1: Version headers - what is the purpose and usage

[Former Member]

Hi Guys,

In order to create a project version in cProjects 3.1, it needs to be based on a "version header". A version header has a validity date and can only be used once per project, but can be used in multiple projects.

I am just wondering what exactly is the purpose and usage of the version header?

From what I understand, a version header is something like a type of version (in overly simplified terms). For example, we could create a version header called "End Phase 2 Snapshot" and this version header can be used by multiple projects, but only once per project. Another example would be creating a version header called "End Feb 2007 Project Status" to create snapshots at the end of each month. Is my understanding of version headers correct and are there any other types scenarios where these can be used.

Cheers,

Lashan

[former_member201206]

Hi Lashan,

I think, you understand it correctly.

The version header is more or less a customizing setting, which is normally done person at a high level administration. It control, which name of version can be used in which time frame. Otherwise the users could use all thinkable version name, which would cause chaos in the version management.

Kind regaerds,

Zhenbo

[Former Member]

Hi Zhenbo,

Thanks very much for the answer. From what I gather from your response, the option to create version headers is not something you would give to users?

You are right in saying that users will create a number of versions. However, I would also prefer not to restrict the project managers (i.e. users with admin authorization to the project) in deciding how many versions to create. What would be the recomended way of managing version headers in a situation where;

1. There is no clear requirement from the business on how many versions to create for each project, and what type of version are required

2. We want to give the project manager the flexibility of deciding how many versions to create.

One solution I could think of is creating generic version headers such as Version 1, Version 2.... Version n. Any other ideas?

I also have a sub-question regarding global and local versions - apologies for using the same thread

This is what the help says;

When you use versions, you differentiate between global and local versions:

Global versions can only be managed by users that have the appropriate authorization for the CPRO_VSHDR authorization object. This authorization object enables you to specify the exact usage of versions throughout your enterprise.

--- I presume "managed" refers to editing of the actual version header and NOT the creation of project versions based on the global version header

Local versions can be created by any project administrator and can be used for your own evaluation purposes.

--- what exactly is meant by "own evaluation purposes"? Does this mean that other project managers (i.e. users with admin authorization to the project) cannot use local versions?

In other words, am I correct in saying that, if the users are not managing the version headers and are only creating versions based on a defined version header, it is transparent to the user whether or not the version header is global or local?

Any SAP documentation available that has more info on project versioning (other than the standard SAP help)?

Thanks...

Lashan

[Former Member]

Hi Lashan,

Did you get any solution for your questions?

Are Versions (not version headers) bearing some date stamp? When they have been taken? That would be quite important.

Thank you,

LM