Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
CNVS (Package) R/3 Application development: Version Management 
Attribute
| Message class |  |
OV | |
| Short Description |  |
PS: Versions | |
| Message Number |  |
004 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20040819 |
Message Text
Help Document
Diagnosis
A project version with version key was already created.
Dependencies
Even if you highlight a single WBS element to save it in a project version, the upward path is always saved along with the project definition. Likewise, when a network activity is saved, the network header is saved with it.
System Response
The objects you highlighted are only saved under the version key if none of these objects are contained in the version.
If the project version already contains a project with network, you can only save objects in it that are not part of the project or network.
If you are using the version key for additional projects, the system does not generate a new version, but enhances the existing version . This can lead to performance problems, among other things. If possible, do not merge various projects into one version.
Note
You cannot subsequently change the version short text and the assignment to a version group.
History
| Last changed on/by | |
19980203 | SAP |
| SAP Release Created in |
