We’re experiencing issues where timecard entries submitted by employees are missing from our BI Publisher reports. The timecards appear correctly in the Time and Labor work area, but when we run our custom attendance reports in BI Publisher, recent entries (last 2-3 days) don’t show up.
This problem started after we applied the 22D quarterly update last month. We have several custom BI Publisher reports built on HCM data models, and all of them are affected. The data eventually appears in reports after 3-4 days, suggesting some kind of sync delay rather than complete data loss.
I’m wondering if the patch affected the base tables that our BI Publisher data model references, or if there’s an issue with how our custom SQL queries are structured. Has anyone dealt with similar BI Publisher data model alignment issues after patches?
We’re using direct SQL queries against HWM_TM_TRANSACTIONS and HWM_TIME_CARD_DETAILS tables. Should we be using different tables or views after the 22D update?
Patches definitely can change underlying table structures or add new tables that should be referenced instead of old ones. First thing to check - are your custom data models querying the transactional tables directly or going through views? Oracle usually maintains views for backward compatibility but direct table access can break.
I remember reading in the 22D release notes that they deprecated some HCM tables and introduced new ones with different naming conventions. Your queries might be hitting old tables that are no longer being populated. Check the readiness documentation for 22D specifically around Time and Labor schema changes.
Look at the HCM Extract Definition and check the incremental refresh schedule. This controls when transactional data gets pushed to the reporting tables. Default schedule might be weekly, which would explain multi-day delays. You may need to increase the frequency to daily or even hourly depending on your reporting SLA requirements.