Controlling the Use of Big Data with SAP Tools

While using big data with SAP tools, it is necessary controlling multiple login at times. The reason is that it won’t be possible installing SAP patches when there are multiple users online. There are different types of user services in SAP. For example; there are service user and reference user in it.

Service User and Reference User

In case of the service users, the initial passwords are usually not checked. Expiration of password is also not checked and often neglected. In any case; only the administrator has the authority to change passwords and the authorization is not extended to other users. Service users are basically meant for anonymous users and only minimum authorization is allowed to them. For the reference users GUI login is not permissible. This type of user is used only in case of emergencies. It also becomes possible in this system providing one user authorization to another user.

Restricting Multiple Logins

To restrict multiple login in SAP while using big data there are certain things that you have to take care of while writing the Ids. First of all, the parameter would be set in RZ10 and all the login/multi login users are set to 1 for activating the parameter. In addition, multiple dialog login in respect of the R/3 systems are blocked. The next step would be disabling login as well as multi GUI login listing out the users who would be allowed repeated login. While writing the user Ids it is necessary that no space is given in between and to ensure that the changes are affected in the R/3 instance.

Changing Number of Work Process

It is possible changing the numbers of work processes at OS level. To increase their numbers it would be necessary to modify the parameter RDISP/WP no so that greater number of work processes can be introduced. The status of the work processes can be checked by way of executing DPMON.

Defining the Logon Process

You can define the logon process using the T-code SMLG. For this you will have to access group. Such groups can be created and thereafter the instances for the particular group can be assigned.

Single Stack System in SAP

Single stack systems in SAP can be defined in two ways. One of the ways is to use the Java runtime engine for the process. Conversely you can also use SAP Netweaver as ABAP in the process. The SAP Enterprise Portal System and SAP ECC are the examples of the single stack system in SAP.

Installing Java Patches

In use of big data with SAP it is possible installing Java patches. In order to ensure this you will have to resort to SAP installer or the SAPinst.exe that can help the process. Java patches can be installed using SDM and JSPM are the latest and most advanced tools for the purpose.

Data Sets in SAP

Data sets in SAP are used to solve the queries that cannot be solved using the traditional method interfaces. In order to check SAP applications at the operating system levels the application SAPMMCS SAP systems a SIDaSyslog is used.

Determining LUW

LUW or Logical Unit of Workin SAP is basically a list of steps that are included in the T-code under the process. There are two types of system copy; homogeneous and heterogeneous. In homogeneous system copy the same operating system and databases are components. On the other hand in heterogeneous system copy, divergent operating systems and databases are used. However it could also be use of different operating systems for the same database.

Functional Modules in BDC

For successful transferor programming data BDC can be used. Basically there are three such modules to be used in a sequence.

• BDC OPEN GROUP is the module where the name, session, and user name etc are specified.


• BDC INSERT helps insertion of data for single transaction into a session.


• BDC CLOSE GROUP can be used for closing the batch input session.

There are many others but these are some of the most effective SAP tools for controlling big data.