Search Results interface_recruitment_id

Overview

The table IGS.IGS_AD_RECRUIT_INT is a public interface (staging) table within the Oracle E-Business Suite IGS product schema. It holds recruitment detail records that are destined for import into the permanent IGS_AD_RECRUITMENTS table by the Admission Import concurrent process. As a transient landing object, it allows external sources — prospect lists, feeder-system extracts, or third-party recruitment feeds — to be loaded, validated, and reconciled before they are promoted into the operational recruitment tables. The object carries an active lifecycle, a display name of "Import Recruitment Detail", and is classified under the business entity IGS_INQ_APPLICATION.

Physically, the table resides in the APPS_TS_INTERFACE tablespace (PCT Free 10) and is registered under FND Design Data as IGS.IGS_AD_RECRUIT_INT. With 40 documented columns, it maps the full set of demographic, academic-interest, and institutional-preference attributes attached to a recruitment record. From a dimensional modeling perspective, the mined dependency structure suggests a link classification, since the table stores relationships between a recruitment interface identifier and numerous code-class reference identifiers rather than a durable hub of business keys or a slowly changing satellite.

Key Information Stored

The surrogate primary key is INTERFACE_RECRUITMENT_ID (NUMBER(15)), which is also the sole documented unique index candidate (IGS_AD_RECRUIT_INT_U1), making it both the technical and business-key identifier for a staging row. The most consequential columns include:

• INTERFACE_ID and INTERFACE_RUN_ID — identify the batch and the import run that delivered the row, enabling per-run reconciliation; both are indexed.
• DUP_RECRUITMENT_ID — references an existing recruitment record used for duplicate detection.
• PERSON_ID and PROGRAM_APPLICATION_ID — link the staged prospect to a person and application context.
• PRIORITY, PROBABILITY, and VIP — capture recruitment scoring and prospect segmentation.
• PROGRAM_INTEREST_ID, DEGREE_GOAL_ID, and UNIT_SET_ID — record academic intent and desired program of study.
• INSTITUTION_SIZE_ID, INSTITUTION_CONTROL_ID, INSTITUTION_SETTING_ID, and INSTITUTION_LOCATION_ID — institutional preference attributes.
• STATUS, ERROR_CODE, and ERROR_TEXT — drive the import process outcome and error reporting.
• DEACTIVATE_RECRUIT_STATUS and MATCH_IND — flags controlling record state.

Common Use Cases and Queries

Typical activity centers on monitoring import health, diagnosing validation failures, and reconciling loaded counts. A run-status query checks outstanding rows:

• SELECT interface_run_id, status, COUNT(*) FROM igs.igs_ad_recruit_int GROUP BY interface_run_id, status;
• SELECT interface_recruitment_id, error_code, error_text FROM igs.igs_ad_recruit_int WHERE error_code IS NOT NULL;
• Duplicate screening: SELECT person_id, program_interest_id, dup_recruitment_id FROM igs.igs_ad_recruit_int WHERE dup_recruitment_id IS NOT NULL;
• Pre-import validation joining coded values to IGS_AD_CODE_CLASSES, and post-import verification against IGS_AD_RECRUITMENTS.

Related Objects

The table participates in several documented reference relationships through IGS_AD_CODE_CLASSES and IGS_AD_UNIT_SETS:

• IGS_AD_RECRUITMENTS — the target of the Admission Import process.
• IGS_AD_CODE_CLASSES — joined on EMPLOYMENT_ID, INSTITUTION_LOCATION_ID, PROGRAM_INTEREST_ID, SEC_SCHOOL_LOCATION_ID, and SPECIAL_INTEREST_ID.
• IGS_AD_UNIT_SETS — joined on UNIT_SET_ID.
• Import concurrent program Admission Import — the consumer that promotes staged rows and populates STATUS, ERROR_CODE, and ERROR_TEXT.