Payroll Balances data validation between OTBI and FDI can be performed reliably when both reports use the same comparison context.
Sharing an approach we used to validate Payroll Balances across both platforms.
The key is to build side-by-side reports with aligned parameters and compare the values at the same level of granularity.
Validation context | OTBI (Payroll - Payroll Balances Real Time) | FDI - HCM - Workforce Rewards - Payroll Balances | Guidance |
|---|
Time | Period Name, Period Number | Year, Quarter, Month, Period Name, Period Number | Use one closed comparison window (year/quarter/month) |
Business Unit | Business Unit Name | Business Unit Name | Select the same Business Unit in both the reports |
Payroll | Payroll Name | Payroll Name | Select same Payroll in both the reports |
Base dimension | Base Dimension Name | Base Dimension Name | Mandatory filter in both the reports |
Base category filter | Base Category Name | Base Category Name | Same Base categories on both the reports (e.g., Standard Earnings / earnings, Supplemental Earnings) |
Measure | Balance Value | Related balance metrics (Standard Earnings, Supplemental Earnings) | Compare totals first, then drill down to balance names and Job details |
Download the attached report exports and import them in to your environment. Update the parameters to match your organization's setup and use these reports to validate data for a selected period, Business Unit, Payroll Name, Base Dimension and Base Category.
Key Considerations:
If numbers still do not match:
- Validate the Cloud HCM Balance Group configuration to ensure the Analytics Warehouse Balance Group mapping includes all expected balance names.
- Review FDI Reporting Configuration under Advanced > Payroll Metric Configuration and ensure it is configured as per oracle guidelines :
HCM Payroll Balance Group Guidelines. - Pay close attention to the anchor date in FDI pipeline configurations , this determines how data is reported. If the payroll effective date is selected, results may differ compared to using the date earned.
- Oracle Fusion Data Intelligence reflects data as of the last successful pipeline run date only. Any updates made in Oracle Fusion Cloud Applications after that run are not yet synchronized, which can cause temporary mismatches between the two systems.
