project version vs controlling version

[Former Member]

Hi Expert,

can anybody tell me when should we use controlling verson and project version.

wat are the adv and dis advantages.

In which table the project verson data are stored?

Thanx in advance.

ashis

[Former Member · Accepted solution]

Hi

Project Version

Project versions document the status of a project at a specific point in time or in a specific action.

Example: While creating a project you have created with 4 Network orders and saved as project version. Later you have deleted one network order for some reason, so the current project will have only 3 network order. At a later time, the project versions are proof of the project status in the past and serve as a comparison with the operative project.

Project Version stored in VSKOPF table.

Thanks

S.Murali

[Former Member]

In addittion to above CO versions are used to copy planned costs from one version to other. You can use tcode like CJ9FS to copy entire cost planning from one version to other. You can also make configuration to decide on whcih version you want to post the actuals.

Project version on other hand are static version or snap shot. You can configure version profile to trigger automatic creation of project version based on various system and user status.

Hope this helps.

Sarang

[Former Member]

hi...

i just need the tables for project verson...from where i can pick cost.rev and budget.....project wise and using version key.

Thanx in adv.

ashis

[Former Member]

Hi

Project Version stored in VSKOPF table.

Thanks

S.Murali

[Former Member]

Table VSRPSCO_CN for Version. May be helpful.

Sudhir

[Former Member]

Hi,

CO Versions:

You can use CO versions in order to save several different cost and revenue plans for one object,

and to evaluate those plans separately or compare them with each other.

CO versions can also be used for cost forecasts, progress analysis.

EG.: In an early planning phase of your project, you can select a rough form of cost planning and save in CO version 1. Later during detailed planning you can save more detailed version in CO version 0.

Project Versions:

Project versions are a "snapshot" of project data. You can create project versions at specific moments and therefore document the progress of your project over time.

project versions are prerequisite for MTA (milestone trend analysis).

You can carry out a time-dependent creation of project version or status-dependent creation of project version. NOTE: status-dependent project version don't necessarily have to reflect the state of a project at a specific point in time.

EG: if you define that the project version with version number "released" must be used when an object is released, the system will a copy of an object to the project version every time object is released.

Regards.