Current Limitation
Customers using advanced HCM Area of Responsibility (AOR) security models cannot fully replicate these security rules in FDI. In particular:
- HCM AOR Exclusion Rules cannot be natively represented in the FDI Security Framework.
- SQL-based security criteria cannot be maintained and synchronized from the HCM security model.
- Dynamic exclusion logic cannot be automatically enforced in FDI.
In previous legacy security implementations, it was possible to introduce custom predicates and query logic in the semantic layer, which partially enabled these scenarios. This capability is no longer available in the current FDI security architecture. As a result, there is currently no standard mechanism to implement advanced AOR exclusion logic in FDI.
Operational Impact
Many enterprise customers rely on dynamic security rules that change frequently throughout the day. For example, Elimination assignments currently require manual uploads and maintenance. In large organizations, manually uploading elimination data several times per day is not operationally sustainable and introduces unnecessary administration effort, data quality risks, and delays in propagating security changes.
Requested Enhancement
Extend the FDI Security Framework to support:
- HCM AOR Exclusion Rules
- Dynamic inclusion and exclusion logic
- SQL-based security criteria
- Automatic synchronization of advanced HCM security definitions
- Dynamic elimination management without manual user uploads
Business Value
- Ensure alignment between HCM security and FDI security.
- Eliminate manual maintenance of elimination assignments.
- Reduce operational risk and administration effort.
- Support enterprise-scale security models.
- Improve governance, auditability, and consistency across Oracle applications.
