RWD Info Pak Template -...

Title: Using the CATT toolCategory 1 : HR Team LeadersCategory 2 : HR Team Leaders

Work Instruction

Using the CATT tool SCAT

PurposeThe CATT tool enables a user to record and save their screen actions in SAP and then replay these generic actions back at a later time.

TriggerPerform this procedure when you wish to:-

Create scripts for use in testing common transactions - e.g. to test after application of patches, OSS notes etc.

Create scripts for use in mass uploads of data - e.g. as an alternative to mass data entry, batch processing. An example would be repeating New Starter actions for a number of new employees.

Prerequisites

Appropriate access to the DEV (test) client.

Some intermediate knowledge of Microsoft Excel. You will need to know how to import text files into Excel and save a spreadsheet back to a text file format.

Menu PathUse the following menu path to begin this transaction:

Select SAP standard menu > Tools > ABAP Workbench > Test > Test Workbench > CATT Extended

Transaction CodeSCAT

Additional Information

Please note that this documentation only covers the basics required for recording a CATT script using a single transaction through to executing this script in a live environment. For help on additional functionality please go to: - Q:\SAP\CATT\CATT.DOC

Filename: document.docReference: HR_TM_SCAT

Version: Not StartedLast Modified: 9/5/2002 9:15 PM

Work Instruction / 49


Procedure

1. Perform one of the following:

If Go To

You wish to record a new CATT script Step 2

You wish to make changes to a field setting Step 23

You wish to make changes to field parameters Step 30

You wish to re-sort a parameter list Step 32

You wish to import files Step 33

You wish to execute a CATT script Step 39

You wish to delete redundant screens in a CATT script Step 52

You wish to remove incorrect screens from a CATT script Step 53

You wish to prepare an MS Excel workbook for use in an export file to CATT

Step 54

2. Start the transaction using the menu path or transaction code SCAT.



Work InstructionPage 1 / 49


Computer Aided Test Tool: Initial Screen

3. As required, complete/review the following fields:

Field Name R/O/C Description

Test case R Enter the description of the Test case.

Example: Z_UOL_HR_NEW_STARTER_TEST

You should adopt the following naming convention:-

Begin every new CATT script name with Z_UOL_

Followed by the SAP module abbreviation (in this case HR_)

Followed by the chosen script identifier (in this case NEW_STARTER_TEST)

4. Click on to start recording. You will be prompted with the following dialog box:-





CATT: Record another transaction

5. Enter the transaction code then click on to continue.

Personnel Actions

The first screen of the chosen transaction appears. Complete as necessary.

6. Click on to proceed through the transaction. You will step through each screen of the chosen transaction, entering data in fields and saving as necessary. In this example you will return to the usual PA40 initial screen upon completion.

It is best if you know what data you need to enter before you commence the transaction. The simple reason for this is to prevent unnecessary, additional screens being recorded as part of the CATT script. For example, if you are unsure which employee subgroup to use and go into the drop down selection box this will appear as





an additional screen capture in the recording of the transaction. This can lead to confusion when you review or change the CATT script.

Personnel Actions

7. Click on to step back out of the transaction. You will now see the following dialog box.

CATT: Record another transaction

8. Click on to stop recording.

8.1 Click on if you wish to start recording another transaction (after entering the appropriate transaction code).

Recording a new transaction will simply append the details to the existing script. It will, however, be shown as a separate entry in the functions list for the script. It is possible, therefore, to string together a number of separate transactions into one test script by this method.





Please note this documentation only walks through creating a single transaction script.

Test case attributes: Change test case Z_UOL_HR_NEW_STARTER_TEST

Selecting stop recording will prompt you to complete the attributes sheet (above).

9. Click in the Component field and select from the drop down list the appropriate component.





Select application component

10. Select component PA-PA-GB-xx, where xx = PD, PY or OD.

11. Click on .






12. Click on to save. You will be prompted with the following dialog box:

Create Object Directory Entry





13. Click on to save your script as a local object (DO NOT type into the Development class field itself).

This allows you to run the script in other clients without the need to do transports between clients. You therefore save the scripts in DEV and run them into QAS for testing or into PRD for data uploads. Details of how to do this are to be found towards the end of this document. See Step 39.


