Search Results attr_type_m

Overview

IGS_OR_FUNC_FLTR_V is an Oracle E-Business Suite relational view owned by the APPS schema, defined over the Oracle Student System (formerly Oracle Higher Education / OSS) module tables IGS_OR_FUNC_FLTR and IGS_LOOKUP_VALUES. The view presents functional filter records that drive how the student system evaluates organizational unit (institutional) context for a given functional code during transaction processing. Each row pairs a functional filter with a descriptive lookup meaning, providing both the stored attribute type code and its human-readable translation. Because the underlying base stack is shared across environments, the view remains functionally identical in EBS 12.1.1 and 12.2.2; the Online Help / ETRM documentation set does not record separate definitions per release.

Underlying Base Objects

The view is defined by an inner join between two base objects:

• IGS_OR_FUNC_FLTR H — the primary filter table holding functional-level attribute configurations (filter ID, function code, attribute type, attribute value, and institutional organization value).
• IGS_LOOKUP_VALUES L — the standard EBS lookup table, joined on H.ATTR_TYPE = L.LOOKUP_CODE with the additional restriction L.LOOKUP_TYPE = 'OR_FTR_ATTR_TYPE'.

The join is an equi-join on the attribute type code, restricted to the OR_FTR_ATTR_TYPE lookup type. This means only filter rows whose ATTR_TYPE is registered under that lookup type will be returned; unregistered or misspelled codes are silently excluded, which is a common cause of "missing rows" when tuning queries.

Key Columns

• ROWID — the row identifier from IGS_OR_FUNC_FLTR, useful for direct DML targeting (the view is not inherently updatable on the lookup side).
• FUNC_FLTR_ID — primary key of the functional filter record.
• FUNC_CODE — the functional code the filter applies to.
• ATTR_TYPE — the coded attribute type (join key to the lookup).
• ATTR_TYPE_M — the lookup MEANING, i.e., the descriptive label for the attribute type; this is the column most often referenced by the search term "attr_type_m".
• ATTR_VAL_DESC / ATTR_VAL — the attribute value and its descriptive text.
• INST_ORG_VAL — institutional organization value used for org-level filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include reporting configured functional filters for a given function code, joining OR_FTR_ATTR_TYPE lookup meanings for user-facing displays, and diagnosing why a filter did not trigger (e.g., missing lookup registration).

Sample query listing active filters with their descriptive attribute types:

SELECT func_code, attr_type, attr_type_m, attr_val, attr_val_desc, inst_org_val FROM apps.igs_or_func_fltr_v WHERE func_code = :p_func_code ORDER BY attr_type;

Diagnostic query isolating functional filter rows with no matching lookup (by de-joining to the base table):

SELECT COUNT(*) FROM apps.igs_or_func_fltr h WHERE NOT EXISTS (SELECT 1 FROM apps.igs_lookup_values l WHERE l.lookup_code = h.attr_type AND l.lookup_type = 'OR_FTR_ATTR_TYPE');

Because ATTR_TYPE_M is derived via join, queries should always constrain LOOKUP_TYPE to 'OR_FTR_ATTR_TYPE' to avoid row duplication from lookup codes reused across types, and should filter on FUNC_CODE or FUNC_FLTR_ID to maintain acceptable performance on large filter tables.