Every batch job has at least one step, and such step is effectively a report call. The Batch Job blink is called with a report name and simply calls transaction SM37 overview of Batch Jobs. The blink application defaults several time spans to select what the end user may need.
Here's a thought: your report needs to be available to several people, but it's slow to run. Schedule it early in the morning and implement the Batch job blink. Then inform your end user that the report output can be picked up from the batch job spool. It's this morning's output, which may be just fine for the task at hand. Beats waiting for fresh output ?
.