Automate SAP R/3 Login with QTP

Test automation for SAP R/3 applications using QTP has become quite an interesting topic and in absolute demand by most companies implementing SAP these days worldwide. As a result, it has become necessary to have, in hand, a ready library of functions which assist to implement QTP scripting for SAP R/3 application quickly and easily.

In this section, we will discuss how to login to SAP R/3 application using QTP and Vbscript when the user credentials are provided through an external spreadsheet. The steps towards building such script would be;
1)       Close any existing excel process running on the system.
2)       Open the spreadsheet where user credentials have been provided and read the 
           credentials.
3)       Read the details like Server name, Client details and Language from the spreadsheet
4)       Login to SAP.
5)       Quit Excel process and close all open objects.

Following sections helps to understand the code used for each steps.
1)       Close any existing excel process running on the system.

The  SystemUtil.CloseProcessByName(“Excel.exe”) method can be used to do this. One needs to note that SystemUtil is a QTP reserved object and can be used only with QTP.

However if one needs to achieve this using vbscript, then the following code may be used. This block of code may also be used to close multiple processes.

myComputer = "."

‘Enter the list of processes in the array. These processes will be closed by the block of code.
myArrayOfTargetProcess = Array("EXCEL.EXE")

Set objWMIService = GetObject("winmgmts:" _
 & "{impersonationLevel=impersonate}!\\" &myComputer & "\root\cimv2")
Set CollectionOfProcesses = objWMIService.ExecQuery("SELECT * FROM Win32_Process")

For Each IndividualProcess in CollectionOfProcesses
 For Each TargetProcess In myArrayOfTargetProcess
                                If LCase(IndividualProcess.Name) = LCase(TargetProcess) Then
                                intReturn = IndividualProcess.Terminate
 End If
                  Next
Next

2)       Open the spreadsheet where user credentials have been provided and read the   
          credentials.  For this, use the following code block.

    PathForLoginSpreadSheet = <enter the path for login spread sheet>
       'Create an excel application                   
                       Set  myExcelForLogin = CreateObject( "Excel.Application")
                      ‘Open the file in the specified location                     
                      myExcelForLogin.WorkBooks.open(PathForLoginSpreadSheet)
                      Set ExcelWorkBook = myExcelForLogin.ActiveWorkbook
                      Set ExcelLoginSheet = ExcelWorkBook.Worksheets("Login")

3)       Read the details like Server name, Client details and Language from the spreadsheet

Let’s assume that the data is entered in the second row of the excel sheet. Data for “Server”, “Client”, “User”, “Password” and “Language” are in the 2nd, 3rd, 4th, 5th and 6th column of the spreadsheet respectively.
This code is in continuation with the previous blocks.

With ExcelLoginSheet
               
                ‘Read the values for “Server”, “Client”, “User”, “Password” and “Language”
                SAPR3ServerName = .Cells(intRow,2)
                SAPR3Client = .Cells(intRow,3)
                SAPUserName=.Cells(intRow,4)
                SAPPassword=.Cells(intRow,5)
                UserLanguage = .Cells(intRow,6)
                               
End With                    
               
4)      Login to SAP.

Use the statement below:

SAPGuiUtil.AutoLogon SAPR3ServerName, SAPR3Client, SAPUserName, SAPPassword, UserLanguage

Please note that SAPGuiUtil.AutoLogon is a QTP reserved keyword.

5)      Quit all created objects.

    myExcelForLogin.Quit
                Set ExcelWorkBook =Nothing
    Set ExcelLoginSheet=Nothing
                Set myExcelForLogin =Nothing

Comments

  1. sap implementation methodologyAugust 13, 2011 at 3:15 AM

    Thanks! Testing while implementing SAP is crucial and it seems to me that what you've posted here will indeed come in handy. I'd appreciate reading more about any other testing tools and functions that you might think will come in handy...

    ReplyDelete

Post a Comment

Popular posts from this blog

Automatic Replenishment ~ Warehouse Management (WM) in SAP

Image
This article is intended for SAP functional consultants to configure automatic replenishment of a particular storage type for transfer orders. Whenever the stock in a bin falls below the MIN value (predefined minimum quantity), it will trigger replenishment or transfer request (TR) which will in turn get converted into a transfer order, so that the workers in the warehouse can carry out the actual physical transfer of stock. We have a provision of assigning a definite storage type from where the stock will be picked up for replenishment.   Step 1 : Material Master has to be maintained with Warehouse Views. Under Warehouse Mgmt 2 Storage bin, Maximum bin Quantity, Minimum bin Quantity and Replenishment Quantity has to be maintained. Configuration Changes: Step 2 : Movement type 320 is copied from existing movement type 319 under Logistics Execution ->Warehouse management->Activities->Transfers->Define Movement Types. Movement type 320 is configured as the follo...
Read more

Teradata - Month End Date

Sql Server: Calculating the last day of the month in SQL Server is pretty simple. Run the following piece of code and its done. SELECT DATEADD(s,-1,DATEADD(mm, DATEDIFF(m,0,GETDATE())+1,0)) CurrentMonthEnd_Day ResultSet: CurrentMonthEnd_Day ———————– 2010-08-31 23:59:59.000 Teradata: However, with reference to Teradata SQL, in our day to day queries in a datawarehouse environment very frequently we need to play with the month end dates that are mostly kept in the date dimension table with one field, i.e. the month end date field. You might require to fetch the month end date which is 4 years back. usually the simplest way in this case will be to calculate 48 months back from the current month end date (in case the monthe end date that long is not stored into the database). This is fair. The piece of code required to do is simple. SELECT (ADD_MONTHS(CAST('2012/08/31' AS DATE),-48)) Result: 2008/08/31 Now trying this simple thing will not work if its a leap year a...
Read more

SQL Optimizer Parameterization

Image
Plan Recompilation Once the Query Optimizer has come up with a plan, which may have taken a considerable amount of work, SQL Server does its best to ensure that you can leverage all that costly work again. It does this by caching the plan it just created, and taking steps to ensure that the plan is reused as widely as possible. It does this by using parameterization options. Parameterization Parameterization is a process whereby SQL Server will take the T-SQL you entered and look for ways to replace values that may be variables with a token, so that if a similar query is processed, SQL Server can identify it as being the same underlying query, apart from some string, or integer values, and make use of the already cached plan. For example, the following is a basic T-SQL query to return data from the Adventure Works 2008 database:    select *    from person.person    where lastname = 'fluffy' The parameterization of this query would result in the string...
Read more