SAP Logon Load Balancing, Logon Groups, SMLG, CCMS

What is SAP Logon Load Balancing?

  • SAP Logon load balancing enables a SAP Basis admin to create various log on groups.
  • Logon groups are logical groups of users that you assign to one or more SAP instances.
  • A group GroupX, Once assigned to an instance I, all users who login using that group in the SAP log on pad client, will automatically login into the instance.
  • If you have two instances I1, I2 then you can create two groups GroupX and GroupY and assign them to I1 and I2 respectively. You can also divide your users according to some criterion (such as Floor1 thru 5 will use GroupX and floor 6 thru 10 will use GroupY) and ask them to use only those groups.
  • In SAP Logon Pad, you can create and delete logon group entries, remove instances from groups, and delete entire logon groups.
  • When you call transaction SMLG, the CCMS: Maintain Logon Groups screen shows a table with entries for logon groups and the associated instances. An entry in this table, which is characterized by an instance and a logon group, is known as an assignment.
  • A logon group to which multiple instances belong therefore consists of multiple assignments in this table, where an assignment contains one instance in each case.

How to Create a Logon Group or Assigning an Instance to a Logon Group

  • Logon groups are important for SAP logon load balancing.
  • Choose CCMS® Configuration logon Groups, or call transaction SMLG.
  • Choose (Create Assignment), and specify the desired name of the logon group in the Logon Group input field. Enter the name of the desired Instance that is to belong to the logon group. The logon group SPACE is reserved for SAP; therefore, do not use this name.
  • Repeat the last step until you enter all instances that are to belong to the logon group.
  • You can assign one group to one or more instances.
  • Save your changes.

How to Delete a Logon Group or Removing an Instance from a Logon Group

  • Choose CCMS® Configuration ® Logon Groups, or call transaction SMLG.
  • Select any assignment for the logon group that you want to delete or from which you want to remove an instance.
  • To remove an instance from the selected logon group, choose Remove Instance, enter the desired instance on the next screen, and confirm your choice by choosing (Delete).
  • To delete the desired log on group, choose Delete Group and confirm your choice by choosing (Delete) on the next screen.
  • Save your changes.

Changing Properties of an Assignment, a Logon Group, or an Instance

  • Choose CCMS® Configuration ® Logon Groups, or call transaction SMLG.
  • To change the properties of an assignment, double-click the assignment, and switch to the Properties tab page.
  • You can change the following properties:
  • IP address of the application server: Only enter a value in this field if the application server associated with the instance needs to be addressed by the front end with a different IP address to the one used for application server-internal communication. This value applies only for the selected assignment.
  • Settings for external RFC call: You can use this indicator to determine whether logon using an external RFC connection is to be permitted. This value applies to the selected logon group.
  • Threshold values for dialog response time and number of users logged on

How it all works

  • We achieve SAP logon load balancing by using logon groups and assigning users to various groups.
  • If you log on using a logon group, the logon is automatically performed using the instance of the group that currently has the best dialog quality. This quality is a key figure that is calculated from the number of users logged on and the average dialog response time.
  • To allow the different prerequisites of different instance to be taken into account in this calculation, you can set threshold values for the dialog response time and the number of users yourself. The larger the actual values for response time and the number of users are in comparison to the threshold values set, the lower the quality. These figures apply for the selected instance.
  • The values for Response Time and Users are not absolute limits, but rather thresholds. Even if the current value for response time or number of users is higher than this threshold value, it is possible to log on to another instance. The threshold values only influence the calculation of the current logon server of the logon groups.
  • You can use a preview to see how the settings of the threshold values can affect the quality calculation, based on the current performance data. Choose test to do this. In a logon group, the instance with the highest quality key figure is always selected for the logon.
  • Choose Copy, and save your changes.

Post Installation Procedures for SAP R/3

Make sure all the below are uptodate

  • Services
  • Users at OS
  • Shared folders
  • Environment Variables
  • File Systems

Install SAP GUI on client systems and create logon pad entries.

Run SAP Server using R/3 MMC or command line

Startsap name=<SID> nr=00 sapdiahost=host name
Stopsap name=<SID> nr=00 sapdiahost=host name
Dpmon pf=d:\usr\sap\DR1\SYS\profile\DR1_DVEBMGS00_ecc6server

Logon to SAP using GUI with SAP* or DDIC into client 000

