Hi Deepak -
I noticed some issues with your script, but I'm not sure if that's directly related to populating the old partner numbers. I saw that the mapping is off. You have serial number in the data file, but serial number is not included in the script, so most of the mapping is off by one column. So that's one of the things you could change up first. I also saw that some of the screens and actions seem to be off as well. For example the partner numbers you are entering seem to have the wrong screen number, and the action to take you to the partner screen is being clicked on while you are already on the partner screen.
I have attached an updated version of the script, but I'm not sure if it will necessarily work, as the config on the SAP system I'm testing on seems to be very different from yours, so I had to make some guesses on what was actually happening on your t-code. But feel free to test it out, especially in step-by-step mode to see where issues may be. The beginning should be fine (I corrected the mapping with the serial number), but the latter screens might end up being a bit different and you may need to make some changes.
One general recommendation I would make as a best practice is to instead of hitting Enter to take you to whatever "next" screen that the t-code might take you to, it is much safer, from a Winshuttle scripting perspective, to explicitly take the action to go to that next screen you want to go to. This could mean hitting that specific tab or clicking on a particular button or menu item. If the script is written to explicitly take you to a particular screen then it's much more likely to go to that screen, instead of assuming that the Enter action and the next screen it might take you to will be the screen you actually want to go to. I also saw many screens in the script where you were just hitting Enter (Ok-Code /00) and you were not filling out any fields on those screens, and those just end up being extra actions that are unnecessary.
Thank you!
------------------------------
JENNIFER HWANG | SE
Winshuttle North America
------------------------------
Original Message:
Sent: 08-07-2020 03:16
From: Deepak Patil
Subject: Multiple Notification creation through IW56
Dear Jennifer,
Thank you for quick feedback. Please find the attached test data and script.
Kindly let me know if any additional information is needed.
Thanks & Best Regards,
------------------------------
Deepak Patil | SAP Business Analyst
Advanced Energy Industries, Inc. |
Original Message:
Sent: 08-06-2020 12:12
From: JENNIFER HWANG
Subject: Multiple Notification creation through IW56
Hi Deepak -
Can you attach your script and sample Excel file?
Thanks!
------------------------------
JENNIFER HWANG | SE
Winshuttle North America
Original Message:
Sent: 08-06-2020 07:55
From: Deepak Patil
Subject: Multiple Notification creation through IW56
Dear Community,
I have been using Winshuttle since few months now and overall seems to be very useful tool. I am stuck with following problem:
I am creating a script to create multiple service notification via IW56 transaction. Script is only working from single notification creation only.
when the second record is processing, its still copying the partner details from previous line, due to this it triggers an additional pop-up screen and which is not included in recording.
Usually partner details should copy from excel sheet, but some how its referring from earlier transaction processed.
Can someone help how to adjust the script in such a way that it should not refer partner details from previous line.
Thanks and Best Regard,
------------------------------
Deepak Patil | SAP Business Analyst
Advanced Energy Industries, Inc. |
------------------------------