To create an SECATT you must first create the Test Script.

After the test script you will create a Test Configuration. Goto SECATT Enter title Enter component Click on Pattern button on menu bar Choose Group value = UI Control Choose Comman value = TCD (Record) Enter tcode and press enter to accept the default interface Click the green check mark <<<Record the function you are attempting to perform>>> After backing out of the function you were recording you will be returned to the SECATT screen and you should see a prompt asking if you want to transfer the data. Answer Yes. Now double-click on the Interface. In this case the interface was named PFCG_1. Using the split screen you must now navigate through the various screens you just recorded replacing fixed values with import variables. (Look at “VALIN” fields with the

input values you specified) This is done by opening the Dynpro menu and going through each numbered screen to review your input. In this process my SECATT will change the description of a role. So I will have two variables: 1) the role name and 2) the description. located the Role Name on the first screen by doubleclicking on the menu node named “Field.” You must then move over to the third subscreen and tab over to the VALIN column where you find the actual value you entered into SAP when recording the interface. You must then change that to a variable . The variable name is Z_ROLENAME. Once you enter the variable name hit the enter key The default parameter type will be Local. You should change this to Import and click on the Yes button. Note the icon has changed from the green square. This icon indicates a variable is present. Now change all the other variables in the same manner. When complete click on the save icon and save as a local object or place in a development class if you desire to transport the SECATT.

Before you can execute the SECATT you must first create a Test Configuration. Do this by executing SECATT transaction code and entering a name for the Test Configuration and clicking on the create icon. This name can be anything in the customer name space. Give the Test Configuration a Name and Component and then click on the Configuration tab Enter the name of the test script you would like to execute when you execute the test configuration Now we need to create the Excel template file to store the variable data in. Do this by clicking on the download icon or just press ctrl-shift-F11. You will then be prompted with a Windows “save as” dialog box. Accept the default name and directory and click save. Click on the Yes icon and you should see the message at the bottom of the screen “variants successfully downloaded.” Now click on the Variants icon.

These scripts can be then tested before go live to Production server. using CATT etc. And if the test results in error than one can analyze the problems from the generated error log.We must now set the default Mode for each time the Test Configuration is executed. eCATT generates a detailed log depending on the processes executed. Thus helps in analyzing the error. which can be used to automate & test business scenarios in R/3. If the testing is smooth with success mode. this means the business scenarios mapped in R/3 system are correct. Why To Use eCATT? . If needed eCATT can be used in production server also provided exact functionality of its usage should be known. What Is eCATT? eCATT is a SAP Testing Tool. After testing. What Are The Various Ways Of Doing Testing? Testing can be done by various ways like Manually. Since we will always be running the script with an external file choose the External Variants / Path option. One can create and execute the eCATT scripts based on business processes mapped in R/3.

This helps.20 or more. SAPGUI 6. Proved to be extremely useful in Rollout projects. . less manpower is required for testing. R/3 4. some system settings need to be done – • Maintaining Table T000 o Start transaction SM31. So those using CATT are forced to update to use eCATT.7. Due to automation. Due to automation. Maintain Table Views. This helps financially. Before creating Test Scripts using eCATT. testing time is reduced to a large extent. Comparative to manual testing.6C or more. manual errors are reduced to large extent. the following are advantages of using eCATT – • Due to automation.20 or more. Hence results in error free testing. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.CATT will be no longer supported for the creation of new development. • • • eCATT Prequisites: Web Application Server (WAS) 6. as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.

o o o .o o o In the Table/View field. choose Customizing of local layout from the Standard Toolbar. Select Enable Scripting. select the relevant client and choose. Choose the Scripting tab. In the Restrictions when starting CATT and eCATT field. Overview screen. (Check whether SAP GUI Scripting component is installed. Choose Options. Choose Maintain. enter T000.) o On any screen. There is an option for installing this component when installing the SAP GUI. In the Change View Clients. select an entry that allows eCATT. o • Enabling Scripting at the front End.

In the Display Profile Parameter Attributes screen. o o . choose Change value from Application Toolbar.o Choose Apply. • Enabling Scripting on application server. On the Maintain Profile Parameters screen. Choose Display. o o Start transaction RZ11. enter sapgui/user_scripting.

• • • • • Test remote systems. Test database updates. Features Available In eCATT: • Test transactions and reports. Test the effect of changes to customizing settings. so allows proper management of scripts using SCAT transaction. Check system messages. Check authorizations (user profiles). Set up customizing tables. Perform load testing. Call BAPIs and function modules.o Enter TRUE in the New value field. Integrated with Test Workbench. • • • • . • The R/3 users executing eCATT scripts should have RFC authorizations.

All eCATT Objects are Repository Objects. • TCD: Suitable for testing transactions (especially who don’t involve activex controls). Test Data & System Data allows for a considerable degree of reuse. load testing. load testing. including those running outside of SAP GUI for Windows and SAP GUI for Java. There can be several versions of Test Scripts.• • Supports CATT migration to eCATT. The separation of Test Scripts. eCATT Objects can easily download & upload in XML with XSD format. There are four different drivers available in eCATT for this testing purpose as follows – • Non-User Interface: Suitable for testing backend R/3 specific modules like function modules & BAPIs. Doesn’t . • • • Ways Of Doing Testing In eCATT: eCATT enables to test all mySAP applications. Therefore one can take advantage of Standard SAP Transport Tools. Interfaces testing in mySAP environment. which allows different implementations with different releases.

so offers maximum speed for testing. Transaction For Using eCATT: • Choose SAP menu-> Test->Test Workbench>CATT->Extended CATT. which are certified against BCeCATT Interface. . Test Configuration data object contains set of reference to a Test Script. System Data Container & several Test Data Containers. Requires GUI for playback & hence very slow. It contains all the information necessary to run an automatic test without further user interaction. • SAPGUI Scripting: Suitable for testing transactions. who involve activex controls. Not suitable for load testing. can be tested who run under GUIs (Other than SAP GUI for Windows & SAP GUI for JAVA) using eCATT. Editors Available In eCATT From SECATT Transaction: • Test Configuration Editor: Used to maintain Test Configuration object.require GUI for playback. • Interface To External Tools: External products. • Transaction code – SECATT.

Test Script Editor has following areas:    Application Toolbar.• Test Script Editor: Used to create & maintain Test Scripts. Information Area Editor Tab –    Parameter List Command Editor Structure Editor  Attribute Tab . There are some recording functions available in this editor.

or tables. Parameters can be ABAP simple types. structures.Test script data object contains an executable script & an interface for data transfer. which contain a set of parameters that can be maintained independently of a test script. Test Data Containers are the data objects. • Test Data Editor: Used to create & maintain the Test Data Containers. • System Data Editor: .

the creation of eCATT scripts using TCD mode of recording will be explained in detail. should be done. which identify instances of SAP systems. They can be maintained independently of the test script like Test Data Containers. Parameterization of the import. In Part II. Execution of test script immediately after recording without parameterization to confirm the errorless recording.Used to create & maintain the System Data Containers. In the subsequent Parts. which prepares the input data for the script and also covers the planned business scenario. System Data Containers are the data objects. • Recording of test script by selecting proper recording mode. Steps Involved In Creation Of eCATT Test Scripts: • Test script is generally series of steps (transactions) involving a business scenario. SAPGUI recording mode of recording and other details of eCATT will be covered. Identification of right transactions for this script. export & variable parameters. • • . The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved.

• •

Preparing variants using Test Data Container. Linking Test Script (TS) & Test Data Container (TD) by Test Configuration (TC). Execution of TS using TC for different Variants.

How To Identify Any Transaction For TCD Recording Mode: • If the transaction runs under SAP GUI for Windows or SAP GUI for Java, it can be recorded by either TCD or SAP GUI mode.

If the transaction doesn’t have any activex controls then TCD recording mode can be used. If the transaction has activex controls and these controls are NOT mandatory for the functionality of the transaction, then also TCD mode can be used as recording mode.

Key Features Of TCD Recording Mode: • It is suitable for the transactions not having activex controls, so it doesn’t require any GUI playback mode.
• •

It is very fast. It has its own built in screen simulation for standard screen elements. Hence while execution, the controls are deactivated and the user’s actions are simulated by reading the recorded data flow.

Steps For Recording Using TCD Mode: • Transaction SECATT.

