Search Results source_promotion_code

Overview

IGS_RC_I_APPL_V is a reporting view delivered within the Oracle E-Business Suite IGS (Student System) product family. The IGS Student System is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2, and this particular view is explicitly noted in the ETRM metadata as "Not implemented in this database." Consequently, it may exist only as a residual or conditional object in certain installations depending on patches, localization, or legacy upgrade history.

The view is designed to expose recruitment and admissions enquiry/application data by joining the Oracle Marketing (OMO) public view AS_SALES_LEADS_V with the IGS_RC_I_APPL_ALL junction table. Its purpose is to present a flattened, report-friendly record that combines lead-source attributes with institution-specific enquiry and application tracking attributes such as academic calendar, admissions calendar, enquiry status, and inquiry entry level. Because it draws on both OMO and IGS constructs, it sits at the boundary between CRM-style lead management and student recruitment processing.

Underlying Base Objects

The ETRM documentation identifies two logical base objects:

• AS_SALES_LEADS_V — the OMO public view supplying sales lead and person/party information. It is aliased in the view text as EAP and PDV, contributing columns such as SALES_LEAD_ID, PERSON_ID, PARTY_NUMBER, PERSON_FIRST_NAME, PERSON_LAST_NAME, and KNOWN_AS.
• IGS_RC_I_APPL_ALL — the IGS junction table supplying institution-specific enquiry and application attributes, including academic and admissions calendar references, enquiry status, and inquiry method.

Additional lookup views and concatenated segments are referenced for descriptive fields, notably IGS_RC_I_STATUS_V for enquiry status descriptions and concatenated (CC1, CC2, CC3) value sets for education goal, how-know-us, and who-influenced attributes. SATV supplies organization unit code and description. No base tables are separately documented in ETRM metadata; the relationship is therefore one of view-over-view and view-over-table composition rather than direct base-table propagation.

Key Columns

• ROW_ID — unique identifier of the lead/application row.
• SALES_LEAD_ID, PERSON_ID, PERSON_NUMBER — lead, party, and party number identifiers.
• ENQUIRY_APPL_NUMBER — enquiry or application reference number.
• ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER, ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER — academic and admissions calendar type and sequence references.
• ENQUIRY_STATUS, DESCRIPTION — status code and its decoded description via IGS_RC_I_STATUS_V.
• DSP_DESCRIPTION, DSP_PREFERRED_NAME, PREFERRED_GIVEN_NAME — display name fields derived from KNOWN_AS or first/last name concatenation.
• INQUIRY_METHOD, INQUIRY_METHOD_CODE, ENQUIRY_DT — method, coded method, and date of enquiry.
• EDU_GOAL_ID, HOW_KNOWUS_ID, WHO_INFLUENCED_ID — concatenated lookup references with accompanying name/description columns.
• ORG_UNIT_CD, ORG_UNIT_DESCRIPTION — organization unit from SATV.
• ATTRIBUTE_CATEGORY through ATTRIBUTE16+ — DFF (descriptive flexfield) columns carried through from the source table.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view is suited to recruitment funnel reporting, lead-to-enquiry conversion analysis, and enquiry status tracking. Because it is documented as not implemented, queries should guard against invalid-object errors.

• Enquiry status tracking: SELECT ENQUIRY_APPL_NUMBER, ENQUIRY_STATUS, DESCRIPTION, ENQUIRY_DT FROM IGS_RC_I_APPL_V WHERE ENQUIRY_STATUS IS NOT NULL;
• Lead-to-person reconciliation: SELECT SALES_LEAD_ID, PERSON_ID, PERSON_NUMBER, DSP_PREFERRED_NAME FROM IGS_RC_I_APPL_V WHERE SALES_LEAD_ID IS NOT NULL;
• Calendar-based recruitment reporting: SELECT ACAD_CAL_TYPE, ADM_CAL_TYPE, COUNT(*) FROM IGS_RC_I_APPL_V GROUP BY ACAD_CAL_TYPE, ADM_CAL_TYPE;

Given the obsolete status of IGS Student System, these queries are primarily relevant to legacy reporting, migration extraction, or historical data reconciliations rather than active production use.