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

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 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

  • 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

  • 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

  • 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

  • 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.

  • 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 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 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

  • ECATT repeating Issue in Transaction Upload.

    Hey Guys,
    I have done the recording of PFCG.
    i have given
    1)Role Name
    2)Desc
    3)MENU tab ADD Transaction
    pop up opens for entering the Transactions
    4)i have added 2 transactions in my recording.
      vl02n
      vl03n
    i have DOwnlaoded the Template From Test Configuration.
    I have modified the Template and Saved it in Tab Delimit Format.
    Now when iam Uploading the Data in foreground.
    it accepts the Role Name,Desc,Goes to menu Tab,Add transaction now the Pop up Opens.
    it Accepts All this from my test File.
    Now Problem is it Does accept the First Record Transaction from My test File va01 but when
    the cursir goes to 2nd line it shows the previous entry just entered.i.e va01.
    where as in 2nd position va02 is supposed to be accepted.
    how do i Clear this..
    while looking at the processing code.
    I get this
    ID WND[1]/USR/TBLSAPLPRGN_WIZARDCTRL_TCODE/CTXTS_TCODES-TCODE[0,0] "VA01
    ID WND[1]/USR/TBLSAPLPRGN_WIZARDCTRL_TCODE/CTXTS_TCODES-TCODE[0,1] "VA01
    Now wht do i do so that it picks other tcode from my test file and not the previous record.
    Any one who could be of Help.
    can anyone leave in his/her Cell No so that I could Call and make u Understand the situation.
    it has been 4 days and iam still Stuck with this.
    Thanks Awaiting,
    Essam

    Hi,
    Try Condense that Field Fval.
    FORM populate_data  USING    value(p_fieldname)
                                 value(p_fieldval).
      CLEAR fs_bdcdata.
      fs_bdcdata-fnam = p_fieldname.
      fs_bdcdata-fval = p_fieldval.
      CONDENSE fs_bdcdata-fval.
      APPEND fs_bdcdata TO t_bdcdata.
    ENDFORM.                             
    Hope this is helpful.
    Thanks
    Kalyan

  • Context Menu - SAPGui issue

    All,
    After restarting my system today, i am not getting any context menus? (Right click menus) Any info ?
    a®s.

    Did you correctly assign %CTX :
      * Start transaction SE41
              o   Program: Zxxxx
              o   Status: Zxxx
    Hit F6 (Change)
    Expand 'Function Keys' line (Hit '+')
    In 'Reserved function keys' box, select first column (function code cell) of line 'Shift-F10'
    Hit Ctrl+F9 (Delete Entry)
    Hit Enter (Continue) in the popup 'Change F Key Setting Used Several Times'
    Enter the value below
              o   First column: %CTX
              o   Second column: Context menu
    Hit Ctrl+F3 (Activate)
    Regards,
    Raymond

  • Ecatt integration of scripts SAPGUI

    Hi,
    Using ecatt SAPGUI mode is it possible to integrate two steps in a single script. Say for example
    Step 1. post a GL transaction like in (SD creation of a sales order)
    Step 2 reverse the above generated document in (SD create a delivery)
    The usual procedure is to create two different unit scripts one script for creation of a GL transaction (creation of a sales order) and thre second script for creation of reversal posting (creation of delivery). In the third script integrate both the scripts for creation of a GL transaction and reversing the document (like in SD creation of sales order and as well as delivery). Is there any possibility of creating only one script which includes both creation of a sales order and create a delivery or posting a GL document and reversing the document
    Regards,
    Manoj

    Hello,
    Its possible , by recording the operations one after the other.
    IF ( '' = '').
    creation of a sales order
    ENDIF.
    IF ('' = '' ).
    create a delivery or posting a GL document
    ENDIF.
    IF ('' = '' ).
    reverse
    ENDIF.
    However this is not the ideal way of doing it from the reusable prespective.
    Each of this operation has to be recorded in seperate scirpts and has to called in your process script.
    Thanks & Best regards,
    Ajay

  • Ecatt: ME21N (document overview)

    Hello ecatt experts,
    I have one question concerning the recording of ME21N with ecatt (sapgui).
    When creating a PO with ME21N I want to link it to a purchase requisition.
    To choose a puchase requisistion I use the document overview.
    The problem which I am facing is, that ecatt doesn't replay the selection of a PR in the document overview.
    Does someone has a solution to this issue ?
    Is sapgui recording correct (or do I maybe have to use web dynpro recording ) ?

    >
    srinivas wrote:
    > In ME21N T-code, while Creating Purchase order. I want DOCUMENT OVERVIEW always ON.
    >
    > Sometimes when other users work with the T-code, it gets off and script is failing .
    >
    > Is it possible to make the scripting independent of the changes.  OR How can I keep DOCUMENT OVERVIEW always ON by the scripting.
    >
    > Please do the needful.
    >
    > Regards
    > Srinivas,K
    Hi Srinivas,
    You can handle this case in two ways.
    Please record in such a way that the document overview is on.Make this screen as optional.You can do in SAPGUI recording more effectively.
    There are some tables where the user-settings get saved after single time execution of these t-codes.You have to place a piece of code that clear those settings within ABAP---ENDABAP commands in the eCATT editor before script execution commands.This will clear the settings and it shows the same way on how you recorded.
    ABAP
    Code to clear settings.
    ENDABAP.
    sapgui (script commands)
    Please let me know if you have any queries.
    Regards,
    SSN.

  • How to execute eCATT's from Solution Manager

    Hey Everyone,
    am using solution manager version 3.1,WAS 620.
    and eCATT SAPGUI 640.all my recording are done with SAPGUI recording in Development System.and i execute via TestPlan STWB_2.
    Now,my question is,How to execute all these eCATT scripts from Solution Manager.Do i need to transport the whole repository of eCATT from development system to Solution Manager?.
    I appreciate if you guys pass some comments on this issue.
    Thanks in Advance,
    sarapu

    Do i need to give target system to development system from solution manager?
    can i give the same system data container in solution manager while creating testplan..
    in prior do i need to create a testcatalog STWB_1 in order to create TestPlan?
    please pass your comments,
    Thanks,
    sarapu

Maybe you are looking for