TCD or SapGui (record)

Hello,
I'm new with eCatt and I have some questions.
I hope somebody can help me.
I read the sap info and found out that it is recommended to use TCD(record) on the first way and than SapGui(record), if it is possible. How are your experiences with controls? How I can on a easy way find out, if my controls are TCD suitable? Or is it necessary to try it at first with TCD(record)?
Regards
Dirk
Message was edited by: Dirk Raschke

I have found that TCD is only suitable for the simplest of transactions in which there are no controls or where the user is not required to interact with a control. Usually these transactions only involve entering text into fields and then pressing a button. If you are fortunate enough to still use these types of older transactions TCD is much more efficient for testing. It executes in a much shorter amount of time and it can be run in the background. The TCD command also provides screen shots for each screen which can be very helpful. Despite these efficiencies I have found TCD to be very limiting. When a transaction is recorded via TCD you are provided with only one command interface which makes it nearly impossible to go back and modify your scripts. SAPGUI recording is far more flexible because it allows you to choose the granularity of recording. In WAS 6.40 the SAPGUI(Attach) command is invaluable for developers who need to fix an existing script without re-recording the entire test.
If you want to determine whether TCD can handle a particular transaction trial and error is probably a good approach. If you record an incompatible transaction and then try to play it back the test should fail at the point a control needs to be touched and you'll know TCD is not suitable. With that said I have experienced situations in which the TCD recording will play back one day and then fail the next day with the message "Control data is obsolete please re-record" particularly with transaction code MIGO and VA01. I have not determined the cause of this type of error but my solution has been to record this transactions with SAPGUI where I have not seen similar problems.
One last point. I think TCD is neccessary for uploading large amounts of data, mass updates and load testing. These repetitive, processor/memory intensive uses would probably require the efficiency of TCD. However for usability acceptance testing, integration testing or regression testing the SAPGUI command is your best bet.

Similar Messages

ECATT - SAPGUI Recording Messages Queries

Jonathan,
With the earlier discussion regarding SAPGUI recording pattern, following were the observations. (More details were posted on September 08, 2005 with the subject - Re: eCATT SAPGUI Recording Queries)
>> The messages, which I got, are not popup dialog boxes. They are at the bottom on status bar. And the system is expected to proceed further with the warning message without any problem. But the SAPGUI recorded script fails due to such unrecorded messages.
TCD handles such situation automatically. But SAP GUI doesn't. So how to handle such unpredicted situation?
>> Again, it is mentioned in help that whenever Controls are involved, one should go ahead with SAPGUI.
What is this 'Control' mean in case of TCD.
Thanks & Regards.

Jonathan,
With the earlier discussion regarding SAPGUI recording pattern, following were the observations. (More details were posted on September 08, 2005 with the subject - Re: eCATT SAPGUI Recording Queries)
>> The messages, which I got, are not popup dialog boxes. They are at the bottom on status bar. And the system is expected to proceed further with the warning message without any problem. But the SAPGUI recorded script fails due to such unrecorded messages.
TCD handles such situation automatically. But SAP GUI doesn't. So how to handle such unpredicted situation?
>> Again, it is mentioned in help that whenever Controls are involved, one should go ahead with SAPGUI.
What is this 'Control' mean in case of TCD.
Thanks & Regards.

Difference between TCD and SAPGUI

Hi all,
What are the differences between TCD and SAPGUI in ecatt?
And also which one is better? Should I used tcd mode of ecatt for any transaction? Or there is any limitations for the same. same for SAPGUI?

Hello Lalit,
TCD & SAPGUI modes have their own advantages & disadvantages. So their usage depends on their requirement in the recording.
Some of the differences between TCD & SAPGUI are as follows -
1. TCD recording mode can run in background as well as foreground.
- SAPGUI recording mode requires GUI playback. But it can run with or without user intervention.
2. TCD is fastest mode of recording as well as replay.
-SAPGUI is very slow.
3. TCD cannot be used for ENJOY transactions (those who have activex controls) where the usage of activex controls is mandatory. It is suitable for simpler transactions where directly values and be placed and results can be seen.
-SAPGUI work with ENJOY transactions. It should be selected only when the usage of the controls is mandatory.
You will conclude more about the TCD & SAPGUI usage gradually as you will work with transaction in eCATT.
More details can be found from the following weblogs -
1. eCATT Introduction
/people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i
2. TCD Recording Mode
/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii
3. SAPGUI Recording Mode
/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii
PS If the answer solves your query, do reward points to everyone responding.
Regards

Problem with SAPGUI Recording

