How the Contains Condition Works
A BAQ combines data sources, selected columns, relationships, and criteria to return records that meet a reporting requirement. A contains-style condition narrows the result set by checking whether a text field includes a target string. The exact operator label and supported syntax depend on the Epicor BAQ designer and the field's data type.
Suppose a user searches a supplier description for the word “Steel.” Records such as “North Steel Supply” and “Steel Components Ltd” may match because the target word appears within the text. A supplier named “North Industrial Supply” would not match that search term unless its relevant field also contains “Steel.”
The condition is most useful for text fields, such as descriptions, names, comments, and reference values. Numeric and date fields generally require comparison operators appropriate to their data types rather than text containment.
Practical Epicor BAQ Contains Examples
Contains-style filtering supports operational and finance reporting when users need to locate records by part of a description or reference. Common examples include:
- Supplier search: Find supplier records whose name or description contains a product category or business term.
- Purchase order review: Identify orders with descriptions containing “repair,” “freight,” or another procurement term.
- Invoice investigation: Search invoice references or comments for a known project code or partial document reference.
- Part description lookup: Retrieve inventory parts whose descriptions contain a material, model, or component name.
- Customer record review: Find customer names or descriptions containing a location or business identifier.
These searches help users build focused lists for review, reconciliation, and follow-up. Before applying a condition to a financial report, confirm that the chosen field contains the information being searched and that the results match the intended business scope.
Configure and Validate a Contains Search
Start by identifying the business question and the text field that can answer it. In the BAQ designer, add the relevant data source, include the target field, and configure the query criteria using the available contains-style operator or equivalent supported expression. Enter the desired search value and preview the results.
For example, to locate purchase order descriptions containing “freight,” select the appropriate purchase order data source, include its description field, and apply the text condition with “freight” as the search value. Review the returned orders to confirm that each record meets the intended requirement. If the field is drawn from a joined table, also validate the join relationship so the results represent the expected records.
For repeatable reporting, document the field being searched, the target string, and any additional filters such as company, site, status, or date range. This makes the BAQ easier to maintain and helps users interpret why a record appears in the results.
Best Practices and Important Considerations
Contains searches are designed for partial text matching, so the target string should be distinctive enough to produce useful results. A short string may match many unrelated records. A longer string can narrow the output, but it may exclude records that use a different abbreviation or wording.
- Confirm the field: Search the description or reference field that actually stores the target information.
- Test representative records: Check known matching and non-matching examples before using the BAQ for routine reporting.
- Review text variations: Consider abbreviations, spacing, punctuation, and differences in how users enter descriptions.
- Combine criteria thoughtfully: Use company, date, status, or other filters to keep results aligned with the business question.
- Validate financial totals: When the BAQ feeds invoice or purchasing analysis, compare counts and amounts with an established report.
Within Epicor ERP, BAQs provide a configurable way to query operational data without treating every search as a separate report. Epicor ERP Modules identify the functional areas from which data may be retrieved, while Epicor Integration Finance describes how ERP information supports connected financial workflows. When extending epicor through integrations, stable field definitions and verified query outputs help preserve consistent reporting.
Using BAQ Results in Finance Workflows
A contains-based BAQ can support invoice investigation, supplier reviews, procurement analysis, or customer account follow-up by locating records from partial text. The result can inform a review queue or dashboard, while approvals, payments, and accounting postings continue to follow their respective controls. For example, purchase order descriptions containing a project name can help a finance team review spending associated with that project. A related reference, What is a Standard Purchase Order? Examples & Templates, explains the purchasing document that may be included in such analysis.
For broader ERP planning, ERP Software Examples: Real Companies, Real Flows provides context on ERP platforms and their business workflows. Where finance teams extend reporting with AI agents, Maximize Finance ROI with AI Automation Insights discusses measuring the value of technology-led finance transformation. Hyperbots Platform supports company-specific configurations, including ERP integrations, workflows, roles, and general ledger structures. Process Specific Capabilities support domain-focused finance workflows, and Ready to Deploy Capabilities provide pre-trained agents and ERP connectors for supported tasks. Human in the Loop supports human review and approvals, while Self Learning Capabilities use feedback to refine supported decisions.
Summary
Epicor BAQ Contains is a partial-text search approach for finding records whose selected text fields include a specified string. It is useful for supplier searches, purchase order reviews, invoice investigations, part lookups, and customer reporting. Select the right field, configure the supported contains-style condition, validate sample results, and combine it with appropriate business filters. These steps help produce dependable query results for operational reporting and financial decisions.