Search Results igs_ad_recruit_int




Overview
Explore in AI Chat

Overview

The IGS_AD_RECRUIT_INT table is a Student System (IGS) interface staging table in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds recruitment details to be imported for a person, functioning as the inbound landing area for prospective-student recruitment data before that data is validated and written into the operational recruitment and admissions tables. Records are keyed by INTERFACE_RECRUITMENT_ID, and each row is associated with an INTERFACE_ID and, where applicable, a REQUEST_ID and INTERFACE_RUN_ID that tie the row back to a specific concurrent program submission and interface run.

Because the table exists to receive externally sourced recruitment attributes, it is transient by nature: rows are inserted, processed, and typically purged or archived after the import completes. Status and error columns support this lifecycle. Under the heuristic Data Vault classification mined from its foreign key structure, IGS_AD_RECRUIT_INT is best modeled as a link — it carries a surrogate primary key together with multiple foreign-key references to code/lookup entities, which is characteristic of a relationship table connecting a recruitment event to a person and to the various coded attributes that describe that person's interests.

Key Information Stored

The table is documented with 40 columns in the 12.1.1 schema. The most significant are:

Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent-program columns (REQUEST_ID, INTERFACE_RUN_ID) are consistent with standard EBS interface-table conventions.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the recruitment import. A common pattern retrieves all rows for a concurrent request and their processing status:

  • SELECT interface_recruitment_id, person_id, program_interest_id, status, error_code, error_text FROM igs.igs_ad_recruit_int WHERE request_id = :request_id;
  • Identifying failed rows: SELECT * FROM igs.igs_ad_recruit_int WHERE status = 'E' OR error_code IS NOT NULL;
  • Joining to IGS_AD_CODE_CLASSES on the coded columns (for example EMPLOYMENT_ID, SPECIAL_INTEREST_ID, INSTITUTION_LOCATION_ID) to translate identifiers into descriptive values for reporting.
  • Counting rows per interface run to reconcile expected versus loaded prospect records.

Because these rows represent unvalidated inbound data, reports should generally be built against the post-import operational tables once processing succeeds, using this table primarily for load diagnostics and exception reporting.

Related Objects

  • IGS_AD_CODE_CLASSES — referenced by five foreign keys: EMPLOYMENT_ID, INSTITUTION_LOCATION_ID, PROGRAM_INTEREST_ID, SEC_SCHOOL_LOCATION_ID, and SPECIAL_INTEREST_ID.
  • IGS_AD_UNIT_SETS — referenced via UNIT_SET_ID.
  • Person / interface parent objects — linked through PERSON_ID and INTERFACE_ID, connecting each staged row to the individual and the interface run.
  • Recruitment operational tables — the validated target into which successfully processed rows are written after the import program completes.

Together these relationships confirm the table's role as a coded-attribute link staging area within the Student System recruitment flow.