Search Results exact_include

Overview

IGS_PE_MTCH_SET_DATA is a reporting and integration view in the Oracle E-Business Suite IGS (Student System) product family. Its purpose is to expose the match set data records used by the person/entity matching engine, allowing consumers to read the configuration rules that govern how attribute values are compared when resolving or matching student and person records. The view is built over the IGS_PE_MTCH_SET_DATA_ALL table and applies an operating unit security predicate, so it presents only the rows visible to the current session's organization context.

The object belongs to the obsolete portion of the Student System module and, as documented in the ETRM metadata, is not implemented in this database. It is therefore recorded for reference and lineage purposes rather than as an active runtime object in a typical 12.1.1 or 12.2.2 instance. The presence of PARTIAL_INCLUDE in the definition directly answers the search context: that column controls whether a data element participates in partial (fuzzy/non-exact) matching.

Underlying Base Objects

The view is defined exclusively over the single base object IGS_PE_MTCH_SET_DATA_ALL, aliased as TAB. No additional referenced base objects are documented in the metadata. The _ALL suffix indicates the underlying table is a multi-organization (operating unit) table; the view does not, however, project a ROW_ID from the base table directly but rather exposes TAB.ROWID as ROW_ID.

The organization security filter is expressed through a comparison of the ORG_ID column against the client information captured by USERENV('CLIENT_INFO'). The predicate decodes the leading ten characters of the CLIENT_INFO value, substitutes NULL for a single blank first character, and converts the result to a number. A default of -99 is applied where no organization can be derived, matching rows whose ORG_ID is likewise defaulted. This is the standard multi-org view construction pattern used throughout EBS, ensuring that only records belonging to the session's operating unit are returned.

Key Columns

• ROW_ID — The physical row identifier of the base table row, exposed for direct row addressing.
• ORG_ID — The operating unit identifier, used both for the security predicate and for partitioning match data by organization.
• MATCH_SET_DATA_ID — Primary identifier for an individual match data element record.
• MATCH_SET_ID — Foreign key to the parent match set, grouping the data elements that together define a matching rule.
• DATA_ELEMENT — The identifier of the person/entity attribute being evaluated within the match set.
• VALUE — The value against which the data element is compared.
• EXACT_INCLUDE — Flag indicating whether the data element participates in exact matching.
• PARTIAL_INCLUDE — Flag indicating whether the data element participates in partial (fuzzy) matching; this is the attribute most relevant to the originating search.
• DROP_IF_NULL — Determines whether a record is excluded from consideration when the corresponding value is null.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard who-column auditability.

Common Use Cases and Queries

The view is principally used to audit or report on match set configuration, particularly to determine which attributes are enabled for exact versus partial matching within a given operating unit.

SELECT MATCH_SET_ID, DATA_ELEMENT, VALUE,
       EXACT_INCLUDE, PARTIAL_INCLUDE, DROP_IF_NULL
FROM   IGS_PE_MTCH_SET_DATA
WHERE  PARTIAL_INCLUDE = 'Y'
ORDER BY MATCH_SET_ID, DATA_ELEMENT;

A second common pattern isolates the elements belonging to a specific match set:

SELECT MATCH_SET_DATA_ID, DATA_ELEMENT, VALUE,
       EXACT_INCLUDE, PARTIAL_INCLUDE
FROM   IGS_PE_MTCH_SET_DATA
WHERE  MATCH_SET_ID = :p_match_set_id;

Because the view is documented as not implemented in the reference database, any query against it must be validated against the specific environment; where the object is absent, equivalent data is generally obtained directly from IGS_PE_MTCH_SET_DATA_ALL with an explicit ORG_ID predicate.