14. Click on to return to the Computer Aided Test Tool Initial Screen.






15. Select Functions and then click on .





CATT: Display Functions Test case Z_UOL_HR_NEW_STARTER_TEST

16. Double click in the Funct field or click on . This will drill down into the list of screens for the recorded transaction.





CATT: Display Details for Functions TCD Test case _UOL_HR_NEW_STARTER_TEST

17. By default the cursor will be placed against the first entry in this list.

If you double click here or click on , this will take you into the initial screen of the recorded transaction.





Simulation of screen "SAPMP50A 2000" (1/21)

18. Click on to step through screen by screen. This enables you to check the recorded details.





Simulation of screen "MP000000 2000" (2/21)

19. Click on to go to the next screen.






Note that you will often see additional fields in infotype screens in a recorded script. These fields are hidden from view when you view the infotype screen in normal circumstances as part of a transaction. Unfortunately, the CATT tool does not give the option of presenting customized views. What you see as part of a recording is the SAP standard view and there is no way of changing this.

Please note that if you see additional screens for an infotype when walking through a recorded script, this means the script has recorded more than one action for that particular screen. Usually this is because you have hit the ‘Enter’ key first THEN chosen to save your data. The script records one screen action for pressing ‘Enter’ and one screen action for pressing ‘Save’. This can be confusing when you come to review the recording afterwards as, in this example, you will see two screens for the same infotype; one with fields containing the data you input and one screen with blank fields. It is possible to delete any surplus screens from the script.

Please see Step 52 for details of how to remove unwanted screens from a script.

It is also possible in some instances to see a totally blank screen as part of a recorded script. This can occur when, for example, as part of the Personnel Action a dialog box





appears prompting you to choose a subtype. If there is only one subtype to choose from then the user simply hits ‘Enter’ to accept the selection and the action carries on. In cases such as this there is no choice in what data to input. CATT does record this but when you step through the screens it appears as a blank screen - even though when you execute the script everything appears to be as it should. In cases such as this if you wish to delete the ‘offending’ screen from the script you can – but do so with caution.

Please see Step 52 for details of how to remove unwanted screens from a script.

To change a field value you will have to return to the Computer Aided Testing Tool Initial Screen.

20. Click on three times.


21. Click on .

22. Drilldown to the transaction screens as before.






Once again you can step through each screen but this time you are able to set default values for a field or save the field as a named parameter for use in an import file – the use of import files is covered later. See Step 34.

A default value is a value the CATT script always uses when executing if you do not provide it with an alternative value. Any of the values you enter as part of the recording can be considered default values if you do not need to supply data for these fields when you execute the script (for example, setting the gender radio button to ‘male’ can be considered to be a default value).

A parameter is a named field in a CATT script which will expect values to be passed to it from an import file when the CATT script is executed. Setting parameters in a CATT script is covered as part of the following section.

To Make a Change to a Field Setting

23. Select the field and select Right mouse click.

24. Select Details.





Maintain field entry

If you wish to save as a parameter choose an appropriate name. In the example above we have entered ‘FOA’ for the ‘Form of Address’ field. Please note that SAP will add an & to the beginning of any name you use by default if you forget to enter this. The & symbol acts as an identifier and delimiter for parameter names in the script, allowing you to include spaces in the parameter name.

The script will use this name to read data in from an imported file with a column header set, by default, to the same name.

If you wish to set a default value for a field leave Param. name blank and enter the default value into Field contents.


Using the Form of address field as an example – setting Field contents to Mr will default this value in when the script is executed. If you do not require a default value simply leave Field contents blank. Default values can also be used with parameter names. Again, this will ensure that a value is entered in the field when the script is executed, even if the import data field beneath a parameter header in the text file is left blank.






The above example shows the parameter field value for Personnel Number being set to a space ( ‘ ‘ ). You must do this at the beginning of any transaction which defaults through a personnel number from a previous action. An example of this is PA40 Personnel Actions which always defaults through the last personnel number you have viewed in PA20 Master Data Display or used in a PA30 Master Data Maintenance or PA40 action. If you do not set this parameter then any script you run will always try to carry out a current action on the previous personnel number!

25. Click on when all changes have been made.

26. Once you have finished setting defaults and / or parameters click on three times to return to the initial screen.