Users we have to create super user, and change the standard password.

Perform installation consistency check SICK/SM28

To find the inconsistency between os kernel ,db kernel and find inconsistency between patch levels Import.

Import the profile parameters os level to sap level in RZ10


  • change the work process parameters, memory parameters,
  • login parameters and buffer parameters.
  • set the parameter login/no_automatic_user_sapstar=0 (in rz10)

Create SAP standard backgrpund jobs and schedule (SM36, SM37)

Create a new client and copy from 000 using local client copy (SCCL)

  • development: customizing(cust), sandbox(sand)
  • quality: test , pre test (ptst)
  • production: production (prd).

Initialize CTS (TCODE: SE06) and Config TMS

  • standard installation
  • sytem copy or migration.

Select standard installation and check perform Post installation activites set cts and perform the following steps:

  • Apply required support packs and install add-ons and pluggins (SPAM, SAINT)
  • Create a local printer
  • Check tablespace, free space stats and add required data files.
  • Take initial DB Backup either online or offline
  • Schedule SGEN
  • Create required RFC connections using SM59
  • Update DB Stats
  • Install sap license
  • Create users and check the user operations password never expires is set

Also do the following for sap accounts <sid>adm, sap service<sid>

  • SAP router configuration: Configure sap router production System
  • Check the system logs.

Scheduling a Background Job