Give the name of the Test Script (TS) in Test Script input box. The Version input by default is with value 1. In the Attributes ->General Data Tab, the value of the Component will be BC-TWB-TST-ECA for eCATT. In the test script editor, choose the Editor tab. Choose Pattern button from the application toolbar. The Insert Statement dialog box appears. From the Command Dropdown List, choose TCD (Record). In the Transaction field, enter the transaction code of the transaction that you want to record, and choose Enter.

• •

• •

In the Interface field, a system-generated name appears. Accept the system-generated name or edit it.

If there is a system data container, you can enter the target system in the Target System field. Choose Enter. The transaction starts recording. Work through the transaction as normal. When you leave the transaction, the system returns you to the script editor with the Recording ended dialog box. Choose Yes to transfer the data. A TCD command and its associated Command Interface will be inserted in test script editor of SECATT.

• •

• •

Execution of Recorded TCD script:

continue with next script. script can be executed. select N – Process in background. a Start Options window appears. System Data – Name of the system data container. o o o o .• Once the recording of the transaction is done and the details of recording are taken back to the test script editor. Give the following values on this window – o • Error Behavior with value S No termination. At the runtime. In TCD section of window. First of all without parameterization the script should be executed to confirm the errorless recording. Target System – Name of the server on which the execution will happen. synchronous local. which contains the Target System. Select the Log Display check box.

• Transaction will start executing. If the recording is error free. variants can be prepared for the recorded test script.o Click on Execute button. one can go ahead with parameterization of the import. export & variables. which appears at the bottom. In the Parameters tab. then success log will appear. After the confirmation of error free recording. In SECATT transaction using Test Data (TD). add all the • • • . And if there is any error in recording of the transaction and its replay then error log with details will appear.

parameters from the test script. The TC is used in managing the scripts in plans/packages using SCAT transaction. . Steps Involved In Creation Of eCATT Test Scripts: • Test script is generally series of steps (transactions) involving a business scenario. as per requirement in the Variants tab. This will appear as ECATTDEFAULT in the Variants tab. In the Part III. On the Variants tab. • In SECATT transaction using Test Configuration (TC). • • The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. the TD & TS can be linked together on the Configuration tab. Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. Hence can be reused wherever required. Add multiple variants. Test Data is independent of test script. the creation of eCATT Scripts using SAPGUI mode is explained in detail. the creation of eCATT scripts using TCD mode of recording is explained in detail. In the subsequent Parts. Management of eCATT scripts via Test Workbench and other details of eCATT will be covered. using Variant Maintenance Assistant required variants values from TD could be linked to TC. In Part II. Identification of right transactions for this script.

it can be recorded by either TCD or SAP GUI mode. Parameterization of the import. • Recording of test script by selecting proper recording mode. then only SAPGUI mode can be used as recording mode.which prepares the input data for the script and also covers the planned business scenario. If the transaction has activex controls and these controls ARE MANDATORY for the functionality of the transaction. Here SAPGUI mode can also work. • . Linking Test Script (TS) & Test Data Container (TD) by Test Configuration (TC). • If the transaction doesn’t have any activex controls then TCD recording mode should be used. Execution of TS using TC for different Variants. export & variable parameters. Execution of test script immediately after recording without parameterization to confirm the errorless recording. • • • • • How To Identify Any Transaction For SAPGUI Recording Mode: • If the transaction runs under SAP GUI for Windows or SAP GUI for Java. should be done. Preparing variants using Test Data Container.

so it requires GUI playback mode.Key Features Of SAPGUI Recording Mode: • It is suitable for the transactions having activex controls. • • • • . • • It is slow comparative to TCD recording mode. the values of the SystemDataContainer should be given which contains all target systems with RFCs on which the script will be either executed or recorded & in the TargetSystem the name of target system (e. • Give the name of the test script (TS) in Test Script input box.g. click on Record Test Script (Ctrl+F5). From the Application Toolbar. Steps For Recording Using SAPGUI Mode: • Transaction SECATT. In the test script editor. recording R/3 server) should be mentioned. The Version input by default is with value 1. In the Attributes ->General Data Tab. the value of the component will be BC-TWB-TST-ECA for eCATT. choose the Editor tab. It is not suitable for load testing. In the Attributes ->General Data Tab.

One window appears on the newly created session of target system as ‘Record SAP GUI • . select each check box of the Automatic Generation section.• One window appears with title ‘Record SAP GUI Command’. • Login in to Target System from SAP Logon or either create a new session on target system. Click On Start Recording button.

This recording window exists till recording ends.Command’. So one can be selective in . • One window with title ‘Recording Running’ will appear. Click on Yes for recording. Select all the check boxes. select the Record with inactive checks radio button. Lots of data of initial state for the mentioned screen element types will be generated. In the section of Record initial state for value check. one table control with the record/ types for GUI elements is mentioned along with check boxes. Select the check box of Closed Recorded GUIs and click finally the Continue (Enter) button. Below the radio buttons.

Once the transaction is complete with the functionality. This will take the recorded details of the transaction to SECATT transaction in the test script editor. A SAPGUI command and its associated Command Interface will be inserted in test script • • . click on End Recording button.selecting the checkboxes. • Recording can be started with the transaction working as normal on the newly generated session. from the Recording Running window.

Give the following values on this window: o Error Behavior S No termination. continue with next script. At the runtime. . Execution of Recorded SAPGUI script: • Once the recording of the transaction is done and the details of recording are taken back to the test script editor. • First of all without parameterization the script should be executed to confirm the errorless recording. script can be executed.editor of SECATT. a Start Options window appears.

Select the Log Display check box. Target System – Name of the server on which the execution will happen.N Do Not Stop Close GUIs . .R Close Generated Sessions After REF    o Click on Execute button. select following options:  o o o Procg Mode SAPGUI .S Synchronous GUI Control Error Mode for SAPGUI .C Continue (Continue on Any Error) Stop When . which contains the Target System. In SAPGUI section of window.o System Data – Name of the system data container.

then success log will appear. This will appear as ECATTDEFAULT in the Variants tab. After the confirmation of error free recording. In SECATT transaction using Test Data (TD). variants can be prepared for the recorded test script. If the recording is error free. Add • • • .• Transaction will start executing. In the Parameters tab. This requires GUI for playback. add all the parameters from the test script. one can go ahead with parameterization of the import. And if there is any error in recording of the transaction and its replay then error log with details will appear. export & variables. by creating a new session.

The TC is used in managing the scripts in plans/packages using SCAT transaction. In Part II. Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. the TD & TS can be linked together on the Configuration tab. Test Data Container. as per requirement in the Variants tab. creation of Test Configuration. import interfaces or local variables of a script. Hence can be reused wherever required. Test Data is independent of test script. What Are Parameters: • Parameters are export. parameterization. In Part IV chaining. In Part III. using Variant Maintenance Assistant required variants values from TD could be linked to TC. the creation of eCATT scripts using TCD mode of recording is explained in detail. • • The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. On the Variants tab. and System Data Container will be explained in detail and in subsequent parts the management of eCATT Scripts via Testworkbench & other details of eCATT will be covered. • In SECATT transaction using Test Configuration (TC). Parameter name can be 30 .multiple variants. SAPGUI recording mode of recording is explained in detail.

char long. • ONLY local variables can be used in the inline ABAP block in the test script editor. Import parameters can hold default value also. export parameter or local variable. The result value is passed into the export parameter when the test returns from the test module. Import Parameters (IP): Import parameters are input values to the script. The first letter should be either an underscore or character. They are passed to the script during execution. • Their visibility within the script is same and outside it is of import parameter. • • . Export Parameters (EP): Export parameters are outcome of the test script execution. They are locally available and test script version independent. The visibility can be set from the parameters list. Import & Export parameters CANNOT be used in the inline ABAP block. They are test script version independent.

Local Variables (LV): Local variables are used in test scripts for calculations, or to receive export parameters from referred test cases or called function modules. They are also used for passing values to and from inline ABAP blocks & are version-dependent – that is, a local variable defined in one version is not automatically defined in another version. System fields can also be used in command editor. They are read-only and are available from SYST structure. There are special read-only eCATT variables, which can also be used in command editor. e.g. &YEARB, &YEARA, &YEAR, &VARID, &USER, &TIME, &SYSTEM, &SUBRC, &SCRIPTVERSION, &SCRIPTNAME, &SAPRL, &REFVERSION, &REFNAME, &REFLEVEL, &OPSYS, &MSX, &MST, &MSN, &MSI, &MSG, &MS4, &MS3, &MS2, &MS1, &M04, &M03, &M02, &M01, &LPC, &LOGID, &LANGUAGE, &HOST, &EXCEPTION, &DBSYS, &DATE, &CLIENT etc. The status of values, either fixed or parameterized or not define, are symbolized as

