Oracle Fusion Data Extraction Tool vs BICC: What Changes for Developers
BICC has a successor. Oracle Fusion now has a Data Extraction tool that reads from a replica (RODS) instead of the live transactional database.
In this short, I cover:
How it differs from BICC, and why extraction load leaves the live pod
Where the files land: UCM, Oracle-managed OCI storage, or your own OCI bucket
The three-step flow: define, schedule, run
What changes for developers: Oracle’s BICC-to-business-view mapping sheet and user-defined queries in BQL (Business Object Query Language)
What to set up first: opt-in, custom role, profile option, OAuth for REST
Heads-up: it works on business objects, not raw tables, and coverage is still growing, so check your objects before you commit.
Official Oracle links:
Data Extraction Tool documentation: https://docs.oracle.com/en/cloud/saas/applications-common/faude/overview-of-the-data-extraction-tool.html
Oracle A-Team intro blog: https://www.ateam-oracle.com/introducing-oracle-fusions-new-data-extraction-tool
BICC-to-business-object mapping spreadsheet: My Oracle Support, KA1401
A full end-to-end demo is coming in the next video. Follow FusionGoEasy for more Oracle Fusion tips.






Comments