Skip to Content
What Is eCATT?
eCATT is a SAP Testing Tool, which can be used to automate & test business scenarios in R/3. One can create and execute the eCATT scripts based on business processes mapped in R/3. These scripts can be then tested before go live to Production server. If needed eCATT can be used in production server also provided exact functionality of its usage should be known. After testing, eCATT generates a detailed log depending on the processes executed. If the testing is smooth with success mode, this means the business scenarios mapped in R/3 system are correct. And if the test results in error than one can analyze the problems from the generated error log. Thus helps in analyzing the error.
What Are The Various Ways Of Doing Testing?
Testing can be done by various ways like Manually, using CATT etc.
Why To Use eCATT?
  • CATT will be no longer supported for the creation of new development. So those using CATT are forced to update to use eCATT. Comparative to manual testing, the following are advantages of using eCATT –
  • Due to automation, testing time is reduced to a large extent.
  • Due to automation, less manpower is required for testing. This helps financially.
  • Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
  • Proved to be extremely useful in Rollout projects.
eCATT Prequisites:
Web Application Server (WAS) 6.20 or more.
SAPGUI 6.20 or more.
R/3 4.6C or more. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.7.

Before creating Test Scripts using eCATT, some system settings need to be done –

  • Maintaining Table T000
    • Start transaction SM31, Maintain Table Views.
    • In the Table/View field, enter T000.
    • Choose Maintain.
    • In the Change View Clients, Overview screen, select the relevant client and choose.
    • In the Restrictions when starting CATT and eCATT field, select an entry that allows eCATT.
    • image
  • Enabling Scripting at the front End. (Check whether SAP GUI Scripting component is installed. There is an option for installing this component when installing the SAP GUI.)
    • On any screen, choose Customizing of local layout from the Standard Toolbar.
    • Choose Options.
    • Choose the Scripting tab.
    • Select Enable Scripting.
    • Choose Apply.
    • image
  • Enabling Scripting on application server.
    • Start transaction RZ11.
    • On the Maintain Profile Parameters screen, enter sapgui/user_scripting.
    • Choose Display.
    • In the Display Profile Parameter Attributes screen, choose Change value from Application Toolbar.
    • Enter TRUE in the New value field.
    • image
  • The R/3 users executing eCATT scripts should have RFC authorizations.
Features Available In eCATT:
  • Test transactions and reports.
  • Test remote systems.
  • Check authorizations (user profiles).
  • Test database updates.
  • Set up customizing tables.
  • Test the effect of changes to customizing settings.
  • Perform load testing.
  • Check system messages.
  • Call BAPIs and function modules.
  • Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
  • Supports CATT migration to eCATT.
  • All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
  • eCATT Objects can easily download & upload in XML with XSD format.
  • There can be several versions of Test Scripts, which allows different implementations with different releases.
  • The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
Ways Of Doing Testing In eCATT:
eCATT enables to test all mySAP applications, including those running outside of SAP GUI for Windows and SAP GUI for Java. 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, Interfaces testing in mySAP environment, load testing.
  • TCD:
    Suitable for testing transactions (especially who don’t involve activex controls), load testing. Doesn’t require GUI for playback, so offers maximum speed for testing.
  • SAPGUI Scripting:
    Suitable for testing transactions, who involve activex controls. Requires GUI for playback & hence very slow. Not suitable for load testing.
  • Interface To External Tools:
    External products, which are certified against BC-eCATT Interface, can be tested who run under GUIs (Other than SAP GUI for Windows & SAP GUI for JAVA) using eCATT.
Transaction For Using eCATT:
  • Choose SAP menu-> Test->Test Workbench->CATT->Extended CATT.
  • Transaction code – SECATT.
