How-toEpicor KineticDashboards / BAQ / Shop Floor, Sales, Purchasing

Epicor Kinetic Dashboard Examples (Shop Floor, Sales, Purchasing) and How to Add Filters

Question
epicor kinetic dashboard examples

Also searched as

  • epicor dashboard filter
  • epicor dashboard examples shop floor
  • epicor dashboard open orders late jobs open po

Short answer

A useful Kinetic dashboard is a BAQ with a small number of well-chosen columns, a date or status criterion, and a grid or chart on top. Good starters are late jobs and operations for the shop floor, open order lines for sales, and past-due PO releases for purchasing. Filters come from BAQ criteria set to prompt for a value, plus grid column filters.

Applies to: Epicor Kinetic (2021 and later) and Epicor ERP 10 dashboards; designer screens differ between classic dashboards and Application Studio

How to build an example dashboard with a filter

  1. 1Open Query Builder (BAQ Designer) and create a new query for the subject, such as late jobs.
  2. 2Add the tables: for the shop floor JobHead and JobOper, for sales OrderHed, OrderDtl and OrderRel, for purchasing POHeader, PODetail and PORel.
  3. 3In Display Fields, choose a limited set of columns and give them clear labels; add a calculated field for days late if needed.
  4. 4In Phrase Build or criteria, add conditions such as JobComplete is false and ReqDueDate is before today, and mark a criteria to prompt for a value if users should choose it.
  5. 5Test the query on the Analyze tab, then save and publish it as a dashboard source.
  6. 6Create the dashboard and add a grid or chart bound to the query, and set the refresh options.
  7. 7Add the dashboard to a menu and assign security; check the filters and the result with a user from the target group.

Shop floor examples

Late jobs: query JobHead where JobClosed and JobComplete are false and the required due date is earlier than today. Show Job Number, Part Number, Required Quantity, Production Quantity, Due Date and days late. Add a priority or customer if planners need it.

Operation load: query JobOper joined to JobHead with a filter on open operations and group by resource group or work center to show remaining hours. A bar chart of remaining hours by resource group shows bottlenecks at a glance.

Sales and purchasing examples

Open order lines: join OrderHed, OrderDtl and OrderRel and filter on open releases with a need-by date in the next N days. Show customer, order, line, part, release quantity and ship-by date. A filter on sales rep or territory makes it usable for a sales team.

Past-due purchase releases: join POHeader, PODetail and PORel with open releases and a due date before today. Show supplier, PO, line, part, due date and the open quantity. Buyers can filter by buyer ID or supplier to work their own list.

Adding filters and parameters

There are three layers of filtering. First, BAQ criteria narrow the data at the database and can prompt the user for a value such as a date range or customer. Second, dashboard parameters or panel links pass a value from one panel to another. Third, the grid itself offers a filter row for quick searching of loaded data.

Prefer criteria in the query for anything that limits large tables, since a grid filter works only on what was already loaded. Keep query criteria on indexed fields such as dates and status flags to avoid slow dashboards. The existing BAQ performance guidance applies to every example.

Try it here, free

Epicor BAQ Query Template Generator

Open full tool

Fill in company, days back and status filters to get a starter SQL for an open jobs BAQ, plus a design checklist for the Query Builder.

Common pitfalls

  • !Loading entire transaction tables and relying on the grid filter to reduce them.
  • !Joining OrderRel without considering one row per release, multiplying line counts.
  • !Using too many columns, which makes grids slow and hard to read.
  • !Forgetting security: a dashboard shows data from the query even where the user lacks the equivalent program access.
  • !Not defining what late means, so different dashboards show different counts.

How an ERP-grounded AI assistant handles this

ERPray can answer the same questions in plain language, for example which jobs are late and which customers they affect, and show the query so a BAQ author can reuse it as the starting point for a dashboard. It reads the live Epicor database through a read-only connection and respects the user's role, and on-premises it runs on your own servers.

Frequently asked questions

What tables do I need for a late jobs dashboard in Epicor?

JobHead is enough for job-level lateness, and JobOper adds operation-level detail. Filter on completion flags and the required date. Join to the part table only if you need descriptions.

How do I add a filter to an Epicor dashboard?

Add a criteria in the BAQ that prompts for a value, or use dashboard parameters and panel links. Grid column filters offer quick filtering of the loaded data.

Can one dashboard panel filter another?

Yes. Use the publish and subscribe settings so a selection in one panel passes a column value as criteria to another panel's query.

Why is my dashboard slow?

Usually the query scans a large table without a selective criteria or uses many joins and calculated fields. Add date and status filters and reduce the column list.

Related

How-to

How to build a Kinetic homepage dashboard in Epicor

Kinetic homepage dashboards are built from Active Homepage Maintenance: create a BAQ that returns the metric or list you want, add a KPI or List widget referencing that BAQ, arrange widgets on the homepage layout, and assign the homepage to a role or company so the right users see it.

How-to

Fixing a Slow Epicor BAQ (Business Activity Query)

A slow BAQ in Epicor is usually caused by unindexed join columns, a subquery or calculated field forcing a table scan, or the BAQ pulling far more rows than the dashboard actually displays before filtering client-side. Fix it by reading the SQL Server execution plan Epicor generates, moving filters into the BAQ criteria instead of the dashboard filter panel, and replacing subqueries with joins where possible.

How-to

How to Create a BAQ in Epicor Kinetic

A BAQ (Business Activity Query) is a saved query in Epicor Kinetic that you build in the Query Builder without writing SQL. Choose the tables, define joins, select display fields, add criteria and calculated fields, test the result, then use the BAQ in dashboards, reports, BPMs or the REST API.

Error fix

Fixing Epicor BusinessObjectException: BPM Directive Errors

A BusinessObjectException that says "A Business Process Management (BPM) directive has raised the following error" means a directive on that business object stopped the transaction, either deliberately via a Raise Exception widget or accidentally via an unhandled .NET error in Custom Code. Expand the InnerException on the error dialog to see the real message and the directive name, then open BPM Designer for that object and method to find the widget that fired.

How-to

Epicor MRP Runs but Generates No Suggestions

When Epicor's MRP process completes without a job or purchase suggestion for a part you expect one for, the cause is almost always the part's own configuration (Part Class Type, Make Direct, Non-MRP flag, planning Time Fence) or the demand not being linked in a way MRP recognizes, not a defect in the MRP engine. Work through the part's Planning tab, its safety stock and lead time setup, and the demand source (sales order line status, job material requirement) before assuming the run itself failed.

Error fix

Fixing Epicor REST v2 API 401 Unauthorized Errors

A 401 Unauthorized calling Epicor's REST v2 (api/v2/odata) endpoint almost always comes down to one of three things: a missing or wrong x-api-key header, valid credentials but an API key scoped to a different company than the one in the URL, or REST services simply not enabled for that endpoint. Confirm the API key exists and is active in Application Studio (or the classic REST API help page), matches the company segment in the URL, and that the account used for Basic auth or OAuth has the right security group.

AI for ERP

AI for Epicor Kinetic, Beyond What Prism Covers

Add AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.

AI for ERP

Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant Boundary

Run a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.

Stuck on Epicor Kinetic?

Talk to engineers who work inside Epicor Kinetic every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software