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.

Similar Messages

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.

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

Message---- End Message in Ecatt - -SAPGUI

Hi Everyone:
    Can some one give me a detailed information about Message and End Message commands in Ecatt-SAPGUI.
    How can they be used?
    What are the main advantages etc.
Thanks,
Rajesh.S

Hello Rajesh
You can basically use the Message/End Message statement to surround SAPGUI or TCD commands to capture messages from the GUI as raised by the MESSAGE ABAP Statement in your programs. The captured messages can then be analysed using a set of specified rules to determine whether the program is functioning as expected or not.
For example, the following eCATT segment was used to capture a message from the program that certain data was successfully generated and saved.
MESSAGE ( OPTIONAL_COMMANDS ).
SAPGUI ( CONFIRM_SAVE ).
SAPGUI ( CONFIRM_GENERATE_SUCCESS ).
SAPGUI ( SAVE_SUCC_MSG ).
ENDMESSAGE ( E_OPTIONAL_COMMANDS ).
The command interface used with the Message/End Message statement, in this case the command interface is called OPTIONAL_COMMANDS, will determine how the eCATT script will respond to the messages received from the SAPGUI commands.
The command interface has a specific parameter called MODE which will determine whether a specific message is allowed, is expected, is considered an error or is obligatory. You can also specify whether the script should exit if the specified condition is not met using the EXIT flag in the command interface. Also note that the command interface used with the Message/End Message statement can contain a number of these kind of rules as to establish a set of rules used to govern the expected behaviour in terms of the messages being raised by the program.
In your recorded SAPGUI or TCD statements specifically look for the Message variant in the recording to see what messages should be raised by the program in terms of the message classes and message numbers since you are going to need these to fully specify your messages to the Message/End Message statement. The following is an example of the message recorded in the CONFIRM_GENERATE_SUCCESS command interface from the above code except that can be used to determine the exact information to use in drawing up the OPTIONAL_COMMANDS command interface for the Message/End Message statement:
Message
Type I
Text Report /EPIUSE/VM3REP_22000003_NEW was generated successfully.
Id    /EPIUSE/VM3MESS
Number 225
Parameter1 /EPIUSE/VM3REP_22000003_NEW
Parameter2
Parameter3
Parameter4
AsPopup X
Here your expected message is an information message (Type I), the message class would be /EPIUSE/VM3MESS as recorded in the Id field and the message number would be 225, do take note of these fields since you are going to need them to draw up the command interface for the Message/End Message statement. The parameters 1-4 might also be used in your Message/End Message statement conditions to really narrow down your expected messages. Well, this is a lot of information for you, I hope it helps...
Stay well
Ettienne Hugo

No matching records found 'Queries' (OUQR) (ODBC-2028) [Message 138-183]

Hello All
I have created a SAP Business One addon in which I have created so many User menus Under 'Administration' , ' Sales A/R', 'Purchasing A/R' and New menu item under 'Modules'. All my program and menus are working fine. But after a certain time of period, when I press any of these menus, I am getting a SAP Status bar error message (RED) that 'No matching records found 'Queries' (OUQR) (ODBC-2028) [Message 138-183]'. Even after the menus are working fine. But I am receiveing this constantly.
I am getting this message even after closing my addon program. So I think this message is coming from SAP itself.
Any clue regarding this?
Anoop

Hi Anoop.....
I guess any of the queries has been removed from Query manager which is applied to the Marketing Docs as FMS......
Please check properly......
Regards,
Rahul

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.

ECATT SAPGUI playback hanging..

Hello,
I have just recorded some new test script using the SAPGUI driver. The recording looks good but when i play back my recording is script hang after the first command and I loose control.
I have tried many execution option but the problem still there - This is a new problem too me as I did some recording in the past with no issue.
The error do not seem to be consistent accross my multiple attempts. Sometime the script "unlock" and then process the rest of the transaction correctly.
It seems that the transition between the session manager command and the actual transaction is not going smootlhy.
Any suggestion on how to address the issue?
My gui version is 640 Patch level 14 build 782634
The sap version is: 4.70 was 620
Thanks for the help.
Gilles

