A data source isn’t limited to one SAP OData service — you can combine several into a single endpoint. This is useful when a report needs to join data from different functional domains, for instance products from API_PRODUCT_SRV and business partners from API_BUSINESS_PARTNER.
Add another service #
On the create or edit form, select Add Service a second time. The same SAP service catalog dialog opens. Pick another service; it shows up as a second expandable panel underneath the first.
From here, you can:
- Expand each service to pick its own entities, fields, filters, and parameters — exactly as you would for a single-service data source.
- Preview the entire selection as one summary table. See Preview data.
- Open the ERD across both services to see the entities you’ve picked. See Preview the ERD.
Remove a service #
Each service panel has a trash icon on its header. Selecting it removes the service and every entity, field, filter, and parameter that belonged to it from the data source. The other services on the form are not affected.
Removal is local to the form until you save. If you change your mind, navigate away without saving to discard the change.
What Power BI sees #
From Power BI’s point of view, the data source is still one OData feed. The selected entities — regardless of which SAP service they came from — appear as separate tables under the same connection. You build the cross-table relationships in Power BI as you would for any multi-table model.
Caveat: separate metadata round-trips #
Each service requires its own metadata fetch on the first call. With two or more services, the first save and the first Power BI refresh can take noticeably longer than a single-service data source. Subsequent refreshes are fast because the metadata is cached on the back end.
Related #
- Create a data source
- Preview the ERD — the diagram shows entities from every service in one view.
