Oracle Analytics BICC vs BIP

JoyP

From Oracle documentation I understand that BI Publisher (BIP) and BI Cloud Connector (BICC) is used for exporting bulk data from ERP Cloud

I have used BIP in the past and am aware of the use cases. I am keen to know the use cases of BICC . E.g. why should one use BICC and not BIP ?

[Deleted User]

BI Publisher is a reporting tool. Not a bulk data extractor: https://docs.oracle.com/en/cloud/saas/procurement/22a/fapaa/overview-of-business-intelligence-publisher.html#:~:text=Oracle%20Business%20Intelligence%20(BI)%20Publisher,reports%20against%20any%20data%20source.

BI Cloud Connector is a literally a bulk data extract and load tool: https://docs.oracle.com/en/cloud/saas/applications-common/22a/biacc/BICCCOverview=GUID-E67B0BE3-EE62-4C63-B52E-64393797A4DE.html

Two different tools for different use cases.

JoyP

Hi Christian,

Thanks for your reply. I am aware that BIP is a primarily reporting tool. However Oracle also recommends BIP as a bulk data export tool using OIC. Have a look at the link below.

https://docs.oracle.com/en/cloud/paas/integration-cloud/int-get-started/extract-bulk-data-oracle-erp-cloud-ftp-server.html

My question is around this - in BIP you can write any query, joining multiple tables and export bulk data . Where as BICC can pretty much has limited capabilites in terms of joins and customization and can only do a part of what BIP can achieve. So yeah - when and why would I use BICC when I can achieve the same results in BIP.

Regards

Joy

[Deleted User]

Hi Joy,

Just because it is a possibility doesn't mean it should be done or that it's even a good idea

Mass export, transformation and load of dat should be handled by bespoke tools for that purpose. I wouldn't use BIP as kind of the "ETL/ELT layer for creating a new DWH or data mart".

C. Joseph

Thank you for this post. We are considering using BICC for the first time to extract Procurement data for load to an external dashboarding tool. Our customers currently run BIP reports with customized SQL with multiple JOINs to extract the needed data for existing dashboards. From Joy's comment that BICC is limited in terms of joining tables and customizing what's extracted, we do have some specific needs and hoped to leverage logic from multiple core BIP reports to create the extract file. Based on reading the BICC documentation, BICC has limited capabilities in configuring the extracted data and really is just that - an extract tool. Based on this, we will either return to a BIP report so that the extracted data is dashboard-ready or consider multiple extracts from separate SaaS Procurement/Inventory tables and perform transformation/customization in the dashboarding tool.