Results for “source_type_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_PE_MATCH_SETS is a reporting and integration view in the Oracle E-Business Suite Student System (IGS) product family. It exposes the operational contents of the person/entity match set configuration used by the Oracle Student System matching engine, which compares candidate person or organization records against configurable rule sets to detect duplicates and propose merges. The view is owned by the APPS schema and holds VALID status in both EBS 12.1.1 and 12.2.2.

Functionally, the view presents the run-time-visible subset of match set definitions. Because Oracle EBS supports multi-organization (multi-tenant) access through the ORG_ID security model, and because the Student System also supports a global (cross-organization) scope, the view applies a row-level filter against the session's CLIENT_INFO value. Only match sets whose ORG_ID equals the organization recorded in the user's session context — or the sentinel value -99 for global definitions — are returned. This makes the view safe for direct use in concurrent programs, OAF pages, and BI Publisher reports without requiring the caller to re-implement organization security logic.

The user search term match_set_name maps directly to the MATCH_SET_NAME column, the human-readable identifier that administrators assign when defining a match set and the value most often used when querying, joining, or displaying match set configuration.

Underlying Base Objects

The ETRM metadata documents a single referenced base object for this view: the table IGS_PE_MATCH_SETS_ALL. The view is a straightforward projection over that table with no joins, aggregations, or scalar transformations applied to the attribute list. Every column in the view corresponds one-for-one to a column in the base table, with the exception of ROW_ID, which is generated as TAB.ROW_ID from the underlying table's ROWID pseudocolumn.

The only logic applied is the organization security predicate in the WHERE clause, which compares the base table's ORG_ID against a value decoded from USERENV('CLIENT_INFO'), the standard EBS mechanism by which applications publish the current organization context to the database session. Definitions belonging to other organizations are excluded; global definitions (ORG_ID = -99) are visible when no organization context is set. Because the view inherits all columns unmodified, it is functionally equivalent to querying IGS_PE_MATCH_SETS_ALL with an organization security filter appended.

Key Columns

• ROW_ID — the ROWID of the underlying base table row; useful for direct row addressing but not a stable primary key for integration.
• ORG_ID — the operating unit or organization that owns the match set definition; -99 denotes a global definition.
• MATCH_SET_ID — the primary key of the match set, used to join to dependent rule, match point, and score configuration tables.
• SOURCE_TYPE_ID — identifies the source type to which the match set applies, allowing distinct rule sets per incoming data source.
• MATCH_SET_NAME — the descriptive name of the match set; the principal column referenced by users and administrators identifying a definition.
• DESCRIPTION — free-text explanation of the match set's purpose.
• CLOSED_IND — indicates whether the match set has been closed and should no longer be applied to new matching runs.
• PARTIAL_IF_NULL — controls whether a candidate with null values in matching attributes qualifies as a partial match.
• PRIMARY_ADDR_FLAG — determines whether primary address data participates in the match evaluation.
• EXCLUDE_INACTIVE_IND — indicates whether inactive records are excluded from matching.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the definition and when.

Common Use Cases and Queries

The view is typically used to list available match sets for administrators, to validate configuration before running duplicate identification, and to join match set metadata to rule-level tables using MATCH_SET_ID. A common retrieval by name is:

SELECT match_set_id, org_id, match_set_name, description, closed_ind
FROM apps.igs_pe_match_sets
WHERE match_set_name LIKE :p_name
AND NVL(closed_ind,'N') = 'N';

To enumerate active definitions for a source type and organization:

SELECT match_set_id, match_set_name, source_type_id, partial_if_null, primary_addr_flag
FROM apps.igs_pe_match_sets
WHERE source_type_id = :p_source_type_id
AND org_id = :p_org_id;

Because the view already enforces organization security, reports executed under the correct CLIENT_INFO context need no additional ORG_ID predicate; adding one is optional and primarily useful for explicit filtering in ad hoc queries.