How to connect Power BI to Baan IV and Baan V
Short answer
Do not point Power BI straight at the live Baan database. Extract the tables you need into a reporting database or warehouse on a schedule, model them with business names, and connect Power BI through the on-premises data gateway.
Baan reports are tied to sessions and print devices, and anyone who has built a management pack from exports knows the pain. Power BI is a natural replacement for the spreadsheet layer, and many Baan sites already hold Microsoft 365 licenses.
The catch is the data model. Baan tables are named by package and number, fields carry short codes, many values are stored as enumerated integers, and multi-company data sits in separate table sets. Power BI will connect, but the result is unreadable without a translation layer.
This page describes a practical build: a reporting database in the middle, a clean model on top, and a few dashboards that matter to manufacturing.
What teams use it for
On-time delivery
Promised versus actual ship dates from sales order and delivery data, by customer and product family.
Purchase price and lead time variance
Compare ordered prices and promised lead times to actual receipts by supplier.
Production order status and WIP
Open production orders with age, operations remaining and component shortages.
Inventory ageing and turns
Stock by warehouse and last movement date, flagged for slow movers.
Backlog and booking trends
Order intake and open backlog over time, by region or product line.
Baan IV / Baan V integration surface
- ODBC: Power BI can read through ODBC, but direct queries on live Baan tables are slow and risk locking; use it for extraction jobs, not interactive reports.
- Underlying database: Oracle, SQL Server, DB2 or Informix depending on your install, each with a native Power BI connector or an ODBC route. Prefer a native connector against a replica.
- Table naming: package, module and number, for example item and order tables with company suffixes, varying by version and customization.
- Enumerated fields: Baan stores many statuses as integers mapped by domains, so you need a lookup table for readable labels.
- Flat file exports: a fallback for small data sets where a database connection is not allowed.
How it works
- 1
Pick the middle layer
A SQL Server reporting database or a lakehouse is typical. Replicate selected tables on a schedule with ETL or database replication.
- 2
Build a business model
Create views with readable names, decode enumerations, and combine companies with a company column.
- 3
Install the on-premises data gateway
The gateway lets the Power BI service refresh from your network without opening inbound ports.
- 4
Build the semantic model
Define relationships, measures and a date table. Keep measures in the model, not in each report.
- 5
Design a small set of dashboards
Begin with delivery, inventory and WIP. Resist copying every old Baan report.
- 6
Set refresh and row-level security
Schedule refresh outside peak Baan hours and apply security roles by plant or sales region.
Example flows
Nightly refresh for the morning meeting
Trigger: Scheduled ETL at 2 a.m.
- Job copies changed rows for orders, receipts and production into the reporting database.
- Views rebuild the business model.
- The gateway refresh updates the Power BI dataset.
Result: A current on-time delivery and WIP view at 7 a.m.
Ask a question in plain language
Trigger: A planner types a question in a Q&A box over the model.
- The question is mapped to measures and fields in the semantic model.
- An optional AI layer drafts a query or visual.
- The user checks the result and pins it to a dashboard.
Result: Ad hoc answers without a report request.
Keeping data on-prem
Power BI Desktop and report server style deployments can keep everything inside your network. The Power BI service is cloud hosted, though, so the gateway-based pattern means aggregated model data is stored in Microsoft's cloud. If that is not acceptable, consider Power BI Report Server on-prem or an open source alternative. For natural-language questions on-prem, point a local model at the reporting database views instead of using a cloud service, so the Baan data never leaves.
Security checklist
- Dedicated read-only account for ETL; never use the Baan application login.
- Run extraction against a replica or off-hours to protect order entry performance.
- Row-level security in the model by plant, company or sales region.
- Exclude cost and price fields from broad audiences.
- Gateway service account with least privilege and monitored refresh logs.
Ways to get it done
Direct connection to a replica
Effort: Days to build, but slow models if views are poor.
Small database, a few users, and simple dashboards.
Reporting database plus semantic model
Effort: Several weeks, mostly the data modelling.
Most manufacturers, with several dashboards and growing use.
Partner build with Netray, including natural-language Q&A
Effort: Scoped pilot after the reporting layer exists.
You want on-prem questions answered by a local model on top of the same model.
Pitfalls
- !Importing raw tables with cryptic names and expecting users to model them.
- !Mixing companies without a company key, which doubles totals.
- !Forgetting enumerated status decodes, so charts show numbers rather than labels.
- !Live refresh during order entry hours causing slow sessions.
Frequently asked questions
Does Power BI have a Baan connector?
There is no native Baan connector that we know of. You connect to the underlying database or through ODBC, and the practical route is a replica or reporting database that you shape for reporting.
Do we need the data gateway?
If you use the cloud Power BI service with data in your network, yes. The on-premises data gateway handles scheduled refresh without opening inbound firewall ports. Report Server style deployments inside the network do not need it.
Can we query live Baan data?
It is possible, but not recommended for large tables. DirectQuery against a production Baan database can slow users and give inconsistent timing. A replica refreshed on a schedule is safer.
How long does a first dashboard take?
If the reporting database exists, a first dashboard can take days. Building the model from raw Baan tables is the main effort and depends on how customized your schema is.
Can we ask questions in natural language?
Yes. Power BI Q&A and Copilot features work on a clean semantic model, and an on-prem model can query the reporting database directly. The quality depends on having clear names and measures.
Want Power BI working on your Baan IV / Baan V?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessmentTry it here, free
Baan IV End-of-Life Risk Cost Calculator
Quantify the hidden annual cost of running unsupported Baan IV - scarce talent premiums, outage exposure, and compliance risk - projected over five years.
New to Infor LN and Baan? Start with the Infor LN and Baan guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.
Keep exploring
Free tools
- Baan IV End-of-Life Risk Cost CalculatorQuantify the hidden annual cost of running unsupported Baan IV - scarce talent premiums, outage exposure, and compliance risk - projected over five years.
- Baan IV and Infor LN BSE Command-Line Tools ReferenceWhat each program and file under $BSE does, with a usage example and Baan IV versus LN notes: bshell, database tools, compiler, shared memory, IPC, config files and clients.
- Baan IV to Infor LN Data Copy Downtime Calculator (bdbpre/bdbpost)Plan the downtime window for a bdbpre/bdbpost data copy from your measured throughput, parallel table lists and reorganize time.
ERP fixes and how-tos
- Private AI Layer for Baan On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Baan on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Baan IV to Infor LN migration checklistPlan a Baan IV to Infor LN move as a re-implementation, not a patch: inventory customizations, convert data, rebuild logic, and run a real parallel test.
- IFS Cloud Power BI Integration Using OData ProjectionsHow to connect IFS Cloud to Power BI using OData projections, which authentication to use, and how to avoid slow reports and overloading the ERP database.
Guides
- BAAN Reporting Modernization and BI Platform MigrationModernize BAAN reporting with BI platform migration, Crystal Reports replacement, real-time dashboards, and self-service analytics for legacy BAAN environments.
- Baan ERP End of Life: What Are Your Real Options?Baan IV and Baan V are end-of-life. Explore your migration options to Infor LN, CloudSuite, or alternative ERPs with realistic timelines and costs.
- BAAN IV End of Life: Migration Options and Upgrade PathsBaan IV end-of-life migration options: upgrade to Infor LN (12-18 months), Baan to SAP S/4HANA (18-30 months), cloud ERP, or staged modernization.
AI on your ERP
- AI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the DoorUse AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.
- AI for Power BI on ERP Data: Answers Beyond the Dashboard You Already BuiltAdd grounded natural-language answers on top of Power BI semantic models and live ERP tables, with row-level security respected and models served on-prem.
Integrations
- How to connect Power BI to Infor LNHow to connect Power BI to Infor LN: direct database, ION and Data Lake options, on-prem data gateway, key manufacturing dashboards and adding natural-language Q&A.
- How to use ChatGPT with Baan IV and Baan VUsing ChatGPT with Baan IV or Baan V: exports versus live access, custom GPT actions, enterprise data controls, and when a private on-prem model is the safer choice.