follows -

Why Parameterization Is Needed: • After recording of the transaction. Transaction can be checked without parameterization for errorless recording. Once the successful recording is confirmed, automation can be parameterized.

Due to parameterization, the recording becomes reusable. Different sets of data can be passed via parameters and the recorded script can be used again and again. This is very similar to concept of Constants in Program (Without parameterization) and using variables for those values (with parameterization). If parameterization is not done than before next execution of automated script, input data will be checked and changed at Test Script level. Due to this the errorless recording time data will be disturbed. Hence parameterization is necessary.

TCD Mode Parameterization:

 If a transaction is recorded via TCD mode, then the screens can be simulated via screen simulation. Screen simulation can be used to edit and parameterize the fields. Screen simulation icon is present in the command interface of the TCD mode. Using Screen simulation Import parameters, Export parameters, field check, and values in the input field can be assigned. To delete the default values space characters (‘ ‘) can be passed via screen simulation. For parameterization, if the field has any value, one can clear it.

 Fields having mode ‘S’ (Set) under each dynpro of the command interface contain some value entered during the recording. This is the value one needs to parameterize as Import Parameter so that with next run a new set of data will be passed to the recording. And recording becomes reusable.  For parameterization, select the Dynpro whose fields need to be parameterized as Import/Export parameter. Click on Screen Simulation icon of the command interface. The system will prompt for the login of recording time target system. Give the login details.  Defining Import Parameters:

Export parameter are necessary for chaining of . The parameter will be inserted into the parameter list.• After step 3. Click on Back (F3) button of the standard toolbar. the screen simulation window will appear. Give the parameter name & default value in the Field contents there. This way one can parameterize all the import values. Press enter. Select the field value & click on Insert Import Parameter (F6) icon from the application toolbar. • One Maintain field entry window appears for the selected field with its technical name.  Defining Export Parameters: • The output results of the transaction are assigned to export parameters.

Give the name of the export parameter. the screen simulation window will appear. Click on Back (F3) button from the standard toolbar. Export parameters can be assigned for these values. Here export parameters can be linked between the two transactions interacting.transactions wherein output of one transaction becomes input for other transaction. Follow step 3. After step 3. • Fields having ‘G’ (Get) as mode are assigned to export parameters. Last dynpro in the dynpro list just before the MSG node in the command interface contains the output messages and other outcomes. . Automatically the name will be included in the Parameters list. Name needs to be given. Click on enter. • • Read field value window appears. The field with the technical name appears against which the Param. Select the field and click on the Read field value (Ctrl+Shift+F3) icon from the application toolbar.

After step 3. it will be created automatically as import parameter in the parameter list. The check value can be a constant or a parameter value. Click on enter. Click . Name. Give the name of the variable in the Param. Click on the Check field (Ctrl+Shift+F2) icon from the application toolbar.  Defining Field Checks: • One can check whether the runtime value of a field is the expected value or not. clear the value of the field. • • Maintain field check dialog box appears. Give the value against this field.This way one can parameterize all the export values. If it doesn’t exist. screen simulation window appears. If the field has already some value. Select the field. • Follow step 3.

Double click on the field number. assign the Import parameter to Value field. Under the ProcessedScreen -> UserChangedState node select the State node of the field. SAPGUI Mode Parameterization:  Defining Import Parameters: • Import parameters are defined for the input values given during the recording of the transaction. These values are present under the ProcessedScreen node of the SAPGUI command interface for the given screen. On right side the command interface will open. On the rightmost section. which needs to be parameterized. • Double click on the command interface of SAPGUI command from the test script editor from the left side. .on Back (F3) button from the standard toolbar.

i.g.e. .  Defining Export Parameters: • Export parameters are used to link transactions while chaining. So the results are captured from Message node under the ProcessedScreen node using MESSAGE-ENDMESSAGE command. • Export parameters are assigned to result of transaction. Export parameter of first transaction becomes the import parameter in chaining.Define this import parameter in the parameter list with the type of the field & assign the default value. This way multiple import parameters can be assigned & created. e. Material Created out of MM01 transaction.

From the Command dropdown. . The message variable number can be confirmed from the command interface from the right side. After that assign the respective message parameter to the export parameter. Click on enter. select the MESSGAE MESSAGE …END MESSAGE option.• Click on Pattern (Ctrl+F6) button from the application toolbar. Place this block around the SAPGUI command from which the export value will be captured. The MESSAGE-ENDMESSAGE for interface MSG_1 will be inserted into the test script editor. The Interface name is automatically populated by system.

in test script editor. Under the ProcessedScreen -> InitialState . And then passing this export parameter as input (import parameters) to subsequent screens. This can be achieved by assigning an Export Parameter to the required value. system generated value for an input field on one screen can be passed to subsequent screen. • Passing Values To Subsequent Screen: In SAPGUI mode. This way multiple export parameters can be declared. E.Declare this export parameter in the parameter list. o Double click on interface from the SAPGUI command in which the parameter to be captured exists. the command interface will open. On the right side. value from one screen can be passed to the subsequent screen.g.

write the Export Parameter name. the value will exist. which is to be captured.node. Make sure that the Check. . which appears in square braces. is blank ‘ ‘ instead of ‘X’. of the topmost GuiElement branch under which the GuiElement exists which needs to capture. On the right side. double click on the number. o Under the State node of the GuiElement. Name & Value will appear. There in Value.

o Declare this export parameter in the parameter list. The export parameter. create a new script. VA01 output of sales order can be given as input to VA02. • • . which is outcome of first transaction. Create two test scripts. E. Each step is automated and then linked together via chaining so as to complete the business scenario. Transaction SECATT. • Chaining mainly involves the linking of script by import & export parameters. is passed as import parameter to second transaction and so on. Chaining Of Scripts: • Test case is a series of steps (transactions) involving one business scenario. For creating chaining of the scripts.g. Click on Pattern (Ctrl+F6) button from the application toolbar. which are related in a way that output of one script becomes input to other. Both the scripts should be parameterized as well. And it can be passed further in same recording to subsequent screens as import parameter.

give the name of test script. On the right side the interface will open with the Importing/Exporting nodes. The Interface name will be automatically populated. all the import parameters appear under the Element column. Double click on Importing node.• One Insert Statement dialog box will appear. On the rightmost side. • Double click on the Command Interface of the inserted REF statement in the test script editor. In the Test Script. which were assigned while creation of that script. The REF command will be inserted into the test script editor. These Importing and Exporting node have import and export parameters. which needs to be linked. . Press Enter. From the Command dropdown. select REF command. Press Enter.

• Double click on Exporting node of the command interface. . On the right side the export parameters. Declare the variables and assign them to the export parameters. Assign the import parameters and variables to the Importing as well as Exporting nodes respectively.Declare all import parameters in the Parameter section above and assign then in Value column below against the Import parameters. • Similar ways include other test scripts also using REF command. which were created during the script creation are displayed.

Click on Save (Ctrl+S) button from the standard toolbar. execute the script and ensure the correctness of chaining. • This ways multiple transactions can be linked together in the final chained script. The parameter list of this chained script contains only the import parameters as well as the variables. The import parameter of chained script is assigned to the respective Importing node element. Once the • . By giving the default values in the import parameters.• The export of one test script will be assigned as import of the next script using variables.

Target systems with their RFCs are mentioned in the SD. Give the necessary details like RFC Destination. Description. Connection Type. . create a RFC destination for R/3 system. which can be used at the recording time and/or at execution time. • Creation of RFC for target system: RFC destination will be created for the target systems.successful execution of the chained script is confirmed. which will be used as recording time and/or execution time systems for eCATT scripts. Creation Of System Data Container (SD): • System data container contains the list of the target servers. TD and TC can be prepared. Using SM59 on source system (where eCATT scripts will be available).

Hence secure. Click on Create Object (F5) icon from the . This ensures that every time.In Logon/Security tab. After RFC creation. login window will be prompted when target system is referred via RFC. • • For SD creation. In the System Data input field give the name of SD. the server can be added to the SD list. recommended is to mention the Trusted system ‘No’. transaction SECATT.

The Instance Description field is automatically filled by system. • Under the System Data tab. • On the create screen. give the name of the target server.application toolbar. Click on Save (Ctrl+S) icon from the standard toolbar. In the Test System column. give the Title (mandatory) for the SD. . Under the RFC Destination column. Append a new row by clicking Append row icon from the toolbar. target system NONE is already present. By this name the target system will be referred in eCATT. select the respective RFC for the target system. in the Attribs tab.

