Categories
- All Categories
- 141 Oracle Analytics News
- 26 Oracle Analytics Videos
- 14.7K Oracle Analytics Forums
- 5.6K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 52 Oracle Analytics Trainings
- 12 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
Oracle Fusion Data Intelligence - Addressing Data Mismatch Scenarios
This video provides essential guidelines to help perform preliminary checks and independently resolve data mismatch or validation issues before escalating them. The objective is to enable proactive issue resolution whenever possible.
Key Validation Checks:
- Understanding Data Sources:
- Fusion serves as the source for both OTBI (via View Objects - VOs) and Fusion Data Intelligence (FDI) (through ETL code and VOs).
- It is crucial to distinguish between Transactional (OLTP) and Analytical (OLAP) data, as their logic and purpose differ.
- Any data discrepancies require an investigation on the Fusion side to review Fusion-specific configurations.
- Module Configuration & Permissions:
- Ensure that all module prerequisites, such as permissions and roles, are correctly configured, especially for newly added modules.
- Error Table Checks:
- Check error table records for any rejected data. If records are missing, it could indicate incomplete or missing data.
- Deleted Records Handling:
- If a record is deleted in the Fusion UI but still appears in Fusion Data Intelligence, perform a soft reset of the relevant module to remove the deleted data and synchronize the records.
- Missing Transactions in Fusion Data Intelligence:
- If a transaction exists in the Fusion source but is missing in Fusion Data Intelligence, verify whether the record was created before the initial extract date.
- POD Synchronization Issues:
- Synchronization issues in the POD environment may indicate the need for a P2T sync at the Fusion Applications (FA) source.
- Source Changes & Reloads:
- A full reload of the source is required if:
- A P2T sync was performed.
- The Fusion Applications (FA) source was changed.
- A full reload of the source is required if:
- Targeted Resets for Data Accuracy:
- If data discrepancies occur in a specific source (e.g., Fusion, BIP, Salesforce, Eloqua), perform a source-specific reset instead of a full reset. This minimizes impact and reduces downtime.
- Warehouse Reset Caution:
- A warehouse reset is a permanent and irreversible action. Once initiated, it cannot be stopped or canceled. It should be performed only as a last resort.
For further reference, we have included a link to the official documentation covered in this video, along with additional product documentation (View latest version) for more detailed guidance. Documentation link:
KB168876 - Best Practices to Avoid Data Mismatch and Validation Issues:
Fusion Analytics modules' prerequisites:
Fusion ERP Analytics FAQ:
FDI Data Validation Feature:
Comments
-
Super helpful information & the documents.
Thanks for sharing @RanaAshutosh-Oracle!
1 -
Thanks for the information! I have a related question. In some cases, there is a field that seems to be missing from the FDI subject areas. An example is the "Quantity" field in the AP Expense (invoice line item) Subject Area. What is the recommended path to address these issues? Thanks for your help!
0 -
@Ann_Roth You can modify custom and prebuilt subject areas. Modify a custom subject area to change the previously selected data elements or add more data elements and modify a prebuilt subject area to add more data elements.
Please refer :
Modify Subject Area
Add Columns
0
