Windows Task Scheduler can launch Fusion Toolkit to submit an Oracle Fusion ESS job. The Windows task and the Oracle request are separate processes. A successful local launch proves nothing about whether the Oracle job finished, so the wrapper must preserve the Oracle result.
Extract the current Windows package and configure a named test profile under the account that will run the scheduled task. Encrypted profiles live in per-user storage. A command that works under your interactive account can fail under a service account because that account has a different profile store.
Confirm the Oracle job definition and parameter order using the ESS import-job guide and the deployed metadata. Use the task account to run the reviewed command manually in a test environment. The scheduled job may create business records, so choose a controlled test case.
Create a PowerShell wrapper that calls the native executable using its full resolved path. Supply the selected Toolkit profile and job arguments. Capture $LASTEXITCODE immediately after the executable completes, then return that value from the wrapper. Later PowerShell commands should not replace the result you intend Task Scheduler to record.
Set the task's program to the approved PowerShell executable and point its arguments to the wrapper file. Set an explicit working directory and use fully resolved file paths in the wrapper. Microsoft's Task Scheduler reference covers the scheduling interfaces and task settings. Keep passwords out of the wrapper and arguments.
Give the Oracle command enough time to poll for completion, then set the Windows task timeout above that bound. If Windows terminates the process first, Oracle may continue processing. Capture the request ID early so an operator can retrieve its state after a local interruption.
Choose the setting that prevents another instance starting while one is running. Avoid automatic restarts around a command that may already have submitted an Oracle request. A network failure after submission needs a status check before another submission. The ESS recovery guide explains this distinction.
Test the scheduled task under its actual account, including a failed command and an unavailable output directory. Check Task History and the wrapper's protected log. Confirm that failure reaches the monitoring system and that successful submission is followed by the required business verification.
This procedure was reviewed on 8 November 2026. Validate one controlled job from Task Scheduler before enabling its production schedule.