Exit maintenance

27. Click on :






28. Select Parameters and click on to view all field parameters.





Display Import parameters Test case Z_UOL_HR_NEW_STARTER_TEST

29. Click on to exit.






30. Click on Parameters and .to change field parameters.





Maintain Import parameter Test case Z_UOL_HR_NEW_STARTER_TEST

31. Enter data in the Default value column to change its value.

It is important that data is entered in the correct format when you are setting parameter values. Appendix B includes a table of correct data format examples for SAP. Please note Appendix B provides advice on completing a spreadsheet to be used as an export file to SAP, but this advice also applies when setting parameter values in the CATT script itself.

To Re-Sort a Parameter List

32. Select a parameter.

32.1 Select EditSortSelect from the Menu bar





Maintain Import parameter Test case Z_UOL_HR_NEW_STARTER_TEST

32.2 Click on a parameter name below the position where you wish to move.

32.3 Select EditSortMove here.

When all editing is complete you are ready to save the script to a text file. This can then be used to import data into SAP when the CATT script is executed.

33. Click on to return to the Computer Aided Testing Tool Initial Screen.






34. Select GotoVariantsExport default.

Transfer to a Local File

35. Click on to accept the default location shown for this file. Alternatively, browse via

the drop down list button to select a new location in Windows Explorer, then click on .

36. Once transferred you can open the file up in Microsoft Excel to view its contents.





Open

Please make sure you have Files of type set to All Files (*.*), as shown above, otherwise you will not be able to see your text file. By default MSExcel only displays its own file types in this Open dialog box. To change to All Files click on the drop down arrow next to the field and select this option.

When opening the file in Excel the Text Import Wizard will launch automatically.





Text Import Wizard - Step 1 of 3

37. Click on to accept the default settings in MS Excel. This will import the file as a tab delimited file.





Microsoft Excel

You can see from the contents of this file that SAP has saved the parameter names you created earlier. (Refer to Step 23.) These act as column headings.

In order for you to import data into SAP using the script you should enter or paste the values under the appropriate headings BEGINNING on row 5.

DO NOT change the contents of rows 1 to 4. Your script will not execute if you do.





Microsoft Excel

38. Once you have entered all the data into the spreadsheet you will need to resave it again as a text file.

38.1 Click on then choose File Close from the menu bar.

38.2 If you are prompted with the following dialog boxes:

38.3 Click on Yes.





38.4 Select Yes to retain the file in the required format – Text (Tab delimited).

38.5 Switch back to SAP Computer Aided Testing Tool: Initial Screen.






It is best practice at this stage to test your script file in DEV before running it for real in PRD. Test the script file on a small number of records. You will have to be sure the data you have included in your text file is valid in the test (DEV) client (e.g. the employees actually exist in DEV!!). You may need to change this data to run it in the test client then change back to live data for running into PRD

Execute a CATT Script

39. Click on to execute your test script.

CATT: Execute Test case Z_UOL_HR_NEW_STARTER_TEST

In Test mode choose the following radio buttons:


Field Name Description

Log typeRetain the default setting – Long





Field Name Description

Processing modeSelect Foreground if the number of test employees is low.

Select Errors where the number of test employees is high - this setting will run in background unless an exception is encountered, in which case processing switches to foreground to allow the user to intervene. After intervention the processing switches again to the background.

VariantsSelect External from file

41. In Variants select . By default the Windows Explorer dialog box should go to the location of the last saved text file.

Choose external variant file

42. Select Open. The full path name of the file you have chosen will now be displayed at the bottom of the Variants box.





CATT: Execute Test case Z_UOL_HR_NEW_STARTER

43. Click on to execute. Executing in foreground mode will take you through screen by screen. You will be prompted to save data as you go along. These are example dialog boxes you will encounter:

Personnel actions

44. Click on to acknowledge these boxes.

Create Actions (000)

45. If you encounter an error message it is possible to step through the screen without saving just

by clicking in the tool bar. This will prompt the next screen to appear.





Remember, if you choose to only display errors all the processing apart from any exceptions will be done in background.

CATT - Test Plan Log for Run 0001323 REP_SAPMSCAT