In the Test Data input field. under the Attributes -> General Data tab in the Header Data section. Variants created in TD are linked in Test Configuration. .This way multiple target systems can be added to the system data. give the name of the test data. Under the Maintenance System. Variant values are also maintained in TD. give Title (Mandatory) and Component (Mandatory). Click on Create Object (F5) icon from the application toolbar. Creation Of Test Data Container (TD): • Test data containers are used for creation of variants. Hence once created can be used for multiple scripts. • On the create screen. TD is independent of test script. • • Transaction SECATT.

Add the lines to the required number of parameters. Add the parameters. ECATTDEFAULT variant will be present as default. This variant contains values . The parameters name & type must match to that of the script to which the TD will be linked. Click on Save (Ctrl+S) button from the standard toolbar. click on Append Parameter icon and the new lines will be appended in the parameter list. Under the Variants tab. which is present in the SD. the column titles are Variant. • Under the Parameters tab. minimum one parameter should be present in parameter list. Description & after that the parameters from the parameters list.give the SystemData Container as well as Target System. • To create variant.

• To add new variants. Click on Save (Ctrl+S) button from the standard toolbar. Add required number of variants this way. In turn these variant . Creation Of Test Configuration (TC): • Test Configuration contains reference to one Test Script (TS). • One more Advantage of using TC is that for any given script. click on Append Variant icon. one System Data container (SD) and can contain reference to multiple Test Data container (TD). Give the details of new variant with values. without changing data at TS level. the script can be checked for different sets of data using Variants of TC.from the Parameters under the Parameters tab. TC is used in scripts management using TestWorkbench in R/3 system.

Hence the errorless recording time data is always maintained in TS. And the Last Changed script attribute (Attributes tab -> Extras tab -> Administration Data) will contain only the details of the person who has made changes to script and not to the data. Also give the name of Test Script.values are captured from TD. give the Title (Mandatory) & Component (Mandatory). transaction SECATT. • On the create screen. • Under the Configuration tab. Give the name of TC in Test Configuration and click on Create Object (F5) icon from the application toolbar. give the System Data Container. • • For TC creation. which contains the Target System. Test Data and an Alias can be added to Test Data .

.section using Append Row icon. The TC references the import part of the data interface of the test script. click on the Append Variant icon. Multiple test data can be given if required. The Alias is an alphanumeric name up to three characters. This will insert a new line for variant under ECATTDEFAULT. o Manually Creating Variants: In the Test Configuration editor under Variants tab. Variants can be prepared either manually by clicking the icons Append Variant/Insert Variants or from the wizard using test data containers referenced in the Configuration tab. • Variants can be added from Variants tab.

The left half of the screen displays the variants belonging . click on the wizard icon (Variant Maintenance Assistant) under the Variants tab. Click on Save (Ctrl+S) button from the standard toolbar. give the name of the variant.  The Variant Maintenance Assistant window appears. Under each parameter either give value or leave the field blank. This way multiple variants can be directly added to Variants list. o Variants from Test Data Containers:  Prerequisite for this option is that Test Data Containers should be maintained under Configuration tab.In the Variants field. To create variants from the Test Data containers.

The value in a field is determined by the following syntax: <parameter name>(<alias>. The links will be present for the values of the parameters from TC to TD.to a test data container. Any changes done at TD side will be referred  . The variant will be copied to Test Configuration side. Click on enter. <variant>) where the parameter name. Select the variant from the Test Data & click on Attach as variant button. and variant all refer to a test data container. The right half of the screen displays the variants belonging to the test configuration. Scrolling between the multiple variants of Test Data is available. Variant will be added to Variants list in TC. alias.  Only the parameters in the test data container that match those of the test script are appended.

Choose Link individual field.dynamically in TC. alias.  Linking single field of Test Data variant to Test Configuration variant: Select a field belonging to a test data container. Select an empty field belonging to the test configuration. Choose Insert in column. The value in a field is determined by the following syntax: <parameter name>(<alias>. The field belonging to the test configuration is filled.<variant>) where the parameter name. Select a field belonging to the test configuration. All the empty fields in the column are filled. and variant all refer to a test data container. Click on enter. This way multiple variants can be created. The value in a field is determined by the following syntax: <parameter . The field will be dynamically linked.  Linking multiple fields in Test Configuration column to a single field of Test Data variant: Select a field belonging to a test data container.

Why eCATT Scripts Management Is Required By Test Workbench By SCAT: • eCATT scripts can be very well executed via the transaction SECATT by which the scripts are created. and variant all refer to a test data container. alias. the creation of eCATT scripts using TCD mode of recording is explained in detail. the management of eCATT Scripts via Testworkbench will be explained. In the subsequent parts eCATT Logs & other details of eCATT will be covered. And Test Configuration is now ready to execute or to link to TestWorkbench depending on the variant selected. creation of Test Configuration. In Part II. At test script level . In Part IV. In Part III. In Part V. the script execution can happen at Test Script (TS) level or Test Configuration (TC) level. Click on enter. System Data Container are explained in detail. the parameterization. o Click on Save (Ctrl+S) icon from the standard toolbar.Test Data Container. The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved.name>(<alias>.<variant>) where the parameter name. In SECATT. SAPGUI recording mode of recording is explained in detail.

This change will override the default recording data of the script. which are as a result of the test carried out during final testing. Now even if the execution can happen via TC. As script executes multiple times. So which log has generated during the final regression testing time is difficult to make out. If the script recording is error free then change of the data at TS level is not recommended. which are picked from Test Data (TD) Container. These log IDs will be available for future use. the data is changed at variant level. the logs are stored against that script.e. the requirement is that somewhere the log IDs should be present along with the scripts.execution. the data may need to be changed depending on the behavior of transaction(s) in the script. Hence execution of the script via TC is adapted. ECATTDEFAULT. • Moreover one has to maintain the log IDs of the scripts being executed via SECATT. which are related depending on a series of functionality or the function module or location against which the test case is being executed. So all the requirements of grouping the scripts on some • . then also clubbing of TCs. Changing data in TD doesn’t affect the default recoding time data i. In TC. Hence for the Regression Test. is not possible via SECATT transaction.

How Scripts Can Be Managed In Test Workbench: • Test cases can be managed in test workbench via Test Catalog. availability of log IDs for future usage will be fulfilled by Test Workbench SCAT Transaction. Test status is in terms of traffic lights for eCATT logs. Test Package .A Test Catalog is a set of test cases in a hierarchical hypertext structure. • • . in a particular period for a particular purpose. The relevant test cases can be divided among several test catalogs. One can create test plans across several test catalogs via the SAP application hierarchy.A test package is a person and period-oriented view of a test plan. • Test Catalog . To be able to use the test catalog to generate test plans. It contains all tests. Test Plans & Test Packages. which are easier to maintain than one large test catalog. Test Plan . This procedure allows creating a lot of small test catalogs. one must put it in the SAP Application hierarchy.A test plan is a set of test cases. which a tester is to perform in a specified period. Also with the Test Workbench test status can be analyzed.defined conditions. which must be tested.

Creation Of Test Catalogs: • Transaction SCAT or Tools->ABAP Workbench>Test->Test Workbench->Test Organizer>Manage Test Catalog. ‚Pass‘ or ‚Fail‘. one can get an overview of the status of all test cases of a test plan with Status analyses. Click on Create (F5) icon from the application toolbar. • Click on menu Environment->Manage Test Catalog. the tester sets the test case status. System Data • • • . e.• After a test.g. Give the name of System Data and Target System in the eCATT section. Test Catalog Information window appears.

• • The Test Catalog is created. In the Responsibility section. Name contains the logged in user name by default. • . Now the Test Configurations need to be added to this test catalog. The title is the name of the catalog by which it will be referred in the Test Plans.container should contain the RFC for the Target System on which the script will execute. Click on Save (Ctrl+S) from the standard toolbar. name of test catalog will appear. Under the Structure. • Select the Test Catalog created in step 8 and click on Change (F6) icon from the application toolbar. • In Test Catalog Header Data section give Title.

Click on F4. select the Special Variant radio button. Give the value from the dropdown list as E eCATT Test Configuration. click on F4 help. so all the scripts. If in case the scripts are selected which don’t have common variant names then only the variants of first test case appears in the list. which will be specific to this particular location. o • • Without Variants – Only with ECATTDEFAULT. should be selected. Select the Test Configurations from the system. . In the Test Case Key. In the Variant Selection.• Select Test Catalog name and click on the button As Subnode (F5) from the application toolbar. Here we are adding the Test Configurations to the test catalog. • Insert Nodes window appears. Now in the list shown by system will show only the common variant to all the select Test Cases from step 13. So select the second radio button of Test Case. As the grouping of the scripts is on the basis of the location against which the test is carried out.

