Stored reports

Stored reports are system reports that have had their query functions modified by the user. They have been given a unique name, and then saved for later recall. Stored reports can be scheduled or unscheduled. Scheduled reports run at specific times or intervals. Unscheduled reports are available to run on demand and can cause unnecessary printing loads on the system.

Note: Journals that are opened through the reporting service, such as in GL Transaction Entry, are not processed if the operator has a journal open. Only one journal can be open per operator during these processes. The scheduled report is set to an error condition and logged to the reporting service error log. The report must then be rescheduled. Any associated group is still available to be rerun. The reporting service processes a report that opens a journal when another journal is open. This is true as long as the journals are not for the same function.

Naming stored reports

The name you specify for a stored report should convey what the report is, its intended purpose, and its expected results. For example, you set up one report to produce daily information. You set up another to produce monthly information. The name should convey that distinction. Do not use special characters or spaces in stored report names.

Using stored reports effectively

You can use stored reports to automatically print reports that you use regularly. Because you can save ranges and options on a stored report, the same profile of data can be printed each time. This reduces the time you spend on report generation.