Search Results igs_ad_relacad_int_pk




Overview

IGS_AD_RELACAD_INT_ALL is an interface (staging) table within the Oracle E-Business Suite IGS – Student System product family. In EBS 12.1.1 and 12.2.2, it holds inbound academic history records for the relatives of a person — typically prospective students, applicants, or continuing students whose family educational background is captured for admissions, recruiting, or financial-aid evaluation. Because it is an interface table, its contents are transient by design: rows are loaded from an external source, validated and possibly corrected, then consumed by a concurrent program that moves valid rows into the base application tables. Once processed, the staging rows are generally purged.

The ETRM metadata explicitly notes that the table is not implemented in this database in the documented environment, and the parent product area is flagged Obsolete. This means the object should be treated as legacy: it exists in the shipped schema definition but may not be instantiated in every release or installation. The heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms, that suggests the table behaves less like a classic hub-and-satellite construct and more like a self-contained staging set, though its relationship to IGS_AD_RELATIONS_INT_ALL gives it a link-like quality for the person-to-relative association.

Key Information Stored

The table is owned by the IGS schema and exposes 30 documented columns in the 12.1.1 physical schema. The most operationally significant are:

Common Use Cases and Queries

The predominant use case is pre-load validation and reconciliation of relative academic-history data before it is promoted to the base tables. A common pattern is to isolate rows that failed import:

  • SELECT INTERFACE_RELACAD_ID, INTERFACE_RELATIONS_ID, ERROR_CODE FROM IGS_AD_RELACAD_INT_ALL WHERE STATUS IS NULL OR ERROR_CODE IS NOT NULL — this surfaces records still awaiting or rejected by the interface program.
  • Reporting on load outcomes by run: SELECT INTERFACE_RUN_ID, COUNT(*) , SUM(CASE WHEN ERROR_CODE IS NOT NULL THEN 1 ELSE 0 END) FROM IGS_AD_RELACAD_INT_ALL GROUP BY INTERFACE_RUN_ID.
  • Multi-org filtering via ORG_ID to restrict reporting to a single operating unit.
  • Joining to IGS_AD_RELATIONS_INT_ALL on INTERFACE_RELATIONS_ID = INTERFACE_RELATIONS_ID to reconstruct the person-to-relative hierarchy and list each relative's schooling.
  • Duplicate analysis using DUP_ACAD_HISTORY_ID and MATCH_IND to assess data quality before promotion.

Related Objects

The following objects are the most significant related to IGS_AD_RELACAD_INT_ALL:

  • IGS_AD_RELATIONS_INT_ALL — the parent interface table; joined via INTERFACE_RELATIONS_ID.
  • IGS_AD_RELACAD_INT_PK — the primary-key constraint on INTERFACE_RELACAD_ID.
  • IGS_AD_RELACAD_INT_ALL_U1 — the unique index enforcing uniqueness of INTERFACE_RELACAD_ID.
  • IGS_AD_RELATIONS_INT_ALL (base/relationship staging counterparts) — the downstream base tables that receive validated rows.
  • Interface/concurrent processing programs in the IGS module that consume INTERFACE_RUN_ID and REQUEST_ID to drive the promotion and error-handling logic.

Because the parent product area is obsolete, reliance on this table should be limited to historical or migration contexts, and any new development should confirm the object's presence in the target 12.1.1 or 12.2.2 instance before use.