This screen details a log of all the actions your script has undertaken. The absence of any red highlights means there were no exceptions and the script ran successfully. If you run the script in foreground or in background with errors you would not expect to see exceptions listed in the log. This is because you should have dealt with any error messages as they occurred in foreground processing.

It is possible to double click on each entry in order to see more detail of the transaction.

An example of a script which has been run in background only and has executed with exceptions is shown below.





CATT - Test Plan Log for Run 0001325 STA_Z_UOL_HR

You can see that the log is quite detailed and shows exactly why a particular action has not completed correctly.

Clicking on the IMPORT entry in this log will show the data the script has imported for this individual.





CATT - Test Plan Log for Run 00001325 STA_Z_UOL_HR

In this case the error has been caused by the omission of an entry in a required field (Work Contract). You have two options with required fields:

All required fields can be set with default values. This will ensure you do not get this error appearing. The downside to this, however, is that if you omit data for an individual in your script file and the default value is taken when the script is executed you may end up with a value which is incorrect for that individual. In the example being used here the Work Contract could have been set to have a default of U1 (full-time). So for each person without a value set for this field in the text file they would become full-time, even though in reality they may be part-time! Even worse, if the value is omitted on gender and the default is set to female then all male employees take a default of female!

The second option is to leave out default values for required fields and to run ALL your processing (both for test and for live runs) in background BUT with ‘Errors’ set. This would then prompt the user to enter an appropriate value if an exception is encountered because of missing data in the source/text file.

Once you are happy with the test results you can rerun into the target system. The example used here is for running a script from DEV into PRD.

46. Click on to return to the CATT: Execute Test case screen.





47. Click on .

Specify RFC target system

48. Click on to specify the target system.

Output System Overview for Remote Submit





49. Select the target system from the displayed list and click on .

Specify RFC target system

50. Click to execute.

SAPR/3

You will be prompted here to log on to the chosen target system. Once logged on the script will execute as before and you will see the CATT test plan log screen upon completion.

51. You have now completed this transaction.





ResultThis is the end of the CATT transaction. Data should either have been successfully tested or successfully loaded into a target SAP system.

Comments

Please note – you should always reconcile the data actually loaded into SAP via a CATT script with your source data file. The easiest way to do this is to build an Ad Hoc Query in SAP to output the same fields you have used in your source file (plus any additional default field values; although this is not strictly necessary).

Output this directly to Microsoft Excel and then do a comparison between the two files (source file and Ad Hoc output).

Deleting Redundant Screens from a Recorded CATT script

52. As required, complete/review the following:

It is possible to have additional screens in a recorded script which do not really serve any purpose. You will only see the surplus screens when you actually step through a recorded script. Although deleting ‘redundant’ screens does help to tidy up the script and avoid possible confusion you should delete them with caution.

Additional screens may appear under the following circumstances:

You have accidentally recorded an additional mouse or keyboard action in error. For example, hitting the Enter key on your keyboard and then saving actually records two screens for the infotype screen you are in – one for the Enter key action and one for clicking on Save. When you step through the recording you will see the first screen containing your input data then a second screen with only blank fields.

You have selected from a drop down list a subtype, for example, because you did not know what to type into a particular infotype field. In this case a second screen is recorded which represents the action of choosing from a drop down list selection. If you make sure you know what data needs to be entered before you start recording this scenario will be avoided.

SAP has included an Infotype subtype dialog box as part of the action where there is only

one entry in this box and the user can only confirm (click on or hit Enter on the keyboard) the selection, i.e. no other choice is possible. In a case such as this a blank screen is recorded as part of the script in addition to the actual infotype screen. This can be confusing for users.

Be aware that making changes to CATT scripts as outlined above will mean your script will throw an exception if you execute in background ONLY. To avoid this set the script to execute in background with errors. The user will be prompted to hit the Enter key when the Infotype subtype box appears, in order for the script to proceed. This will be





a nuisance if the number of records in the export file is large. If export files with large numbers of records are going to be used it would make sense to leave the additional, blank screen in as part of the script. The script could safely run in background without exceptions being thrown (i.e. without records from the file not being processed).

The following example details both of the above scenarios and the steps you should take if you wish to delete the redundant screens.

