Understanding Secured List Views in Oracle BI Publisher
Oracle BI Publisher supports robust security controls in HCM through Secured List Views, enabling organizations to restrict report data dynamically based on users’ roles and privileges. This blog post explores how Secured List Views work and why they are crucial for compliant, secure reporting in Oracle Cloud HCM.
What Are Secured List Views?
Secured List Views are database views configured to enforce row-level security on sensitive data for BI Publisher reports. They provide data access control by filtering the rows a user can see, ensuring that sensitive information is only available to authorized individuals.
How Do Secured List Views Enhance Reporting Security?
Role-Based Filtering: Secured List Views apply predicates that restrict data based on the user’s assigned roles.
Dynamic Security: The filtering adapts dynamically to the user running the report, so a single report template can be safely reused across multiple user groups.
Simplified Report Development: Developers can build reports off secured views rather than embedding complex security logic in the SQL query or BI Publisher template.
Compliance Assurance: Helps organizations meet data privacy and audit requirements by preventing unauthorized data exposure.
How Do Secured List Views Enhance Reporting Security?
Human Capital Management reports exposed to different managerial levels only show relevant employee data.
Payroll reports can be filtered by payroll, legislative data group, or legal employer, depending on user access.
Procurement reports restricted to specific sourcing events or suppliers.
Best Practices
Use secured list views as the data source for your BI Publisher reports whenever possible.
Coordinate with security administrators to understand and leverage the role privileges that govern data access.
Test reports thoroughly with different user roles to verify that access controls are functioning correctly.
Keep your report templates simple by pushing security enforcement to the database layer via secured views.
Implementation Steps
Join the required secured list in the WHERE clause of your query
01.
Incorporate a secured list
Find an example below using per_person_secured_list_v :
SELECT Person.person_number
, PersonAsgmt.assignment_number
, PersonName.first_name
, PersonName.known_as
, PersonName.last_name
FROM per_all_people_f Person
, per_all_assignments_m PersonAsgmt
, per_person_names_f_v PersonName
, per_person_secured_list_v PersonSecurity
WHERE TRUNC(SYSDATE) BETWEEN Person.effective_start_date AND Person.effective_end_date
AND Person.person_id = PersonAsgmt.person_id
AND TRUNC(SYSDATE) BETWEEN PersonAsgmt.effective_start_date AND PersonAsgmt.effective_end_date
AND PersonAsgmt.effective_latest_change = 'Y'
AND PersonAsgmt.assignment_type = 'E'
AND Person.person_id = PersonName.person_id
AND PersonName.name_type = 'GLOBAL'
AND TRUNC(SYSDATE) BETWEEN PersonName.effective_start_date AND PersonName.effective_end_date
AND Person.person_id = PersonSecurity.person_id
AND TRUNC(SYSDATE) BETWEEN PersonSecurity.effective_start_date AND PersonSecurity.effective_end_date
Workforce Secured Lists
- PER_ALL_PEOPLE_F (PER_PERSON_SECURED_LIST_V)
- PER_PERSONS (PER_PUB_PERS_SECURED_LIST_V)
Payroll Secured Lists
- HR_ALL_ORGANIZATION_UNITS_F (PER_LEGAL_EMPL_SECURED_LIST_V)
- PER_LEGISLATIVE_DATA_GROUPS (PER_LDG_SECURED_LIST_V)
- PAY_ALL_PAYROLLS_F (PAY_PAYROLL_SECURED_LIST_V)
- CMP_SALARY (CMP_SALARY_SECURED_LIST_V)
- PER_ALL_ASSIGNMENTS_M (PER_ASSIGNMENT_SECURED_LIST_V)
Compensation Secured Lists
- CMP_SALARY (CMP_SALARY_SECURED_LIST_V)
Compensation Secured Lists
- PER_ALL_ASSIGNMENTS_M (PER_ASSIGNMENT_SECURED_LIST_V)
Summary
Secured List Views provide a powerful foundation for enforcing data security in Oracle BI Publisher reports. By harnessing these views, report developers can ensure users see only the data they’re authorized to access, improving security posture, reducing risk, and streamlining compliance with internal and external data governance policies.
If you are developing or managing Oracle Cloud BI Publisher reports, understanding and implementing secured list views should be a cornerstone of your reporting strategy.
Need some assistance?
Ready to bring clarity to customer, supplier and employee communications? With BI Publisher, we specialise in customising customer, supplier, and employee-facing documents such as invoices, purchase orders, payslips, and statements to meet your exact branding, compliance, and operational needs. From layout design to data logic enhancements, we help you deliver clear, consistent, and impactful outputs across your organization. Contact us today to discover how our expertise in BI Publisher can streamline your document processes and elevate your business communications.