Hi all,
I am facing problems while playing back the recording done through SAPGUI(record).
Let's say for creating a sales order through VA01. I did the recording. The recording is smooth without any errors. In the Structure editor also, it shows the same windows and values .
But while playing back (Parameterized or not)after entering the values in the first screen of VA01, it opens 2 new windows with the same screen( First screen of Va01).
The first opened session terminates along with the 2 others after some time giving an error.
From the log I could not find out the problem. If anyone has any idea regarding this problem, please reply back.
Thanks & regards,
Sasmita

Hello Sasmita, hello SAP Developer,
just to clarify: the ResetGUI flag doesn't doesn't determine whether a new GUI session should be opened or not. It only determines whether the transaction in this SAPGUI command will be started newly (if ResetGui='X') or not (if ResetGui=' ').
In the meantime I noticed that I forgot one important issue in my last answer: opening a new session can also be caused by a change in the logical system name of the target system. So altogether we have three parameter that might lead to opening a new session: the ConnectionID, the SessionID and the logical system name. If one of these parameters in the current SAPGUI command is different from the parameters in the earlier SAPGUI commands, a new GUI session will be opened.
One example:
- First SAPGUI command: ConnectionID '/app/con[0]', Session ID 'ses[0]', target system 'MY_TARGET_SYS'
- Next SAPGUI command:
a) ConnectionID '/app/con[0]', Session ID 'ses[1]', target system 'MY_TARGET_SYS' -> a new GUI session will be opened, because the SessionID is different.
b) ConnectionID '/app/con[0]', Session ID 'ses[0]', target system 'MY_TARGET_SYS2' -> a new GUI session will be opened, because the logical name of the target system is different.
c) ConnectionID '/app/con[0]', Session ID 'ses[0]', target system 'MY_TARGET_SYS' -> no new GUI session will be opened, because everything stayed the same.
One comment on the logical target system name: only the name has to be different. Even if two logical system names point to the same target system, this will still open a new GUI session.
So, if you want to ensure that the SAPGUI commands are replayed in the same GUI session, you have to ensure that these three parameters are the same in all SAPGUI commands of the execution.
One last remark: in eCATT as of 6.40 there is always the start option "Execute all SAPGUI commands in a single session per destination". This start option will overwrite the behaviour caused by different combinations of ConnectionId and SessionID. In this case only the logical system name is relevant for opening a new GUI session or not.
Best regards,
Markus

How to deal with generated programs in eCATT SAPGUI recording?

Hi experts and professionals,
I am trying to automate testing of our solutions by eCATTs and so far i have not been able to find solution for following problem.
Whole test scenario is very simple:
Check InfoProvider data (query, lookup, listcube,...)
Create DAP on InfoProvider
Archive InfoProvider
Check InfoProvider data (query, lookup, listcube,...) again
Compare results from step 1. and 4. (must match)
Reload archived data
Check InfoProvider data (query, lookup, listcube,...) again
Compare results from step 1. and 7. (must match)
As you can see, one of the required test steps is to check InfoProvider's data in transaction LISTCUBE.
But transaction LISTCUBE generates its program "name" every time it is executed and
I am struggling to find a way how to deal with these generated programs in eCATT SAPGUI recording.
Key is that solution must be generic and work for all SAP BW releases from 7.0 upwards
(having in mind that LISTCUBE can read NLS data from SAP BW 7.3 release).
Error description from eCATT log:
Screen Check Error: Expected Transaction: LISTCUBE, Actual Transaction: LISTCUBE.
Expected Program: GP0KOZE7EFIUBN10MZUFWX90W80, Actual Program: GPBP24INA6VV77SL0XKU5NA642O.
Expected Screen Number: 1000, Actual Screen Number: 1000.
There Is Probably an Error in SAPGUI recording.
ExceptionClass:CX_ECATT_APL_CAPTURE ExceptionId:SCREEN_CHECK_ERROR
RaisingClass:CL_APL_ECATT_LINE_INTERPRETER Include:CL_APL_ECATT_LINE_INTERPRETER=CM00J Line:443
Is there any way how to avoid program check in eCATT script?
Anything that would help me to find solution will be greatly appreciated.
Best Regards,
Igor

Dear Igor,
Your issue is caused by the "screen check" which eCATT processes here.
In General this screen check is a very usefull activity, since is ensures that only those screens are processed by automation, which initially where recorded. This should ensure as much as possible to invoke only intended activities.
Remember, that the driver of the screen flow is still the automated transaction program ( but not the test tool). So application logic decides which screen is send next.
Using screen check the test tool tries to ensure that menu items and buttons and other activities are only automated when the tool "believes" to work on the intended screen.
For generic test scripts and often in context of generated programs the screen check might hurt a bit.
To overcome this, one might try to make the check dynamic (as Sheetal suggests correctly).
If here the name of program cannot be determined for any reason, one can use another method and do following:
- Change the value of ProcessedScreen-Active to 'R'
This will disable/skip the screen-check for this ProcessedScreen.
Sure the solution includes a certain risk, since not checking the correct screen to appear might lead to automation of actions with not desired impact.
Maybe this can improve your solution.
Kind Regards
Jens

