Profiles

There are three system profiles available for SAP to work on

a. Start profile
b. Instance Profile
c. Default Profile

SAP profiles are operating system files that contain instance configuration information. SAP systems
can consist of one or more instances.

The SAP profiles are stored in a special file directory. This directory can be made accessible from all
hosts, depending on current requirements.

UNIX systems:/usr/sap/<SID>/SYS/profile

Microsoft Windows NT systems: \\<SAPGLOBALHOST>\sapmnt\<SID>\sys\profile\

Start Profile: START_DVEBMGS<nr>_<hostname>

E.g. START_DVEBMGS10_IDESBASIS1

When you start an SAP instance on a host, the start profile defines which SAP services are started
(message server, dialog, gateway or enqueue process. for example). The startsap program is
responsible for starting these service processes, and it uses a start profile to begin the startup
process.

The processes that can be started include:

Application server

Message server

SNA Gateway

System log send demon

System log receive demon

Instance Profile:

Instance profiles provide an application server with additional configuration parameters to

complement the settings values from the default profile. Typically, these parameter settings adapt
the instance according to the desired resources. They also define the available instance resources
(main memory, shared memory, roll memory and so on), and how to allocate memory to the SAP
application buffers
Default Profile:

If you want to assign the same parameter value for all application servers (such as the name of the
database host, or the host on which the message server is running), enter it in the default profile. In
general, you can list any parameter you like here.

You cannot choose a name for the default profile. It is always called DEFAULT.PFL . The default
profile, like all other profiles, is located in the global profile directory of the SAP System. For
example, under UNIX it is located in the directory /usr/sap/<SID>/SYS/profile ( <SID> = SAP System
name). There is always one active

default profile.

Importing Profiles

When you first install an SAP System, upgrade to a new SAP release or add a new application server,
the system automatically generates or updates SAP instance profiles at operating system level.
Unfortunately, the installation program cannot save these profiles directly to the database. You must
therefore import the SAP instance profiles before you can then edited them.

Procedure.

1. Call the CCMS profile maintenance tool by choosing CCMS-> Configuration -> Profile Maintenance.
Alternatively, call Transaction RZ10.

2. Choose Utilities -> Import profiles -> of active servers. The system imports the default profile and
all start and instance profiles that are used by the SAP instances. The system checks the profiles and
displays a log. The names of the profiles in the database are taken from the corresponding file
names on the operating system.

If you import the instance profile /usr/sap/GPD/SYS/profile/GPD_DVEBMGS00_GPLDEV, then the

profile in the database will be called GPD_DVEBMGS00_GPLDEV.

Once you have finished importing the profiles, position the cursor on the Profile field and press F4 .
The system displays the names of the profiles that were imported.

Change Profile Parameter:

System Profiles: RZ10

1. Execute RZ10 -> select the profile from drop down menu -> click in extended maintenance ->
click on change as shown in Fig-9 below.

Fig-9

2. In next screen , click on create parameter. .

3. Provide the parameter name and value as shown in Fig-10

Here the parameter login/system_client = 300.

That means when any user will login, the default client will be ‘300’ instead of ‘000’

4. Click on Copy button.

5. Click on Back arrow button.
6. check your new parameter is added to the profile
7. If you want to add more parameters then repeat from step-2 to step-5
8. If nothing more to add then click on button again from the profile screen.
9. Click yes on the screen to save the change as shown in Fig-11

Fig-12

10. Now click on Save button from RZ10 main menu. If you see the following screen then click on
“No”.

Fig-13

11. Click “Yes” on next screen.

Fig-14

12. Now you got a confirmation that profile is activated as shown in Fig-15 below.
13. Now you got a confirmation that profile is activated as shown in Fig-15 below.

Fig-15

14. Click on Continue button

15. Now In order to make this parameter into effect, you have to restart sap. Do not stop database
and OS as shown below the warning for restart.

Fig-16

16. After SAP is restarted, you can see your new client 300 is the default client to login.

PROFILE MANAGEMENT

Documentation for profiles are available in RZ10

Profiles resides in the table - TPFYPROPTY

RZ11 is also used to change some parameters dynamically without restarting the system but
they will be reset once the system is restarted.

RZ10 changes are permanent

The field type 'T' Specifies the dynamic parameters.

RZ10
There are three types of Administration.

1. Administration data

No need to maintain using this option. It only specifies the path of the
parameters.
2. Basic Maintenance:

It is used to maintain the profile parameters without any technical names. GUI
based using mouse

3. Extended Maintenance

Used by administrator using parameter names

Specify the input by including new parameters or modify the existing one.
Copy > Save and Activate the profile.
The profile changes are updated at OS level and the existing profile is marked as .BAK and
a new profile is created in the profile directory. It will effect only after restarting the Server.

Profiles are changed on SAP recommendation or based on experience. Do not change any
of the profiles on trail and error method. System will hang and may not restart.
Interview Q &A

How would you troubleshoot a problem with a user’s profile?

A: In my last role as an SAP Basis Administrator, I encountered a situation where one of our users
was having trouble logging in to their profile. After checking the user’s credentials, I noticed that
they were using an old password. I reset the password for the user and sent them an email with
instructions on how to log back in. The user responded later that day thanking me for resolving the
issue

What is the difference between a local and a global profile?

A: A local profile is used for storing data that is only available within a single system, while a global
profile stores data that can be accessed by multiple systems. Local profiles are useful when you want
to store information about users or objects that are specific to a particular system, such as user IDs
or passwords. Global profiles are more appropriate for storing information that needs to be shared
across multiple systems, like company-wide policies or standard business rules.