Best practice to schedule reports on HR tablesIssue There were scheduled reports on sn_hr_core_profile table which generate blank data in the output ReleaseAny ReleaseCauseThere are ACL's configured on sn_hr_core_profile table which block reports generated by impersonating a user. Though the scheduled reports have the run-as field configured with a user who has all roles on the hr tables, it is system user who actually starts initiating the report and then impersonates the run-as field user to execute the report. As there are ACL's which will not allow an impersonated user to generate the reports on HR tables , the reports show blank data.ResolutionThere are different ways to chase this issue which are defined in this solution To have the ACL check, there is an option on the HR Properties menu under the Hr Integration module. Disabling this option will bypass the configured read ACL's and allow an impersonated user to run the reports successfully. But this is NOT recommended as a normal user who was not supposed to view HR data can impersonate the actual HR Admin user and run the reports.The best practice is to Create a new user who has ONLY web services access who is treated as a non-interactive user Use this user in the run-as field on the respective schedule reports of hr tables Modify the default read ACL on sn_hr_core_profile table this way to allow this non-interactive user to run reports answer = (new hr_CoreUtils().impersonateCheck() == false) || gs.isInteractive() == false); Note: This will stop ONLY the interactive user to generate reports by impersonation and will still allow the non-interactive users to run the reports though there are impersonated by system user when executing the scheduled reports