How a BAQ Connects to Epicor Data Discovery
The process begins with a BAQ created in Epicor Kinetic or another supported Epicor environment. The query determines the source tables, joins, calculated fields, and filters needed for the analysis. Epicor Data Discovery then uses the available query data to build visual reports and dashboards.
Successful connections depend on the query being available to the appropriate user and supported by the EDD configuration. The exact menus and configuration steps can vary by Epicor version, deployment model, and security settings. Users should verify the available BAQ integration options in their installed EDD environment before configuring the connection.
ERP integration also determines how analytical tools access operational information. The principles discussed in ERP Integration Layer: How It Powers Finance Automation help explain why reliable connections between ERP data sources and reporting tools matter for finance workflows.
Steps to Connect a BAQ to Epicor Data Discovery
Follow a structured process to prepare the query, establish access, and validate the resulting analysis.
- Create the BAQ: Open the BAQ designer in Epicor and define the required tables, relationships, fields, and filters. Use descriptive field names and include only the information needed for the report.
- Validate the query: Execute the BAQ and confirm that the returned records, calculated values, and filters match the intended business requirements. Check whether joins create duplicate records or exclude expected transactions.
- Confirm permissions: Verify that the relevant users can access the BAQ and that its underlying data is available under their assigned security permissions.
- Open Epicor Data Discovery: Access the appropriate EDD workspace and locate the supported method for selecting or importing BAQ data. Depending on the installed version, this may require configuring a data source or using an available query integration option.
- Configure the data source: Select the BAQ through the supported connection workflow, then configure the required fields, refresh behavior, and available filters.
- Build and test the visualization: Create a table, chart, or dashboard using the connected data. Compare sample results against the original BAQ output before sharing the report.
These steps provide a practical workflow rather than a universal menu-by-menu procedure. Epicor version-specific documentation should guide the exact connection settings and available data-source options.
Prepare the BAQ for Reliable Reporting
A well-designed BAQ makes dashboards easier to interpret and maintain. Choose fields that directly support the business question, use appropriate date ranges, and verify the meaning of calculated fields. For financial reports, distinguish transaction dates, due dates, posting dates, and document balances so users understand what each metric represents.
For example, a receivables BAQ might return customer ID, invoice number, invoice date, due date, open balance, and payment status. An EDD dashboard can then group balances by customer or aging category, provided the BAQ calculates or exposes the necessary values correctly.
Organizations extending Epicor reporting into other systems may also use API Data Integration to exchange information between applications through defined interfaces. However, an API connection and a BAQ-to-EDD connection are different approaches; an API is not automatically required when EDD supports the BAQ directly.
Security and Data Refresh Considerations
Access should follow the organization's ERP security model. Confirm which users can run the BAQ, view its output, and access the resulting dashboard. Review the data included in shared reports, particularly when they contain customer financial details, employee information, or confidential operational records. ERP Security Best Practices for Finance Teams (2026) provides additional context for protecting information across connected finance systems.
Also establish how frequently the dashboard needs refreshed data. A report used for daily cash planning may require a different refresh schedule from a monthly management dashboard. Confirm the refresh capabilities supported by the EDD version and connection method, and validate that refreshed results continue to agree with the source query.
Common Business Uses and Integration Choices
Connecting BAQs to EDD supports operational and financial analysis without requiring users to interpret raw ERP tables manually. Common applications include accounts receivable aging, accounts payable status, inventory valuation, purchase order tracking, sales performance, and production reporting.
Businesses evaluating broader ERP changes should distinguish reporting improvements from process changes. ERP Modernization vs Finance Automation: Key Differences explains how system modernization and workflow execution address different needs. For organizations selecting systems across multiple business models, ERP for Retail Industry: 2026 Guide to Platforms & AI offers a retail-focused perspective on ERP capabilities.
Additional finance applications may connect ERP reporting with Company Specific Configurations, allowing workflows and data structures to reflect business requirements. The Hyperbots Platform applies agentic AI to finance and accounting tasks, while integrations support data exchange with leading ERP systems. Its Process Specific Capabilities address particular finance workflows, and Ready to Deploy Capabilities provide preconfigured functionality for supported use cases.
When evaluating a wider data architecture, teams may also consider a Sustainability Data Platform for organizing sustainability-related business information and Data Platform Implementation Finance for understanding the implementation of data platforms in finance environments. These concepts concern broader data management rather than the specific mechanics of connecting a BAQ to EDD.
Summary
Connecting a BAQ to Epicor Data Discovery involves preparing a valid Epicor query, confirming permissions, using the supported EDD data-source workflow, and validating the resulting visualizations. The exact connection method depends on the Epicor version and deployment configuration. A carefully designed BAQ, appropriate security, and a verified refresh schedule help produce dependable dashboards for financial reporting, operational monitoring, and business decisions.