Search Results frm_user_value_mappings




Overview

The FRM_USER_VALUE_MAPPINGS table is a Report Manager (FRM) repository object in Oracle EBS 12.1.1 and 12.2.2 that stores the mappings between application users and specific values, along with the permissions granted to those users for those values. In practice, it functions as an authorization and value-assignment table: it answers the question of which user is permitted to see or act upon which value within a defined value set. The table resides in the FRM schema and is reported as VALID in the ETRM 12.2.2 physical schema metadata.

Under the heuristic Data Vault classification mined from its foreign key structure, FRM_USER_VALUE_MAPPINGS is satellite-leaning. This suggests that it is best modeled as a descriptive satellite attached to a hub or link (here, the value set and value identifiers plus the user), rather than as an independent hub. Modelers should treat it as an attribute-bearing association table that records permission state against a business key.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • VALUE_SET_ID – Identifies the value set to which the mapped value belongs; part of the primary key and the foreign key to FRM_PART_VALUE_SETS.
  • FLEX_VALUE_ID – Identifies the specific value within the value set that the user is mapped to; part of the primary key.
  • USER_ID – Identifies the application user receiving the mapping/permission; part of the primary key.
  • VALUE – The descriptive or display value associated with the mapping.
  • PERMISSION_CODE – The permission granted to the user for the referenced value (for example, read versus update privileges).
  • OBJECT_VERSION_NUMBER – Optimistic locking column used by the Framework to detect concurrent updates.
  • CREATION_DATE, CREATED_BY – Standard audit columns recording who created the row and when.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns recording the most recent modification, its author, and the login session.

The surrogate primary key is FRM_USER_VALUE_MAPPINGS_PK, defined over (VALUE_SET_ID, FLEX_VALUE_ID, USER_ID). A unique index, FRM_USER_VALUE_MAPPINGS_UK1, covers the same three columns and represents the business-key candidate. Because the PK and UK share the same column set, the combination of value set, value, and user is guaranteed unique.

Common Use Cases and Queries

Typical uses include reporting which users are authorized for a given value, auditing permission grants, and joining mappings to value-set definitions for access reviews. A representative query to list permissions for a value set is:

  • SELECT user_id, flex_value_id, value, permission_code FROM frm.frm_user_value_mappings WHERE value_set_id = :p_value_set_id;
  • SELECT value_set_id, flex_value_id, user_id, permission_code FROM frm.frm_user_value_mappings WHERE user_id = :p_user_id;

Because OBJECT_VERSION_NUMBER is present, reporting should always read the current row state rather than cached extracts. For access certification, join to FRM_PART_VALUE_SETS on VALUE_SET_ID to resolve value-set names, and filter by PERMISSION_CODE to isolate elevated permissions.

Related Objects

The most significant related objects, grounded in the documented relationships, are:

  • FRM_PART_VALUE_SETS – Parent table joined via FRM_USER_VALUE_MAPPINGS.VALUE_SET_ID = FRM_PART_VALUE_SETS.VALUE_SET_ID; the FK identifies the owning value-set definition.
  • FRM_USER_VALUE_MAPPINGS_PK – The primary key constraint enforcing uniqueness of VALUE_SET_ID, FLEX_VALUE_ID, and USER_ID.
  • FRM_USER_VALUE_MAPPINGS_UK1 – The unique index implementing the business-key candidate over the same three columns.

Additional dependencies typically include FRM value and value-set definition objects referenced by FLEX_VALUE_ID, and user-identity tables referenced by USER_ID within the EBS application schema. These joins are essential when translating the numeric identifiers into human-readable value and user names for audit and reporting purposes.