Results for “igs_da_ftr_values”

27 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.IGS_DA_FTR_VALUES is a reporting and integration object within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to expose the set of permissible feature code values that drive configuration-driven behaviour in the IGS data administration and admissions processing areas. In practical terms, the view acts as a consolidated value list: it resolves the feature value type definitions held in the feature value mapping table against the corresponding lookup meanings registered in the Oracle Application Object Library, producing a human-readable description alongside the coded value.

Because the view draws values from FND_LOOKUP_VALUES_VL, it is frequently consulted when form or report configuration requires the valid entries for a given lookup type. The "yes_no" search that surfaced this object reflects a common enquiry: users wish to understand how boolean-style indicators are represented as feature values within IGS. The view includes the lookup type YES_NO among its enumerated lookup types, so yes/no responses are exposed as feature values with their associated meaning text. The view is owned by the APPS schema and carries a VALID status, indicating it is a supported, compile-clean database object in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined as a compound query (UNION ALL) over several base objects, each supplying values for different feature codes. The documented view text references the following:

No base objects are separately documented in the ETRM metadata beyond those visible in the view definition itself; the view is therefore best understood as a presentation-layer union of lookup-driven, party-driven, and calendar-driven value sources.

Key Columns

  • FEATURE_VALUE_MEANING — the descriptive text a user sees, drawn from FND_LOOKUP_VALUES_VL.MEANING or, for party and calendar rows, from the corresponding descriptive attribute.
  • FEATURE_VALUE — the stored code, taken from LOOKUP_CODE, HZ_PARTIES.PARTY_NUMBER, or IGS_CA_INST_ALL.ALTERNATE_CODE.
  • FEATURE_CODE — from IGS_DA_FTR_VAL_MAP, identifying which configuration feature the value belongs to (for example EOI, RAI, RAY, TRM, or PAO).
  • TRANSFER_EVALUATION_IND — an indicator governing whether the feature participates in transfer evaluation processing.
  • FEATURE_VAL_TYPE — the value type controlling how the feature value is presented. Note that types LOV, DATE_PICKER, and TEXT_FIELD are deliberately excluded from the lookup-based branch.

For the "yes_no" enquiry specifically, records where the underlying lookup type is YES_NO will present the standard Yes/No meanings in FEATURE_VALUE_MEANING with their codes in FEATURE_VALUE, allowing callers to determine the accepted responses for a boolean-style feature.

Common Use Cases and Queries

The primary use case is resolving valid values for a feature code so that forms, reports, or interfaces can present or validate entries consistently. A typical enquiry lists all values for a feature code, ordered for display:

  • Retrieve every value associated with a given feature: SELECT feature_code, feature_value, feature_value_meaning FROM igs_da_ftr_values WHERE feature_code = :p_feature_code ORDER BY feature_value_meaning;
  • Resolve yes/no style values: SELECT feature_value, feature_value_meaning FROM igs_da_ftr_values WHERE feature_code = :feature AND feature_value IN ('Y','N');
  • Validate a submitted value before insertion, or drive a validation LOV in a custom form or concurrent program parameter set.
  • Populate report parameter lists for admissions transfer evaluation and reporting features, filtering by FEATURE_VAL_TYPE or TRANSFER_EVALUATION_IND.
  • Data-extraction and reconciliation queries that compare the configured feature values against reference lookup values in FND_LOOKUP_VALUES_VL.

Because the view is a union, callers should always filter by FEATURE_CODE or FEATURE_VAL_TYPE to avoid mixing organisation, calendar, and lookup value sets in a single result. This keeps result sets deterministic and aligned with the intended feature configuration.