Search Results frm_part_value_sets_uk1




Overview

FRM.FRM_PART_VALUE_SETS is an Oracle E-Business Suite table that records the value sets referenced by Oracle's User-to-Value security model. User-to-Value security allows an administrator to restrict what data a specific application user can see based on Flexfield values, typically via a security rule assigned to a responsibility or user. This table acts as the registry of value sets that have been participating in that security framework. It is owned by the FRM schema, has the status of VALID, and is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The table is registered in FND Design Data as FRM.FRM_PART_VALUE_SETS and is maintained under standard Oracle EBS multi-org and OA Framework conventions.

From a Data Vault modeling perspective, the mined relationship data classifies this object as hub-leaning. In practice, this means the table functions as a central, relatively stable reference point for a business concept — the value set identifier — and is referenced through foreign keys by many downstream transactional and configuration tables. This is a modeling suggestion rather than a rigid classification, but it accurately reflects the table's role as a stable anchor around which other objects cluster.

Key Information Stored

The table contains eight documented columns. The most important are summarized below:

  • VALUE_SET_ID — A NUMBER(15) column described in the metadata as an "Entity Identifier across all applications." It is the surrogate primary key of the table (via FRM_PART_VALUE_SETS_PK) and is also the only column in the unique index FRM_PART_VALUE_SETS_UK1, making it the sole documented business-key candidate. Because the identifier is global across EBS applications, it links this table to value-set definitions maintained elsewhere in the Flexfields infrastructure.
  • PARTICIPATION_FLAG — A VARCHAR2 column indicating whether the associated value set has been used by User-to-Value Security. This is the operational heart of the table: it tells consumers whether the value set is actively participating in the security model or merely registered.
  • OBJECT_VERSION_NUMBER — The applications standard column used for optimistic locking in a stateless environment, supporting concurrent update control in OA Framework-based pages.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard WHO audit columns that record provenance and the last-known update context of each row.

The surrogate primary key is VALUE_SET_ID, and the same column is the unique, business-key candidate. No other unique constraints are documented, so downstream consumers rely exclusively on the value set identifier for correlation.

Common Use Cases and Queries

The table is most frequently queried when diagnosing User-to-Value security behavior — for example, determining whether a value set is participating, or locating the value sets referenced by a responsibility's security rules. A simple lookup is:

  • SELECT VALUE_SET_ID, PARTICIPATION_FLAG FROM FRM.FRM_PART_VALUE_SETS WHERE VALUE_SET_ID = :value_set_id;
  • Listing participating value sets: SELECT * FROM FRM.FRM_PART_VALUE_SETS WHERE PARTICIPATION_FLAG = 'Y';
  • Reporting on recent changes via WHO columns: SELECT VALUE_SET_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM FRM.FRM_PART_VALUE_SETS ORDER BY LAST_UPDATE_DATE DESC;

Because the identifier is application-wide, the table is also useful as a join anchor when reconciling which modules consume a given value set — for example, joining to FRM_USER_VALUE_MAPPINGS or PA_MAP_VALUE_SETS to trace actual security assignments.

Related Objects

The table is referenced through VALUE_SET_ID foreign keys by a large number of EBS objects spanning several modules. The most significant include:

Additionally, the table is referenced by its own derived object FRM_PART_VALUE_SETS#, which typically represents the editioning or interface variant used in the 12.2 online patching architecture.