Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

hi about CATT

Former Member
0 Kudos

hi Experts,

can anybody pls tell me about the CATT

3 REPLIES 3

Former Member
0 Kudos

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

Usually from what I have seen CATT is not used for regular transactions in the productive environment. I have only seen LSMW used for the transfer of data from non-SAP systems to SAP systems. It guides you thru your data migration tasks.

http://help.sap.com/saphelp_nw04/helpdata/en/d7/e21017408e11d1896b0000e8322d00/content.htm

- SAP advise not to use CATT in productive systems.

http://www.planetsap.com/basis1.htm

- Start of CATT processes allowed: This option determines whether you want to allow the CATT (Computer Aided Test Tool) process in the client or not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different functionality of the SAP system. To run the CATT tool you can execute transaction SCAT. CATT process changes the database extensively and requires lot of system resources. So we recommend not to chose this option if you are in the production environment.

There has also been some comments on LSMW on this forum:

https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/t...

- The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.

My 2 cent would be why not develop a solution using Batch Input, BAPI etc?

Check these links

http://help.sap.com/saphelp_nw04/helpdata/en/48/c521a8f6ec11d2bdde080009b4534c/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/ae/410b37233f7c6fe10000009b38f936/frameset.htm

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

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

h_senden2
Active Contributor
0 Kudos

You can use the search function of this forum : a lot of threads will be found.

regards,

Hans

Please reward all helpful answers !!!!!

Former Member
0 Kudos

hi ...

go thru the below details...

reward points if it is useful...

CATT: Enhanced Mode (BC-CAT-TOL)

http://help.sap.com/saphelp_nw04/helpdata/en/ae/410b37233f7c6fe10000009b38f936/frameset.htm

Use

The Test Workbench contains the Computer Aided Test Tool (CATT) to create manual or automatic test cases.

Manual test cases

Manual test cases are most useful for acceptance tests. They are descriptions of tests which a tester must perform manually on the system.

Automatic test cases

Automatic test cases are performed by the R/3 System without user dialog, and are most useful for function tests. The result of an automatic test case is a detailed log which documents the test. The use of automatic tests can considerably reduce the test effort.

Test cases test individual transactions or whole business transactions. Test cases are constructed modularly, to minimize the creation and maintenance effort, above all for business transactions.

The procedure for testing one transaction or function is described in test modules. The creation of test modules is greatly simplified by the CATT recording functionality.

Test procedures can be constructed from the test modules. Test modules are referred to and linked in the test procedure.

In modular test procedures:

n test modules can be reused

n changes to test modules are immediately effective in the test procedures which use them.

Simple test case creation

The transaction test procedure is recorded with a transaction recorder for the test module. The creator runs the application as in normal dialog operation. At the end of the transaction, you go back to CATT.

You can make test cases flexible by subsequently replacing the values input when recording by parameters.

You can store frequently used parameter settings in variants which you use in tests.

This functionality has been available since 4.6 in an additional CATT maintenance mode which can be used by users without technical background knowledge.

Implementation notes

Test cases usually make R/3 System database changes, so they should not run in the productive system. To control this centrally, the client table maintenance has a flag which allows tests to be run in the system.

Authorizations are also checked in CATT.

Integration

The ABAP Workbench infrastructure provides general functions such as correction and transport, the Repository information system, and multi-lingual applications.

In addition, it guarantees the correctness of a test run by updating synchronously, thereby explicitly refreshing the table buffer. This is especially important for transaction chains, where transactions use the results of previously executed transactions.

You can also test processes from one central R/3 system in a different R/3 or R/2 satellite system. The test procedure runs in the central R/3 system and controls the transactions via Remote Function Call (RFC) in the satellite systems.

The CATT logs created contain all information relevant for the test run and are stored centrally in the database of the executing R/3 system.

Functions

CATT can:

• test transactions

• check system messages

• check authorizations (user profiles)

• testing results and database updates

• setup customizing tables

• test the effect of customizing setting changes

These processes are less suited for CATT:

• lists and display results

• menu paths

• Online help (F1, F4)

• editor functions

Restrictions

You cannot use CATT for the following transaction types:

• Transactions that contain the statement LEAVE TO TRANSACTION