All the selected scripts along with the variant name will appear under the Test Catalog name. All Variants Excluding Default Variant – All the variants excluding ECATTDEFAULT variant. test catalog must be present in SAP Application Hierarchy. To achieve this.. o o • Select the variant for the location against which testing is carried out and press enter. • Click on Save (Ctrl+S) button from the standard toolbar. In order to use the test catalog in Test Plans.o All Variants Including Default Variant – All the variants including ECATTDEFAULT variant. which are common to all the selected test cases. Special Variants – Only for the selected variants from the list. click on button Library (Ctrl+F12) from the application toolbar or • .

• • One Information popup appears ‘ The two structures are from different mySAP components’. Give the name of Test Catalog created in step 16 in the Description field. • Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. click on Nodes (Insert Nodes F5) button from the application toolbar. One small window of Create Link appears. Select the catalog and press enter. Press Enter.click on GOTO menu -> Library. Click on (Find) Test Catalog button. . With the Test Catalog selected. The name will appear in the search help output window. The catalog will be added under the Test Catalog node.

the plan will be referred. give the name of System Data Container & Target system on which the scripts will • • . Creation Of Test Plans: • Transaction SCAT. Create Test Plan window appears. In the Template. select Application Component Hierarchy. With the Test Plan Title. This way multiple test catalogs can be prepared depending on some defined conditions like different locations against which the testing will be carried out. give the Test Plan Title.• Click on Save button from the standard toolbar. Click on the Create (F5) icon from the application toolbar. In the eCATT section. Now the catalog is present in the application hierarchy. • Click on menu Environment->Manage Test Plans. Under the Test Plan & Header Data section. These test catalogs then can be used for the preparation of test plans.

Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. This test catalog is the one whose scripts will be pulled in the test plan and then subsequently in test package of that plan. Here from this SAP Application Hierarchy. • The system will take to Crate Test Plan screen where the Test Organizer Library is displayed. Select the scripts from single or multiple Test Catalogs as . Scripts from multiple test catalogs can be taken.execute. Click on Enter. select the test catalog.

• Test Organizer – Test Package Management screen comes. Click on Create Test Package . One can prepare the Packages from this plan by some defined conditions like scripts of foreground execution. • Click on Generate (F8) button from the application toolbar. Test Plan is ready now. background execution or different tester or different target systems at execution time. Creation Of Test Package: • Select the test plan created in step 6 above. After the plan is generated save it. Click on Test Packages (Ctrl+F9) button from the application toolbar.per the requirement.

Click on Enter. The Create Test Package window for title appears.button. By this name the package will be referred always. • It will display all test catalogs under that test plan. • Once the package is prepared. select the package name and click on Status button for refresh. After selecting the scripts. click on Generate (F8) button. the right panel will show the number of scripts against that package under the Error/No Result/Ok columns. Once the refresh is done. Give the name of the package in the title. Select the scripts from the required test catalogs depending on the condition on which that package is planned. .

Test Cases can be executed at Test Catalogs level/Test Plan level or even at Test Package level. Execution Of Test Cases Series Via Test Workbench: • Test Cases can be executed via different ways at different levels in test workbench system. And finally executing these Test Packages which give the transparent picture of how the testing was planned and carried out. Then from those test catalogs preparing Test Plans depending on some defined conditions. So transaction SCAT.The package is also now ready. This way multiple packages can be prepared which will involve all the scripts of the plan in totality. Click on Test Packages (Ctrl+F9) button from the application toolbar. • The scenario depicted here is by creating a pool of test cases in Test Catalogs. From these plans again preparing Test Packages. Click on menu Environment->Manage Test Plans. Select the Test Plan. • • • • . which needs to be executed.

Then click on Automatic Test button from the application toolbar. Before the execution. Click on Enter.• Select the package. By default all the scripts under the package are selected for execution. then select the required once. o . Select the following options – o • • Error Behavior . continue with next script. One window with title ‘Start Options (eCATT Mass Start)’ will appear. System Data – Name of the system data container. the status in traffic light for each of the script will be untested. select the package. If in case all the scripts need not to be executed at a given time. Test Case Selection window appears. • For the mass execution of the complete package. which contains the Target System.S No termination.

C Continue (Continue on Any Error) Stop When .S Synchronous GUI Control Error Mode for SAPGUI . In SAPGUI section of window. select following options  o o o o Procg Mode SAPGUI . In TCD section of window.R Close Generated Sessions After REF    .o Target System – Name of the server on which the execution will happen. select N – Process in background.N Do Not Stop Close GUIs . Select the Status In TWB check box. synchronous local. Select the Log Display check box.

o Click on Execute button. the logs are taken back to test workbench and the status of traffic light will either change to green for • . the system prompts for login & password window of Target System. Once the execution is completed. Give the login details and execution of scripts will start in series. • On execute button click on Start Options window.

SAPGUI recording mode of recording is explained in detail. The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. the creation of eCATT scripts using TCD mode of recording is explained in detail. creation of Test Configuration. . In Part IV chaining. In Part II.success or red for error. Test Data Container. In Part III. the management of eCATT Scripts via Testworkbench is explained. In Part VI. In Part V. the eCATT Logs will be explained in detail & in the subsequent parts other details of eCATT will be covered. and System Data Container are explained in detail. parameterization. What Are eCATT Logs: • eCATT Logs are generated every time a test script or test configuration is executed either by SECATT or SCAT transaction.

execution mode like With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background for TCD & without user intervention for SAPGUI) etc. Import/Export/Local parameters details. variants etc. As all the system messages are stored in the logs. and displayed as a structure with nodes. Source System details. Each test script in turn may contain one or many recorded transactions. This also includes any inline ABAP code or any other eCATT commands if used. time taken for each step of automated steps as well as total execution time in seconds. Test Data container.• The log is hierarchically structured according to the test script used. • Advantages Of eCATT Logs: • eCATT log stores all the steps of the test case along with lots of other useful information about systems. • These logs help in analysis of the business process. which are generated during . executed variants details. Target System details. Each of the eCATT log shows the execution status of each of the step executed for the given test script along with necessary details like unique log ID.

So they can be maintained for the defined time frame. • The expiry date of logs can be changed. • How To Look In eCATT Log From Log ID: • Transaction SECATT. the script can be again executed and the new log will be generated. They are not necessary in this case. as Log ID is known. Remove the values from the Starter & Start date input fields. in Currt. • Click on Logs (Ctrl+F12) icon from the application toolbar. And hence the results of one regression testing can be used as reference for next regression testing.execution of the given script. After necessary corrections. In case log ID is not known & • . The success. So it becomes much more user friendly to analyze. Input field give the log ID. • Under the Log Selection section. system prompts the relevant messages. This helps in rollout projects. it becomes simple to analyze the result set. error or execution status is depicted by colors in logs. which help in understanding of the process that has gone wrong. In case of errors. Procedure No.

one wants to analyze all the logs generated on a particular date by a particular tester then give these input fields. the combination of other input fields becomes useful. Expiry date. By click on Expand All Nodes (F5) button. Other input fields include Test Configuration. In absence of eCATT Log ID. which in this case are not mandatory. Test Script. eCATT Log with the Log ID in title appears in next window. . • • Click on Execute (F8) button. all the nodes will be drilled down till end. Different input combinations can be made for eCATT logs depending on what kind of input is in hand.

And the detailed view of log will be displayed. Menu Environment -> Manage Test Plan. The execution status of the package is in terms of traffic lights under the Status column with • . Give the name of test plan. Click on Status Analysis button from the application toolbar. • • • Transaction SCAT. logs from test package will be analyzed here. How To Look Into eCATT Logs From Test Workbench: • With the assumption that test package is executed.

Click on Log (Shift+F1) button from the application toolbar. . Status Maintenance window appears.description under Status Text column. • Click on the traffic light of the required test configuration. After click. Status of execution etc. This window contains Test Case details.

Analysis Of eCATT Logs: • Top Level Information: The first line of the log displays the log identification number.• Detailed eCATT Log is displayed against that test configuration with unique log ID. . other information is also displayed: o The number of test configurations executed. (This information appears if the execution happens from the test workbench via SCAT). Depending on the tests.

