Sap Profile Management

PROFILE MANAGEMENT

INSTANCE: - It provides a set of Services, Work process, buffer areas, to an Application. Instance is controlled by various parameters

1. Startup Parameter

2. Instance Parameter

3. Default Parameter

These parameters resides in \usr\sap\<sid>\sys\profile Directory

1. Default Profile: - (Default.pfl) it provides default parameters for all Instances in the R/3 Systems

Some of the parameters are

1. Login/system_client=

Client number to be displayed by default for all the users

2. zcsa/system_languge

To specify the language during log on

3. Login/*

All the login parameters to control password, user id etc.

2. Startup Profile: - It’s used to start the instance parameters should not be changed

Changes are allowed only if there is a change in hostname or SID

Naming Convention

START_DVEBMGS<nr>_<Hostname> for Central Instance

START_D<nr>_<Hostname> for Dialog Instance

Sapcpe.exe:- used to communicate with D/B when a Dialog Instance is installed and its initialized Central instance and D/b are installed separately

3. Instance Profile: -

It consists of Instance Specific Parameters like Work process, Buffers. Go to table “TPFYPROPTY” to display the Instance specific parameters grouped by Dispatcher, ABAP etc. Some parameters are

            rdisp/wp_no_dia

            rdisp/wp_no_btc

            rdisp/wp_no_vb

            rdisp/wp_no_vb2

            rdisp/wp_no_spo

            rdisp/wp_n0_enq

Note: Only 1-Default Profile for all Instances and 1-Startup Profile and 1-Instance Profile for each Instance.

Ex: - If total 5 Instances then there will be only 1-Default profile and 5-Satrup Profiles and 5-Instance Profiles. Totally 11 Profiles.

If the parameter fields-change options

X-Change Permitted

E-Change Generates Errors

W-Change Generates Warnings

All the parameters with value X can be changed dynamically. With out Restarting the Server other wise we need to Stop and Start the R/3 Instances.

RZ10 (Static Profiles): -To import the profiles from OS level to DB level. Table “TPFET” is used to store the parameter values with versions.

1. Administrative Data: - Which will give the path of each profile. Do not change this until there is change in path of profile

2. Basic Maintenance: - This is used by Technical Team where maintenance is performed without knowing the parameter names. We can toggle between the values. It’s used to maintain Work process, Buffers, Memory Management.

3. Extended Maintenance: - It’s used to change the parameters based on parameter names. It’s used by experts and ensures that necessary care is taken while modifying the parameters.

Note: - Instance may not start due to change in parameters (wrong parameters)

The changes made to the parameter get effect after restarting the system the existing sys/profile will be renamed to .bak and coped from Database to OS level

RZ11 (Dynamic profile):- Get the documentation of the parameter. Be fore making changes to the parameter (RZ10)