Getting the most out of Run Preferences in Automate Studio Manager or Evolve: Run Preferences give platform administrators fine grained control over how Studio and Query scripts are executed against SAP including who can schedule runs, what output formats are available, and what safeguards runners see by default. Here's a breakdown of each section and where the settings make a real difference.
Setting available under: Configuration → Preferences → Run Preferences
Scheduling: These settings control whether desktop scheduling is available and how it behaves when script settings have changed. It helps the users to enable execution only on server at times for complete visibility.
Transaction Script through Desktop Scheduling Enables users to schedule Transaction (write/upload-to-SAP) scripts to run at a future date and time via the desktop client. When it helps, Master data changes that are approved but need to take effect at a specific time for example, a price list update that should go live at midnight on the first of the month, or a new vendor that can only be activated after a contract is signed. Schedulers set it and walk away and SM/Evolve handles execution.
Schedule with Changed Settings when active, any run settings a user modifies in the file (e.g. switching from Test to Production mode) are carried through into the scheduled run, overwriting the recorded defaults. When it helps, Useful where scripts are first validated in test mode and then deliberately switched to production before scheduling. Without this toggle, the scheduled run would revert to the script's recorded settings, potentially running in the wrong mode. Turning this on gives schedulers confidence that what they configured is what runs.
Query Script through Desktop Scheduling (Excel, XML, Access, Text, SAP API/JSON) controls which Query output formats can be scheduled for desktop execution. Each format can be toggled independently. When it helps, A Finance team that runs a weekly open items Query to Excel for cash flow reporting can schedule it to run Friday at 5 PM, the file is ready Monday morning without anyone logging in over the weekend. Disabling XML or Access for most users while keeping Excel active keeps the experience simple for business runners who don't need specialized formats.
Run Options Panel: These settings define what runners see as defaults in their Studio run panel there by reducing setup errors and enforcing best practices without removing flexibility entirely.
Back up SAP Data When active, runners see the Back up SAP Data checkbox pre-checked before every run. When it helps, For any script touching master data such as material master extensions, customer account changes, having a backup means that if a run produces unexpected results, the prior state can be restored. Making this the default reduces the chance a runner forgets to check it before a critical load.
Run only Unprocessed Rows Pre-checks the option so that runners only submit rows not yet processed by a previous run. When it helps, Essential for large batch loads where a run may have partially completed due to a timeout or connection issue. With this on by default, re-running the script picks up exactly where it left off, preventing duplicate SAP postings.
Production Server Warning on Run Displays a warning prompt when a runner is about to execute against the Production SAP system. When it helps, A clear safety net for teams that work across Development, QA, and Production SAP systems. The additional prompt forces a conscious confirmation before any data hits Production there by reducing the risk of test data being posted to live systems by mistake.
Adjust based on your team's SAP landscape, compliance requirements, and runner skill level.
------------------------------
Neha Datta
*Precisely Software Inc.
------------------------------