I think this should work fine. Winshuttle is pretty stable, and even if it fails, you can run skipping completed errors - and basically continue.
------------------------------
Alexey Skotnikov
Abbott Rapid Diagnostics AS
------------------------------
Original Message:
Sent: 04-07-2023 09:09
From: Barb Cardenuto
Subject: Maximumn number of rows to process in Automate
Thanks Alexey. I believe the script was created in Change (standard recording mode). If it would improve performance I can try to record a new script in Batch Input mode. We've used the script thousands of times but in much smaller runs usually less than 20 rows but have run 600 rows without issues.
I don't have access to the Evolve server. I can only run it in the Winshuttle Studio application or externally with the script published to the excel file.
Barb Cardenuto
------------------------------
Barb Cardenuto
Lamb Weston
Original Message:
Sent: 04-07-2023 04:20
From: Alexey Skotnikov
Subject: Maximumn number of rows to process in Automate
I don't think there is a restriction (if these are 117K separate transactions - not one PIR with 117K items) and you should be fine. But just to be on the safe side, i would split this into 2 files per 64k and executed this on Evolve server (if you have one). A lot depends on how script was recorded and for such volumes it better be optimized and carefully tested.
------------------------------
Alexey Skotnikov
Abbott Rapid Diagnostics AS
Original Message:
Sent: 04-06-2023 18:49
From: Barb Cardenuto
Subject: Maximumn number of rows to process in Automate
Hi experts,
I'm using Winshuttle v20.2.8 (32 bit) and need to process over 117K new PIRs. What is the maximum number of rows you recommend for processing in a single session?
I noticed in the KB that the max number of Loops for VK11 is 999. Is that max also true for creating new PIRs?
If I publish the script to excel, would that make a difference in the max number of rows to process rather than running in the Winshuttle app?
Do you recommend closing and re-launching Winshuttle between processing each new load sheet?
When I'm creating scripts I sometimes see memory errors when I've had the applicaton open too long. I see a big red X across the excel sheet. I don't want to overload the system or hang my SAP session.
Thanks for your guidance.
Barb
------------------------------
Barb Cardenuto
Lamb Weston
------------------------------