ECATT

Refer links below:

http://www.sap-img.com/sap-catt.htm

http://sap.ittoolbox.com/documents/popular-q-and-a/catt-procedure-1795

http://www.thespot4sap.com/Articles/CATT.asp

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCATTOL/BCCATTOL.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCATTOL/CACATTOL.pdf

Regards.

Hi Chandra,

SAP CATT - Computer Aided Test Tool

Just sharing my experiences with CATT (although, I have not used this feature in the last 2 years or so !).

Simply, any one in SAP can use this tool as long as you can access to the tcode. I used CATT atleast in 3 different SAP modules. Typically, in SAP projects, CATT execution is a favorite task for "technical" associates. When the technical resources are either not available immediately or their plate is full with other important tasks, functional associates can simply jump into this activity, since there is no coding or programming involved. This tool has been a great gift from SAP since I am a functional person and could not do coding ! I can remember at least 30 or 40 occassions where I used CATT to get this and that done.

Below find few examples:

1. Created multiple sales orders (excess of 200) in a matter of minutes for the purpose of end user training

2. Created multiple purchase ordes (excess of 200) in a matter of minutes for the purpose of end user training

3. Created Deliveries for the sales orders in a matter of minutes for the purpose of end user training

4. Created config. entires, if the volume of records is large. I remember once I entered 900 records.

5. Extensively used in preparing the transactional data for the purpose of archiving. It worked impeccably.

6. Loading of master data (example: material groups)

Note: Upon execution of CATT, it is very possible that some records will fail, which have to be addressed manually. SAP really needs to further enhance this area of CATT because, there is no easy way of identifying the failed ones, it has to be done manually. One workaround is simply download the result into an Excel and using sort feature of Excel, identify the failed ones and deal with them manually.

With Compliment by: Ranga Rachapudi

CATT stands 4 Computer Aided Testing Tool

Although CATT is meant for as a testing tools, many SAP users have now use CATT frequently to upload vendors master data and make changes to other master record.

SAP Consultant and Abapers tends to used it for creating test data.

With CATT, you don't have to create any ABAP upload programs and this save on development time. However, you still have to spend time on data mapping into the spreadsheet format.

The transactions run without user interaction. You can check system messages and test database changes. All tests are logged.

What CATT does is record you performing the actual transaction once.

You then identify the fields that you wish to change in that view.

Then export this data to a spreadsheet to populate with the data required.

This is uploaded and executed saving you keying in the data manually.

To perform CATT, it has to be enabled in your production environment (your systems administrator should be able to do this - SCC4).

You will also need access to your development system to create the CATT script.

User Guide for Data Upload

The use of CATT is for bulk uploading of data. Although CATT is primarily a testing tool, it can be used for the mass upload of data. The way CATT works is like a real user actually inputting on the SAP screen. You prepare a set of data that are required to be input into the system and execute what you called a Test Case and CATT will do the boring task of keying for you.

Over-all procedure

The over-all procedure to upload data using CATT is as follows:

· Creation of the CATT test case & recording the sample data input.

· Download of the source file template.

· Modification of the source file.

· Upload of the data from the source file.

Details of each step are provided in the following paragraphs.

Detailed Procedure

Creation of the CATT test case:

Creation of the test case is completed as follows:

· Execute Transaction SCAT

· Name the test case. Test case name must start with “Z”. It is also good practise to include the transaction code in

the test case name (e.g. Z_IE01_UPLOAD for the upload of equipment)

· Click the “Record” button.

· Enter the transaction code (e.g. IE01)

· Continue recording the transaction. Ensure data is entered into every field that is to be used during the upload.

· Save the test case.

Download the source file template

Download of source file template is conducted in two stages as follows:

· Creation of import parameters:

· Within transaction SCAT, Double Click on the TCD line in the “Maintain Functions” screen.

· Click the Field List button (Field list is displayed).

· For every field that you wish to upload data, double click in the Column New field contents (This creates an

import parameter).

· In the Maintain Import Parameter Pop-Up:

· Delete the default value if not required.

· Press Enter

· The New field contents column now contains the character & followed by the field name (e.g. &EQART). This

is the name of the import parameter.

· Repeat this for every field (in every screen) to be uploaded.

· Back out and save the CATT test case

· Download of source file template:

· Use the path GOTO -> Variants -> Export Default

· Select path and file name (e.g. C:TEMPZ_IE01_UPLOAD.TXT)

· Click Transfer

Modify the source file

The downloaded source file template is now populated with the data that is to be uploaded. This is completed as follows:

· Using Excel, open the tab-delimited text file.

· Do not change any of the entries that already exist.

1st row contains the field names.

2nd row contains the field descriptions.

3rd row displays the default values which are set in the test case.

4th row contains a warning that changing the default values in the spreadsheet has no effect on the actual default values.

· The data to be uploaded can be entered in the spreadsheet from row 4 onwards (delete the 4th row warning &

replace with data for upload).

· Save the file as a Text file (Tab delimited).

Upload data from the source file

Uploading the data is completed as follows:

· Execute the CATT test case

· In the Execute screen:

· Set processing mode to Errors or Background (your choice).

· Set variants to External from file.

· Click the Choose button and select the file to be uploaded.

· If uploading to another client, click the Remote execution button and select the RFC connection to the required client.

· If uploading to the current client, click the execute button.

kindly reward points if found helpful.

cheers,

Hema.

Hi Chandra, also read this.

eCATT is extended Computer Aided Test Tool and used to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java. In order to offer a complete test solution that covers other GUIs, eCATT has interfaces to third party tools.

Implementation Considerations:

Test cases usually make database changes. Therefore, you should not normally run them in productive systems.

In general, do not use eCATT to manipulate data in a productive system: eCATT is a test tool. Instead, use techniques such as Batch Input.

eCATT can be used with the Test Workbench.

You can migrate test cases from Computer Aided Test Tool (CATT) to take advantage of the better features of eCATT.

eCATT is also integrated with the Object Navigator (SE80).

Features:

1) Test transactions, reports, and scenarios

2) Call BAPIs and function modules

3) Test remote systems

4) Check authorizations (user profiles)

5) Test updates (database, applications, GUI)

6) Test the effect of changes to customizing settings

7) Check system messages

Constraints:

eCATT runs in a system based on SAP Web Application Server 6.20 or higher. However, you can use this system to test systems with Release 4.6C or higher.

And,

eCATT provides a environment for developing functional tests. Rather than create a single object that defines every aspect of a test, eCATT has four separate object types. The first three form the building blocks of a test, and the fourth combines the others into a complete test case. The following graphic summarizes the development process and how the different eCATT objects fit into that process.

The process is as follows:

1. Define what you want to test within the scope of your project and make sure that the test system and the systems to be tested are prepared for use with eCATT.

2. Create a system data container in which you map out the system landscape for the project. Without a system data container, you cannot write test scripts that access other systems.

3. Create the test scripts themselves.

4. Consider the data that you will need to run the tests and arrange it in test data containers to allow the maximum degree of reuse and to eliminate as much redundancy as possible.

5. Assemble the test configurations from the other eCATT objects.

6. Test configurations can be assigned to test catalogs and test plans within the Test Workbench. The configurations can then be assigned to individual users for testing.

An executed test configuration produces its results in the form of a log. Not only does the log provide a simple pass or fail result for the complete test, it also provides a permanent and detailed record of the test.

For furhter information you can refer to help provided by SAP which is very good source of information to start with eCATT scripting...

path: Help-->Application Help

cheers,

Hema.