Infor VISUAL report builder: build a custom work order report
infor visual report builder
Also searched as
- infor work order report
- infor visual crystal reports
- customize infor visual reports
Short answer
VISUAL reports are commonly built in Crystal Reports connected to the VISUAL SQL Server database, and then added to the application so users can run them. A work order report joins WORK_ORDER, OPERATION and optionally REQUIREMENT and PART, filters by work order, and formats it for the shop floor.
Applies to: Infor VISUAL with Crystal Reports based reporting. Tooling and menus differ by version.
Build a work order report
- 1Install the Crystal Reports designer version that your VISUAL release supports.
- 2Create an ODBC or OLE DB connection to the VISUAL database with a read-only login.
- 3Start a new report and add WORK_ORDER, OPERATION and PART tables.
- 4Set the joins on base ID, lot and split, and sub IDs as they exist in your schema.
- 5Add a parameter for work order number so users pick the order at run time.
- 6Group by work order and list operations in sequence order with resource and hours.
- 7Add requirements and notes as sub-reports if needed, then test on real orders.
- 8Register the report so it appears for users, following your version's process, and set security.
Tables and joins
A work order in VISUAL is identified by a combination of fields rather than one key: a base ID, lot ID, split ID and sub ID. Joins from operation and requirement rows back to the work order must include all of them, or you will duplicate or lose rows. Check the key columns in your schema before building the join.
Reading the PART table gives you description and unit of measure, and SHOP_RESOURCE gives you the machine description for each operation.
SELECT w.BASE_ID, w.LOT_ID, w.SPLIT_ID, w.SUB_ID, w.PART_ID, w.DESIRED_QTY,
o.SEQUENCE_NO, o.RESOURCE_ID, o.SETUP_HRS, o.RUN_HRS
FROM WORK_ORDER w
JOIN OPERATION o
ON o.WORKORDER_TYPE = w.TYPE AND o.WORKORDER_BASE_ID = w.BASE_ID
AND o.WORKORDER_LOT_ID = w.LOT_ID AND o.WORKORDER_SPLIT_ID = w.SPLIT_ID
AND o.WORKORDER_SUB_ID = w.SUB_ID
WHERE w.BASE_ID = ?;Design for the shop floor
A work order traveler should be readable at arm's length: large order number, part and quantity at the top, operations in a clear table, and a barcode for the work order if scanning is used. Keep it to one page where possible and put notes where the operator will see them.
Use parameters and record selection in the report rather than filtering after data is fetched, so the database does the work.
Customisation and upgrade safety
Keep custom reports separate from delivered ones, name them with a clear prefix, and store the .rpt files in version control. Delivered reports are overwritten on upgrades, so copy before editing. Retest after any VISUAL or SQL Server upgrade.
Try it here, free
Infor VISUAL SQL Query Generator for Work Orders
Build a SQL Server query for open or late VISUAL work orders by filling a few fields, then copy it into your query tool.
Common pitfalls
- !Joining on only the base ID and duplicating rows across lots and splits.
- !Editing a delivered report in place and losing it at upgrade.
- !Connecting with a login that can write.
- !Pulling all data and filtering in the report.
- !Not testing with split or sub work orders.
How an ERP-grounded AI assistant handles this
A grounded assistant can draft the SQL and field list for a report from a plain request, such as a traveler with operations, hours and material, which a report author then reviews and formats. Netray builds this on-prem so the schema stays inside your network.
Frequently asked questions
What reporting tool does VISUAL use?
Crystal Reports has been the common designer for VISUAL custom reports. Confirm the supported version and any newer reporting options for your release.
Why does my report duplicate rows?
Usually a join that omits lot, split or sub IDs on the work order key. Include every key column.
Will upgrades break my reports?
Custom reports usually survive, but delivered reports can be replaced. Keep copies and retest after upgrades.
Related
Infor VISUAL query tool and shop resource maintenance
To query VISUAL data, use a read-only SQL login in SQL Server Management Studio or a reporting tool against the VISUAL database, or the in-application query and reporting options your build provides. Shop resources, the machines and work centers that operations are scheduled on, are maintained in the Shop Resource area and drive scheduling, load and costing.
How-toInfor VISUAL REST API: what exists, the API Toolkit and how to wrap it
Classic Infor VISUAL integrates through the VISUAL API Toolkit (COM objects that apply business logic), direct SQL access for reads, and flat-file or EDI imports. A native REST API is not the traditional route. Most teams expose REST themselves by wrapping the Toolkit or SQL reads in a small service, or use Infor ION where their version and licence support it.
How-toSyteLine customer on-time shipments: which dates to compare and how to report OTD
On-time shipment in SyteLine is the actual ship date on the shipment record compared with a target date on the order line, either the customer due date or your promise date. Decide which target you are measured against, then count lines shipped on or before it. A SQL query against the shipment and order line tables gives you OTD percent by customer, product or month.
Error fixInfor VISUAL error 19005: causes and step-by-step fix
Error 19005 is not a code we can tie to a single documented meaning, and published answers vary. In practice, numbered errors in VISUAL usually come from the database layer: a lost or failing SQL Server connection, an ODBC or client mismatch, or a permissions problem. The reliable way to fix it is to capture the full message text, test the connection outside VISUAL, and check the SQL Server error log.
How-toInfor VISUAL system requirements: server, SQL Server, client and network
VISUAL runs on Windows with Microsoft SQL Server, using Windows client workstations. The exact supported Windows and SQL Server versions depend on the VISUAL release, so take them from Infor's release documentation, not from memory. This page lists what to verify, how to size, and where upgrades commonly break.
How-toInfor VISUAL Price Book: How Customer Pricing and Price Breaks Are Set Up
In Infor VISUAL, a selling price reaches an order line from a hierarchy of sources: the part's list price and quantity breaks, any customer-specific pricing, and manual override on the line. A price book approach means maintaining those sources deliberately and in one place, then testing the result on order entry. Exact window names depend on your version.
AI for ERPAI for Infor VISUAL ERP: Answers and Agents for Job Shops
Add AI to Infor VISUAL ERP for make-to-order and job shop manufacturers: quoting, scheduling, and shop floor answers grounded in live VISUAL data, on-prem.
Stuck on Infor VISUAL (VISUAL Manufacturing)?
Talk to engineers who work inside Infor VISUAL (VISUAL Manufacturing) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor VISUAL SQL Query Generator for Work OrdersBuild a SQL Server query for open or late VISUAL work orders by filling a few fields, then copy it into your query tool.
- Infor VISUAL Database Table ReferenceA searchable lookup of the main VISUAL Manufacturing tables, what each holds and the usual join keys, for report writers and analysts.
- Infor VISUAL Work Order Status and Structure ReferenceA searchable lookup of VISUAL work order statuses, the work order ID structure and the records that hang off a work order, with what each means on the floor.
ERP fixes and how-tos
- Infor VISUAL query tool and shop resource maintenanceHow to query Infor VISUAL data safely with SQL or the built-in query options, and how shop resources are defined and maintained for scheduling and costing.
- Private AI Layer for Infor VISUAL On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor VISUAL on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Infor VISUAL REST API: what exists, the API Toolkit and how to wrap itWhat integration options Infor VISUAL really offers: the VISUAL API Toolkit, SQL access, ION and building your own REST wrapper, plus where to find documentation.
Runs with your ERP
- MachineMetrics with Infor VISUAL: Machine Data and Work OrdersHow MachineMetrics machine monitoring syncs work orders, schedules and labor with Infor VISUAL through an edge connector. Setup, pitfalls, alternatives, FAQ.
- 1 EDI Source EDI Integration with Infor VISUALHow 1 EDI Source connects Infor VISUAL to trading partners for EDI orders, invoices and ship notices via ION or direct API: setup, pitfalls and private AI.
- Infor VISUAL Shop Floor Mobile for Labor TrackingHow Infor VISUAL Shop Floor Mobile captures clock-ins and labor data from shop-floor devices directly into VISUAL: data flow, setup, pitfalls and private AI.
Guides
- Visual Manufacturing to CloudSuite Industrial MigrationMigrate from Infor Visual Manufacturing to CloudSuite Industrial. Understand architectural differences, data migration steps, and timeline expectations.
- How to Create Custom Reports in SyteLineStep-by-step guide to creating custom reports in Infor SyteLine using Report Builder, IDO queries, and SQL views for tailored manufacturing analytics.
- How to Configure Crystal Reports in SyteLineLearn how to configure SAP Crystal Reports integration with Infor SyteLine for advanced formatted reports, sub-reports, and cross-tab analysis.
Integrations
- How to use ChatGPT with Infor VISUALHow to use ChatGPT with Infor VISUAL data: exports, custom GPT actions over a small API, enterprise data controls, and when a private model is the better fit.
- How to build an MCP server for Infor VISUALHow to build a Model Context Protocol server for Infor VISUAL: tool design, SQL Server access, stdio vs HTTP, permission scoping and audit for any MCP client.