# How to connect Power BI to Baan IV and Baan V

> Source: https://netray.co/integrations/baan-power-bi
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## 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.

## System

Baan IV / Baan V

## Capability

power-bi

## Intro

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.

## Use Cases

### On-time delivery

**Description:** Promised versus actual ship dates from sales order and delivery data, by customer and product family.

### Purchase price and lead time variance

**Description:** Compare ordered prices and promised lead times to actual receipts by supplier.

### Production order status and WIP

**Description:** Open production orders with age, operations remaining and component shortages.

### Inventory ageing and turns

**Description:** Stock by warehouse and last movement date, flagged for slow movers.

### Backlog and booking trends

**Description:** Order intake and open backlog over time, by region or product line.

## System 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

### Pick the middle layer

**Detail:** A SQL Server reporting database or a lakehouse is typical. Replicate selected tables on a schedule with ETL or database replication.

### Build a business model

**Detail:** Create views with readable names, decode enumerations, and combine companies with a company column.

### Install the on-premises data gateway

**Detail:** The gateway lets the Power BI service refresh from your network without opening inbound ports.

### Build the semantic model

**Detail:** Define relationships, measures and a date table. Keep measures in the model, not in each report.

### Design a small set of dashboards

**Detail:** Begin with delivery, inventory and WIP. Resist copying every old Baan report.

### Set refresh and row-level security

**Detail:** 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.

**Steps:**

- 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.

**Steps:**

- 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.

## 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

- 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.

## Options

### Direct connection to a replica

**Fit:** Small database, a few users, and simple dashboards.

**Effort:** Days to build, but slow models if views are poor.

### Reporting database plus semantic model

**Fit:** Most manufacturers, with several dashboards and growing use.

**Effort:** Several weeks, mostly the data modelling.

### Partner build with Netray, including natural-language Q&A

**Fit:** You want on-prem questions answered by a local model on top of the same model.

**Effort:** Scoped pilot after the reporting layer exists.

## 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.

## Faq

### Does Power BI have a Baan connector?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

baan power bi, power bi for baan erp, connect power bi to baan, baan iv reporting, baan v dashboard, baan odbc power bi, baan data warehouse, baan erp analytics

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json