Automate

 View Only

  • 1.  Invalid Value Error

    Posted 03-31-2020 06:21
      |   view attached
    Good morning,

    I'm doing a script which I had already tested and it worked.

    I'm changing a wbs element after creating the basic structure. My 3rd level lines should have the account assignment element and planning element selected (operative indicators) as per image:


    It happens that now, after winshuttle select these two options, it does not go forward, stating to input a valid value:

    This is strange, because it was working before, and also when I do the steps manually it works.

    I'm attaching my script to be easier to identify.

    Thanks for the help.

    Joao






    ------------------------------
    joao.rino |
    SIEMENS SA (GSS A&F CENTER Lisbon) |
    ------------------------------

    Attachment(s)

    Txr
    CJ20_ChangeWBS_WO_CTR.Txr   456 KB 1 version


  • 2.  RE: Invalid Value Error

    Posted 03-31-2020 09:40
    Hi Joao -

    Can you first try clicking the "Start SAP GUI" checkbox on the Run tab?   

    Thank you!

    ------------------------------
    JENNIFER HWANG | SE
    Winshuttle North America
    ------------------------------

    Original Message


  • 3.  RE: Invalid Value Error

    Posted 04-02-2020 05:44

    Hi Jennifer,

    sure, but that's only to run SAP automatically, right? I always put that before the run. But that was  not my problem.

    Anyway I think it's working now. Is it possible that we have to use X in caps to select those two options?

    Thanks
    Joao



    ------------------------------
    joao.rino |
    SIEMENS SA (GSS A&F CENTER Lisbon) |
    ------------------------------

    Original Message


  • 4.  RE: Invalid Value Error

    Posted 04-02-2020 08:49
    Hi Joao -

    The Start SAP Gui is not necessarily checked automatically, only sometimes. But you are correct, any time you have checkboxes, having the box checked should be a capital X and not a lower case x.  This applies for all checkboxes in SAP.

    Thank you!

    ------------------------------
    JENNIFER HWANG | SE
    Winshuttle North America
    ------------------------------

    Original Message


  • 5.  RE: Invalid Value Error

    Posted 04-02-2020 11:26
      |   view attached

    Hi Jennifer,

    I'm facing other issue. In this same script I have to put an if condition because, although i'm using wbs editing, the SAP menu differs depending on the type of wbs.

    I came up with an if condition, as is in the attached script, winshuttle is identifying well which menu it has to open, but then, in the "else" procedure it doesn't populate the fields. It leaves them blank. I made a script recording separately and copy to new one. One works, the other not.


    Is this because I'm using the same columns? I don't get it.

    This is a chain of 5 scripts. This specifi parte takes info from Q column until AB.

    Thanks.

    Joao



    ------------------------------
    joao.rino |
    SIEMENS SA (GSS A&F CENTER Lisbon) |
    ------------------------------

    Attachment(s)

    Txr
    CJ20_ChangeWBS_WO_CTR.Txr   629 KB 1 version
    Original Message


  • 6.  RE: Invalid Value Error

    Posted 04-03-2020 09:55
    Hi Joao -

    If once the Else condition is run and none of the fields are populating, that indicates that the screen number contained in the script vs the screen number that is showing up during the run is not the same, hence it does not know what to do on the screen.  Does that screen work in the separate recording by itself outside of any IF condition?  

    So in using this CJ20, you are entering the project number initially, and then positioning on the WBS element to go into its details.  What if you went into the WBS directly from the main CJ20 screen instead?  So you would not need positioning.  Then if you go into the details do you always end up on screen 0999 or will there also be cases where you end up on screen 1999?  I am unable to replicate a situation where I end up on that "flexible" screen 1999 so I cannot test your script. 

    My only other thought is that even though screen 1999 is showing up during the recording process because you are doing a manual run during the recording, when it runs it since it's being run in the background it shows screen 0999 instead.  

    Have you also tried recording in Batch mode to see if it works differently there?

    If you continue to have issues after troubleshooting it might make more sense to open up a Support ticket so that they can go over this with you with more details in a web session.  Good luck!

    Thank you!

    ------------------------------
    JENNIFER HWANG | SE
    Winshuttle North America
    ------------------------------

    Original Message


  • 7.  RE: Invalid Value Error

    Posted 04-03-2020 10:03
    Hi Jennifer,

    that's correct. I found out that the screen is different because I tried to do a new script only for that cases.

    So, depending on the wbs code, it opens ​0999 or 1999, and that's why the else condition is using the 1999. When I use the same procedure outside the else condition it works, but when I combine to the if condition it does not populate.

    I will try to do the run in the background to see if 0999 works instead of manually.

    Thank you for the feedback.

    Joao


    ------------------------------
    joao.rino |
    SIEMENS SA (GSS A&F CENTER Lisbon) |
    ------------------------------

    Original Message


  • 8.  RE: Invalid Value Error

    Posted 04-03-2020 10:17
    Hi again,

    so if I run the script in the background it happens the same.

    So I would say that the screen is indeed the 1999. And if I run only the script separately, it works, that's what intrigues me. Does the if condition somehow changing something?

    Do you have any suggestion?

    Thanks.

    Joao​

    ------------------------------
    joao.rino |
    SIEMENS SA (GSS A&F CENTER Lisbon) |
    ------------------------------

    Original Message