Que

[Former Member]

Hi,

1. What is the tool you are using for testing purposes in your project?

2. What is the landscape you are following, which one you prefer to test functional module level changes?

3. Could you explain about sales deals?

4. What is Task and how to create the tasks and how to release that?

Thanks

[Former Member]

hi

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.

________________________________________

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:\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.

/people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i

/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii

/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii

/people/sapna.modi/blog/2006/04/18/ecatt-logs-part-vi

http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/12/6efc3f8fc2c542e10000000a1550b0/content.htm

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

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

Role of sap Consultant in Testing

http://www.sap-img.com/general/role-of-sap-consultant-in-testing.htm

http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm

Creating Sales Deals

http://help.sap.com/erp2005_ehp_02/helpdata/en/93/74340e546011d1a7020000e829fd11/frameset.htm

Creating Condition rtecords for sales deals

http://help.sap.com/erp2005_ehp_02/helpdata/en/93/74341b546011d1a7020000e829fd11/frameset.htm

Promotional Pricing Agreements:

http://help.sap.com/erp2005_ehp_02/helpdata/en/93/743401546011d1a7020000e829fd11/frameset.htm

System Landscape

http://help.sap.com/erp2005_ehp_02/helpdata/en/93/743401546011d1a7020000e829fd11/frameset.htm

Transport and Change Managemet

http://help.sap.com/erp2005_ehp_02/helpdata/en/b9/8e80420267c353e10000000a1550b0/frameset.htm

Copying the Master Repository

http://help.sap.com/erp2005_ehp_02/helpdata/en/1c/7c01ea0f73e646921e1e140379328c/frameset.htm

Creating Task List

http://help.sap.com/erp2005_ehp_02/helpdata/en/0d/1d3c377d190718e10000009b38f936/frameset.htm

Creating Standard Task

http://help.sap.com/erp2005_ehp_02/helpdata/en/04/92717b46f311d189470000e829fbbd/frameset.htm

Implementing Task specific customization

http://help.sap.com/erp2005_ehp_02/helpdata/en/32/b5c037e98911d1a9720000e8a6f09e/frameset.htm

Maintaining Task Lists

http://help.sap.com/erp2005_ehp_02/helpdata/en/60/a996dfc8e111d386d6006008dc11b8/frameset.htm

Creating Maintanence Task List

http://help.sap.com/erp2005_ehp_02/helpdata/en/c0/04c9734ebb11d189110000e8322f96/frameset.htm

Standard Task TS20000004 (PMO Order Created)

http://help.sap.com/erp2005_ehp_02/helpdata/en/23/fab7dfa20511d194e500a0c93033d8/frameset.htm

Reward if USeful

Thanx & Regards.

Naren..

[Former Member]

1.mercurey

2.Sandbox env. for trial and error

- Development env. for actaully creating transports(CTS)

- - Prod. env. the actual production system

you will be doing the testing in quility server

3.A sales deal defines a marketing deal for a certain product. Depending on the setting, it can be allocated to a higher-level promotion.

Special condition records can be allocated to a sales deal. If relevant, the records also contain the number of the promotion allocated to the sales deal.

The control of sales deals includes the following options in Customizing:

Define agreement types for sales deals

The agreement type indicates the type of the sales deal, for example, whether it refers to a product or product line. The standard system contains sales deal type 0020.

Define and allocate condition type groups

A condition type group defines a group of condition types and condition tables which can be used together in the sales deal. Using the condition type group, it is possible to deal with individual products differently in a sales deal and, for example, to grant discounts specific to a customer or material.

Actions

Proceed as follows to define your own sales deals:

1. Create an agreement type by specifying a numeric key with a maximum of four digits and a description for the agreement type.

2. Specify the different control data on the detail screen of the agreement type (for example, validity period as default value, overview screen). In the agreement hierarchy, specify whether an allocation to a promotion may, can or must be made.

3.

4. Note

5. Further down in the Pricing chapter in Overviews you can also select a certain overview for sales deals as the default screen for maintenance of master data. For example, you can define an overview that should only be displayed for maintaining payment conditions for certain condition records.

4.The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.

Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.

The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.