Editors Available In eCATT From SECATT Transaction:
  • Test Configuration Editor:
    Used to maintain Test Configuration object. Test Configuration data object contains set of reference to a Test Script, System Data Container & several Test Data Containers. It contains all the information necessary to run an automatic test without further user interaction.

  • Test Script Editor:
    Used to create & maintain Test Scripts. There are some recording functions available in this editor. Test Script Editor has following areas:

    • Application Toolbar.
    • Information Area
    • Editor Tab –
      • Parameter List
      • Command Editor
      • Structure Editor
    • Attribute Tab

    Test script data object contains an executable script & an interface for data transfer.
    image

  • Test Data Editor:
    Used to create & maintain the Test Data Containers. Test Data Containers are the data objects, which contain a set of parameters that can be maintained independently of a test script. Parameters can be ABAP simple types, structures, or tables.
  • System Data Editor:
    Used to create & maintain the System Data Containers. System Data Containers are the data objects, which identify instances of SAP systems. They can be maintained independently of the test script like Test Data Containers.
To report this post you need to login first.

35 Comments

You must be Logged on to comment or reply to a post.

  1. Balaji Shinde
    I had the glance of this article, too good, very informative & excellent work, It seems that you have put in lot of hard work.
    Keep it up, keep the tempo on all the time to add the study material to the knowledge Bank.

    Best of Luck for future articles.

    Balaji Shinde.

    (0) 
  2. Amarendar Kumar
    Let me first have few words of appreciation for the efforts you have put on in compiling all the information at one place. The article is too good because good is no better these days, very informative & excellent work.
    Keep it up

    Hope to read more such articles in near future.
    Amarendar Kumar

    (0) 
  3. M V
    Sincere and dedicated efforts!!! This article is very informative and useful. Even a layman can use this article to understand eCATT. The flow of the information throughout the article is very nice. The author has taken lot of efforts to explain difficult concept in a simple manner.

    Thanks for such a nice article…Keep it up!!!

    Regards,
    Mangesh Vingkar

    (0) 
  4. jigs d
    Hi sapna,
      Its really nice that u have posted so many blogs for eCATT. All are very helpful to understand eCATT.

    Keep it up.
    Thanks,
    Jigs

    (0) 
  5. Giridhargopal H
    Hi,
    I went thro all the weblogs posted by you on ecatt. It is very much helpful. I am stuck at one of the step in recording in SAPGUI.
    Request your help in this regard.
    The issue is how to handle ecatt recording for the HTML control. I am recording the co60 , (PI sheet cockpit). I am doing this recording thro SAPGUI mode.

    (0) 
    1. Sapna Modi Post author
      Hello Giridhargopal,

      If this transaction co60 interacts with web or is on web using some HTML controls then eCATT can’t record it. For web based transactions or related Mercury is the recording tool. Once the scripts are recorded in Mercury, they can link to SAP via eCATT.

      Hope this helps.

      Regards,
      Sapna N. Modi

      (0) 
  6. Anonymous
    Hi Sapna,

         This is one of the best articles i have seen on eCATT. Keep up the good work.

    Regards,
    Sachin

    (0) 
  7. Bianca Bill
    Hallo Sapna,
    I’ve read all 4 sections of your eCATT introduction and I’m really impressed by your work. It’s easy to understand and to follow by
    Thank you so much for your effort – it’s highly appreciated. Good luck for your further career
    (0) 
  8. Prabhu Shankar C
    Hi Sapna ,
              It was a great write-up about eCATT, very useful to functional consultants like me…keep up the good work.. Thanx…

    Prabhu

    (0) 
  9. Sandeep Gupta
    eCATT can be used to do customizing. I suppose this is done using BC sets. Is anyone aware as to how to create ecatt scripts for customizing, using BC sets?
    (0) 
  10. Sampath Eggadi
    Hi Swapna,

    I am running a test configuration with test script where in TCD is defined on F-28 for customer line items payment posting. I am executing this test config using external variants.

    After execution if I see the log, execution is terminated if the first record is an erroneous one and not proceeding further with next records in the input file. Execution ended abruptly here after first record got into error.

    But if I use ‘ON_LAST_MESSAGE_CHECK ( * )’ command all the records are getting processed but log is not displayed properly.

    Even if a record is not posted and was erred. Still log is indicated in green and perceived as successful if we do not expand the node.

    Code in the script is as below.
    ****************************************
      ON_LAST_MESSAGE_CHECK ( * ).

    * TCD Transaction /////////////////////.
      TCD ( F-28 , F_1 ).

      LOG ( &MSG ).
    ****************************************

    Hoping for your kind attention and solution.

    Regards
    Sampath

    (0) 
  11. Anonymous
    This is a good blog.
    However, I do NOT see SM4.0(or SM7.0) is mentioned here. Why?
    Thanks!
    (0) 
  12. Axel Arnold Bangert
    Hi Sapna,
    dom you perhaps know someting about the IDES training data configuration via scat skripts which you can find under scat. There are for example zt_SAP01 and so on.

    I installed an IDES ERP ECC6.0 SP2 traing system, but I can’t get the full IDES Training data in it via the scat scripts. There must be a certain “trick” for it.
    I already searched the installation guides etc. buit I can’t find anything about it.

    The last installation step in ECC6 is:
    minimal IDES configuration.

    What I need is the ongoing configuration catt skript.

    Best regards
    Axel

    (0) 
  13. Axel Arnold Bangert
    Dear Sapna,
    I shall install
    1.     Windows Enterprise Server 2003 R2 SP2  
            64-bit
    2.     SolMan 7.0 with SPS15
    3.     SAP IDES ERP ECC6.0 SP2 (on the same
            Server)
    Is that right up to that point 3?

    4.     The question then is, how I get the full
            IDES training data into the system ECC6
    5.     Therefore I would like to get your price
            for a tutorial concerning that point 4(I
            guess that its all done with eCatt?)

    Full IDES training data means, that I have the ability to update all data for the original
    SAP training courses like TAW12-1 or SCM500 or AC100 or PLM100 and so on.

    Best regards
    Axel

    (0) 
    1. Lifeng Wu
      Axel:
      I am reading SAP material SCM510. But the data contained in SCM510 such as material T-M510A01, T-M510B01, etc., is not contained in the ECC 6 IDES system.   I would like to run eCATT to populate the data. But where do I get the data set?
      (0) 
  14. Axel Arnold Bangert

    Hi,

    SAPUSER woks with developer key 36687663221261278694 only for Z_* named programs. This works in 4.6, 4.7 and in ECC6.0 SP2 and ECC6.0 SP3.
    BCUSER woks with developer key 29671482393151224771 in the MiniSAP.

    But – those above mentioned keys do not work for function groups with S* named programs and so on.

    For there are 3 types of keys:
    1.License key (for the SAP system),
    2.Developer key (enables the user to create/modify/remove programs and developer objects) and the
    3.Program Access Key (enables a developer user to edit standard (SAP) programs (S*)).

    And I guess, that there are two kinds of type 2 (Developer keys).

    Axel Arnold Bangert Herzogenrath 2009

    Hi,

    here are some level1 developer keys for IDES (only for Z*):
    IDES : 03910972740124722739
    IDADMIN : 01117013812115625646
    SAPUSER : 36687663221261278694
    DEVELOPER : 11337534700275594978
    BOLLINGER : 26958317752423978612

    Axel Arnold Bangert Herzogenrath 2009

    Hi,

    man kann aber folgenden Trick anwenden.
    1. Man öffnet das Programm, das man bearbeiten möchte – z.B.: SAPBC400WBS_GETTING_STARTED
    2. Man kopiert dieses Programm (rechte Maustaste – “Kopieren”) nach Z_SAPBC400WBS_GETTING_STARTED
    3. Und sichert das im Paket $TMP

    Danach kann man mit dem level1 Entwickler Schlüssel alles bearbeiten und entsprechend ändern etc…..

    Beste Grüße aus Herzogenrath bei AIX LA CHAPELLE

    Axel Arnold Bangert Herzogenrath 2009

    Hi,

    here is the screenshot of that trick:

    Axel Arnold Bangert Herzogenrath 2009

    (0) 
  15. Anonymous
    Hi,

    Sapna Modi

    I am new in eCATT and  I had to prepare dems for my presentations and your articles help me a lot to prepare my demo

    Thanks & Regards
    Akhilesh Singh

    (0) 

Leave a Reply