Hi Gabriela,
just to explain that behavior:
eCATT SAPGUI recoding in 6.20 starts the GUI not directly into the transaction to be recorded. Depending on system settings transactions called SESSION_MANAGER, S000 or even other "startup-transactions" do come up first, before you enter "/n<TACODE>" in your OK-Code field. (BTW: you should avoid starting transaction to be recorded by menu path').
Unfortunatelly SAPGUI recording does also record that start transaction, but as Jon wrote, you can decomment or drop this line.
For a "perfect" transaction recording you should also active the RESET_GUI flag with 'X' in the SAPGUI command containing the real first screen of your transaction (the screen after SESSION_MANAGER). This causes eCATT to send a "/N<TA_CODE>" before starting replay. That way you can be sure to start with the right transaction.
Now the reason for your error message:
Sometimes during replay unfortunatelly the start screen is not the same as during recording. There is a certain check in SAPGUI command to avoid replay on wrong screens and that causes the message you saw.
From 6.40 on eCATT starts recording always directly in the trasaction to be recorded. You have to specify it at the "insert pattern" screen for SAPGUI recording. So screen with TA SESSION_MANAGER should not appear anymore in new recorded SAPGUI commands.
Best regards
Jens

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

Ecatt sapgui issue

Hi,
I am trying to record co60 transaction thro ecatt sapgui mode.
I have issue while specifying batch number, qty on the main cockpit sheet. Scripting is not recognizing the actual fields on the PI sheet. Anyone faced this issue ,kindly share your thoughts.
Thanks in advance
Giridhar

Hello Giridhar
The PI sheet is a quite old-fashioned report with editable fields that, unfortunately, escape the eCATT recording.
However, there might be trick how to record these fields nevertheless. For example:
- The field "QUANTITY" is (on our system) located within a block "Phase". The line begin with the phrase "Control Instruction" which occurs several times on the PI sheet but this is the last occurrence.
Phase          : 0952 / Instruction no.: 0010
Control Instruction            :               QUANTITY :
Text could not be read                         ORDER COMPLETE?
So, if you can navigate unambigously to the line where you want to modify values using the SEARCH button (Ctrl+F) you are halfway through. Let us assume that you could navigate to the line begin with "Control Instruction". How do you get to the editable "QUANTITY" field? By moving the cursor with the "Right-Arrow" button. The distance between the beginning of the line and the editable field should be fixed.
I know it sound a bit weird but I have used this workaround already to get to specific nodes of old-fashioned trees (RS_TREE_...).
Good luck.
Regards
   Uwe

ECATT SAPGUI Recoring for co60

Hi,
I am trying to record co60 transaction thro ecatt sapgui mode.
I have issue while specifying batch number, qty on the main cockpit sheet. Scripting is not recognizing the actual fields on the PI sheet. Anyone faced this issue ,kindly share your thoughts.
Thanks in advance
Giridhar

Hi Giridhar,
Check the SAPGUI Recording if some of the steps are not recorded itself or if the SAPGUI's are jumbled(this happens some times, then split to the least level and arrange the SAPGUI's in order) correct them and execute them.
Execute the Script highlighted, so that you will exactly know where the problem is..
That should be a temporary problem. CO60 is a normal transaction which doesnt have any controls in it also, so handling that transaction for SAPGUI should not be a problem.
Try to record the TA again(my last suggestion)..
Besr regards,
Harsha
PS: Reward points if this is helpful

ECATT SAPGUI method to capture ALV grid contents

Dear All,
I am using eCATT SAPGUI method to record the transaction VF04. The problem here is I am unable to capture the contents of the ALV grid present in the transaction.
Were any one of you able to capture the contents of ALV grid using SAPGUI method, if so, please do help me to solve this problem.
Thanks in advance,
Sidharth

Hi Sidharth,
Did u find any solution for this problem .
Iam facing same problem for MRIS,MRRL alv reports.Iam recording through SAP GUI but I want One out put field in log. If U find any solution for this plz forward to me.
Thanks in advance
Raju.K

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.

There is no source data for this data record, Message FZ205

Hi Experts,
I am facing a problem with the DME File download. This problem happened all of sudden in our production system since last month and it was never before. Our system landscape has also not been changed but as per our basis consultant he has added two-three more new application server to the Production client. Even we do not have this problem in our testing clients.
Please note that we have been using the output medium '1' from the day one and thus the system has been generating the DME in 'File System' which we download on the desktop and upload the same to the bank online. After running the payment run when we trying to download the DME File, the system gives the error "There is no source data for this data record, Message FZ205".
I tried to fix this issue through many ways but not able to. So can you please let me know the reason of this error and solution to fix this.
With best regards,
BABA

Hi Shailesh,
Please share how you solved this problem.
Many Thanks,
Lakshmi

ECATT - SAPGUI Recording Messages Queries

Similar Messages

Maybe you are looking for