Results for “igs_ad_spltal_int_all”

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

Overview

IGS_AD_SPLTAL_INT_ALL is a table in the Oracle E-Business Suite IGS — Student System product family, which is marked Obsolete in current ETRM documentation. The table is described as holding applicant special talents details. In the Oracle EBS recruitment and admissions model, applicant special talents represent non-academic attributes recorded against an applicant — for example, athletic ability, musical proficiency, artistic skill, or other distinctions that an admissions office may consider during evaluation. The table name suffix _INT_ALL identifies it as an interface (staging) table rather than a base transactional table. Interface tables in EBS are populated by external feeds or by concurrent programs prior to validation and migration into the corresponding base tables; the _ALL component typically signals a multi-organization or multi-record-scope design common across IGS.

Per the documented ETRM metadata, the table is not implemented in the current database, meaning the object exists in the data model but has no physical presence in the installed environment. Its Data Vault classification, derived heuristically from the foreign-key structure, is standalone. In Data Vault modeling terms this suggests the table functions as an independent structure that neither resolves into a hub-and-satellite pair nor participates as a link between two hubs; any integration relationships would need to be inferred through matching business keys rather than enforced referential constraints. Analysts should treat this classification as a modeling suggestion rather than a validated architectural fact.

Key Information Stored

The documented metadata identifies a small number of distinct columns and constraints. Because the table is an interface object and standby in the data model, only the following specifics are authoritative:

• INTERFACE_SPLTAL_ID — the single documented column, serving as the surrogate primary key for each staged applicant special talent record. This identifier is generated on staging and is used to link the interface row to its destination record during the conversion process.
• IGS_AD_SPLTAL_INT_PK — the named primary-key constraint enforcing uniqueness on INTERFACE_SPLTAL_ID. This is the only documented index and is the surrogate, not a business key.

No alternate unique index or business key is documented in the ETRM excerpt. In comparable IGS applicant interface tables, business-key candidates typically include an applicant identifier, a talent code, and a talent sequence number, but those are not confirmed here and should be verified against the physical definition if and when the table is instantiated. The absence of documented foreign keys is consistent with the standalone classification.

Common Use Cases and Queries

The primary purpose of this object is to support batch loading of applicant special talent data into the student system. Typical scenarios include admission cycle data intake, external recruitment-agency feeds, and remediation of failed conversion rows. Because the object is inert in the documented environment, queries are most meaningful against a development or target environment where the interface is populated.

A representative pattern for inspecting staged records follows:

• SELECT interface_spltal_id FROM igs_ad_spltal_int_all WHERE interface_spltal_id = :id;
• Row counts and duplicate detection by surrogate key: SELECT interface_spltal_id, COUNT(*) FROM igs_ad_spltal_int_all GROUP BY interface_spltal_id HAVING COUNT(*) > 1;
• Reconciliation of staged volumes against the destination base table once mapping is confirmed.

Reporting use cases centre on exception handling — identifying rows that failed validation, monitoring feed throughput per admission term, and auditing which applicant talents were successfully migrated. In practice, the limited column documentation constrains ad hoc reporting to surrogate-key-based tracing.

Related Objects

The documented metadata supplies no foreign-key relationships, only a self-contained primary key and the standalone Data Vault classification. Consequently, related objects must be described in terms of product-family context rather than documented FK joins:

• IGS_AD_SPLTAL_INT_PK — the primary-key constraint on INTERFACE_SPLTAL_ID; the only confirmed dependent object.
• Destination applicant special-talent base table(s) — the migration target for validated rows, related through the surrogate key carried on the interface record (exact object name not documented).
• Applicant base tables in the IGS_AD schema — the parent context for any applicant talent, linked by applicant identifier once that column is confirmed.
• IGS concurrent programs that load and validate the interface table (specific program names not listed in the metadata).

Consumers integrating with this object should confirm the physical column list and any undocumented relationships in the target environment before relying on join assumptions, given the standalone classification and its obsolete status.