Profile Versions  

Definition

When you modify and save a profile, the old status in the database is not overwritten. Instead, a separate version with the changed values is created. The R/3 System allocates an individual number for each profile version. For example, when you create a new profile, it has the version number 1. Additional versions are numbered 2, 3, 4,... etc.

The associated profile file at operating system level is only overwritten if explicitly specified within the profile maintenance transaction (the system prompts you accordingly when you save a profile). You can only activate the most recent version of a profile. However, old versions can also be activated again by copying.

For each individual profile parameter you have changed, an appropriate comment is stored in that same profile.

For example, user BATCHMAN changes the number of update work processes in an instance profile from 0 to 1. The following entry is made:

# old value: 0 changed by: BATCHMAN, 9.8.1995, 16:45:38

rdisp/wp_no_vb = 1

Using the versions of the profile and the associated modification comments, you should be able to trace the history of all changes.

 

See also:

When is a Profile Change Active?

Checking Active Parameters

When Must Profiles be Maintained?

Start Profile: Changing Instance Services

Default Profile: Changing Global Instance Parameters