Parameterization in ecatt

Question

hi,
Is Parameterization  require in ecatt ? when we transfer catt to ecatt .
supriya.

Answer 1

Hi
Parameterization in eCATT
By Venkat
In eCATT script we can pass 3 types of parameters.
Import
Export
Local variables 
Import Parameters: Import Parameters are input values to the test script. These variables are the local to the script i.e. Import Parameters can access only in eCATT script editor but not in ABAP…ENDABAP block. These are version independent. 
Export Parameters: Out put result values after executing the script are caught in Export Parameters. These variables are the local to the script i.e. Export Parameters can access only in eCATT script editor but not in ABAP…ENDABAP block. These are version independent. 
Local Variables: Local Variables are used in both eCATT script editor and ABAP…ENDABAP block. These are version dependent i.e. local variables defined in one version is not automatically defined in other version. 
After the recording has been done for the particular transaction without parameterization, we need to check whether the recording is error free or not. Once it is confirmed error free then we go for parameterization of required fields. Usually we go for parameterization for reusability of eCATT script. Different set of data can be passed via parameters and recorded script can be used again and again. 
Parameterization in TCD mode: 
Fields having mode ‘S’ (Set) under each dynpro of command interface contains some values entered during the recording. These are the values need to be parameterized as Import, Export or Local as shown below. 
Replace the value ‘P’ in VALIN with I_MBRSH parameter. 
And now double click on the parameter I_MBRSH then the following screen will appears. 
Select Local and click ‘YES’. 
The output result of transaction is assigned to Export parameters. These are very useful in chaining of transactions where the output of transaction is input to another transaction. 
In this mode, last dynpro of the dynpro list just before the MSG node in the command interface contains the output messages as shown below.  
Here we have to change the mode ‘O’ (Field output) to mode ‘G’ (Get) and assign Export parameter in VALIN as shown below. 
Parameterization in SAPGUI mode: 
Now double click on each step of command interface of SAPGUI command from the test script editor. In this case, first double click on “ME01_200_STEP_2”. Then you will get following screen. 
Now replace value of material number T-BW06-02 with parameter. Here, T-BW06-02 is replaced with I_MATNR. 
Now double click on I_MATNR then you will get pop-up box as shown. 
Click ‘YES’. The entry appears in Parameter list and provides parameter reference. 
The output result of the transaction in this mode can be captured using MESSAGE….ENDMESSAGE node. 
Click the Pattern button from the application tool bar and select MESSAGE…ENDMESSAGE option as shown. 
And click ‘OK’.
Now the following screen appears. 
Now place the command interface between MESSAGE….ENDMESSAGE command to capture the export parameter. 
Here, the material number is captured in parameter1 (MSGV1). Now we can assign this value to export parameter as shown below. 
if found useful award points.