ECATT, SAPGUI recording

Hi..
I'm working on eCATT with SAPGUI recording mode,
I recorded VA01 transaction, In this after enterring some articles i'm getting a statusbar message,
If I press enter then i'm able to enter order quantity,
But, my problem is, I'm not getting the status bar message regularly (i think the message is appearing only on holidays)
So, i want to execute the command only when the message appeared,
For this Shall I use message..endmessage block,
or any work around is there to handle this,
If i use message..endmessage block, how to define the rule and how to use the rule to execute/not execute the required step after appeating the message,
can anyone help me in this regard..
Thankyou...
Chandra shekhar

Hi Chandra Sekhar,
Using a Message - End Message block would not solve your problem.
Message block basically captures your messages(that arise while execution) but you cannot use it for standard instructions. All you could do is Allow that message(which in this case could mean nothing).
You could do some thing like this..
Use the SAPGUI ATTACH, record the message and the Enter button.. Make both the steps Optional. So, while execution, sapgui handles these optional steps when needed and in the other times, it wont consider.
Hope this helps..
Best regards,
Harsha
PS: Reward points if this answers your query.

SAPGUI Recording : Getting Server Time

Dear All,
I need to get the server time where i am doing the recording.
Ex : Sys1 is my eCATT Server.
and sys2 is my application server on which i am doing SAPGUI recording.
i used x = &time and i am getting the time of sys1(eCATT Server)
How to get time on sys2( Application server) ?
Thanks in Adavance
sreedhar d

You can execute this RFC MSS_GET_SY_DATE_TIME to get the time and date on any application server.

Problems with ECATT recording using SAPGUI Record

Hello,
I got a problem with my recording. All the prerequisites are done. The problem is, that when the recording is done i don't see the recording in SECATT testcase. Normally when you do a recording you see at the bottom right of the gui a red/white icon active. When i do a recording now, this red/white icon isn't active.
For my it's a very strange error. I hope somebody can give me a hint where i can look,
Thanks in advance.
Kind regards,
Maarten.

Maarten,
First when you start the recording using SAPGUI, you will get the pop-up whether to record this new session. You need to select Yes before continuing your recording.
Secondly check the scripting values in the target system whether it is enabled or disabled using the RZ11 transaction. Mostly SAP Basis team have authorization to change these values for us.
Here is the parameter we need to check in RZ11 - sapgui/user_scripting. It should be TRUE.
Let me know if this helps.

ECATT Adding new Line in VL02N shutdown the SAPGUI recording (and SAP too!)

Hello dear eCATT players,
I'm trying to automate the following test case:
- add a line to an existing outbound delivery with VL02N transaction.
I use SAPGUI recording. I do not do any scrolling at all , i use add item icon.
and all the SAP sessions (recorded or not recorded, even non eCATT related mode) are randomly shutdown .
By randomly i mean :
- sometimes i'm able to enter Material reference only
- sometimes i'm able to enter Material, QTY,PCE only
- sometimes i'm able to enter the whole line,
press save and it crashes during the saving.
Do you guys have any input on such issue?
I cannot provide log since it's a complete shutdown without dump.
I'm using :
Wingui 6400 Rev 2 Patch Level 0 minor version 157 as client
on a SAP Basis 6400 level 00017 as server.

Hello All,
I'm able to provide additionnal informations regarding this issue
this what i find in the err.trc file:
(Error)(15.02.07 18:09:13.390): SizeChecking: there are size conflicts between the container '1000>SUBSCREEN_HEADER:SAPMV50A:1502' and the control 'RV50A-TXTWE' from the type 'Edit'
(Error)(15.02.07 18:09:13.400): SizeChecking: '1000>SUBSCREEN_HEADER:SAPMV50A:1502': width=145 height=2; 'RV50A-TXTWE': left=36 top=1 right=156 bottom=2
(Error)(15.02.07 18:09:40.469): SizeChecking: there are size conflicts between the container '1000>SUBSCREEN_HEADER:SAPMV50A:1502' and the control 'RV50A-TXTWE' from the type 'Edit'
(Error)(15.02.07 18:09:40.479): SizeChecking: '1000>SUBSCREEN_HEADER:SAPMV50A:1502': width=145 height=2; 'RV50A-TXTWE': left=36 top=1 right=156 bottom=2
(Error)(15.02.07 18:09:48.741): SizeChecking: there are size conflicts between the container '1000>SUBSCREEN_HEADER:SAPMV50A:1502' and the control 'RV50A-TXTWE' from the type 'Edit'
(Error)(15.02.07 18:09:48.751): SizeChecking: '1000>SUBSCREEN_HEADER:SAPMV50A:1502': width=145 height=2; 'RV50A-TXTWE': left=36 top=1 right=156 bottom=2
Thanks for your help

