Integrating BI Publisher with OBIEE and E-Business Suite

Explain the common integration patterns connecting BI Publisher with OBIEE subject areas and Oracle E-Business Suite/ERP data sources.

BI Publisher rarely operates in isolation in a real Oracle shop — it's frequently the pixel-perfect output engine sitting downstream of both OBIEE's governed semantic layer and Oracle's transactional applications like E-Business Suite (EBS), and interviewers probe this to check whether a candidate has worked in a realistic, integrated Oracle stack rather than a standalone BIP sandbox.

Using an OBIEE subject area as a BI Publisher data source is like having the same trusted accountant (the RPD) prepare numbers for both the boardroom dashboard and the printed annual report — one source of truth feeding two different output formats, instead of two accountants who might disagree.

Key Concepts

The OBIEE integration pattern lets a BI Publisher data model use an OBIEE subject area directly as a data source (instead of raw SQL), meaning the data model issues logical SQL against the RPD, inheriting all of the RPD's governed calculations, aggregate navigation, and — critically — its row-level security, since the query still passes through the BI Server under the running user's security context. This is the recommended pattern whenever a pixel-perfect document needs to use the exact same "single version of the truth" metrics as the interactive dashboards, rather than reimplementing the same business logic in raw SQL a second time.

OBIEE integrationOBIEE subject arearow-level security

The E-Business Suite integration pattern is different: BI Publisher ships embedded within EBS specifically to replace legacy Oracle Reports output for things like invoices, purchase orders, and checks, pulling data via EBS's own concurrent program / PL/API layer rather than a generic SQL data model, and it's registered as an XML Publisher output type on an EBS concurrent program, meaning the report can be launched from the standard EBS Submit Request screen and inherit EBS's own responsibility-based security and concurrent manager scheduling infrastructure.

E-Business Suite integrationXML Publisher output type

A nuanced interview point: candidates should distinguish "BI Publisher standalone" (Oracle Analytics Server) from "BI Publisher embedded in EBS" — they share the same templating/data-model concepts, but the embedded EBS version is tightly coupled to EBS's concurrent processing and security model, while standalone/OAS BIP is a general-purpose reporting server that can connect to any data source, including but not limited to EBS or an OBIEE RPD.

"BI Publisher standalone" (Oracle Analytics Server) from "BI Publisher embedded in EBS"