Search Results frm_part_value_sets




Overview
Explore in AI Chat

Overview

FRM_PART_VALUE_SETS is an Oracle E-Business Suite table owned by the FRM (Report Manager) schema. In EBS 12.1.1 and 12.2.2, it stores the master list of value sets that are referenced by User-to-Value security within Oracle Report Manager and its dependent products. A value set in this context defines the domain of permissible values that a security rule can grant or restrict for a given user or responsibility. The table therefore acts as the registration point for every value set that participates in the Report Manager security model.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as hub-leaning. The eight-column physical definition, a single-column primary key, and the absence of descriptive satellite attributes support treating VALUE_SET_ID as a durable business key (hub) rather than a transactional or link entity. This is a modeling suggestion only; the physical implementation remains a standard EBS transactional table with WHO columns.

Key Information Stored

The documented schema contains eight columns. The most significant are:

  • VALUE_SET_ID — The surrogate primary key (FRM_PART_VALUE_SETS_PK) and also the sole business-key candidate, enforced by unique index FRM_PART_VALUE_SETS_UK1. It is referenced by every dependent table in the FRM security model.
  • PARTICIPATION_FLAG — Indicates whether the value set participates in the User-to-Value security mechanism. This flag governs whether security rules may be authored against the value set.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OA Framework and concurrent programs to detect conflicting updates.
  • CREATION_DATE, CREATED_BY — Audit columns recording when and by whom the value-set registration row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns capturing the most recent modification and the login session responsible for it.

Because the table stores only identifiers and audit attributes, descriptive value-set names and validation metadata are resolved through the underlying Oracle Application Object Library (FND) value-set definitions rather than being duplicated here.

Common Use Cases and Queries

Typical reporting and support scenarios include identifying which value sets are actively secured and tracing the security mappings that reference them. A common query joins the hub to its primary dependent table to list all user-to-value mappings for a given value set:

  • Listing active secure value sets: SELECT value_set_id, participation_flag FROM frm.frm_part_value_sets WHERE participation_flag = 'Y';
  • Tracing mappings: SELECT m.* FROM frm.frm_user_value_mappings m, frm.frm_part_value_sets p WHERE m.value_set_id = p.value_set_id AND p.value_set_id = :bind;
  • Auditing recent registrations: filter on CREATION_DATE or LAST_UPDATE_DATE to identify value sets added during a security rollout.
  • Locating orphaned registrations: outer-join to FRM_USER_VALUE_MAPPINGS to find value sets with no active mappings.

Because the table is referenced across many product schemas, it is also useful as a starting point for impact analysis before value sets are deprecated.

Related Objects

The following tables depend on FRM_PART_VALUE_SETS through the VALUE_SET_ID column and are the most significant for day-to-day investigation:

Analysts should treat FRM_PART_VALUE_SETS as a shared hub and expect value-set identifiers to appear across FRM, EGO, PA, XLA, and AME schemas simultaneously.