Search Results igs_or_func_fltr_u2

Overview

IGS.IGS_OR_FUNC_FLTR is a configuration table in the Oracle E-Business Suite higher-education schema (IGS), which underpins the Student System and related institution-facing modules. The table stores organization function filters, the rules that determine which attributes of a functional area — typically a form or function identified by a form code — are restricted by organization or institution context within Oracle EBS 12.1.1 and 12.2.2. It is a low-volume reference/configuration object rather than a transactional table.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and is owned by the IGS schema. From a Data Vault modeling perspective, the mined relationship data classifies IGS_OR_FUNC_FLTR as standalone, and its single non-key attribute set — ATTR_TYPE, ATTR_VAL, ATTR_VAL_DESC, INST_ORG_VAL — behaves like a small satellite of descriptive filter attributes attached to a function code. Because it has no foreign keys referencing other objects and no documented inbound dependencies beyond the APPS synonym, the standalone classification is a reasonable modeling suggestion: the surrogate key FUNC_FLTR_ID functions as a hub-like identifier for each filter row rather than as a link between two entities.

Key Information Stored

The table comprises eleven columns, of which the most significant are:

• FUNC_FLTR_ID (VARCHAR2(30)) — the surrogate primary key, defined by the primary key constraint IGS_OR_FUNC_FLTR_PK and by the unique index IGS_OR_FUNC_FLTR_U1. It is the unique identifier of each filter record and is the column most commonly searched for by name.
• FUNC_CODE (VARCHAR2(30)) — the form or function code that the filter applies to; this is the principal business key used in application lookups.
• ATTR_TYPE (VARCHAR2(30)) — the attribute type code being filtered.
• ATTR_VAL (VARCHAR2(30)) — the value of the attribute type against which filtering is applied.
• ATTR_VAL_DESC (VARCHAR2(80)) — the descriptive text for the attribute value, providing a reportable label.
• INST_ORG_VAL (VARCHAR2(30)) — indicates whether the form is filtered on Organization or Institution; documented valid values are I and O.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row creation and last modification metadata.

Two indexes are documented: IGS_OR_FUNC_FLTR_U1 is a UNIQUE index on FUNC_FLTR_ID in APPS_TS_TX_IDX, and IGS_OR_FUNC_FLTR_U2 is a NONUNIQUE index on the composite business key (FUNC_CODE, ATTR_TYPE, ATTR_VAL). The composite U2 index represents the natural business-key candidate for a filter rule.

Common Use Cases and Queries

Typical usage centers on resolving which filter rules apply to a given form and on reporting the configured restrictions. A search on the identifier column retrieves the full filter row:

• Lookup by surrogate key: SELECT * FROM IGS.IGS_OR_FUNC_FLTR WHERE FUNC_FLTR_ID = :p_id;
• Enumerate filters for a form: SELECT FUNC_CODE, ATTR_TYPE, ATTR_VAL, ATTR_VAL_DESC, INST_ORG_VAL FROM IGS.IGS_OR_FUNC_FLTR WHERE FUNC_CODE = :p_func_code;
• Locate a specific rule via the composite business key: SELECT FUNC_FLTR_ID FROM IGS.IGS_OR_FUNC_FLTR WHERE FUNC_CODE = :p_func AND ATTR_TYPE = :p_type AND ATTR_VAL = :p_val;
• Report organization versus institution filtering: SELECT INST_ORG_VAL, COUNT(*) FROM IGS.IGS_OR_FUNC_FLTR GROUP BY INST_ORG_VAL;

These queries support configuration review, migration validation between 12.1.1 and 12.2.2 environments, and troubleshooting of unexpected filtering behavior in student-facing forms. Because the table is small and static, it is often extracted wholesale for comparison between instances.

Related Objects

The documented dependency data indicates that IGS.IGS_OR_FUNC_FLTR does not reference any database object and is referenced only by the APPS synonym IGS_OR_FUNC_FLTR, through which application code accesses the table. No foreign keys, views, or PL/SQL APIs are documented against it in the ETRM metadata, and its Data Vault classification is standalone. Consequently the practical relationships are logical rather than enforced: joins on FUNC_CODE and ATTR_TYPE/ATTR_VAL are made against function and organization reference data maintained elsewhere in the IGS schema, and the FUNC_FLTR_ID column serves as the join anchor for any downstream extension or configuration table that chooses to reference this object by its primary key.