# Infor M3 Ad Hoc Report: Your Options, Step by Step, and Their Limits > Source: https://netray.co/erp-help/infor-m3-ad-hoc-report-options-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer There is no single ad hoc report tool in M3. Users pick from five routes depending on volume and skill: export the list they already see, build a report in an Excel or BI tool connected to M3, call M3 APIs for exact data, query a replicated data lake, or use a natural-language layer. The right route depends on how many rows you need and whether the result must be repeatable. ## Kind how-to ## System infor-m3 ## Erp Infor M3 ## Module Reporting / Business Intelligence ## Query infor m3 ad hoc report ## Alternate Queries - infor m3 ad hoc reporting - infor m3 adhoc report - ad hoc report infor m3 ## Applies To Infor M3 on-prem and cloud; available tools depend on your Infor OS components and license, so confirm with your Infor partner ## Steps ### How to choose and build an ad hoc report **Items:** - Define the question and the grain: one row per what (order line, item, customer, lot) and for which date range and division. - If the data is already on a list panel and the row count is modest, filter the list in M3 and export it. This is the fastest route for one-time questions. - If you need data joined across programs, use your reporting tool connected to M3 (BI or an Excel connector) and build the join and filter once, then refresh. - If you need exact business-level data without screen scraping, call the M3 MI APIs for the relevant programs and load the results into a spreadsheet or database. - If you need history or large volumes, query the replicated data in the Infor data lake (if licensed) with SQL, which avoids loading the production M3 database. - Add parameters (period, division, customer) so the report is reusable rather than a one-off file. - Validate the first run against a screen total in M3 for one customer or item before sharing the numbers. - Save the definition, name an owner and document the filters so a colleague can rerun and trust it. ## Sections ### The five routes and their limits **Body:** List export is the simplest and the most limited: you get what is on screen, subject to the list row limits, and the columns are those of the panel. It is ideal for ad hoc questions and unsuitable for scheduled reporting. BI and Excel connector routes allow joins and refresh but require a modeled data source and someone to maintain it. API routes give precise business-level data but need development skills and attention to pagination and authorization. Data lake SQL scales to history but depends on the replication being configured for the tables you need and the lag between M3 and the lake. ### Governance for ad hoc reporting **Body:** Ad hoc reports quickly become shadow reports. Keep a register of who owns which, which filters are applied and which M3 version they were validated against. A report that sums order lines in different units of measure and nobody remembers why is the usual root of a numbers dispute. Respect authorization. A tool that reads M3 data through a service account may expose data the individual user is not allowed to see, so restrict access at the report level too. ### When to stop building and ask a question instead **Body:** Many ad hoc requests are one question asked once: how many open customer order lines for item X are past due. Building a report for that is overhead. A grounded query layer that reads M3 data with the user's authority and answers directly is often quicker, and the answer can be saved if it turns out to be recurring. For recurring operational reporting, a proper BI model is still the better answer. Use ad hoc routes to discover what is needed, then promote the stable ones. ## Pitfalls - Exporting a list capped at a maximum row count and presenting it as complete. - Reporting from the production database with heavy queries during business hours. - Joining on item number without the facility or warehouse where required. - Mixing units of measure in totals. - Sharing a one-off spreadsheet as the system of record. ## Ai Angle For one-off questions, ERPray lets users ask M3 in plain language, shows the query or API calls it ran, respects M3 roles and is read-only by default, so an ad hoc question does not need a new report. It can be deployed on-prem next to M3 with an open-weight model. ## Faq ### How do I create an ad hoc report in Infor M3? **Answer:** Choose by need: export a filtered list for small one-off questions, use a BI or Excel connection for joined and refreshable reports, use MI APIs for exact data, or query the data lake for history. There is no single tool for all cases. ### Can I export M3 data to Excel? **Answer:** Yes, from list panels and through reporting tools or APIs. See the separate page on exporting M3 data to Excel for the common limits and pitfalls. ### Is the data lake required for ad hoc reporting in M3? **Answer:** No. It helps with history and volume but is a licensed component with its own setup. Smaller needs can be met with list exports or API calls. ### Why do my report totals differ from the M3 screen? **Answer:** Typical causes are different filters, unit of measure conversions, status filters, a row-capped export, or data lake replication lag. Reconcile for one customer or item to find which applies. ## Search terms infor m3 ad hoc report, infor m3 ad hoc reporting, infor m3 adhoc report, ad hoc report infor m3, infor m3 business intelligence, infor m3 reporting tools, infor m3 data lake, infor m3 excel report --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json