Schedule a SAP Background Job Dialog

  • To schedule/create a background job, use the menu path: Tools CCMS Jobs definition (or transaction SM36).
  • When creating a background job, you must specify a job name and a job class (priority level A, B, or C with A being the highest priority- data transfer form external system. B – important periodic jobs performance statistics.  C – non-critical jobs: list and queries.
  • The target host is not required.  Normally, you will just leave this field blank.  However, if you are using an SAP system that has multiple application servers (and each of these servers has background work processes), you can specify the specific application server on which the background job should be processed.
  • Next, you should enter the steps (i.e., programs) to be included in the background job

Include an ABAP Program as a step inside a SAP background job

To include an ABAP/4 program in a background job, you must specify the program name and, if necessary, its variant. A variant is a set of parameter values needed for the execution of a particular program.

External programs may only be executed by users having the same authorization as the system administrator The name of the server where the external program is executed must be specified.

External commands can be executed via background jobs defined with transaction SM36 as shown above These commands are defined by the administrator and protected with authorizations.

Use transaction SM69 to define and maintain external commands. External commands that defined by SAP can not be changed


  • Logical command name
    • External commands are uniquely identified by a logical name and the assignment of an operating system
  • Operating system (CASE SENSITIVE FIELD)
    • External commands can be restricted to execute on a particular operating system (AIX) or any operating system (ANYOS)
  • Operating system command (PATH NAME)
    • Name of an operating system program
  • Parameters for operating system command
  • Check module
    • Optional function module to further check a user’s authorization to execute this command. Then maintaining external commands (SM69), you can specify the name of a check module, which is a function module that is executed immediately before the command, and can decide whether the command will be executed.

Background Processing in SAP R/3

Programs can execute in the background of the SAP system while online operation is occurring. SAP’s background processing system is easy to use and completely integrated within the system. Suppose a manager wants an accounting report ever Monday morning. Rather than having the manager execute this program online every Monday morning, it could be scheduled to run every Sunday night so that the report would already be printed for the manager when she arrived to work. This scheduling of a report program is accomplished with SAP’ background processing system. SAP Dialog, Update, Enque Spool Background Processes

  • The SAP R/3 Dispatcher and its Work Process constitute the R/3 Runtime System.
  • From the perspective of the host operating system, the R/3 Runtime System appears as a collection of parallel processes.
  • On each application server, these parallel processes include a dispatcher and work processes, the exact number of work processes is variable and depends on the specific configuration.
  • There are five types of work processes:
    • Dialog work process for executing sequential steps in business transactions
    • Update work process updates the database. It has two types of components:
      • U1 components for executing time-critical database changes
      • U2 components for executing non-critical database changes
    • Enqueue work process for setting and releasing locks on SAP R/3 business objects
    • Spool work process for spool formatting
    • Background work process for executing background jobs
  • In this chapter, we will examine background processing
  • Background processing enables you to plan the start of ABAP/4 programs. Then, at the given time, they are started by special work processes called a Background (Batch) work processes.
  • Background processing runs are composed of jobs.  Each job consists of one or more steps (i.e., programs) that are processed one after another.
  • In general, job processing is not triggered immediately; usually, a specific start time is defined when the job is planned.

SAP Background Work ProcessBackground processing enables you to plan the start of ABAP/4 programs. Then, at the given time, they are started by special work processes called a Background (Batch) work processes. Background processing runs are composed of jobs.  Each job consists of one or more steps (i.e., programs) that are processed one after another.In general, job processing is not triggered immediately. Usually, a specific start time is defined when the job is planned.

The three phases of background processing are:

  • Job Scheduling
  • Job Processing
  • Job Overview

First, we are going to cover the Job Scheduling phase.

How to change/modify profile parameters in SAP R/3 – transaction RZ11

When you change the parameter, it is changed in Db only so when you re-start the instance again the change will be lost. Need to click on save button and the profile file will be saved and a backup is created at OS level.


Click on Param Name button


If the required param is not in the listed 500 inputs, simply click on the down arrow button at the top of the above screen. Type in the parameter name partially with * before and after the partial name and hit enter. Choose the required param and double click.

SAP-R-3-Profile--DEV_DVEBMGS00 SAP-Parameter-Name

Enter the param value and click copy. It will copy and notify you in the status bar “Changes were made”. Now click on back arrow on the top and it will ask you to save the profile. Click OK and it will save the profile to OS.


Then it will ask you to change and activate the profile. Click ON and it will save the profile. Now open the profile in notepad and you will see the changes made to the instance profile (DEV_DVEBMGS_CHALAKI in this case)


The effect of activating a profile is simply that the profile is stored at OS level. For the profile to take effect for a application server you need to re-start the server SAP-DEV_DVEBMGSOO

SAP R/3 System Profiles, RZ10 – Manage Profiles

Choose One of Administration data, Basic Maintenance or Extended Maintenance and click display button to view the data or Change button to Change the data.


Basic Maintenance: Change work processes and buffer Values Extended Maintenance You can manage all the parameters in this screen. Click on Param, Param+ and Param- buttons to change the value of a parameter.


How to Maintain or Manage SAP R/3 Profiles – transaction RZ10

Use RZ10 transaction code to Manage Profiles of all Instances running in a SAP R/3 system.

when you run RZ10 the following screen will apear. You will see option to Edit Profile

  • Administration data
  • Basic Maintenance
  • Extended Maintenance


Click on Utilities/Import Profiles/Of Active Servers. This will import all profiles in all the active instances.


Click on Profile Button to see list of all imported profiles.


Select the one that u need to maintain and click ok.

Maintain the Profile

Administration data Profile


SAP – CCMS Maintain Operation Modes

Now go to ‘Operation Mode’ view. Choose the instance name and click on menu ‘Maintain instance/Work process distribution’


Double click on the ‘* All operation mode’ and it will show you the following screen. In this click on other op mode button and then on click on operation mode entry field to choose an op mode.



You can right mouse click on a op mode and choose to delete it once its assigned to an instance.


Work process distribution for the op modes across the instances



Double click on the op mode to see the work process distribution dialog. Click on the Background or update or spool work process and use + or – button to increase or decrease the work processes.

Manually switching the operation modes.

  • Choose RZ03
  • system displays list of OP modes


Choose the target op mode by clicking on “Choose operation mode” button


  • Choose the op mode and click ‘choose’
  • To switch all servers to the op mode chose in above step use:
  • Control/Switch Operation Mode/All Servers
  • To switch selected servers to the op mode chose in above step use:
  • Control/Switch Operation Mode/ selected Servers


Maintain Operation Modes with SAP CCMS (Computing Center Management System)


Give name and short description and click save. Repeate this for all the op modes. Once all the op modes are created you will see a list of op modes. Also you will see an additional op mode called DUMMY listed along with the ones create by the admins.

Assign a time table to the op modes.

Click on time table and choose normal operation and click on change button.



Choose the time interval and click ASSIGN button. Next screen will let you choose an op mode to assign to the time interval chosen from the previous screen.


Choose the appropriate op mode and click OK to save. Now choose another interval and assign to another op mode. You need to repeat this step till all 24hr time slots are assigned to any op mode.

Copyright 2005-2016 KnowledgeHills. Privacy Policy. Contact .