Search Results degree_goal_id




Overview
Explore in AI Chat

Overview

The IGS_AD_RECRUITMENTS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically under the IGS (iGrad Student) schema. It functions as the primary repository for storing detailed recruitment information pertaining to prospective students or applicants. Its role is to support the admissions and recruitment lifecycle by capturing a prospect's likelihood of enrollment, their specific academic and institutional preferences, and other critical data points used for targeted recruitment campaigns, forecasting, and applicant relationship management. The table's design, with numerous foreign key columns linking to reference data, underscores its central position in modeling a complex recruitment profile.

Key Information Stored

The table stores a wide array of recruitment attributes. The primary identifier is the RECRUITMENT_ID. A crucial link is the PERSON_ID, a foreign key to HZ_PARTIES, which ties recruitment data to the universal person/party record within EBS. The table captures the prospect's academic intent through columns like DEGREE_GOAL_ID and PROGRAM_INTEREST_ID. It also stores preferences and characteristics related to the institution, such as INSTITUTION_CONTROL_ID, INSTITUTION_SIZE_ID, and HOUSING_ID. Operational recruitment metrics are held in fields like PRIORITY, PROBABILITY (of enrollment), and VIP status. Notably, the user's search for "degree_goal_id" is directly addressed, as DEGREE_GOAL_ID is a significant column and is indexed via the IGS_AD_RECRUITMENTS_N2 index to optimize query performance for reports filtering on a prospect's intended degree objective.

Common Use Cases and Queries

This table is integral to admissions operations and reporting. Common use cases include generating lists of high-priority recruits (VIPs) for outreach, analyzing enrollment probability for forecasting, and segmenting prospects based on their academic interests or institutional preferences. A typical query might involve joining with person (HZ_PARTIES) and reference tables to create a detailed recruitment dashboard. For example, to find high-probability recruits interested in a specific degree goal, one might use a SQL pattern such as:

  • SELECT r.PERSON_ID, p.PARTY_NAME, r.PRIORITY, r.PROBABILITY
  • FROM IGS.IGS_AD_RECRUITMENTS r, HZ_PARTIES p
  • WHERE r.PERSON_ID = p.PARTY_ID
  • AND r.DEGREE_GOAL_ID = :target_degree_goal
  • AND r.PROBABILITY > 0.7
  • ORDER BY r.PRIORITY, r.PROBABILITY DESC;

Another common scenario is updating the recruitment status or probability based on new interactions, which would involve DML operations on this table.

Related Objects

The IGS_AD_RECRUITMENTS table has extensive relationships within the EBS data model. Its primary relationship is with the HZ_PARTIES table via the PERSON_ID foreign key, anchoring it to the Trading Community Architecture. It is referenced by numerous non-unique indexes (N1 through N14), each optimizing access via a specific foreign key like DEGREE_GOAL_ID, SPECIAL_INTEREST_ID, or UNIT_SET_ID. These indexed columns imply the existence of corresponding reference code tables (e.g., for degree goals, special services, religions) within the IGS schema, though their exact names are not specified in the provided metadata. The table's storage in the APPS_TS_TX_DATA tablespace and its indexes in APPS_TS_TX_IDX align it with standard EBS transactional data. As a foundational table, it is likely referenced by various IGS admission forms, concurrent programs, and PL/SQL APIs that manage the recruitment process.