Results for “igs_rc_i_appl_all”

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

Overview

IGS_RC_I_APPL_ALL is a recruitment and admissions table within the Oracle E-Business Suite Student System (IGS) product family. It stores one row per enquiry application made to an institution, capturing the prospective student's expressed interest in a particular program, faculty, or service — for example, accommodation details for a faculty of education. The table therefore acts as the master record for an enquiry, distinct from a formal admissions application.

The table's primary key is IGS_RC_I_APPL_ALL_PK, defined on the composite of PERSON_ID and ENQUIRY_APPL_NUMBER. Because this is a natural composite key built from a party reference plus a business-assigned sequence, the metadata's heuristic Data Vault classification of satellite-leaning is a reasonable modeling suggestion: most of the descriptive attributes (codes for education goal, referral source, and influence, plus calendar references) behave like satellite attributes attached to the enquiry entity rather than hub-style identifiers.

Key Information Stored

The most significant columns documented for this object include:

• PERSON_ID — foreign key to HZ_PARTIES; identifies the person making the enquiry. Part of the primary key.
• ENQUIRY_APPL_NUMBER — the business-assigned enquiry application number. Part of the primary key.
• PARTY_ID — foreign key to HZ_PARTIES; the party record associated with the enquiry.
• REGISTERING_PERSON_ID — foreign key to HZ_PARTIES; the person who registered the enquiry (may differ from the enquirer).
• SALES_LEAD_ID — foreign key to AS_SALES_LEADS; links the enquiry to a CRM sales lead.
• EDU_GOAL_ID — foreign key to IGS_AD_CODE_CLASSES; the enquirer's stated educational goal.
• HOW_KNOWUS_ID — foreign key to IGS_AD_CODE_CLASSES; the channel or source by which the enquirer learned of the institution.
• WHO_INFLUENCED_ID — foreign key to IGS_AD_CODE_CLASSES; the party or factor that influenced the enquiry.
• INQ_ENTRY_LEVEL_ID — foreign key to IGS_RC_I_ENTRY_LVLS; the entry level associated with the enquiry.
• ADM_CAL_TYPE and ADM_CI_SEQUENCE_NUMBER — foreign key references to IGS_CA_INST_REL; identify the admissions calendar instance.
• ACAD_CAL_TYPE and ACAD_CI_SEQUENCE_NUMBER — calendar references for the academic instance linked to the enquiry.

The composite primary key provides uniqueness; no separate surrogate key column is documented, so PERSON_ID plus ENQUIRY_APPL_NUMBER are the de facto business keys.

Common Use Cases and Queries

Typical reporting and operational scenarios include tracking enquiry volumes by source, measuring conversion to sales leads, and analyzing enquiry demographics. A common pattern joins the enquiry to party data and code classes:

• Enquiry counts by referral source: join HOW_KNOWUS_ID to IGS_AD_CODE_CLASSES.
• Lead linkage analysis: join SALES_LEAD_ID to AS_SALES_LEADS to assess CRM pipeline alignment.
• Person-level enquiry history: join PERSON_ID to HZ_PARTIES to retrieve enquirer attributes.
• Calendar-instance reporting: join ADM_CAL_TYPE/ADM_CI_SEQUENCE_NUMBER to IGS_CA_INST_REL to trend enquiries by admissions cycle.

A representative pattern is: SELECT a.ENQUIRY_APPL_NUMBER, a.PERSON_ID, a.HOW_KNOWUS_ID FROM IGS_RC_I_APPL_ALL a WHERE a.PERSON_ID = :p_person_id; then join to IGS_AD_CODE_CLASSES on the code columns to resolve descriptions.

Related Objects

Key related objects, based on documented foreign key relationships, include:

• HZ_PARTIES — referenced via PERSON_ID, PARTY_ID, and REGISTERING_PERSON_ID; the primary party master for the enquirer and related persons.
• IGS_AD_CODE_CLASSES — referenced by EDU_GOAL_ID, HOW_KNOWUS_ID, and WHO_INFLUENCED_ID for code lookups.
• IGS_RC_I_ENTRY_LVLS — referenced by INQ_ENTRY_LEVEL_ID; defines enquiry entry levels.
• IGS_CA_INST_REL — referenced by ADM_CAL_TYPE and ACAD_CAL_TYPE calendar columns; the calendar instance master.
• AS_SALES_LEADS — referenced by SALES_LEAD_ID; links enquiries into the CRM lead model.
• IGS_RC_I_A_CHARTYP — child table referencing PERSON_ID and ENQUIRY_APPL_NUMBER; stores chart-type detail for the enquiry.
• IGS_RC_I_A_PKGITM — child table referencing PERSON_ID and ENQUIRY_APPL_NUMBER; stores packaged or requested items associated with the enquiry.

These relationships confirm that IGS_RC_I_APPL_ALL functions as a central enquiry header entity within the Student System, with its dependent detail tables keyed on the same composite primary key.