Search Results jtf_dac_criteria_pk

Overview

The JTF_DAC_CRITERIA table is a core data object within the CRM Foundation (JTF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is a structural component of the Data Access Control (DAC) framework, which governs the granular security and visibility rules for CRM-related data. The table's primary role is to store the specific criteria or condition sets that define the scope of data access permissions. These criteria are linked to user roles and permissions, enabling the enforcement of complex, rule-based data security policies. Notably, the official ETRM documentation explicitly advises "Do not use," indicating this is a seeded, internal table critical to the DAC infrastructure and not intended for direct customization or transactional use by implementers or developers.

Key Information Stored

The table's central column is CRITERIA_ID, which serves as the primary key to uniquely identify each criteria definition. The metadata confirms this column is the sole component of the JTF_DAC_CRITERIA_PK primary key constraint. A critical foreign key column is ROLE_PERM_ID, which links each criteria set to a specific role permission record stored in the JTF_DAC_ROLE_PERMS table. This linkage establishes which permission a given criteria set applies to. While the provided metadata does not list other columns, typical implementations of such a table would include columns to store the conditional logic (e.g., attribute, operator, value), an active date range, and creation/modification audit information.

Common Use Cases and Queries

Direct interaction with this table is strongly discouraged per the documentation. Its use cases are internal to the DAC engine's operation. The primary function is to retrieve the applicable security filters when a user attempts to access CRM data. The DAC framework queries this table to fetch all CRITERIA_ID values associated with a user's active permissions, which are then dynamically applied to data queries. A sample diagnostic query to understand existing criteria mappings might be:

• SELECT cr.criteria_id, rp.role_perm_id FROM jtf_dac_criteria cr, jtf_dac_role_perms rp WHERE cr.role_perm_id = rp.role_perm_id;

Any reporting or administrative needs related to data access security should be addressed through dedicated CRM administration interfaces or APIs, not via direct SQL against this table.

Related Objects

The JTF_DAC_CRITERIA table has documented foreign key relationships with two other DAC tables, forming the core of the security rule definition.

• JTF_DAC_ROLE_PERMS: This is the parent table. The foreign key JTF_DAC_CRITERIA.ROLE_PERM_ID references JTF_DAC_ROLE_PERMS. This join defines which role permission a criteria set belongs to.
• JTF_DAC_ROLE_PERM_CRIT: This table references JTF_DAC_CRITERIA via the foreign key column JTF_DAC_ROLE_PERM_CRIT.CRITERIA_ID. This relationship likely manages the assignment or grouping of multiple criteria records, further refining the permission structure.

These relationships underscore that JTF_DAC_CRITERIA is a central node in a network of tables designed to assemble and manage detailed data access rules.