Results for “interface_alias_id”

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

Overview

IGS_AD_ALIAS_INT_ALL is the open interface (staging) table within the Oracle EBS Student System (IGS) product that holds person alias details awaiting import into the core person/alias tables. It resides in the IGS schema and is classified as VALID in the ETRM 12.1.1 / 12.2.2 reference. Its functional purpose is to buffer externally sourced alias records — for example, alternate or previous names received from a legacy student system or third-party feeder — so that the concurrent import process can validate each row before committing it to the production alias entity.

Because the table is a pure interface object, it does not participate in enforcing business relationships with other IGS entities. Mined FK structure returns a Data Vault classification of "standalone," meaning no foreign key dependencies were detected. In Data Vault terms this is best modeled as a staging or satellite-style structure (an interface satellite) rather than a hub or link; the surrogate identifier is local to the staging load, and the business entity it describes (a person alias) lives in the target tables. The heuristic classification should be treated as a modeling suggestion only.

Key Information Stored

The table documents 24 physical columns. The most significant are:

• INTERFACE_ALIAS_ID — the surrogate primary key (IGS_AD_ALIAS_INT_PK) that uniquely identifies each staged alias row. It is a processing key, not a business key.
• INTERFACE_ID — the business identifier carried from the source system, used to correlate the staged record back to its origin and to resolve it against existing person records.
• ORG_ID — the operating unit / organization context, enabling multi-org aware processing of the import.
• ALIAS_TYPE — the category of alias being imported (for example a previous surname or alternate name), which drives validation and target-column mapping.
• SURNAME, GIVEN_NAMES, TITLE — the core name attributes of the alias record.
• ALIAS_COMMENT — free-text notes associated with the alias.
• START_DT, END_DT — the effective date range during which the alias applies.
• MATCH_IND — an indicator recording whether the staged alias matched an existing person.
• STATUS, ERROR_CODE — the interface processing state and the reason a row failed validation or import.
• DUP_SEQUENCE_NUMBER — distinguishes multiple alias rows that would otherwise collide within the same interface load.
• INTERFACE_RUN_ID — groups all rows belonging to a single import run, supporting failure recovery and reprocessing.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — the concurrent request and program that created or last processed the row, providing the standard EBS audit lineage.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and PROGRAM_UPDATE_DATE complete the audit footprint. No unique business-key index is documented beyond the primary key.

Common Use Cases and Queries

The principal scenario is pre-import validation and error triage. Analysts query failed rows to correct source data before rerunning the import:

• Identify failures for a run: SELECT * FROM igs.igs_ad_alias_int_all WHERE interface_run_id = :run_id AND status = 'E';
• Locate unreconciled rows: SELECT interface_alias_id, interface_id, surname, error_code FROM igs.igs_ad_alias_int_all WHERE status = 'N';
• Audit a specific concurrent request: filter on request_id to see exactly which rows the program staged.
• Reporting on alias provenance: count staged aliases by alias_type, org_id, and start_dt to reconcile source counts against imported counts.

Because it is an interface table, rows are transient — typically purged or truncated between loads. Reporting should generally target the production alias tables rather than persist against this object.

Related Objects

The documented FK/PK analysis shows no enforced relationships, so related objects are inferred from column semantics and the IGS Student System data model:

• Person alias base table(s) in IGS — the import target, joined on the alias identifier derived from INTERFACE_ID.
• IGS_PER_PERSON_INT_ALL / person interface tables — sibling staging objects for person records that must be loaded before aliases.
• HZ_PARTIES / HZ_PERSON_PROFILES — the TCA party layer that supplies the matched person identified by MATCH_IND.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the import program run.
• FND_APPLICATION / FND_PROGRAM — resolved via PROGRAM_APPLICATION_ID and PROGRAM_ID for lineage.
• Import concurrent program / PL/SQL API in IGS — the consumer that reads STATUS and ERROR_CODE to drive processing.