# Epicor BAQ Report: Parameters, Running Manually, Scheduling and Triggering From Code

> Source: https://netray.co/erp-help/epicor-baq-report-parameter-schedule-run
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

To make a BAQ report prompt for values, mark the BAQ criteria as parameters, then build a BAQ report from that BAQ. Users run it from its menu item and click Submit; to schedule it, use the schedule options in the submit dialog so the System Agent runs it. Code can submit a report through the report service.

## Kind

how-to

## System

epicor

## Erp

Epicor Kinetic

## Module

BAQ Reports / Task Agent

## Query

epicor baq report parameter

## Alternate Queries

- epicor print baq report from code
- epicor schedule baq report
- running reports in epicor
- in epicor 10 how do i run a report manually

## Applies To

Epicor Kinetic and 10.x. Menu wording differs a little between releases. Scheduling needs a running System Agent.

## Steps

### How to build, run and schedule a BAQ report

**Items:**

- In Query Builder, open the BAQ and in Table Criteria mark the filter as a parameter so users can enter the value at run time. Give it a clear prompt.
- Save and test the BAQ with a parameter value.
- Create a BAQ Report from it with the BAQ Report Designer (search the menu), and pick the report style layout.
- Add a menu item for the report in Menu Maintenance and set security.
- To run manually, open the menu item, fill in the parameters, then click Submit or Print Preview.
- To schedule, use the recurrence or schedule setting in the submit dialog, choose the System Agent and the repeat pattern, and save.
- Check the schedule in System Monitor and verify the output was produced.

## Sections

### Parameters in a BAQ report

**Body:**

A BAQ with parameters turns into a prompt screen for the report. Name each parameter plainly, set a default where it helps, and decide whether it is required. A date range with defaults of the start of this month and today saves users from filling it each time.

Test with an empty parameter. If you want blank to mean all, the query criteria must be written so it does; otherwise a blank value returns nothing. Keep parameters few, because every one is a way for the user to get an unexpected empty result.

### Running and scheduling

**Body:**

Manual run: open the report menu, enter parameters, and submit. The report goes to the System Agent, which creates the output you view from the preview or the report monitor. Printing straight to a printer needs the printer set up for the agent's account.

To schedule, use the schedule section in the submit dialog and pick a recurrence such as every weekday at six in the morning. The System Agent must be running and connected to the right app server. If a scheduled job does not run, check System Monitor for the agent status and the scheduled task list.

### Triggering from code or a function

**Body:**

Epicor report services follow a pattern: get a new parameter row from the report service, fill the parameters, and call a submit method to queue it on the System Agent. You can call this pattern from an Epicor Function, from a BPM, or from the REST v2 API on the report service endpoint. Check the available methods for your report in the REST help page for your server, because names are generated per report.

Do not run a long report inside a transaction-sensitive directive. Queue it to the agent and return, so the user is not left waiting. For regular delivery, schedule it to email the output where that is configured.

## Pitfalls

- Scheduling when the System Agent is not running or points at the wrong server.
- A blank parameter returning no rows because the criteria never treated blank as all.
- Running the report as a developer and missing user permission problems.
- Printing to a printer the agent account cannot reach.
- Triggering long reports inline in a directive.

## Ai Angle

An assistant can check a BAQ report setup against what the user asked for: which parameter fields exist, which are required, and what a blank returns. It can also draft the function that queues the report. A developer still tests and approves it.

## Faq

### How do I run a report manually in Epicor?

**Answer:** Open the report from its menu item, enter the parameters, and click Submit or Print Preview. Output is created by the System Agent and shown from the preview or the report monitor.

### How do I schedule a BAQ report in Epicor?

**Answer:** Use the schedule or recurrence options in the report submit dialog, choose the System Agent and repeat pattern, and save. The System Agent must be running. Check System Monitor afterward.

### Can I print a BAQ report from code?

**Answer:** Yes. Use the report service to get the parameter row, fill it, and call its submit method. This can be done in a function, a BPM or through REST. Method names vary by report.

### Why does my scheduled report not run?

**Answer:** Usually the System Agent is stopped or points at a different server, the user account lacks rights, or the output printer is missing. Check System Monitor first.

## Search terms

epicor baq report parameter, epicor schedule baq report, epicor run report manually, epicor print baq report from code, epicor system agent schedule, epicor baq report designer, running reports in epicor, epicor report submit

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json