Client.e. Release. ApplicationServer. User.o The name of the test script or test configuration executed via SECATT. description & execution time taken by the complete script is displayed in seconds. Database System. The status of execution of scripts is depicted by colors either green background color for success or red . the test script details like test script name. o o • After the top line following information is displayed in one line: System. Language. Operating System. The system Data Container as well as Test Data container are also displayed. The execution mode i. • Script Details: After the detailed systems information. With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background for TCD & without user intervention for SAPGUI) . version. Time of execution. Date of exeuction. The version number of the test script.

Display Comments. • Comments. the RFC destination is displayed and the detailed component information is shown below it. Duration. Successful Script Script in Error • Maintenance System: If a test script has a maintenance system. IF-ENDIF structure: To display comments. duration time in seconds in the log.background color for error. Select the check boxes of Disp. click on Settings…(Shift+F7) icon from the application toolbar. . Press Enter. Duration.

• Errors. duration time will be displayed. If the IF-ENDIF structure is executed. Error message is immediately displayed after that step and even after the . If a node is marked as containing an error. Multiple Variants. Messages. it is displayed with green color otherwise not. Navigation: o Error: If a script contains one or more errors. the node above it in the hierarchy is also marked as containing an error with red color.The log with the comments. it is in error with background red color.

script details. one can navigate to the test script. o Navigation: By clicking on the hyperlinks from the log. o Messages: Messages during the execution are displayed in the log under messages node. system data or test data etc. Messages can also be seen in XML data. When a recorded transaction uses a print function that sends a document to the spool. o Multiple Variants: Script can be executed using multiple variants. The variant names appear one after the other in the log. . a message is recorded in the log.

• XML Data: XML data is generated when testing function modules and transactions. Here is an extract of XML-DATA-01 from the log shown above. click the hyperlink name of the XML data in the log. . To view XML data. How To Change Expiry Dates/Deletion/Archiving Of eCATT Logs: • Transaction SECATT.

Click on Execute (F8) button. Select all the logs by clicking on Select All icon on left top of the grid. end date. • Logs from the selection screen are displayed in the tabular format with the details like status. Click on Change Expiry Date (Ctrl+F8) button from the application • .• Click on Logs (Ctrl+F12) icon from the application toolbar. in Currt. start date. test script. Input field give the log IDs by clicking on the Multiple Selection button. Procedure No. test configuration etc. window appears. • • On the Log Selection window. Click on Execute (F8) button. starter. Under the Log Selection section. the multiple selection button will show green status for having multiple values of Log Ids. Multiple Selections For Currt. Procedure No. expiry date. The entire log IDs should be given here.

• Date change window appears. • When the expiry date reaches for any log. Also the logs can be archived. the log is automatically deleted. Set the required expiry dates to the logs. If the automatic deletion is not required. explicitly also the log can be deleted from the menu Log Selection>Delete (Shift+F2). Click on Enter. Select the log from the list. The Expiry date will change for the all the selected logs to this new value. from the menu Log Selection -> • .toolbar.

tables are displayed for eCATT Log. • • On the Tables & Archiving Objects window.Archiving On/Off (Ctrl+F7). in the Tables from which data is archived section. Click on Database Tables button from the application toolbar. How To Find Database Tables For eCATT Logs: • Transaction SARA. • In the Object Name input field give value ECATT_LOG. These are the tables in which the log is stored in the .

the creation of eCATT scripts using TCD mode of recording is explained in detail. the eCATT Logs are explained in detail. In Part II. tips & l inks of eCATT will be covered. In the subsequent Part. Delete. the management of eCATT Scripts via Testworkbench is explained. Rename. In Part IV chaining.database. creation of eCATT Scripts using Non-User Interface mode will be explained along with the details of Copy. The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. Test Data Container. parameterization. Sapna Modi is a Software Engineer. In Part VII. the creation of eCATT Scripts using SAPGUI mode is explained in detail. In Part VI. In the Part III. Key Features Of Non-User Interface Recording Mode: . and System Data Container are explained in detail. creation of Test Configuration. Upload and Download of eCATT objects. In Part V. Select the All Tables radio button.

