Forum Discussion
Challenges moving Oracle Fusion data into a data warehouse for reporting?
Beyond the issues already mentioned in your post (reporting gaps, slow queries, API limits, schema changes, etc.), here are additional real-world challenges teams face when extracting Oracle Fusion data into a data warehouse:
- Limited Joinability Across Subject Areas - OTBI and BIP subject areas are siloed
- Inconsistent Business Definitions - Same KPI or field name may mean different things in different subject areas
- Frequent Logic Changes in Upstream Systems- Fusion configurations or setups may change
- Access & Security Model Limitations - OTBI/BIP reports reflect user security roles — which can limit access to full datasets during extraction
- Lack of True CDC (Change Data Capture)
- Version Skew Between Environments
What can be done different
- Build schema drift detection into the pipeline early on
- REST APIs or BI Cloud Connector (BICC) wherever possible, and only use OTBI for ad hoc needs or pre-built summaries.
- Design robust watermarking strategies (composite keys, last run logic)
If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Super User
Beyond the issues already mentioned in your post (reporting gaps, slow queries, API limits, schema changes, etc.), here are additional real-world challenges teams face when extracting Oracle Fusion data into a data warehouse:
- Limited Joinability Across Subject Areas - OTBI and BIP subject areas are siloed
- Inconsistent Business Definitions - Same KPI or field name may mean different things in different subject areas
- Frequent Logic Changes in Upstream Systems- Fusion configurations or setups may change
- Access & Security Model Limitations - OTBI/BIP reports reflect user security roles — which can limit access to full datasets during extraction
- Lack of True CDC (Change Data Capture)
- Version Skew Between Environments
What can be done different
- Build schema drift detection into the pipeline early on
- REST APIs or BI Cloud Connector (BICC) wherever possible, and only use OTBI for ad hoc needs or pre-built summaries.
- Design robust watermarking strategies (composite keys, last run logic)
If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!