|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Parameterization in eCATT
In eCATT script we can pass 3 types of parameters.
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
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.
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.
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.
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
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
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.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards