Search Results igs_da_ftr_val_map_pk

Overview

The table IGS_DA_FTR_VAL_MAP is a data storage object within the Oracle E-Business Suite (EBS) Student System (IGS). As indicated by its description, its primary role is to serve as a mapping repository between configurable features and their corresponding lookup values. This structure is essential for maintaining referential integrity and enabling dynamic configuration within the student system's functionality. It is critical to note that the IGS module is marked as "Obsolete" in the provided ETRM metadata, signifying that this table and its associated features are part of a legacy codebase that is no longer under active development. Furthermore, the documentation explicitly states it was "Not implemented in this database," which suggests the table's structure was defined but may not have been deployed or populated in standard instances, or its functionality was superseded.

Key Information Stored

Based on the documented primary key, the table's structure is anchored by the FEATURE_CODE column. This column uniquely identifies a specific configurable feature within the system. While the full column list is not provided in the excerpt, the table's purpose implies the existence of at least one additional column to store the mapped "lookup values." This would typically be a VALUE column or a set of columns (e.g., LOOKUP_TYPE, LOOKUP_CODE) that define the permissible or assigned values for the given FEATURE_CODE. The primary key constraint IGS_DA_FTR_VAL_MAP_PK on FEATURE_CODE enforces the rule that each feature has a single, definitive mapping record within this table.

Common Use Cases and Queries

The primary use case for this table would be to retrieve the valid lookup values for a specific configurable feature, often for validation, defaulting, or display purposes within application forms or batch processes. A typical query would involve joining this table to a feature definition table using the FEATURE_CODE. Given the obsolete status, direct operational use in current implementations is unlikely. However, analysis or data migration efforts for legacy data might require querying this mapping. A sample SQL pattern to retrieve all mappings would be:

• SELECT feature_code, lookup_value FROM igs_da_ftr_val_map ORDER BY feature_code;

Reporting use cases would center on auditing the configuration setup, such as generating a list of all configurable features and their associated value sets.

Related Objects

The ETRM metadata documents two explicit foreign key relationships where other tables reference IGS_DA_FTR_VAL_MAP via the FEATURE_CODE column. This confirms its role as a master table for feature definitions.

• IGS_DA_CNFG_FTR: The foreign key from IGS_DA_CNFG_FTR.FEATURE_CODE references this table. This suggests IGS_DA_CNFG_FTR stores details of configured features, which are validated against the master list of mappable features in IGS_DA_FTR_VAL_MAP.
• IGS_DA_REQ_FTRS: Similarly, the foreign key from IGS_DA_REQ_FTRS.FEATURE_CODE references this table. This table likely stores features required for specific processes or entities, again relying on the master mapping for valid feature codes.

These relationships indicate that any transactional data involving a FEATURE_CODE would be validated against the entries in IGS_DA_FTR_VAL_MAP to ensure data consistency.