Versions

Configuration Document
Sudarshan Reddy M

Sudarshan Reddy M

Versions 1 Simulation Purpose

When you are planning complex projects, for instance in engineering-to-order, it is often necessary to simulate and save changes to a project, without affecting the operative project. To do so, you use simulation versions that can be changed, costed and scheduled.

Features
You can create a new simulation versions for a project by either transferring data from an existing operative project or completely independently, for instance in the quotation phase of a project. You can only simulate one sub-tree in a project

1.1 Stipulate Version Keys for the Simulation

IMG Project System Simulation Stipulate Version Keys for the Simulation In this step you define the numbers that are valid for project versions for simulation. These project versions have the category 3, simulation. You can use special characters to define a name range.

You can use * as a wildcard. With one or more + you stipulate that any character is allowed at that position.

Numbers for simulation versions are not allowed to be longer than 12 characters.

Click on New Entries

Sudarshan Reddy M

Versions 3

Key in the Version Key and its description. Click on Save

1.2 Stipulate Simulation Profiles

IMG Project System Simulation Stipulate Simulation Profiles In this step you define the objects that you want to transfer from a simulation to an operative project. You can select the following objects:

PS texts Documents Long texts

Standard settings In the standard system the following objects are transferred automatically:

Structures Dates Costs Material components Milestones Billing plans

Activities 1. Select the objects to be transferred.

Click on New Entries

Sudarshan Reddy M

Versions 4

It is here; we key in the Simulation Profile and its description and also check the objects which we want to be transfer from a simulation to operative project. Click on Save .

Constraints
The following functions are not available for simulations: Manual planning of costs, revenues and payments in WBS elements If you transfer an operative project to a simulation version, the planned values are transferred to the WBS elements. However they cannot be changed directly in the simulation version. Leveling of Capacities Integration with SD (quotation processing/assembly processing) Integration with PP/MM Material requirements planning Delivery information Status Management

There are no system statuses in simulation versions. You can, however, set deletion flags.

Sudarshan Reddy M

Versions 2 Project Versions Purpose

A project version shows the state of the project at a certain point in time or at a certain status. Project versions: Are the basis for statistical evaluations, for example, in earned value analysis Can be used in Milestone Trend Analysis [Ext.] Document (as a history) the state of the project in the past Can be used for comparison purposes

You can create as many project versions in networks, work breakdown structures, and in the information system as you like. There is a difference between project and plan versions: Project versions are a snapshot of a project at a certain point in time. Plan versions are created in accounting and store the various costs plans for a project, such as best and worst case scenarios.

When Are Project Versions Created?

Project versions are: Time-dependent Status-dependent
Time-Dependent

At a particular point in time, you create a project version manually. You can do this in the WBS, network, or information system.
Status-Dependent

The system automatically creates a project version when there is a system and/or user status change in the selected objects. You define the user/system statuses which trigger creation of project versions in Project System customizing.

2.2 Create Profile for Project Version

IMG Project System Project Version Create Profile for Project Version You require profiles for project versions if you are working with status-dependent project versions:
Sudarshan Reddy M

Versions
You stipulate the following in the profiles:

The objects which appear in the project version, such as WBS elements, activities, PRT, or costs User and/or system statuses which trigger the storage of a project version The version key for the project version

You can define as many user and/or system statuses in a profile as you want. Example In the profile, you have stipulated that a project version is created when the Released status is set. The system then creates a project version each time an object which is to appear in the project version is released.

When you release a network, a project version is created showing all the objects defined in the profile. When you release a version-relevant activity in the network, this activity is entered in the project version.

Standard settings SAP does not delivery any profiles for project version in the standard system. Activities 1. Enter the key and name for a profile. 2. Select the objects which are to appear in the project version. 3. Maintain system and/or user statuses for the profile. 4. Save your data. 5. Enter the project version profile in the network profile and project profile.

Click on New Entries In the version profile, you specify the objects to be included in a project version, (for example, WBS elements, activities, production resources/tools, or costs) and when the project version should be created.
Sudarshan Reddy M

Versions 7

Click on Save

. and click on New

Select the Profile which we created now and double click on Entries

Key in the data as shown above and Click on Save

.
Sudarshan Reddy M

Versions
In the version profile, you can enter as many user and/or system statuses as you want for creating a project version. For status-dependent project versions, you specify the key to be used every time this status triggers a project version. The key for status-dependent project versions will be the same for all versions of projects with the same status, regardless of the project name.

Sudarshan Reddy M