In the Attributes ->General Data Tab. The Version input by default is with value 1. • • • . the value of the component will be BC-TWB-TST-ECA for eCATT.• The non-user interface can be used for testing back-end R/3-specific modules. It is fast. recording R/3 server) should be mentioned. It should be the preferred driver for interface tests in the mySAP environment. such as function modules and BAPIs. In the Attributes ->General Data Tab. • • Steps For Recording Using Non-User Interface Recording Mode: • Transaction SECATT. • Give the name of the Test Script(TS) in Test Script input box. efficient. Click on the Pattern (Ctrl+F6) button from the application toolbar. the values of the SystemDataContainer should be given which contains all target systems with RFCs on which the script will be either executed or recorded & in the TargetSystem the name of target system (e.g. and suitable for load testing.

Click on enter. The Interface name will automatically appear (E. Here BAPI_MATERIAL_SAVEDATA is used).g. On the right side. the command interface will open in a window. Click on enter. The command interface will have all the IMPORT/EXPORT/TABLES/EXCEPTIONS parameter . In the Function Module give the name of the function module/BAPI.• From the Command dropdown. select FUN. • Double click on the Command Interface (e. which needs to be tested. BAPI_MATERIAL_SAVEDATA_1) from this FUN syntax in the command editor.g. The FUN with the function module/BAPI name along with the command interface will be inserted into command editor.

The declaration of these parameters will happen at the Parameter List as either Import/Export/variable. like the other recording modes. all the import parameters. export parameters. • Under the IMPORTING/EXPORTING/TABLES/EXCEPTIONS node. similar ways values will be passed here in terms of Parameterization. These parameters can be parameterized. can be captured from the . The output message variables. If the function module or BAPIs are called in the ABAP Program then the way the values are passed to those parameters. tables & the exceptions belonging to that function module/BAPI are present.of the given function module/BAPI.

Before this a unique material number is generated by system using another BAPI. This is written in ABAP-ENDABAP block. BAPI is used for Material create and saving this data.Exporting node. So the variable is used. As import and export parameters cannot be used in inline ABAP code. • In the current example. • All the parameters needed for the execution of the function module/BAPI will be declared in parameter list and then parameterized. After the number is generated. This variable is then passed as import parameter to . this newly generated number is assigned to a variable.

The script is ready for execution. There is no specific Start Options mode available for Non-User Interface mode at execution time.BAPI. And if there is any error in recording of the transaction and its replay then error log with details will appear. which is to be tested via this recording. then success log will appear. • Once the parameterization is done. • If the recording is error free. It always executes in Background mode. .

Export parameter along with the execution mode and time taken for each of the individual step and complete execution. It shows Import.• Analyze the generated log (weblog Part VI). Following is the log generated for the example mentioned here. .

. It shows the results also. one can go ahead with the preparation of TD. The Importing/Exporting parameters along with the message generated. TC for the TS. • After the confirmation of error free recording. • The function module/BAPI is also shown in log.• Inline ABAP code is also shown in the log.

(Weblog Part V). Add multiple variants. Test Configuration. Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. Test Data is independent of test script. In SECATT transaction using Test Configuration (TC). Rename & Delete eCATT Objects: • One can copy all the eCATT Object i.e. . (Weblog Part IV). add all the parameters from the test script. the TD & TS can be linked together on the Configuration tab. The TC is used in managing the scripts in plans/packages using SCAT transaction. On the Variants tab. (Weblog Part IV). • • • How To Copy. • Transaction SECATT.• In SECATT transaction using Test Data (TD). Hence can be reused wherever required. Test Script with Version. This will appear as ECATTDEFAULT in the Variants tab. (Weblog Part IV). as per requirement in the Variants tab. using Variant Maintenance Assistant required variants values from TD could be linked to TC. variants can be prepared for the recorded test script. In the Parameters tab. Test Data & System Data.

The new test configuration will be ready. For Test Configuration copy. give the new names and click on Copy button. System Data Copy- . give the name of the new TC and click on Copy button.• Click on Copy Object (Ctrl+F5) icon from the application toolbar. for Test Data and System Data. • Copy dialog box appears with the copy detail for the eCATT Object whose radio button was selected on SECATT. • • Similar way.

Depending on the eCATT object selected.• For copying Test Script. system gives one Version input field on Copy dialog box. Give the new name and click on Rename button. renaming can be done. Otherwise only the specified version is copied. Similar ways all other eCATT objects can be renamed. click on Rename Object (Ctrl+F6) icon from the application toolbar. the Rename dialog box will appear. On the application toolbar of SECATT transaction. The object will be renamed. • Rename eCATT Object: Similar to copying the eCATT objects. If this field is left blank then all the versions are copied to new name. .

There is no dependency on objects for deletion. all the eCATT objects can be deleted. Test Data & System data can be downloaded via SECATT transaction. If the version field is left empty. the entire linked object . Click on Yes for the deletion of object. Test Script. All the objects i.e. In case of Test Scripts deletion. These files can be further uploaded to any system. Similar way all the other eCATT objects can be deleted. Confirmation Prompt dialog box will appear. Click on Delete Object (Shift+F2) from the application toolbar of SECATT transaction. Hence the reuse of objects and their transfer amongst the R/3 system is facilitated. Meaning deletion of TC won’t affect the TD & TS inside it. Test Configuration. For a script to work successfully. How To Download eCATT Objects: • eCATT objects can be downloaded in XML & XSD format. to delete specific version mention it in the transaction. all the versions are deleted.• Deletion Of eCATT Objects: Similar to Copying & Renaming.

• • Transaction SECATT. Test Configuration & multiple Test Data containers.should be present along with it like System Data. . Menu Goto -> Reference List. Give the name of Test Configuration or Test Script or Test Data or System Data. This linking of objects can be known and the entire related object could be downloaded in one shot. which needs to be downloaded. Object Type & Object Name automatically appears depending on the selected eCATT object on SECATT screen. • • One List Of Referenced Objects screen comes.

• Click on Execute (F8) button from the application toolbar. Click on Ok. The files will be downloaded at the given . All the objects from the referenced list will be downloaded at the path given in the Browse For Folder dialog box. • Click on Download All Objects (F5). List of referenced objects will appear.

. • Downloading Individual eCATT Object: Individual objects can also be downloaded instead of the complete reference list from transaction SECATT. From the menu <eCATT Object>-> Download.destination in XML XSD format. Give the object name and click on the Display (F7) icon from the application toolbar. Similar way other eCATT objects can be individually downloaded. the given object can be downloaded.

Test Data.e. Test Configuration as well as System Data can be uploaded via SECATT transaction from the XML. Select the eCATT object. In case of Test Script.How To Upload eCATT Objects: • eCATT objects i. Select the file and click on Open button. The object will be uploaded and directly taken to SECATT window. • Select Files For Upload dialog box appears. Test Script. • • Transaction SECATT. Change eCATT objects to be uploaded window appear. The prerequisite is that both the XML & XSD files should be present in the same folder. XSD files. Menu eCATT Object -> Upload. • . the Target Version (TV) number can be given. give the target object name if not present & click on Enter.

the management of eCATT Scripts via Testworkbench is explained. In Part V. the eCATT Logs is explained in detail. parameterization. In Part IV chaining. System Data Container Upload/Download: When uploading or downloading system data containers for copying to another system. the name of an RFC destination remains unchanged in the RFC Destination field. In the Part VIII. In Part VI. Sapna Modi is a Software Engineer The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. Rename. and System Data Container are explained in detail. this name might not exist or might be that of a different RFC destination. tips & links of eCATT will be covered. In Part II. RFC destination needs to be maintained. the creation of eCATT Scripts using SAPGUI mode is explained in detail. the creation of eCATT scripts using TCD mode of recording is explained in detail. However. creation of Test Configuration. In the Part III. Delete. Upload and Download of eCATT objects. in the new system. In this case. .This way multiple objects can be uploaded. creation of eCATT Scripts using Non-User Interface mode is explained along with the details of Copy. Test Data Container. In Part VII.

On 2nd time onwards. If the recording is successful. system may prompt some error messages. Execute the script manually directly on R/3 for at least 2-3 times with the same set of data. then only go for parameterization otherwise do the corrections by rerecording if needed. without parameterization check for the errorless recording by execution. Recording will now include the extra popup. Before recording of the script via eCATT. which normally don’t come. the default user ID settings are done on the system . Make sure that before replaying those recorded eCATT scripts. After recording. warning messages. Make these screens optional in SAPGUI mode. Correct the data only for the error messages and let the warning messages & popup be as it is. This way the data is ready which gives all possible behavior of the transaction. work with the script on R/3 system directly with a given set of valid data for the entire script.Tips To Be Followed Before or During Recording: • Test case is generally a series of transactions pertaining to one business scenario. warning messages etc. Now record the script with this data. • There can be some default settings for the parameters values on the user ID by which the recording is done.

do the following setting before recording of that transaction. in the Controls section select the checkboxes of Show keys in all . always help in the successful execution of the scripts.on which the final execution will happen. o Log on to target R/3 system. Select the Options -> Expert. On any transaction. Following such prerequisites in terms of user ID settings or some behavior of transaction of first run. in same session with some default data etc. This helps in replaying the transaction successfully. o On the Expert tab. Due to following settings. click on Customizing Of Local Layout (Ctrl+F12) icon from the application toolbar. the keys will be assigned to each item in the dropdown in sorted manner and recording will happen for these keys values. • If the transaction to be recorded on R/3 involves dropdown list box.

dropdown lists & Sort items by keys. o Transaction with dropdown without keys setting – Transaction with dropdown keys settings – .

• It happens at times that the screen size reduces at the time of recording in width and height. then click on the item for further processing. • If the recording includes searching some value from ALV grid and the value is known then don’t scroll and look for the value. adding some value to the table then don’t scroll up to blank line. Use directly the Create Item icon and then add the new values. Use the TAB key till that field is . Scrolling fails at the time of replay. Once the search item is found.• If the recording includes. then don’t scroll. Use the Search icon from the ALV toolbar for searching. In such scenario if the field to be captured during recording is present somewhere at the bottom.

• Warning messages are automatically handled by TCD mode but in SAPGUI recording mode they need to be handled if they require user intervention for further processing. But in TCD screens can’t be • .g. capture the value from the generated list manually and pass it to the next recording. SAPGUI & TCD Recording Modes: • Error messages can be recorded and replayed by Only SAPGUI recording mode and NOT by TCD mode.reached. During this WAIT XXX seconds. Pressing and enter key will enable all the fields after warning message) Screens can be made Optional for execution in SAPGUI mode. Due to Scroll functionality possibility of script failure becomes high. If the recording includes a dynamically generated list and one value (which is not known until execution) from this list needs to pass to the subsequent step in recording then use foreground mode of recording for this dynamically generated list. • It is not possible to capture the value from a dynamically generated list. This optional screen will be handled automatically at runtime even if not in the screens flow. (E. Use WAIT XXX statement after its recording.

. Rather in TCD screens can be made active or deactivated in the cases where depending on some input values. SAPGUI Confirm Popup: In order to avoid the following popup for SAPGUI recording. Passing values to subsequent screens at runtime is only possible in SAPGUI and not in TCD mode. The screens sequence should be known well in advance in TCD for making any screen active or not. • Only local variables from the eCATT Parameters can be used in Inline ABAP code. the recording can be reused.made optional which may or may not occur during execution. Select the Options menu. option is available in R/3 System. • • Click on the icon with tool tip Customizing Of Local Layout (Alt+F12) in the standard toolbar on any transaction of R/3 system. Import and Export parameter are not allowed.

the interface will open.Optional (will execute only when it will be in . Change Active 'X' to 'O'. uncheck the check box of Notify when a script attaches to a running GUI.From the Options -> Scripting. which needed to make optional on the left side in the command editor. On right side. Click on Apply -> Ok. 'X' . Double click on the screen or message popup. • Making SAPGUI Screen Optional: It is possible in SAPGUI recording mode to make screens optional. The popup won’t appear onwards.Active (Compulsory will execute) 'O' . first option is Active 'X'. Under the ProcessedScreen node.

WAIT_ON_DYNPRO • . ENDABAP. IF. REFEXT. WAIT. EXIT. REFCATT. CHEVAR. RESTAB. LOG. ON_LAST_MESSAGE_CHECK. SETTAB. ENDDO. =.g. REMOTECATT. CLEAR. TCD. DO. Comments (*). MESSAGE. ENDIF. CHETAB. of eCATT Commands are *. Comments (*) and assignments (=) are exceptions to this rule. ELSE.execution flow). and inline ABAP are exceptions to this rule. eCATT Commands: • An eCATT script consists of individual eCATT commands. REF. Each command begins with a command word and ends with a period. assignments (=). FUN. • There can be several commands on the same line. ENDMESSAGE. SAPGUI. E. ABAP. SENDEXT. GETTAB. ELSEIF.

• There are examples involving these eCATT commands. • On the next screen eCATT – Search Of eCATT Commands in Test Script. in the Command input field. Finally selecting the set of data. . give the name of the eCATT Command from the F4 help. which gives maximum possible messages/popup for the given transaction. which can be found from the menu Goto-> Use Of Command. List of examples will be in the output. Key Points Can Be Followed For Successful Testing Via eCATT: • Analysis of transactions with different behaviors for different sets of data. And click on Execute (F8) button from the application toolbar.

Analyzing the behavior of transactions for the background/ foreground execution mode. Scorecard can be something like as follows - • • • • eCATT Weblog Links From SDN: . This helps for future reference of script results.• Automation along with the verification before final regression on Quality Server. which helps in preparation of data for the scripts before execution. Maintaining the results in scorecard with log IDs for each location the scripts being tested during regression on Quality. Also the transaction settings for those user IDs. Accordingly preparation of packages for background & foreground execution. Preparing the prerequisites for the regression as a whole considering the user ID settings. Preparation of variant files with details having comments on each value.

Test Configuration.sap.sap.sdn. Delete.com/irj/sdn/weblogs? blog=/pub/wlg/3464 eCATT Chaining. Creation Of Test Data. Copy.sdn.com/irj/sdn/weblogs? blog=/pub/wlg/3497 eCATT Scripts Management Via Test Workbench (Part V) https://www.sap. System Data (Part IV) https://www.• eCATT An Introduction (Part I) https://www.sap.sdn.sap.sdn. Upload & Download eCATT Objects: • • • • • • .sdn.com/irj/sdn/weblogs? blog=/pub/wlg/3489 eCATT Scripts Creation Non User Interface Mode & Rename.com/irj/sdn/weblogs? blog=/pub/wlg/3418 eCATT Scripts Creation .sdn.com/irj/sdn/weblogs? blog=/pub/wlg/3334 eCATT Scripts Creation .com/irj/sdn/weblogs? blog=/pub/wlg/3483 eCATT Logs (Part VI) https://www. Parameterization.SAPGUI Mode (Part II) https://www.sap.TCD Mode (Part II) https://www.

https://www.sdn.sap.com/irj/sdn/weblogs? blog=/pub/wlg/3519

eCATT - Creating A Test Case For WebDynpro: https://www.sdn.sap.com/irj/sdn/weblogs? blog=/pub/wlg/3154

eCATT Links From SAP Help: • Online SAP Help For eCATT: http://help.sap.com/saphelp_nw04/helpdata/en/2 0/e81c3b84e65e7be10000000a11402f/frameset. htm

TCD Parameterization: http://help.sap.com/saphelp_erp2004/helpdata/e n/b5/c5f60a2b5bc74f8ca0eef40158806c/content .htm TCD Command Interface: http://help.sap.com/saphelp_erp2004/helpdata/e n/82/fc193c66f5dc1ce10000000a11405a/frames et.htm Setting Field Values Dynamically In TCD: http://help.sap.com/saphelp_erp2004/helpdata/e n/05/33384162316532e10000000a1550b0/fram eset.htm SAPGUI Command Interface: http://help.sap.com/saphelp_erp2004/helpdata/e

n/bc/6d7290f64c11489f2c9b03458ef53f/framese t.htm

Execution Start Options: http://help.sap.com/saphelp_erp2004/helpdata/e n/bc/6d7290f64c11489f2c9b03458ef53f/framese t.htm

eCATT Links From SAP Service Marketplace: For accessing site from SAP Service Marketplace, user ID & Password is required.

eCATT Details On Service Marketplace: https://websmp204.sap-ag.de/~form/sapnet? _FRAME=CONTAINER&_OBJECT=011000358700 003012112003E eCATT Frequently Asked Questions: https://websmp104.sapag.de/~sapidb/011000358700003021722003E# availablesince eCATT Security Guide: https://websmp204.sap-ag.de/~form/sapnet? _FRAME=CONTAINER&_OBJECT=011000358700 003043282003E

Useful eCATT Links From SDN Forum: • How To Find eCATT Version: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=133916&messageID=1 501467

eCATT Error - ‘Error In Control Details: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=93680&messageID=11 18406 eCATT Error – ‘Control Data Obsolete’ Details: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=119488&messageID=1 341439 Testing Custom Report Output Using eCATT: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=116180&messageID=1 314407 eCATT - Problem With ME21/MIRO/MIGO: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=111435&messageID=1 250733 eCATT Error – Screens Smaller When Replayed & Caused Error: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=105315&messageID=1 172785 eCATT - Executing Several Variants At Once: https://www.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=102398&messageID=1 136307

sdn.sap.com/irj/sdn/thread? forumID=117&threadID=111915&messageID=1 250664 eCATT Error -GUI Recording Not Working With VA01 (RE) Return: https://www.com/irj/sdn/thread? forumID=117&threadID=102281&messageID=1 145386 eCATT – Running eCATT Scripts In Batch: https://www.com/irj/sdn/thread? • • • • • .com/irj/sdn/thread? forumID=117&threadID=95332&messageID=11 89737 eCATT – Updating Automatic Execution Result In Solution Manager: https://www.sdn.• eCATT – Creating Summary Report Based On Logs: https://www.sap.sdn.sap.com/irj/sdn/thread? forumID=117&threadID=104183&messageID=1 160394 eCATT – Which Dynpro Of Recording Corresponds To Which Screen Of Transaction: https://www.com/irj/sdn/thread? forumID=117&threadID=101100&messageID=1 120564 eCATT – SAP’s Best Practice For eCATT: https://www.sdn.sdn.sdn.sap.sap.sap.

sdn.sdn.sap.sdn.com/irj/sdn/thread? forumID=117&threadID=92276&messageID=11 09375 eCATT – SAPGUI Mode – Making Screen Optional: https://www.sdn.sap.sap.com/irj/sdn/thread? forumID=117&threadID=100727&messageID=1 114139 eCATT – Meaning Of Transactions Containing Controls (SAPGUI): https://www.com/irj/sdn/thread? forumID=117&threadID=99895&messageID=11 14172 eCATT – Workflow Testing By eCATT: https://www.sdn.sap.sap.com/irj/sdn/thread? forumID=117&threadID=100213&messageID=1 109073 .forumID=117&threadID=90723&messageID=11 18452 • eCATT – Testing eCATT Scripts In Multiple System: https://www.com/irj/sdn/thread? forumID=117&threadID=99899&messageID=11 09306 • • • • eCATT – Parameterize The Input Date As System Date: https://www.

sdn.com/irj/sdn/thread? forumID=117&threadID=88577&messageID=10 24748 eCATT Error: Problems Due To Changed Configuration & Master Data: https://www.sdn.com/irj/sdn/thread? • • • .com/irj/sdn/thread? forumID=117&threadID=93392&messageID=10 95800 New To eCATT: https://www.sap.sap.com/irj/sdn/thread? forumID=117&threadID=74987&messageID=81 1963 eCATT Error .sap.sap.com/irj/sdn/thread? forumID=117&threadID=71007&messageID=76 6225 eCATT – Uploading Data From Excel: https://www.sdn.com/irj/sdn/thread? forumID=117&threadID=76268&messageID=82 2111 • • eCATT – Security Testing Via eCATT: https://www.sdn.sap.sdn.sap.sdn.Problem In Recording ME5J/ME53N: https://www.• eCATT – Impact Of Solution Manager Version Upgrade On eCATT: https://www.

com/irj/sdn/thread? forumID=117&threadID=62605&messageID=67 7802 eCATT Error – Testing Webdynpro Logon Error: https://www.com/irj/sdn/thread? forumID=117&threadID=129928&messageID=1 454221 eCATT .sap.com/irj/sdn/thread? forumID=117&threadID=102199&messageID=1 131919 eCATT .forumID=117&threadID=71087&messageID=76 6488 • eCATT – SAPGUI Recording Queries: https://www.sdn.sap.sdn.sdn.com/irj/sdn/thread? forumID=117&threadID=125316&messageID=1 404040 eCATT Error – eCATT Not Supported In SAPGUI For JAVA: • • • • • .com/irj/sdn/thread? forumID=117&threadID=122017&messageID=1 367122 eCATT – TCD Mode – Dynamically Assigning Parameter Value – https://www.sap.Difference Between CATT & eCATT: https://www.sdn.RFC Functions In eCATT: https://www.sap.sdn.sap.

sap.com/irj/sdn/thread? forumID=117&threadID=126226&messageID=1 411441 • eCATT – Log Export RFC Function Module: https://www.sdn.com/irj/sdn/thread?forumID .https://www.sdn.sap.