Search Results exclude_inactive_ind

Overview

IGS_PE_MATCH_SETS_V is an Oracle EBS Applications view owned by the APPS schema that exposes configuration metadata for person and organization match sets used by the Person/Entity (PE) matching engine within the Oracle Student System / Higher Education product family. A match set defines a named collection of matching rules and behavioral flags that the matching engine applies when it searches for, scores, and consolidates duplicate person or organization records. The view presents the header-level definition of each match set — its identity, source type, operational status, and default matching behaviors — without exposing the individual match rule lines that belong to it.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as the reporting and integration surface over the underlying match set configuration. Rather than querying the base table directly, external processes, concurrent programs, and custom reports can use the view to enumerate active match sets, resolve a match set identifier to its descriptive name, and determine whether partial or null-key matching and primary-address preference are enabled.

Underlying Base Objects

The view is defined as a simple projection over a single base table. The documented view text is:

• IGS_PE_MATCH_SETS MS — the sole referenced base object. The view selects a fixed column list from this table, aliased as MS, with no joins, unions, or aggregation.

Because the definition is a straight SELECT ... FROM IGS_PE_MATCH_SETS MS, the view is effectively a column-subset and naming-alias layer. The base table's ROWID is exposed as ROW_ID, giving each row a stable physical row identifier even though the primary key MATCH_SET_ID is also available. No additional base objects are documented in the ETRM metadata. Filtering, ordering, and any translation of coded values remain the responsibility of the consuming query; the view itself imposes no predicate or restriction on the rows returned.

Key Columns

• ROW_ID — the base table ROWID, exposed for row-level identification and update targeting.
• MATCH_SET_ID — primary identifier of the match set. This is the value referenced by match rule and match result records that point back to a specific set.
• SOURCE_TYPE_ID — identifies the source type the match set applies to, distinguishing, for example, person-origin versus organization-origin matching contexts.
• MATCH_SET_NAME — the user-visible name of the match set, used in setup screens, lookups, and report labels.
• DESCRIPTION — free-text explanation of the match set's purpose or scope.
• CLOSED_IND — indicates whether the match set has been closed and is no longer available for new matching activity.
• PARTIAL_IF_NULL — controls behavior when a matching attribute is null, allowing a partial rather than a full-match outcome.
• PRIMARY_ADDR_FLAG — indicates whether the primary address is used as the address attribute for matching.
• EXCLUDE_INACTIVE_IND — determines whether inactive records are excluded from the matching candidate population.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last changed each row.

Common Use Cases and Queries

The view is typically used to enumerate the match sets configured in an environment, to validate that a referenced match set is still open, and to drive audit or migration comparisons of matching configuration between instances.

List all open match sets with their matching behavior flags:

SELECT match_set_id, match_set_name, source_type_id,
       partial_if_null, primary_addr_flag, exclude_inactive_ind
FROM   apps.igs_pe_match_sets_v
WHERE  closed_ind = 'N'
ORDER  BY match_set_name;

Resolve a known identifier to its name and description:

SELECT match_set_name, description, closed_ind
FROM   apps.igs_pe_match_sets_v
WHERE  match_set_id = :p_match_set_id;

Audit recently modified configurations:

SELECT match_set_name, last_updated_by, last_update_date
FROM   apps.igs_pe_match_sets_v
WHERE  last_update_date >= :p_since_date
ORDER  BY last_update_date DESC;

Because the view is read-only in intent and defined over a single table, it can be queried safely in custom concurrent programs and reports without concern for join cardinality or duplicate rows. Consumers requiring the rule lines belonging to a match set should join on MATCH_SET_ID to the corresponding match rule table.