You can see below screen captures from a PA40 transaction for a ‘UoL Prom/ASI/DI’ action. In the first screen (1 Copy Actions 000) data has been entered into the Reason for action field and the user has hit the Enter key on the keyboard. This has then prompted a message at the bottom of the screen informing the user he/she must save the data in order to continue. A second action is now necessary on the same screen before the PA40 action can continue. The CATT tool will record both actions (Enter and Save). This will result in two screens in the recording for this part of the PA40 action.

Copy Actions (0000)

The next screen capture (Copy Actions 000) shows the Subtypes for infotype 0008 (Basic Pay)’ dialog box which displays after the user has chosen to save the input data. This dialog box only has the one selection available. The user cannot make a choice

and can only click or hit Enter on the keyboard to continue. In this instance the CATT script will again record an additional screen for this part of the PA40 action, but this screen will contain no data and no fields.





Copy Actions (0000)

You can see from the next screen capture (Simulation of screen “SAPMSSY0 0120 (4/6) it is totally blank!





Simulation of screen “SAPMSSY0 0120” (4/6)

Removal of Incorrect Screens

53. To delete the ‘offending’ screens do the following:

53.1 Return to the Computer Aided Test Tool: Initial Screen






53.2 Select Functions.

53.3 Click on .





CATT: Maintain Functions Test case Z_UOL_TEST_DELETE_SCREEN

53.4 Click on .





CATT: Function Details TCD Test case Z_UOL_TEST_DELETE_SCREEN

The above screen capture shows the list of screens which make up the recorded script. There are two entries here which we may wish to remove:

Program MP000000, Screen 2000, BDC_OKCODE=/00, etc.

This is the additional screen as a result of pressing Enter before saving the data. You can verify this is the correct screen by placing the cursor on this entry and clicking on

selecting to view. To remove this entry from the script place the cursor on the

same line as 2000, BDC_OKCODE=/00, etc and clicking on .

Program SAPMSSY0, Screen 0120, BDC_OKCODE==PICK, etc.

This is the additional screen for the Infotype 8 subtype dialog box which produces the blank screen in the recorded script. Again, you can verify this by placing the cursor on

this entry and clicking on to view the screen. To remove this entry from the script place the cursor on the same line as 0120, BDC_OKCODE==PICK, etc and click on

.





53.5 View the screen after processing changes:

CATT: Function Details TCD Test case Z_UOL_TEST_DELETE_SCREEN

53.6 You can confirm the screens have been successfully deleted by clicking on and

then to step through screen by screen.

Preparing an MS Excel Workbook for use in an Export file for CATT


This appendix contains a list of hints to help you enter data into MS Excel to be used in an export file to SAP.

Column Headings – you will find it easier if you name column headings in your Excel worksheet the same as the parameter names being used in the export file (even better, just enter data directly to the export file). You should also try to keep the order of your columns the same as the order of the parameter names in the export file. This helps to keep things consistent.

54.1 View the example export file.





Example Export File

54.2 View the example Worksheet.

Example Worksheet

54.3 If the columns are in the same order as the parameter names it is easy to copy and paste directly into the export file.





Example Export File with data

Data Format – the following table shows examples of some of the required formats to be used in export files. SAP is pretty unforgiving when it comes to these so beware! The general rule here is:-

For an input field in SAP which requires the user to type in a value. You should always make sure the data looks the same in your spreadsheet as it does in SAP.

Subtype lists (such as Full-time / Part-time) require the indicator (U1 or U2) rather than the text description you see in the Infotype field in SAP.

Data Type Where used Required Format (Examples)

Excel Format Category

Date Start date, end date, etc.

01.02.2002, 01.02.02, 01022002, 010202 are all acceptable

DO NOT use 01/02/2002 – although some transaction screens accept this format most do not.

Text (not numeric)

Character Infotype subtypes

01

ALWAYS include the leading zero

Text (not numeric)

Character Address Lines

3 Kirkbygate

DO NOT use commas e.g. 3, Kirkbygate

Text





Data Type Where used Required Format (Examples)

Excel Format Category

Character Text descriptions of subtypes e.g. Contract Type, Nationality

U1 (for Full-time)

GB (for British GB)

Text

ResultYou have completed this exercise.

CommentsNone.





This page is intentionally left blank.




RWD Info Pak Template -...

Documents

Transcript of RWD Info Pak Template -...