ECATT-SAPGUI Recording error

Hi All,
I am trying do the GUI recording of the transation ME51N.I have done the recording with proper set of data and at the end i got PR number.And it given SAP GUI command on the ecatt editor(say SAPGUI ( SAPGUI_1 ).
when i double click on the command it exapand as ProcessedScreen[1]>UserChangedState>GuiElement[1]-->here we need to get the Value.Then we can perameterized this value to be available for other set of data.
but when i try to replay it running successfully and giving PR nuber.
But in this case i am unable to get values under the "VALUE"(like material, quantity, plant...) which i entered during the GUI recoding.Can any one provide solution.
and VALUE is not displayed.
When i try this for VA21, it works good, the problem with ME51N.
It will be great help if any one provide solution.
Regards
RAJ

Dear Igor,
Your issue is caused by the "screen check" which eCATT processes here.
In General this screen check is a very usefull activity, since is ensures that only those screens are processed by automation, which initially where recorded. This should ensure as much as possible to invoke only intended activities.
Remember, that the driver of the screen flow is still the automated transaction program ( but not the test tool). So application logic decides which screen is send next.
Using screen check the test tool tries to ensure that menu items and buttons and other activities are only automated when the tool "believes" to work on the intended screen.
For generic test scripts and often in context of generated programs the screen check might hurt a bit.
To overcome this, one might try to make the check dynamic (as Sheetal suggests correctly).
If here the name of program cannot be determined for any reason, one can use another method and do following:
- Change the value of ProcessedScreen-Active to 'R'
This will disable/skip the screen-check for this ProcessedScreen.
Sure the solution includes a certain risk, since not checking the correct screen to appear might lead to automation of actions with not desired impact.
Maybe this can improve your solution.
Kind Regards
Jens

ECATT - SAPGUI record 6.2 vs 6.4

When I was recording eCATT's with SAPGUI on 6.2 I did not have to enter a t-Code, it would just open a session and I could enter what ever in that session and it was recorded till I stop record
Now on 6.4 I'm required enter a t-code and start with it. What if you want to record some other action other then a t-code, is there a way to still do that?
Thanks
Rudy

Hello Rudy,
you still can use the attach function to record any possible action in a SAPGUI you started from SAPLOGON.
On the other hand there is nearly nothing one could record without a transaction running. Even if you would like to start your transaction from sap menu, this menu itself is hosted in a transaction.
Best regards
Jens

How To Handle Error Message In TCD Recording?

Hi All,
I tried recording a transaction (my own transaction) by not enterring value in an obligatory field. the error message came. but when i executed the script, it showed an error. but actualy, the error message was expected right? how to handle this situation? i tried with tcd and sapgui recording. both gave almot the same result.
i am including the script which i have written.
MESSAGE ( MSG_1 ).
*TCD ( ZCUST , ZCUST_1 , ECC ).
SAPGUI ( SAP_1 , ECC ).
ENDMESSAGE ( E_MSG_1 ).
v_mno = &tfill.
v_msg = E_MSG_1[v_mno]-msgtext.
v_mtp = E_MSG_1[v_mno]-msgtyp.
If Msg Type is E *** **** It Has To Be E ****
IF ( v_mtp = 'E' and v_msg = 'Account no AC02 does not exist EXIT = X').
logtext(0,'Passed').
ELSE.
log(v_mtp).
log(v_msg).
logtext(1,'Failed').
ENDIF.
End Of The Condition For Message Type E ******

I have recording messages using the TCD command.
My script (very simple):
MESSAGE ( MSG_2 ).
TCD ( ME21 , ME21_1 , R3 ).
ENDMESSAGE ( E_MSG_2 ).
In the MESSAGE command interface, I defined rules to allow several kind of messages.
Execution: 3 mesages found:
      * transform PR into PO
       MESSAGE     MSG_2 [1,009 sec]
         RULES MSG_2 = XML-DATA-01
        Message MODE EXIT TYPE ID    NR
        [1]      'A'         'I'   06    456
        [2]      'A'         'W'   'ME' 080
        [3]      'A'         'E'   'ZE' 029
         TCD    ME21                 [0,545 sec N] Target sys R3 -> ZDA010A219
        S06017 Standard PO created under the number 8201075606
           Tgt System Z_A219->R3->ZDA010A219 (ZDA 010 ... HP-UX ORACLE)
           CALL TRANSACTION ME21 ME21_1 XML-DATA-01
           03 MESSAGES FROM ME21 ME21_1 XML-DATA-01
           I 06 456 Release effected with release code 00001
           W ME 080 Delivery date: next workday is 02.05.2007
           S 06 017 Standard PO created under the number 8201075606
       ENDMESSAGE E_MSG_2 (&TFILL = 0)
As you can see, 3 messages are found but the &TFILL variable is still 0.
I guess (but cannot test yet) I would manage to record those messages using SAPGUI command.
Is there anything wrong with my script?
My SAP_BASIS component is in version 620. I'm not using the ultimate version of eCATT (no WEBDYNPRO command, etc.). Could it be an explanation?
Thank you in advance,
Olivier

Error in TCD recording

Dear Folks - I am getting an error when doing a TCD recording for IW21 trxn in the "Main/Fault Damage" screen filed "Fault Code" and the next field adjacent to it. As soon as I do an F4 (or even F1) I get the following error:
SAPHTML_E_CALL_METHOD_FAILED: 桓睯慄慴("HTML000004.htm")
Please assist. Thanks.
Pat

>
Pat Kail wrote:
> Dear Folks - I am getting an error when doing a TCD recording for IW21 trxn in the "Main/Fault Damage" screen filed "Fault Code" and the next field adjacent to it. As soon as I do an F4 (or even F1) I get the following error:
>
> SAPHTML_E_CALL_METHOD_FAILED: 桓睯慄慴("HTML000004.htm")
>
> Please assist. Thanks.
> Pat
Hi Pat,
Please check are you getting this error when you do the same steps in the transaction manually.
Else,
1) You can record using SAPGUI recording.
2) Try to directly input the value in the field(Identify the value manually);instead of using F4 and continue
recording using TCD.This remains robust.
3)Make sure you are in latest patch.
Hope this info helps.
Regards,
SSN.

