Transfer of Operative Data and Simulation Data
Use
You can transfer simulation versions and operative data as follows:
Source |
Target |
Operative project |
Simulation Version |
Simulation Version |
Simulation Version |
|
Operative project |
Features
In the standard system the following objects are transferred automatically:
Actual and commitment values as well as actual dates are not transferred from a simulation version to an operative project.
Settlement rules are not transferred and you cannot maintain them in the simulation version.
In Customizing for the Project System you can stipulate whether PS texts, documents and long texts for the project are also transferred.
You can execute a test run before you actually transfer the data. You can then goto the project planning board or project information system, to check the effects of the data transfer.
If certain data cannot be transferred, the system produces a
log.If you want to select and evaluate projects, whose simulations influence each other, create the simulation versions for these projects with the same key.
Project P1 should be realized in simulation version 0000005. You want to compare a simulation version from project P2 and P3 with project P1. Create a simulation version with key 0000005 in both projects.
Activities
If you transfer a simulation version to an operative project, the system sets the Transferred indicator.
If there are other simulation versions for the project, the Inactive indicator is set for them, so that they cannot be processed inadvertlenty. You can however display these simulation versions. You can also reset the Inactive indicator in the
Administrative DataIn general there is no point in changing operative data while you are simulating different variants of a project. If you were then to transfer a simulation version back to the operative project, the changes you have just made in the operative project would be overwritten.