Automate

I am brand new to WInshuttle Runner. I was not able to complete my script successfully because I get this message:

No batch input data for screen SAPLMEOR 0205

Please help!

------------------------------
Susana Raygoza | Commodity Manager
Celestica International L.P. | 520-469-5813
------------------------------

That message means you are trying to input a field that is not open for input on the screen. This usually happens when you record in one system where a window pop ups asking for a company code or controlling area, for example, but in production that value is defaulted in your parameters in t-code SU3.  If you can run the template in the foreground to watch it populate the screens you will see where the error is occuring. Or you can run manually run the t-code in the environment where you are getting the error and make sure the fields you are populating in your recording are available and open for input in the SAP screens. 

Good luck!

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company
------------------------------

Jack,
Thank you for your help. When you say SU3 parameters, when I look at that screen, there are no parameters listed. Do I have to create one to get rid of this error message?

------------------------------
Susana Raygoza | Commodity Manager
Celestica International L.P. | 520-469-5813
------------------------------

Original Message:
Sent: 02-14-2019 08:43
From: Jack McGarry
Subject: No batch input data for screen SAPLMEOR 0205

That message means you are trying to input a field that is not open for input on the screen. This usually happens when you record in one system where a window pop ups asking for a company code or controlling area, for example, but in production that value is defaulted in your parameters in t-code SU3.  If you can run the template in the foreground to watch it populate the screens you will see where the error is occuring. Or you can run manually run the t-code in the environment where you are getting the error and make sure the fields you are populating in your recording are available and open for input in the SAP screens.

Good luck!

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company
------------------------------

It's difficult to say without knowing what field this message is being returned for. If it's company code, then you need a default entry in the parameters tab  of SU3 for BUKRS. If it is Controlling Org then you need an enter in the parameters tab of SU3 for CAC. It could be another field, but those 2 are common.

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company
------------------------------

Original Message:
Sent: 02-14-2019 15:01
From: Susana Raygoza
Subject: No batch input data for screen SAPLMEOR 0205

Jack,
Thank you for your help. When you say SU3 parameters, when I look at that screen, there are no parameters listed. Do I have to create one to get rid of this error message?

------------------------------
Susana Raygoza | Commodity Manager
Celestica International L.P. | 520-469-5813
------------------------------


Original Message:
Sent: 02-14-2019 08:43
From: Jack McGarry
Subject: No batch input data for screen SAPLMEOR 0205

That message means you are trying to input a field that is not open for input on the screen. This usually happens when you record in one system where a window pop ups asking for a company code or controlling area, for example, but in production that value is defaulted in your parameters in t-code SU3.  If you can run the template in the foreground to watch it populate the screens you will see where the error is occuring. Or you can run manually run the t-code in the environment where you are getting the error and make sure the fields you are populating in your recording are available and open for input in the SAP screens.

Good luck!

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company

Hi Susana, 

It looks like you are using t-code ME01. While, I myself am not familiar with this t-code, it appears that MRP Area (BERID) is greyed out on this screen (see attached screen shot) and therefore not open for input. If the same is true on your system and you have this field mapped in your template, you are going to receive the no batch input for screen error.  You can default a value for BERID in SU3 if needed but you will still need to remove it from the mapping in your template.

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company
------------------------------

Original Message:
Sent: 02-14-2019 15:01
From: Susana Raygoza
Subject: No batch input data for screen SAPLMEOR 0205

Jack,
Thank you for your help. When you say SU3 parameters, when I look at that screen, there are no parameters listed. Do I have to create one to get rid of this error message?

------------------------------
Susana Raygoza | Commodity Manager
Celestica International L.P. | 520-469-5813
------------------------------


Original Message:
Sent: 02-14-2019 08:43
From: Jack McGarry
Subject: No batch input data for screen SAPLMEOR 0205

That message means you are trying to input a field that is not open for input on the screen. This usually happens when you record in one system where a window pop ups asking for a company code or controlling area, for example, but in production that value is defaulted in your parameters in t-code SU3.  If you can run the template in the foreground to watch it populate the screens you will see where the error is occuring. Or you can run manually run the t-code in the environment where you are getting the error and make sure the fields you are populating in your recording are available and open for input in the SAP screens.

Good luck!

------------------------------
Jack McGarry | Sr Business Systems Analyst | Airgas, an Air Liquide company

Hi Susana, 
This is one of the most common errors when running scripts and quite easy to fix if you can run this in Debug mode and identify where the process stops. 

If you do not see a debug option in the Excel -> Winshuttle Addin -> Run settings, Please try to do this with the script author (Developer) who should have this option enabled. 

Best Regards
Jayasri


------------------------------
Jayasri Varyani | Solutions Engineer
Winshuttle North America |
------------------------------