Search Results func_code

Overview

IGS_OR_FUNC_FLTR_V is a view within the IGS – Student System product family in Oracle E-Business Suite. Its documented description is "Organization Function Filter Details View." The view surfaces configuration records that determine how organizational units are filtered against functional attributes inside the student system. It joins the filter definition base table to the Oracle Applications lookup mechanism so that coded attribute types are presented alongside their user-facing meanings, producing a reporting-ready projection of organization function filter data.

The IGS product line is flagged as obsolete in the ETRM metadata, and the view is documented as "Not implemented in this database." This status matters for both 12.1.1 and 12.2.2 deployments: the object may not exist in a given environment, and any concurrent program, report, or interface referencing it should be validated before use. Where it does exist, it functions primarily as a query and reporting layer rather than a transactional entry point.

Underlying Base Objects

The view text defines the relationship explicitly. It is constructed over two objects:

• IGS_OR_FUNC_FLTR — the filter header table, aliased H, which stores the organization function filter records themselves.
• IGS_LOOKUP_VALUES — the standard Oracle lookup values view, aliased L, which supplies the decoded meaning for the attribute type.

The join is an equality between the filter's ATTR_TYPE column and the lookup's LOOKUP_CODE, constrained by LOOKUP_TYPE = 'OR_FTR_ATTR_TYPE'. The view also selects H.ROWID as its first column, which enables the view to be used in some updatable-context and row-identification scenarios even though it is principally a read-only projection. No additional documented base objects are recorded beyond these two.

Key Columns

• ROW_ID — the row identifier from the base filter table; used for row-level addressing.
• FUNC_FLTR_ID — primary identifier of the function filter record.
• FUNC_CODE — the function code against which filtering is applied.
• ATTR_TYPE — the coded attribute type, joined to the lookup.
• ATTR_TYPE_M — the decoded, user-facing meaning of ATTR_TYPE from IGS_LOOKUP_VALUES.MEANING.
• ATTR_VAL — the attribute value used by the filter; this column is directly relevant to the common search term "attr_val" and holds the operative filter criterion.
• ATTR_VAL_DESC — a descriptive form of the attribute value.
• INST_ORG_VAL — the institution organization value associated with the filter.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, inherited from the base table and used for change tracking and data lineage.

Common Use Cases and Queries

The view is typically used to audit or report which attribute values drive organizational function filtering, and to present those values in a readable form by decoding ATTR_TYPE through the lookup join. A representative query follows:

SELECT func_fltr_id, func_code, attr_type, attr_type_m, attr_val, attr_val_desc, inst_org_val FROM igs_or_func_fltr_v WHERE attr_val = :p_attr_val;

Filtering on ATTR_VAL is the most direct application of the view, and it can be combined with FUNC_CODE or INST_ORG_VAL to narrow results to a specific function or institution. Because the view is documented as obsolete and not implemented in the reference database, DBAs should confirm object existence in each target instance and consult the corresponding base table directly if the view is absent.