Skip to Content


The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. In Part II, the creation of eCATT scripts using TCD mode of recording is explained in detail. In Part III, SAPGUI recording mode of recording is explained in detail. In Part IV chaining, parameterization, creation of Test Configuration, Test Data Container, and System Data Container are explained in detail. In Part V, the management of eCATT Scripts via Testworkbench is explained. In Part VI, the eCATT Logs will be explained in detail & in the subsequent parts other details of eCATT will be covered.
What Are eCATT Logs:
  • eCATT Logs are generated every time a test script or test configuration is executed either by SECATT or SCAT transaction.
  • The log is hierarchically structured according to the test script used, and displayed as a structure with nodes. 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.
  • 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, executed variants details, Import/Export/Local parameters details, Target System details, Source System details, Test Data container, time taken for each step of automated steps as well as total execution time in seconds, 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.
Advantages Of eCATT Logs:
  • eCATT log stores all the steps of the test case along with lots of other useful information about systems, variants etc.
  • These logs help in analysis of the business process. As all the system messages are stored in the logs, which are generated during execution of the given script, it becomes simple to analyze the result set.
  • The expiry date of logs can be changed. So they can be maintained for the defined time frame. And hence the results of one regression testing can be used as reference for next regression testing. This helps in rollout projects.
  • In case of errors, system prompts the relevant messages, which help in understanding of the process that has gone wrong. After necessary corrections, the script can be again executed and the new log will be generated. The success, error or execution status is depicted by colors in logs. So it becomes much more user friendly to analyze.
How To Look In eCATT Log From Log ID:
  • Transaction SECATT.
  • Click on Logs (Ctrl+F12) icon from the application toolbar.
  • image
  • Under the Log Selection section, in Currt. Procedure No. Input field give the log ID.
  • Remove the values from the Starter & Start date input fields. They are not necessary in this case, as Log ID is known. In case log ID is not known & one wants to analyze all the logs generated on a particular date by a particular tester then give these input fields. Other input fields include Test Configuration, Test Script, Expiry date, which in this case are not mandatory. Different input combinations can be made for eCATT logs depending on what kind of input is in hand. In absence of eCATT Log ID, the combination of other input fields becomes useful.
  • image
  • Click on Execute (F8) button.
  • eCATT Log with the Log ID in title appears in next window. By click on Expand All Nodes (F5) button, all the nodes will be drilled down till end. And the detailed view of log will be displayed.
  • image
How To Look Into eCATT Logs From Test Workbench:
  • With the assumption that test package is executed, logs from test package will be analyzed here.
  • Transaction SCAT.
  • Menu Environment -> Manage Test Plan.
  • Give the name of test plan. Click on Status Analysis button from the application toolbar.
  • The execution status of the package is in terms of traffic lights under the Status column with description under Status Text column.
  • image
  • Click on the traffic light of the required test configuration. After click, Status Maintenance window appears. This window contains Test Case details, Status of execution etc. Click on Log (Shift+F1) button from the application toolbar.
  • image
  • Detailed eCATT Log is displayed against that test configuration with unique log ID.
  • image
Analysis Of eCATT Logs:
  • Top Level Information: The first line of the log displays the log identification number. Depending on the tests, other information is also displayed:
    • The number of test configurations executed. (This information appears if the execution happens from the test workbench via SCAT).
    • image
    • The name of the test script or test configuration executed via SECATT.
    • The version number of the test script.
    • The execution mode i.e. With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background for TCD & without user intervention for SAPGUI) .
    • image
  • After the top line following information is displayed in one line: System, Client, User, Language, Release, ApplicationServer, Operating System, Database System, Date of exeuction, Time of execution.
  • image
  • Script Details:
    After the detailed systems information, the test script details like test script name, version, description & execution time taken by the complete script is displayed in seconds. The system Data Container as well as Test Data container are also displayed. The status of execution of scripts is depicted by colors either green background color for success or red background color for error.

    Successful Script
    Script in Error

  • Maintenance System:
    If a test script has a maintenance system, the RFC destination is displayed and the detailed component information is shown below it.
  • image
  • Comments, Duration, IF-ENDIF structure:
    To display comments, duration time in seconds in the log, click on Settings…(Shift+F7) icon from the application toolbar. Select the check boxes of Disp. Duration, Display Comments. Press Enter.
    The log with the comments, duration time will be displayed. If the IF-ENDIF structure is executed, it is displayed with green color otherwise not. image
  • Errors, Multiple Variants, Messages, Navigation:
    • Error: If a script contains one or more errors, it is in error with background red color. If a node is marked as containing an error, the node above it in the hierarchy is also marked as containing an error with red color. Error message is immediately displayed after that step and even after the script details.
    • Messages: Messages during the execution are displayed in the log under messages node. Messages can also be seen in XML data.
    • Multiple Variants: Script can be executed using multiple variants. The variant names appear one after the other in the log.
    • Navigation: By clicking on the hyperlinks from the log, one can navigate to the test script, system data or test data etc. When a recorded transaction uses a print function that sends a document to the spool, a message is recorded in the log.
  • XML Data:
    XML data is generated when testing function modules and transactions. To view XML data, click the hyperlink name of the XML data in the log.
    Here is an extract of XML-DATA-01 from the log shown above.
How To Change Expiry Dates/Deletion/Archiving Of eCATT Logs:
  • Transaction SECATT.
  • Click on Logs (Ctrl+F12) icon from the application toolbar.
  • Under the Log Selection section, in Currt. Procedure No. Input field give the log IDs by clicking on the Multiple Selection button. Multiple Selections For Currt. Procedure No. window appears. The entire log IDs should be given here. Click on Execute (F8) button.
  • image
  • On the Log Selection window, the multiple selection button will show green status for having multiple values of Log Ids. Click on Execute (F8) button.
  • image
  • Logs from the selection screen are displayed in the tabular format with the details like status, start date, end date, starter, expiry date, test script, test configuration etc.
  • Select all the logs by clicking on Select All icon on left top of the grid. Click on Change Expiry Date (Ctrl+F8) button from the application toolbar.
  • image
  • Date change window appears. Set the required expiry dates to the logs. Click on Enter. The Expiry date will change for the all the selected logs to this new value.
  • image
  • When the expiry date reaches for any log, the log is automatically deleted. If the automatic deletion is not required, explicitly also the log can be deleted from the menu Log Selection->Delete (Shift+F2).
  • Also the logs can be archived. Select the log from the list, from the menu Log Selection -> Archiving On/Off (Ctrl+F7).
  • image
How To Find Database Tables For eCATT Logs:
  • Transaction SARA.
  • In the Object Name input field give value ECATT_LOG.
  • Click on Database Tables button from the application toolbar.
  • image
  • On the Tables & Archiving Objects window, in the Tables from which data is archived section, tables are displayed for eCATT Log. These are the tables in which the log is stored in the database. Select the All Tables radio button.
  • image
1 Comment
You must be Logged on to comment or reply to a post.
  • Every blog u had given is clear but if it can be mentioned in particular way that even a functional guy can also understand, for each application.

    as per the links u mentioned little bit confusion is there that which particular link can be reffere at which point.

    if u upload the details in such a way that if this is an error then the solution is this.

    that would be help ful for all.