Search Results interface_relations_id




Overview
Explore in AI Chat

Overview

APPS.IGS_AD_REL_CON_INT is a reporting and integration view in the Oracle E-Business Suite student system (the IGS product family, associated with Oracle Student System / Admissions). It exposes the contents of the interface staging table IGS_AD_REL_CON_INT_ALL, which holds contact point information — e-mail addresses and telephone numbers — destined for validation and loading against admissions relations records. In the EBS architecture the "AD" prefix denotes admissions, "REL" denotes relations (for example applicant or person relationships), and "CON_INT" denotes the contact interface. The view is read primarily by concurrent programs and PL/SQL APIs that reconcile staged contact data, set match and error indicators, and then transfer the surviving rows into the permanent contact tables.

The view is a thin projection rather than a transformation: it performs no joins and applies no filtering, so each row corresponds one-to-one with a row in the underlying _ALL table. The object is defined over an org-striped (multi-org) table, hence the presence of ORG_ID and the _ALL suffix. The user search term interface_relations_id identifies the foreign key that links a staged contact point to its parent interface relations record.

Underlying Base Objects

The documented definition resolves entirely to a single base object: IGS_AD_REL_CON_INT_ALL. The view text is expressed in the form SELECT tab.rowid row_id, ... FROM igs_ad_rel_con_int_all tab, which confirms that the ROWID of the base table is made available as ROW_ID. This ROW_ID mirrors the ROWID pseudo-column referenced in the OAF/ADF view object definition, allowing the framework to navigate the underlying rows despite the multi-org WHERE clause that EBS applies at runtime. Because the view is not a join, no other documented base objects are referenced; validation against relations, contact point types, and phone or e-mail formats occurs in the calling concurrent program rather than in the view itself.

Key Columns

Common Use Cases and Queries

Typical uses include diagnosing failed contact imports, auditing which phone and e-mail rows remain unvalidated, and confirming the relations parent for a staged contact point. A representative query listing problematic rows is:

SELECT interface_rel_con_id, interface_relations_id, contact_point_type,
       email_addrress, phone_number, status, match_ind, error_code
 FROM apps.igs_ad_rel_con_int
WHERE org_id = :p_org_id
  AND status = 'ERROR'
  AND error_code IS NOT NULL;

To inspect all contacts for a given relations record:

SELECT c.interface_rel_con_id, c.contact_point_type, c.primary_flag,
       c.email_addrress, c.phone_number, c.status
 FROM apps.igs_ad_rel_con_int c
WHERE c.interface_relations_id = :p_interface_relations_id;

Because the view exposes REQUEST_ID and the PROGRAM_* columns, it is also useful for correlating staged contact rows with the concurrent request that generated or last updated them, a common step when troubleshooting import programs in EBS 12.1.1 and 12.2.2.