How to connect Power BI to SAP Business ByDesign
Short answer
The standard route is to publish analytics data sources from ByDesign as custom OData services and load them into Power BI with the OData feed connector. For larger volumes or history, copy the data into a warehouse first and point Power BI at that.
ByDesign has its own reporting in the Business Analytics work center, and for many questions it is enough. Teams reach for Power BI when they want to combine ERP data with other sources, build a shared executive dashboard, apply the corporate Microsoft stack, or keep history longer than operational reports allow.
The integration is not a database connection. ByDesign is multi-tenant SaaS, so there is no SQL access to its tables. You work through the interfaces SAP exposes, which shapes how you design models, refresh schedules and row volumes.
This page covers the connection options, the dashboards manufacturers usually build first, and how to add natural-language questions on top without bypassing the data model.
What teams use it for
Order book and backlog
Open sales order value by customer, requested week and delivery status, with late lines highlighted for the planner.
Supplier on-time delivery
Compare confirmed and actual receipt dates by supplier and material group to find chronic delays.
Inventory health
Stock value by site, slow movers and stock below safety level using stock and planning data sources.
Margin by product and customer
Combine invoiced revenue with cost data to rank profitability and spot discount creep.
Cash and receivables ageing
Open customer items by ageing bucket with expected payment dates, shared with finance and sales leaders.
Project or service profitability
For project-based businesses, budget versus actual effort and cost by project and resource.
SAP Business ByDesign integration surface
- Analytics data sources in the Business Analytics work center, which can be released for use in custom OData services. This is the usual source for Power BI.
- Custom OData services, consumed by the Power BI OData feed connector with basic authentication for a technical user; check how your tenant requires credentials to be configured.
- Reports exported to Excel or CSV for a one-off or small dataset, loaded through files in OneDrive or SharePoint.
- SAP's analytics tools and data warehouse offerings as an alternative where licensed; availability depends on your contract and release.
- Your own warehouse or lake (Azure SQL, Fabric, Snowflake) loaded on a schedule by a pipeline that calls the OData services, then used as the single Power BI source.
How it works
- 1
Inventory the questions
List the dashboards you need and the grain of each: line, document, day. Grain drives row counts.
- 2
Prepare data sources in ByDesign
Create or adjust analytics data sources with the needed fields and key figures, and release them for OData use following SAP's process for your release.
- 3
Create a technical user for reporting
Give it a business role limited to the relevant data and use it only for the refresh. Do not use a named employee.
- 4
Load with Power Query
Use the OData feed connector, select only needed columns and filter by date at the source to avoid pulling history on each refresh.
- 5
Choose direct refresh or a warehouse
For small data, scheduled refresh in the Power BI service may be enough. For large or historical data, land snapshots in a warehouse and add incremental refresh.
- 6
Build the model and publish
Create a date table, relationships and measures. Publish to a workspace with row-level security if audiences differ.
- 7
Add natural-language Q and A
Use Power BI's own Q and A or Copilot features if licensed, and curate synonyms. For deeper questions use a grounded assistant over the same model.
Example flows
Weekly backlog dashboard
Trigger: Scheduled refresh each morning before the planning meeting.
- Power BI calls the order data source filtered to open lines.
- Measures calculate value by week and days late.
- The planner opens the report and filters by plant.
- Late lines drill through to the document ID in ByDesign.
Result: A shared, current backlog view instead of manual spreadsheet exports.
Supplier delivery scorecard
Trigger: Month start, when purchasing reviews suppliers.
- A pipeline lands purchase order and goods receipt data in the warehouse nightly.
- Power BI reads the warehouse with incremental refresh.
- A measure compares confirmed and actual dates.
- Buyers see rankings and trend lines per supplier.
Result: Evidence for supplier reviews that does not depend on someone building a report by hand.
Keeping data on-prem
Because ByDesign is cloud-hosted by SAP, you normally do not need an on-premises data gateway to reach it, since the OData endpoints are reachable over the internet. The gateway becomes relevant when your warehouse or other sources sit inside your network. Keep the extraction pipeline and warehouse in your environment if your policy requires it, and have Power BI read the warehouse through the gateway. Natural-language questions over the same data can be served by a private model that reads the warehouse, so no row ever goes to a hosted language model.
Security checklist
- Use a read-only technical user with the narrowest role that covers the data sources.
- Apply row-level security in Power BI where different audiences should see different companies or plants.
- Store credentials in the Power BI service data source settings, never in shared files.
- Restrict workspace access and sensitivity labels for pricing, cost and payroll-related content.
- Review what Copilot or Q and A sends to Microsoft services under your tenant settings.
Ways to get it done
Excel export into Power BI
Effort: Hours, but manual refresh.
Good for a first dashboard or small data volumes.
OData feed from custom services
Effort: Days per data source including testing.
The standard approach for scheduled dashboards on moderate volumes.
Warehouse plus Power BI via a partner
Effort: A few weeks for the pipeline and first models.
Fits larger data, history, multi-system reporting and private natural-language access, which Netray can add.
Pitfalls
- !Expecting SQL access to ByDesign tables; there is none on a SaaS tenant.
- !Pulling full history on each refresh and hitting timeouts or service limits.
- !Using key figures without checking aggregation behaviour, which leads to totals that disagree with ByDesign reports.
- !Leaving a named employee's credentials in the data source, which breaks when they leave.
- !Ignoring time zone and posting date versus document date differences between systems.
Frequently asked questions
Can Power BI connect directly to SAP Business ByDesign?
Yes through OData feeds that you publish from analytics data sources, using the OData feed connector. There is no direct database connection because ByDesign is a hosted multi-tenant service.
Do I need an on-premises data gateway?
Usually not for ByDesign itself, because its endpoints are reachable over the internet. You may need a gateway if you also read from a warehouse or database inside your own network.
Why does my Power BI total differ from the ByDesign report?
Common causes are different aggregation of key figures, date logic such as posting versus document date, filters applied in the data source, and unreleased or draft documents. Reconcile one slice first, then scale.
When should I use a data warehouse?
When volumes are large, you need history beyond what operational reports keep, you combine ByDesign with other systems, or refresh times are becoming a problem. It also gives a single place for natural-language access.
Can I ask questions in plain English?
Power BI offers Q and A and Copilot depending on licensing, and they work best on a well-named model. For questions that span systems or need strict data control, a private assistant over the same model is an option.
More for SAP Business ByDesign
Want Power BI working on your SAP Business ByDesign?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment