VersionenThroughout DEM, both modeling and run time processes take place in versions. By using versions, business models and model items can be made uniquely identifiable. Before you can start modeling, you must first define versions and version authorizations in the masterdata. Derived from version If the current modeling version B (derived version) is derived from version A (derived-from version), all components of version A can also be used in current modeling version B, even though these components still belong to version A. Consequently, you cannot change the model items from version A in version B. To change these model items, you must first copy them to version B. Therefore, model items can only be changed if they belong to your current modeling version. Beispiel In version A, the following business functions are included in the business function repository:
The version of each separate business function is also A. If your current modeling version B is derived from version A, the three business functions mentioned above are also available in version B. If you want to change the description of business function Executive Support into Support in version B only, you must first copy that business function to version B, after which you can change the description. The description of that business function remains unchanged in version A . If you want to use another description in both versions, you only have to change it in version A. Current modeling version This version you select in the repository and use to model your model items. So, before you can start modeling, you must first select a current modeling version for which you are authorized. If you want to select or change your current modeling version, use one of the following sessions in the repository: Runtime version This version you select in run time model control. The run time version provides the runtime project model and optimization phase. If you want to select or change your run time version use the following session:
| |||