Results for “interface_relations_id”

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

Overview

IGS_AD_IMP_NEAR_MTCH_ALL is a transactional staging and resolution table within the Oracle E-Business Suite Student System (IGS) module. It stores the outcome of the near-match evaluation performed when admission or person records are imported into the system, capturing the relationship between incoming interface data and pre-existing person or party records that resemble one another but do not constitute an exact match. The table therefore acts as the holding area where clerical or duplicate-resolution decisions are recorded before an imported record is either linked to an existing party or created anew.

The table resides in the IGS schema and is classified as VALID in both 12.1.1 and 12.2.2. Its documented primary key is IGS_AD_IMP_NEAR_MTCH_PK, defined on the NEAR_MTCH_ID column. The Data Vault classification mined from the foreign-key structure is link, which is best treated as a modeling suggestion: the object behaves as an associative link that resolves many-to-many style relationships between imported interface records, existing HZ_PARTIES rows, match sets, and party sites, rather than as a pure descriptive hub or satellite.

Key Information Stored

The physical schema documents twenty columns. The most significant are:

• NEAR_MTCH_ID — surrogate primary key from IGS_AD_IMP_NEAR_MTCH_PK; uniquely identifies each near-match row. No separate business-key unique index is documented beyond this key.
• INTERFACE_ID — identifies the inbound import record being evaluated.
• PERSON_ID — foreign key to HZ_PARTIES, pointing to the existing person or party that closely resembles the imported data.
• MATCH_IND — indicator flag reflecting the match result or confidence state.
• ACTION — the resolution action to be taken (for example, accept the match, reject, or defer).
• PARTY_SITE_ID — foreign key to HZ_PARTY_SITES, linking the near match to a specific address or site.
• PERSON_ID_TYPE — foreign key to IGS_PE_PERSON_ID_TYP, qualifying the type of person identifier involved.
• MATCH_SET_ID — foreign key to IGS_PE_MATCH_SETS_ALL, grouping related match criteria or match runs.
• INTERFACE_RELATIONS_ID — foreign key to IGS_AD_RELATIONS_INT_ALL, tying the row to the inbound relations interface record.
• ORG_ID — multi-org operating unit context.
• ADDR_TYPE — address type associated with the evaluated party site.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program and audit lineage columns identifying the process that generated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for auditing.

Common Use Cases and Queries

Typical scenarios include duplicate-person resolution during admission imports, batch cleanup of ambiguous matches, and reconciliation reporting of unresolved near matches before records are committed to HZ_PARTIES.

• List unresolved near matches for a given import run:
  SELECT n.NEAR_MTCH_ID, n.INTERFACE_ID, n.PERSON_ID, n.MATCH_IND, n.ACTION FROM IGS.IGS_AD_IMP_NEAR_MTCH_ALL n WHERE n.REQUEST_ID = :request_id AND n.ACTION IS NULL;
• Resolve a match to an existing party and site:
  SELECT n.NEAR_MTCH_ID, p.PARTY_NAME, s.ADDRESS1 FROM IGS_AD_IMP_NEAR_MTCH_ALL n JOIN HZ_PARTIES p ON p.PARTY_ID = n.PERSON_ID JOIN HZ_PARTY_SITES s ON s.PARTY_SITE_ID = n.PARTY_SITE_ID WHERE n.MATCH_SET_ID = :match_set_id;
• Report by match set and person identifier type: join IGS_PE_MATCH_SETS_ALL on MATCH_SET_ID and IGS_PE_PERSON_ID_TYP on PERSON_ID_TYPE to categorize match volumes.

Because rows are link-style associations, reporting queries typically aggregate counts of pending versus actioned near matches per ORG_ID and per concurrent REQUEST_ID.

Related Objects

• HZ_PARTIES — joined on IGS_AD_IMP_NEAR_MTCH_ALL.PERSON_ID = HZ_PARTIES.PARTY_ID; the existing party against which the imported data is compared.
• HZ_PARTY_SITES — joined on PARTY_SITE_ID; supplies address/site context for the near match.
• IGS_PE_MATCH_SETS_ALL — joined on MATCH_SET_ID; defines the matching criteria group.
• IGS_PE_PERSON_ID_TYP — joined on PERSON_ID_TYPE; classifies the person identifier.
• IGS_AD_RELATIONS_INT_ALL — joined on INTERFACE_RELATIONS_ID; the inbound relations interface source.

Together these foreign-key relationships place IGS_AD_IMP_NEAR_MTCH_ALL at the center of the admission import matching workflow, linking inbound interface data to the master party model maintained by HZ and the IGS match-set configuration.