SAP CATT - Computer Aided Test Tool

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

• 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:\TEMP\Z_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.

SAP users use CATT frequently to upload master data or to make changes to master data records. SAP Consultants and Abapers tend to used it for creating test data. The transactions run without user interaction. You can check system messages and test database changes. All tests are logged. The CATT records your keystrokes while performing the actual transaction. 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.

The process of uploading data with a CATT

Activate CATT in your client

• In transaction code SCC4 - click the change button

• Double click on the client number

• In the Restriction section, tick Allows CATT processes to be started.

Upload data using CATT

1. Create Import variant for the fields you need

• Transaction SCAT

• Goto Parameters

• Create Import Variant

• Goto Variant -> Edit

• Goto Variant -> Fast entry or F9

• Duplicate 01

2. To change the MRP Group for a list of Material

Assuming that I want to change the MRP Group for a list of Material.

My text files should look something like this:

[Variant ID] [Variant Text] &ZDISGR &ZMATNR

--> Parameter texts MRP group Material

--> Default Values M1 A001

      • Changes to the default values displayed above not effective

#01 M1 A001

#02 '' A002

#03 M1 A003

Note : '' denotes a blank in the field. e.g. Material A002 MRP group will be replaced by a blank.

3. Configure the recorded entry fields to read from the imported text file data

• In the CATT : Maintain functions test case Screen

• Double click on the Object Name

• Double click on the screen number with your desired fields

• Park the cursor on the fields

• Click Edit -> Details

• Fill in the Parameters Name and Field Contents

• Finish Save it.

• Assign your text file data.

• In the CATT : Execute test case Screen

• Click External from file and choose your text file

• CATT will now read from your text file and update whatever data you have specified.

Summary:

How can I use the CATT procedure?

Full Article:

Disclaimer: Contents are not reviewed for correctness and are not endorsed or recommended by ITtoolbox or any vendor. FAQ contents include summarized information from ITtoolbox SAP-R3-Log discussion unless otherwise noted.

1) Adapted from response by Pat on Fri, 12 Apr 2002

http://Groups.ITtoolbox.com/archives/archives.asp?l=sap-r3-log&i=84548

CATTs are very useful for creating mass transactions. I use them when I don't have an abap programmer available to write a BDC.

I actually use CATTs to load inventory, change material type, extending views, change valuation, creating master data for storage bins in WM. You name it, a CATT can be used to create the transaction. It's kind of hard to use for BOM's and Routings but not impossible.

Think of it like a macro.

2) Adapted from response by Anja on Fri, 12 Apr 2002

http://Groups.ITtoolbox.com/archives/archives.asp?l=sap-r3-log&i=84509

Transaction SCAT

1. Record your transaction

2. Save the CATT

3. Go into your recorded CATT Procedure and edit the parameters - you set these per SCREEN that you have visited. Double click on the screen number - you will get the screen layout. Place your cursor on a field and mark it as "input", "constant",...

4. Save again

5. If you have input parameters, you can prepare your input file in Excel. Display your parameters. The first ROW in Excel contains the technical description of the parameter. The second row in Excel contains the parameter description the third row contains a default value (this record is therefore NOT uploaded in the CATT) from the 4th row onwards, you will upload the data.

6. Save the Excel file as

7. Run the CATT (choose the processing you like, point it at the text tab delimited file) and go.

3) Adapted from response by Chris on Fri, 12 Apr 2002

http://Groups.ITtoolbox.com/archives/archives.asp?l=sap-r3-log&i=84720

If you really want to get into CATT, try the book Testing SAP R/3 Systems; Authors: Gerhard Oberniebermaier / Marcus Geiss; yr: 2000; Pearson Education, LTD. It compliments relatively good documentation that SAP provides in the Application Help area.

More information:

More information on SAP R/3 Logistics is available in the SAP-R3-Log discussion group. Enter a topic or subject and click the search button for detailed results.

SAP CATT (Computer Aided Test Tool) Tutorial Hints and Tips

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.

SAP CATT Books

Testing SAP(R) R/3(R) Systems: Using the Computer Aided Test Tool

CATT activation

Activate CATT in your client