Explore this series on enabling AOR-based security in Fusion HCM Analytics

This article provides an overview of Oracle Fusion Cloud HCM Areas of Responsibility (AOR) and how they’re used to enable AOR based security in Oracle Fusion HCM Analytics. It describes key concepts and steps to use AOR and lists additional posts that cover detailed use cases. 

This summary article brings together links to all AOR-related blogs, making it easy to navigate detailed AOR scenarios.

This section will be updated with the links as each of the articles is published.

What are Areas of Responsibility?

Areas of Responsibility (AOR) in Oracle Fusion Cloud Human Capital Management (Fusion HCM) allow you to set security roles based on a person’s or team’s scope of responsibility, which determines which records they can see and act on. This approach has distinct advantages, including improving security performance and reducing the number of profiles and data roles that you must manage and update as people’s roles change.

For details, see the documentation for assigning areas of responsibilities and guidelines for securing person records using AORs.

The AOR Security Configuration Flow: From Fusion Applications to FDI

The AOR security implementation follows a multi-step process:

  • Oracle Fusion Cloud HCM Prerequisites
  • Oracle Fusion HCM Analytics Security configuration
    • Enable HCM Security configurations functional area
    • Auto-provisioning roles in FDI
    • Map auto provisioned application roles to FDI Groups (Cloud HCM Job Roles)

AOR Security Flow

How AOR Security Works in FDI

When a user creates a report or dashboard in FDI, the system automatically:

  • Identifies the user’s application role assignments
  • Retrieves the assigned AOR values of the user for any dimension (Single dimension or 2 dimensions in single AOR as permitted in Cloud HCM)
  • Applies filters to the query to restrict data to authorized values
  • Returns only the data that the user has permission to view based on AOR assignments

What Users Experience

  • Seamless Access: Users access reports and dashboards normally without needing to specify security filters.
  • Automatic Filtering: Data is automatically filtered to their authorized scope.
  • Consistent Security: The same security rules apply across all reports and dashboards.

Conclusion

Configurable Area of Responsibility in FDI provides robust, scalable security that ensures users access only the data appropriate to their organizational roles. By understanding the end-to-end flow from Person Security Profile configuration in Fusion Applications, through AOR assignments, to reporting results in FDI, organizations can implement effective data security that safeguards sensitive information while enabling analytics.

The key to successful AOR implementation is:

  • Thoughtful profile design aligned with organizational structure
  • Proper configuration in both Fusion Applications and FDI
  • Thorough testing with representative users
  • Ongoing monitoring and maintenance

When implemented correctly, configurable AOR becomes invisible to end users. They simply access the analytics they need, confident that security is automatically enforcing appropriate boundaries.

Call to Action

Follow the steps outlined in this article, along with the detailed article, to configure Area of Responsibility (AOR)-based security in Oracle Fusion HCM Analytics.

If you have any questions or run into any issues, post them in the Oracle Analytics Community, where you can also ask questions and post ideas.

For more information about Oracle Fusion HCM Analytics, see the Help Center Documentation.