!--a11y-->
Scheduling a Package as a Job 
You have assigned one or more Reporting Agent settings to a scheduling package.
...
1. In the right-hand tree of the Reporting Agent Scheduler, select the scheduling packet you want to use.
2. From the context menu, choose Schedule. The Change Job RA (name of the scheduling packet) screen then appears
3. Specify the execution target.
4.
Using
Start Condition on the Change Job
RA (Scheduling Package Name) screen, you get to the Start Time
dialog window. Enter the data that the system asks you
for.
If you want the system to execute the job periodically, set the indicator to Execute Job Periodically and specify the repetition period for the job using Period Values.
You can limit the factory or annual calendar start time via Restrictions.

You can only execute a scheduled job after releasing it. Users need the corresponding authorizations for the background run in order to do this.
You can find additional information in the Computing
Center Management System documentation under
Scheduling Background
Jobs.
The following functions are available in the right-hand screen area in the Reporting Agent Scheduler:
|
Function |
Information |
|
|
You get to the Alphabetical Job Overview screen. Listed are the status of the scheduled jobs: · planned · released · ready · active · finished · cancelled |
|
|
The SAP Server screen then appears. You can you find out about the current processes and possible execution targets here. |
|
In the Exceptions function area:
|
The entries in the Alert Monitor are displayed. You
reach the default view using |
|
in the Web Templates function area.
|
The Document Overview screen displaying the pre-calculated BW Web Reporting HTML documents appears. The tree structure is constructed as follows: There is an index for each Scheduling Package. In this index, the background run jobs that have just been executed are displayed in individual indexes in turn. In each job index, there is an individual index for each device class that includes Web templates generated and saved as HTML pages during background processing. · PIE for the device class Pocket IE. Each PIE index contains a Documents index with the calculated HTML pages. · WWW for the Web Browser device class. Each WWW index contains an index for each Setting. Under which there are the following indexes: Documents with the calculated HTML pages. Icons with links that lead to the symbols, Java Script with the files that may be required to fill the selection lists, Style Sheets with links that lead to the style sheets, When pre-calculating Web templates user-specifically, the directories of the individual device classes contains directories for the individual users. The respective document links are in the index file for all filter values and variables. |