eCATT can be used for testing and data-migration.

1. Prepare the system for using eCATT

  • Check that eCATT is configired to be allowed to run using SM04. Type SCC4 in the bottom row. This will display whether locked. If locked unlock this. You'll get a warning that this is a cross-client configuration change.
  • maintain table T000 to define whether or not test scripts can be started in a specific client. To do this enter transaction SCC4 and check section "eCATT and CATT restriction section" that eCATT is allowed

Add the correct 

Add a nam

  • run RZ11 and select parameter name sapgui/user_scripting
  • Ensure the setting are as follows:


Recording a Script

  • System/Services/eCATT/Record
  • /Tools/ABAP Workbench/ Test/Test Workbench/Test Tools
Assign a name. This must start with Y or Z or the namespace prefix in the customer namespace (other you can save it). It's recommend to add the transaction code within the name of the test script. This makes it easier to search for relevant test scripts in the future.


Press Create Object to Create the scripts. If the name already exists you'll be prompted to add a new version.

SECATT - versions

Press "Yes" to add the new version.  The name and version is displayed in the create screen

SECATT - Create

  • Add a descriptive title
  • Responsible person (default to current user)
  • Application component: in this case SD-SLS-SD or if you were creating a vendor the vendor master is in Financial Accounting/ Accounts Payabel/Basic Functions/Master Data (FI-AP-AP-MD)
SECATT Application Components


If the script is to be run on the current client then use $TMP otherwise you'll need to enter a package that supports the transport process. Then it can be used on other clients too. 


Running the eCATT Script


SSECATT-Record-Insert Statement

  • Change the Group field to ALL COMMANDS 
  • Change the Command field to TCD (Record)
  • Enter the transaction code (in this case FK01) 
  • Press enter and the interface will be populated 
  • Press enter again to confirm

The system now takes you through all screen templates of FK01  (create vendor master)

The system will start the transaction. Run manually through the transaction to record each step. When saving the system recognises that the transaction has been completed and prompt you to save. Press yes. 

For example in the ZVA01 example, the follow screen appears: 

SECATT -  change test script

Execution of the test script

 When saved the test script can be executed immediately by pressing the execute button. 
SECATT - Execute eCATT script

The following dialog appears

  • Select UI control tab and select the mode it should run in. To check the script, I normally select a "A process in foreground, Synchronous Local"