Criticality in recording Credit memo and debit memo using SAPGUI -ECATT

Hi all,
The challenging task for you all guys once again.
Whenever I am recording credit memo or debit memo using SAPGUI(ECATT) driver,I am facing the following troubles.I need all your suggestions to over come it.
1.Depending on the invoice number the number of lineitems in the items-overview will differ.My situation is like,I have to select the lineitem which is editable[All are not editable,only few are editable] among the items available and I have to change values and I have to record those values.
2.Since,the number of lineitems is varying depending upon invoice,I am not able to detect which one is editable or not.Everytime the position of the lineitem will change,as the number of lineitems is changing everytime.
[Please note that SAPGUI is more sensitive to location].
So,I need help how to overcome this situation by SAPGUI
recording (or) Is there anyway of controlling the recording or identifying the item which is editable through ABAP code.
Please suggest on this.

Hi!
Are you sure you are making a testcase, not an interface? Then a BAPI or IDOC would be more suitable.
If you are really interested in a flexible recording, then you have to split this into multiple recordings.
Make one recording for memo creation.
Make one for line editing. Use button 'item on top' to place desired line into first screen line.
Between the two executions you can place some abap for identifying changeable lines - ask your consultants for rules.
Second recording can be used (in a loop) for all line changes.
Maybe there are other ways, would be nice to know.
Regards,
Christian

Parameterizing the text data recorded using SAPGUI.

Hi all,
Is it possible to record the text input we are providing at item data level say for example,Packing item text for the transaction VA01 using SAPGUI recording.
I am able to capture the text input after recording those values inside but I am not able to parameterize so that I can change the data everytime to be given as input.
If it is possible to parameterize what steps that we need to followed?
It is urgent.
Regards,
Vishwakarma.

i dont think u can use recording method to upload ur LONG TEXTS since these texts are not stored as other fields in the table. they can instead be put using FM 'SAVE_TEXT' in which u need to provide the id,object and name. These parameters u can have an idea by going into the SApscript editor of the text ( in the transaction itself, below the box where u enter the text, u have a DETAIL button, click it), then in the editor GOTO>HEADER> u ll c the parameters.
Text Name
Language
Text ID
Text object
These r to be passed to the FM to upload the text properly. The parameter NAME & ID depends on the item no.
other 2 are fixed.
Hope it helps.
regards,
Bikash

TCD or SapGui (record)

Similar Messages

Maybe you are looking for