1. Starting eCATT with TCD Recording MethodStep1: Use the Transaction code SECATT to test the data using eCATT (Extended Computer Aided Tool). Provide Test Script name in the initial screen of eCATT. Here, in the scenario I have given Test Script as ZDEMOTEST and version as 1. Click CREATE button. Step2: In the next screen, we have TWO tabs. 1. Editor Tab where we can write our own ABAP code and use the eCATT special commands. 2. Attribute Tab where we can provide Title, Component to which we are testing data. Step3: Click the Pattern button on Application tool bar to select recording method. Select TCD (Recording) method. Step4: Select the pattern button. A pop-up box appears where you have to select GROUP as UI Control. And COMMAND as TCD (Recording) as shown. Provide the transaction as MM01 and press enter. Then the system automatically proposes Interface name and dont change this Interface name. In this scenario system proposes MM01_1. Now, click OK button to start recording. Step5: After the recording is done, you will get message the Recording Ended and press YES. And the following screen appears. Save and check syntax check. Step6: First of all execute the script without parameterization to confirm errorless recording. At the run time, a start options window appears. Select the following options as shown. And in UI Control Tab, Click on Execute button. Step7: After execution of the transaction, if the recording is free from errors, then the success log would be displayed. Suppose if there are any errors in recording of the transaction then the detailed error log would appear. If the transaction has executed successfully, you would get the following messages.

2. Creating a simple eCATT Test Script for MM02 transactionA Simple scenario on eCATT Test Script to the Standard Transaction.In this scenario, I would like to explain about create Test Script for MM02.Procedure Start transaction SECATT.On the eCATT initial screen, select the System Data radio button and enter a name for your new system data container in the field beside it. For this tutorial, we will refer to it as ZTEST_SDC.

On the Attributes tab, enter a title for the system data container for example, System Landscape for MM02.

In the System Data tab, you would notice a default target system called NONE. Save your system data container.Creating Your Test ScriptIn this section, you will create an empty test script and assign to it the system data container that you created earlier. You will then execute the test script.

On the Attributes tab, enter the following information:Title : Test Script for MM02 Component: BC-TWB-TST-ECA System Data Container: ZTEST_SDCLeave the Target System field empty.

Save your test script. Choose Execute Button and Execute the Test Script.The Start Options are displayed.Accept the defaults but make sure that Log Display has been selected. Select the checkbox Highlight All Called GUI Elements. This option is cosmetic but will help you see which elements are being selected during replay. Leave the other default options as they are. Execute the test script. The log will then be displayed and should look something like the following: Get back to the Test Script Editor. Recording the TransactionStarting the Recordern the test script editor, choose the Pattern function to display the Insert Statement dialog.

In the dialog, change the group to UI Control, choose SAPGUI (Record) for the command.

Specify the transaction MM02 that you want to record. Additionally, select the check box that will automatically generate a new SAPGUI command after every screen change ( You must first deselect manual generation).

Choose Start Recording or Enter

Click on Yes. A new session is automatically created. You can, and should, switch back and forward between the two sessions using the taskbar as shown below. Enter the Material

Select the Basic Data1 Basic Data1 Screen as shown.

Change the Gross Weight.

Save and Close the screen Ending the Recording Select the Close Recorded GUIs check box and then choose Stop Recording.The recorded session closes and you now see the SAPGUI commands in the command editor of the test script editor.

Above the command editor is the parameter list. You can use the button at the top left of this section to toggle between the display of normal parameters and the command interfaces. Choose Save. Executing Your Test Script In the test script editor, choose Execute button. Choose Execute Button in the Start Options screen.Check the log.

3. Starting eCATT with SAPGUI Recording MethodStep1: Use the Transaction code SECATT to test the data using eCATT (Extended Computer Aided Tool). Provide Test Script name in the initial screen of eCATT. Here, in the scenario I have given Test Script as ZDEMO_TEST and version as 1. Click the Create button. Step2: In the next screen, we have TWO tabs. 1. Editor Tab where we can write our own ABAP code and use the eCATT special commands. 2. Attribute Tab where we can provide Title, Component to which we are testing data.

Here, I selected the component MM-PUR-SQ- SLI (Source List). Step3: To do the recording, click the Pattern button in the application tool bar. Here, we can do recording in TWO ways. 1. SAP GUI(Recording) 2. TCD(Recording) Now, we use SAP GUI (Recording). Step4: Select the pattern button. A pop-up box appears where you have to select GROUP as UI Control.

And COMMAND as SAP GUI (Recording). Click OK button. Step5: Click YES. The following screen will appear. Select all check boxes of Automatic Generation. Provide the T-code to which we have to be started recording. Now select Start Recording button to start recording of the corresponding transaction code we have mentioned. You will get pop-up box and click YES to continue recording. Step6: After recording, a SAP GUI command and its associated command interface will be inserted in the test script editor. Save and check syntax check. Step7: First of all execute the script without parameterization to confirm errorless recording. At the run time, a start options window appears. Select the following options as shown.

And in UI Control Tab,

Click on Execute button. Step8: After execution of the transaction, if there is no errors are found while recording, then you will get success log. Suppose there is error in recording of the transaction then the detailed error log will appear.