Search Results ego_flex_value_set_intf

Overview

EGO_FLEX_VALUE_SET_INTF is a staging and interface table in the EGO schema (Advanced Product Catalog) in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description indicates, it stores value set definitions — the descriptive attributes of Oracle Flexfields value sets — as they are imported, loaded, or migrated into the Product Catalog and related flexfield infrastructure. Functional administrators and implementation teams use it as the landing area for bulk value set loads, conversions, and data migration from legacy systems.

The table is documented with 39 columns and a foreign key from VALUE_SET_ID to FRM_PART_VALUE_SETS, linking the interface row to its persisted counterpart in the Oracle Product Hub / Product Information Management value set repository. The ETRM heuristic Data Vault classification for this object is standalone, meaning it is best modeled as an independent entity rather than as a hub, link, or satellite. In practice, the single outgoing foreign key to FRM_PART_VALUE_SETS suggests the interface row functions as a staging satellite whose business key is the combination of VALUE_SET_NAME and VERSION_SEQ_ID, resolving to the surrogate VALUE_SET_ID in the target table after processing.

Key Information Stored

The columns fall into three logical groups: identity and versioning, validation and formatting rules, and programmatic processing metadata.

• VALUE_SET_NAME — the business key identifying the value set being described; combined with VERSION_SEQ_ID it uniquely identifies a version of a value set definition.
• VALUE_SET_ID — the surrogate identifier used to join to FRM_PART_VALUE_SETS; populated during the load/validation phase.
• VERSION_SEQ_ID and VERSION_DESCRIPTION — version sequencing and human-readable version label for the definition.
• DESCRIPTION — free-text description carried through to the persisted value set.
• VALIDATION_TYPE and FORMAT_TYPE — control how entered values are validated (e.g., independent, dependent, table-validated) and formatted (character, number, date).
• LONGLIST_FLAG — indicates whether the value set supports a longlist, affecting UI behavior in the catalog.
• PARENT_VALUE_SET_NAME — supports dependent value set hierarchies.
• START_ACTIVE_DATE and END_ACTIVE_DATE — effective-dating window for the value set version.
• MINIMUM_VALUE, MAXIMUM_VALUE, and MAXIMUM_SIZE — range and length constraints enforced during validation.
• TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME — identify the source table when VALIDATION_TYPE is table-based, with the value/ID/meaning column name, type, and size columns supplying the mapping.
• ADDITIONAL_WHERE_CLAUSE — predicate applied to table-validated lookups.
• PROCESS_STATUS, SET_PROCESS_ID, and REQUEST_ID — concurrency and batch-tracking fields that indicate a row's state in the import pipeline.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — identify the concurrent program that last processed the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard WHO audit columns present on almost all EBS interface tables.

Common Use Cases and Queries

Typical scenarios include bulk migration of legacy value sets into the Product Catalog, reconciliation of interface rows against successfully loaded value sets, and monitoring the import concurrent program.

• Pending interface rows: SELECT VALUE_SET_NAME, VERSION_SEQ_ID, PROCESS_STATUS, ERROR_MESSAGE FROM EGO_FLEX_VALUE_SET_INTF WHERE PROCESS_STATUS IS NULL OR PROCESS_STATUS = 'ERROR';
• Join to persisted value sets: SELECT i.VALUE_SET_NAME, i.VALIDATION_TYPE, v.VALUE_SET_ID FROM EGO_FLEX_VALUE_SET_INTF i, FRM_PART_VALUE_SETS v WHERE i.VALUE_SET_ID = v.VALUE_SET_ID;
• Rows by concurrent request: filter on REQUEST_ID and PROGRAM_ID to trace a specific load run.
• Effective-date validation: query rows whose START_ACTIVE_DATE and END_ACTIVE_DATE do not overlap expected fiscal periods.

Related Objects

• FRM_PART_VALUE_SETS — target parent table; joined via EGO_FLEX_VALUE_SET_INTF.VALUE_SET_ID = FRM_PART_VALUE_SETS.VALUE_SET_ID.
• FND_FLEX_VALUE_SETS — the core Flexfields value set definition table; interface rows usually resolve here after validation.
• FND_FLEX_VALUES and FND_FLEX_VALUES_TL — hold the individual values belonging to a value set once the definition is loaded.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — provide the REQUEST_ID/PROGRAM_ID context for monitoring the import run.
• EGO_FLEX_VALUES_INTF — companion interface table that carries the individual values for the value sets described here.
• EGO_ITEM_CATALOG_GROUPS_B and related catalog group tables — consume value sets for catalog attribute validation in the Product Catalog.

Because the table is an interface object, its rows are typically transient: records are inserted before a validation/import program executes and are either purged or archived after the target value sets are created. Retention and purge strategy should be defined alongside the concurrent program schedule.