We’re experiencing data accuracy issues with our Schedule Management reports in Oracle Fusion Cloud 23c. The OTBI report shows scheduling data that doesn’t match our operational dashboard. We’ve checked the report data source configuration and it points to the correct subject area, but discrepancies appear in resource allocation percentages and task completion dates.
The report filters are set to show active schedules from the last 90 days, but some completed projects from 6 months ago are appearing in the results. When we drill down into specific schedule data, the assignment dates differ from what’s recorded in the Schedule Management module itself. This is causing confusion for our project managers who rely on these reports for capacity planning.
Has anyone encountered similar issues with schedule data synchronization in OTBI reports? We need to understand if this is a data refresh timing issue or something with how the report filters are being applied to the underlying schedule data.
I spent two weeks troubleshooting this exact scenario last quarter. Here’s what you need to check systematically:
Report Data Source Configuration:
First, verify your subject area is using the correct presentation layer. Navigate to Administration → Manage BI Presentation Catalog → Subject Areas and confirm your Schedule Management subject area points to the right database schema. Often after updates to 23c, subject area mappings can get reset to default configurations.
Schedule Data Synchronization:
The core issue is likely in your ETL process timing. Schedule Management data flows through a staging area before reaching the analytics warehouse. Check your scheduled processes under Tools → Scheduled Processes → Schedule New Process. Look for “Refresh Schedule Analytics” jobs and verify they’re running successfully. The default frequency is every 4 hours, but if your operational data changes more frequently, you’ll see lag.
For the specific discrepancy you’re seeing:
Go to your report definition and examine the filters section
Change your date filter from “Status = Active AND Last 90 Days” to use explicit date comparisons: “Completion Date IS NULL OR Completion Date >= TIMESTAMPADD(SQL_TSI_DAY, -90, CURRENT_DATE)”
Add a secondary filter: “Schedule Status IN (‘Active’, ‘In Progress’) AND Effective End Date IS NULL”
Report Filter Optimization:
The completed projects appearing from 6 months ago indicates your filters aren’t properly handling effective dating. Schedule data uses temporal tables with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns. Your report needs to filter where EFFECTIVE_END_DATE is null or greater than your target date range.
Create a custom filter in your report:
Add a filter on “Schedule Effective End Date” IS NULL
OR “Schedule Effective End Date” >= CURRENT_DATE - 90
AND “Schedule Status” NOT IN (‘Completed’, ‘Cancelled’, ‘Archived’)
This three-part filter logic ensures you’re only seeing currently active schedule records within your desired timeframe.
Validation Steps:
After making these changes, run a comparison query directly against the Schedule Management transactional tables using SQL Developer to verify your report results match. If discrepancies persist, you may need to rebuild your subject area cache or contact Oracle Support to verify your 23c analytics warehouse configuration is correct.
The assignment date differences you mentioned suggest you might also need to check if you’re pulling from the right date column - there’s often confusion between Created Date, Scheduled Start Date, Actual Start Date, and Assignment Date in schedule reports.
This draft is based on general Oracle Fusion Cloud knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
I’ve seen this before. Check your incremental data refresh settings in the OTBI catalog. Schedule data often has a delayed sync cycle compared to real-time operational data. Navigate to your subject area properties and verify the refresh schedule - it might be running only once daily while your operational dashboard pulls live data.
We had a similar problem last year. The issue was with our report filters not properly handling schedule status changes. When a schedule moves from ‘Active’ to ‘Completed’, there’s a transition period where the status flag might not be immediately reflected in the analytics warehouse. Try adding an explicit date range filter based on actual completion dates rather than just status flags. Also verify your schedule data source includes the right effective dating parameters.
Check if you have any custom attributes or flexfields in your Schedule Management setup. These sometimes don’t map correctly to the OTBI subject areas unless explicitly configured. I’d recommend opening the subject area in the BI Administration tool and verifying that all your schedule-related dimensions are properly joined to the fact tables. The discrepancy in assignment dates specifically suggests a problem with how temporal data is being handled in your star schema.
This could be a caching issue at the report level. OTBI caches query results based on your cache persistence settings. If your operational dashboard bypasses the cache or has different cache invalidation rules, you’ll see data mismatches. Try purging the cache for your Schedule Management reports and see if that resolves the immediate issue. Long-term, you’ll want to align your cache refresh policies with your data warehouse ETL schedule.
Have you validated that your report is using the correct logical SQL? Sometimes when you create reports through the wizard, it doesn’t properly apply all the necessary filters from the underlying schedule data model. I’d suggest reviewing the Advanced SQL tab in your report definition to see if there are any WHERE clauses that might be pulling in historical data unintentionally. The 6-month-old completed projects appearing suggests your date filtering logic might be using OR instead of AND conditions somewhere in the query structure.