Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: compatible with BI Broker Mode (Oracle Fusion Cloud Applications - FSCM(ERP & SCM))

Answered
Deepesh Jain User

We have requirements for 30 minute latency and we need ~90 PVOs to be incrementally synched in that period of time. 
Per Oracle's Best Practice documentation (https://docs.oracle.com/en/cloud/saas/procurement/24d/fainp/prc-business-intelligence-cloud-connector.html#Best-Practices)

"Use broker mode to enhance the performance of data fetching. Broker mode helps parallel processing and efficient data transfer, which significantly improves the speed and reliability of large data extractions." 
Since this is such an important issue for us, we have experimented enabling Broker mode and setting the Initial Extract Date and chunking parameters at the data source level. 
These parameters were not used by the Fivetran BICC job, so we even modified the Fivetran job to use Broker mode and Initial Extract Date. The synch still ignored these parameters and it appears these job settings were cleared by the connector. 

Can this be made an urgent product feature enhancement? 

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Deepesh, 

    At this time Oracle Fusion source itself does not allow enablement of Broker mode via API. This is a key blocker for us to use Broker mode. We've created a request for Oracle to support this here. Please help upvote this so that it can be prioritized by Oracle. 

    Frank

  • Andy Thompson User

    Thanks for cutting and pasting from my original incident.  What the feature request really should say is:

    By default, please change your Fusion connector to attempt to use BI Broker mode for all extracts. Given, some objects aren't compatible, it should attempt it for all when it creates it's BICC jobs.  This will ensure extracts execute as fast as possible.  Additionally, please add the ability to  pass thru user-selected BICC job parameters for each PVO.  In particular, the Initial Extract Date.  (perhaps, chunking parameters at the data store level, too.)

  • Chris Tyler User

    This is a critical feature.  Extracts will not complete based on current capabilities.